So, here's the story:
The Pentaho Jira is a server instance. Atlassian stopped support and won't even renew licenses. Our license ran out more than a year ago. We found ourselves in a situation where we were unable to perform security updates and we were getting slammed by spammers. Around the time our license ran out we lost the ability to serve read-only to anonymous users. We had been working with Atlassian on our migration plan for what seems like years now, but putting off the migration to cloud as the existing migration tooling wasn't serving our needs and we had a great deal of custom integrations that needed to be implemented.
Its been a long time coming, but we are finally getting this done. We are tentatively planning to migrate jira.pentaho.com to pentaho-community.atlassian.net, where the wiki was migrated to, starting FEB 3rd. We will send out notices to all existing users early next week regarding the migration. Once the migration is complete, the content will once again be anonymously readable and anybody will be able to join. Atlassian does a much better job of weeding out the spammers than we were capable of doing. That is why we had to shut off new signups a few months back. We couldn't update to stop the bots from successfully signing up and spamming.
If you aren't already a user on jira.pentaho.com and would like access before the migration you can contact Pentaho support and we will create an account for you.
Also, we are aware that the public Confluence wiki content is terribly out-of-date. I believe that will start to get the updating it deserves after the Jira migration.
-Steve
HV Eng DevOps