Hey can someone (@popey?) give me access to post on #announcements or at least tell me how I can have somenoe else post there? I’d like to put out an official call for nominations.
Also, if anyone is interested in putting a name in the hat, please send your nominations to the Community Council mailing list at community-council@lists.ubuntu.com. I have access there, so will be able to see it. The name and Launchpad ID of whomever your nominating should be included in that email. (also don’t forget Ubuntu Membership is a prerequisite)
Absolutely. Just make sure you’re an Ubuntu Member. I’m going to get an announcement going soon with all the details but you can look at some old calls for nominations to get an idea of how this all works:
I have created a group here called “community-council” which (currently) contains @sabdfl as owner, and @wxl as a member. Granted that group access to post to the Announcements category on the site. Hope that’s suitable.
(no, we don’t have any kind of automatic sync between launchpad groups and here, yet).
I also posted this to a variety of relevant (community/news-related) Ubuntu mailing lists. Unfortunately, I got flat out rejected by ubuntu-announce. Is that something you could help with @vorlon?
@wxl posting to ubuntu-announce requires a specific header. However, the audience for ubuntu-announce is quite loosely connected to Ubuntu as a community, and I don’t think you would get any good nominations from that list that you wouldn’t already get from posting to other lists. Do you want to post this to ubuntu-devel-announce instead?
Well, the description for the list makes it seem pretty vague (essentially “announcements related to Ubuntu”), so I figured it would be more appropriate. ubuntu-devel-announce, being specific to developers, seems like it wouldn’t be.
Right but if you look at the history of posts, it’s basically just announcements of new Ubuntu releases and their end-of-life. So if you are getting your information about the Ubuntu release cycle via that mailing list, you’re…probably not a good candidate for the CC?
I certainly see what you’re saying and for my purposes, I’ll just consider it irrelevant. However, it may be good for other folks for the description of the list to more clearly define what it’s about.
Ugh I forgot about that, despite your previous reminder. I thought I had access and was going to check that and must have got distracted. Rather than try to figure that all out, I’ll take you up on your offer. Please post it up. And anywhere else you might like.
Just one other thing I would like to mention: I know that the status of some boards and councils have already or will degrade without intervention from the CC or Canonical IS (which will ultimately need authorization from the CC or Mark himself to act) before we have a new CC in place. Getting those boards and councils back up and running is going to be an important first task of the new CC.
Until then, my suggestion to these boards and councils: don’t be dismayed! You’ll be back up and running soon enough. I would encourage you all to continue your work as normal. Sure, there will be some things you won’t have the authority to execute, but keep track of those things and that will be part of our clean up work when we get the ball rolling again.
If someone with access (ahem @sabdfl) wants to be a dear and perhaps renew everyone on all councils and boards for about a month or two, that should cover us while we figure this all out.
When I requested an extention on the membership board, Canoical IS was very helpful via the “#canonical-sysadmin” channel (IRC). They will apparantly be extending the membership board by a month until a more permanent solution (IE CC is back) is ready.
I know that we who are on the Ubuntu Forums Council have had to scramble a few times to find someone to extend our expiry dates in the absence of an approving authority, which we have been doing for some time by begging on the IRC.
Thanks to Wild_Man for sharing this development with us there.
I’m pleased to announce that I have emailed @sabdfl the list of nominees for the Community Council. As soon as he provides a shortlist of the nominees, I will create an election so that the Ubuntu Members can approve the candidates and then we’ll have the Community Council back!
According to the documentation on restaffing, we should expect the time to get the shortlist to be about 1 week. After that, voting by Ubuntu Members should occur over about a 2 week period.
That said, now is the time to make sure your Ubuntu Membership is up to date and that your Launchpad account includes an email, since if you look at the documentation to create an election, you’ll notice a script is used to scrape this information off of Launchpad. If either of those two conditions are not met, your ballot will not be sent.
If you have lapsed on your Ubuntu Membership, please contact the Ubuntu Membership Board immediately to get that resolved. Similarly, I would contact them if you would like to become a member (just keep in mind that you earn one for contributing, not just because you ask nice ).
You’re very welcome QIII and I will post the results of the nominations on the forum as well when it’s available so the Ubuntu Members on the forum will have an opportunity to vote.
Just a quick note to say that I have the shortlist in my hands and will get started on creating the election shortly. Hopefully you’ll all have ballots in your inboxes by the end of the day (my time at least).
That said, again remember that in order to receive your ballot, you need to be an Ubuntu Member and make sure you have an email listed in Launchpad.
I’ll post again when the ballots have been sent. If you don’t get one after seeing that post, please get in touch.
Ok, all the ballots have been sent. I’m still working on reaching out to those Ubuntu Members that do not have a public email. If you want to save me the trouble, please get in touch.
That said, voting is now underway and will continue until Saturday October 24 2020 00:01 UTC. As the top 7 candidates will be elected, please make sure to rank all of the candidates in order of preference.
(though we might want IS to force https)
).