NULL AND VOID
The results of these measures are considered null and void. Please read https://composr.app/news/view/announcements/re-vote-previous-two.htm?blog=0
Hello everyone!
On the release of Composr 11 beta8, I launched voting for two measures: blocking AI bot access to composr.app, and prioritising the v11 branch on our git repositories.
Voting has closed on both measures as per a 14-day open voting period (votes were weighed based on a member's voting power in the community). And the results are in.
Blocking AI bot crawlers to composr.app
REJECTED
This measure was rejected with 89% no and 11% yes. As such, no change will be made. And AI bots will continue to be allowed to crawl and access composr.app without restriction (aside from a rate limiter which applies to all composr.app traffic).
Prioritising v11 Branch on GitLab / GitHub
PASSED
This measure passed with 100% yes and 0% no.
In the near future, our GitLab and GitHub branches will be updated so that:
- the v11 branch is the first one you see (it is primary) when going to the repositories, and
- the master branch will be renamed to v10.
Additionally, it will now be standard for us to name every branch as follows:
- For version branches... the name "vX" where X is the numeric major[.minor] version number
- For feature branches, the name "feature_some_keywords_vX" where X is the target numeric major[.minor] version number
- For bug fix branches, the name "bug_some_keywords_vX" where X is the target numeric major[.minor] version number
Thank you everyone who voted on these measures! Keep an eye out later this year as we will have a very important measure coming out to vote in the new Composr Constitution and the Board Members. There may be other, more minor measures before that.
Comments
1) A bug in Composr (now fixed on composr.app; will be pushed to 11 beta9). The newsletter system was respecting the setting for allowing e-mails from other members… it should have been respecting the setting for allowing e-mails from staff.
2) My server had issues sending e-mails to you. I'm not sure why. Gmail is complaining my server has an invalid PTR record. But I ran a test by sending an e-mail to my own Gmail account, and it worked just fine.
…I just overrode the bounce and sent a test e-mail to you. And it seemed to went through that time. So it might have been a one-off issue.
Unfortunately, I cannot determine directly if the newsletter went out to you or not because mail logs do not go that far back.
However, I did find something interesting. There might be a bug in the newsletter system. Your e-mail address does not show up in the list of "Send to site members" subscribers on the back-end even though you have an e-mail set and you have "receive site newsletters" ticked on your profile.
I am going to look into this. If it is indeed a bug, I'll fix it. And then I will also have to revoke the results of those polls since it's very likely other people didn't get the e-mail either… and we will have to re-conduct voting on those measures.
I will update you.