Dear Gustaf thanks for this good work. Github does appear to be superior to Bitbucket on many fronts.
Will the tar.gz files for each release continue to be published to https://sourceforge.net/projects/naviserver/files/naviserver/ ? best wishes Brian ________________________________ From: Gustaf Neumann <neum...@wu.ac.at> Sent: Sunday 19 November 2023 5:17 pm To: naviserver-devel@lists.sourceforge.net <naviserver-devel@lists.sourceforge.net> Subject: Re: [naviserver-devel] NaviServer 4.99.29 available Dear all, This is a follow-up to my own mail. The problem due to the changes of the billing rules on Bitbucket (see below) are somewhat sorted out, I have again access to the repository, but many of the former contributors are deleted from the "naviserver" group to get it functioning. There was also a change with "managed accounts", which made the problem for me even more complicated. In total, I count 31 emails with Atlassian support to sort these things out. Anyhow, these changes are signs that Atlassian does not have a high priority on open source projects with free accounts. We have discussed this with Zoran, and we came to the conclusion that it is the best to move the NaviServer repositories to GitHub https://github.com/orgs/naviserver-project/repositories We have now on GitHub an organization "naviserver-project" which contains now the 54 sub-repositories. This is essentially the same structure we had before. We also have a certain hope, that the move to GitHub will rather improve the visibility of NaviServer. All the newest commits were done on these new repositories. The plan is to move completely to GitHub and to delete the repositories on Bitbucket to avoid confusion. Please adjust your install/update scripts to point to the new link. All the best -g On 02.11.23 15:30, I wrote: So far, these changes are only available on sourceforge, since i have lost write access to the repository at bitbucket. The people on Atlassian seem to have changed some account types, and - on to of this - they annouced via the Blog post on September 27, 2023, that the billing model changed (where they also refer to the "unified-user-management"). It took me a while to figure out, what happened. The blog post states: >From October 31st, 2023, Bitbucket Cloud will begin counting all workspace >members as a billable user. .... Free plans: If you're on a free plan and your billable user count is higher than 5 as per the new definition of billable user, all repositories in your workspace will become read-only until you remove some users or upgrade your workspace to a paid plan. It seems that the users of the "naviserver" group are now counted as "billable users", and it contains 19 users. According to support, we have to reduce this number to 5, otherwise nobody will be able to commit anything. Due to the ability with PRs, i think the reduction will be possible without too much loss in functionality. If nobody objects, i will go back in history and reduce the number of commit-member based on the most recent direct commits. I hope, that non of the "old members" will be offended by this. One other option would be to upgrade to a paid plain - but i am not sure, who is gonna pay for this.
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
