[openstack-dev] [all][tc][elections] Stein TC Election Results
Please join me in congratulating the 6 newly elected members of the Technical Committee (TC): - Doug Hellmann (dhellmann) - Julia Kreger (TheJulia) - Jeremy Stanley (fungi) - Jean-Philippe Evrard (evrardjp) - Lance Bragstad (lbragstad) - Ghanshyam Mann (gmann) Full Results: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f773fda2d0695864 Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. Voter turnout was significantly up from recent cycles. We need to ensure your voices are heard. -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Last day for TC voting
We are coming down to the last hours for voting in the TC election. Voting ends Sep 27, 2018 23:45 UTC. Search your gerrit preferred email address [0] for the following subject: Poll: Stein TC Election That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleages to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/#stein-tc-candidates What to do if you don't see the email and have a commit in at least one of the official programs projects[1]: * check the trash of your gerrit Preferred Email address[0], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the program project repos[1] and email the election officials [2] If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Last time we checked, there were over 1200 unvoted ballots, so your vote can make a significant difference. [0] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml?id=sept-2018-elections [2] https://governance.openstack.org/election/#election-officials -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][tc][election] TC Election Campaigning Period
Developers, The TC Election Campaigning Period has now started (1). During the next couple days, you are all encouraged to ask the candidates questions about their platforms (2), opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform (2), and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. Scheduling Note: This cycle, the campaigning season overlaps with PTG. While our community strives to have many of our persistent communications in fora that permit participation by all, in-person discussions on some issues raised in campaigning will be inevitable. For those that are attending PTG, if you feel that an in-person discussion related to campaigning is of interest to the wider community, please summarise it to the mailing list. For those not attending, if you have a query raised on the mailing list that you feel is not receiving attention, consider asking someone attending PTG to relay the question to a candidate. 1: https://governance.openstack.org/election/ 2: http://git.openstack.org/cgit/openstack/election/tree/candidates/stein/TC -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][election] Nominations for OpenStack PTLs (Project Team Leads) are now open
Nominations for OpenStack PTLs (Program Team Leads) are now open and will remain open until July 31st, 2018 23:45 UTC. This term is expected to be slightly longer than usual, as the release cycle is expected to adjust to match the Summit schedule. All nominations must be submitted as a text file to the openstack/election repository as explained at http://governance.openstack.org/election/#how-to-submit-your-candidacy Please make sure to follow the new candidacy file naming convention: $cycle_name/$project_name/$ircname.txt. In order to be an eligible candidate (and be allowed to vote) in a given PTL election, you need to have contributed to the corresponding team[0] during the Queens-Rocky timeframe (February 5th, 2018 00:00 UTC to July 24th, 2018 00:00 UTC). You must also be an OpenStack Foundation Individual Member in good standing. To check if your membership http://governance.openstack.org/election/#how-to-submit-your-candidacy Additional information about the nomination process can be found here: https://governance.openstack.org/election/ Shortly after election officials approve candidates, they will be listed here: https://governance.openstack.org/election/#stein-ptl-candidates The electorate is requested to confirm their email address in gerrit[1], prior to July 24th, 2018 midnight UTC so that the emailed ballots are mailed to the correct email address. This email address should match that which was provided in your foundation member profile[2] as well. Happy running, [0] https://governance.openstack.org/tc/reference/projects/ [1] https://review.openstack.org/#/settings/contact [2] https://www.openstack.org/profile/ -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Election Season, PTL July 2018
Election season is nearly here! Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Please note, if only one candidate is nominated as PTL for a program during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a program's PTL position. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/election/#election-officials -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] use of storyboard (was [TC] Stein Goal Selection)
Doug Hellmann wrote: > If an epic is just a list of stories, doesn't that make it a worklist? Worklists are one way to do epics. In prior discussion about epics, a number of people have raised the idea that an epic contains more than just a list of stories, but also connective narrative (think about all the “I’ll kill you in the morning” parts of Arabian Nights, for example). In that case, a wiki page may be a better solution, where the wiki page has the connective narrative, perhaps a list of personae, or whatever is appropriate for the specific requirements analysis procedure being used, and links to individual stories that together will enable the epic (but may also appear in different epics with different personae, etc.). Such a textual document with links could also be implemented using the specs infrastructure, rather than a wiki page. I suspect there are other ways that I do not recall at the moment, or I have not heard proposed. At a high level, I think epics are important, but I think that more experimentation with ways to connect collections of stories is necessary before we can collectively understand what would make sense. We should try several things (likely adoptions from the various ways we are doing similar tracking now), and I expect us to slowly converge on two or three solutions that are known to work well for our teams, depending on the individual characteristics of the teams. — Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] storyboard evaluation
Emilien Macchi wrote: > What we need to investigate: > - how do we deal milestones in stories and also how can we have a > dashboard with an overview per milestone (useful for PTL + TripleO > release managers). While the storyboard API supports milestones, they don’t work very similarly to “milestones” in launchpad, so are probably confusing to adopt (and have no UI support). Some folk use tags for this (perhaps with an automatic worklist that selects all the stories with the tag, for overview). > - how to update old Launchpad bugs with the new link in storyboard > (probably by hacking the migration script during the import). There had been a task on the migration story to do this, but it it was dropped in favour of project-wide communications, rather than per-bug communications. An add-on script to modify bugs after migration is complete is probably a richer solution than direct modification of the current migration script (which allows multiple runs to keep up to date during transition), if tripleO wishes per-bug communication. Some context at https://storyboard.openstack.org/#!/story/2000876 — Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Switching to longer development cycles
Dirk Müller wrote: > 2017-12-13 17:17 GMT+01:00 Thierry Carrez <thie...@openstack.org>: > > > - We'd only do one *coordinated* release of the OpenStack components per > > year, and maintain one stable branch per year > > - We'd elect PTLs for one year instead of every 6 months > > - We'd only have one set of community goals per year > > - We'd have only one PTG with all teams each year > > Well, I assume there would still be a chance to have a mid-cycle PTG > independent of the 1 year release schedule proposal if there > is a need for it. I wonder if we may find it easier to take opinions on this if we separate the ideas of “we should only have one formal coordinated release a year, because teams are finding the cadence too fast to do the sort of work required in each release, and consumers are finding the cadence too fast to prepare downstream editions of each release” from “we should reduce the frequency of in-person meetings”. From my perspective, both are important debates to have, and both potential decisions have wide-ranging consequences, but I find the conflation to distract from reasoned consideration of each. — Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][tc][election] TC Election Campaigning Period
Developers, The TC Election Campaigning Period started about 19 hours ago (1). During the next couple days, you are all encouraged to ask the candidates questions about their platforms (2), opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform (2), and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and from questions from the wider community will help ensure the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. All, The election officials would like to apologise for the delay in kicking off campaigning, and to thank Zane Bitter for assisting in starting the discussion (3). After the conclusion of the current election, we will be seeking input on mechanisms that can improve the utility of the campaign period for the electorate, the candidates, and observers. 1: https://governance.openstack.org/election/ 2: http://git.openstack.org/cgit/openstack/election/tree/candidates/queens/TC 3: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123524.html — Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][elections] TC nomination period is now over
Sean McGinnis wrote: > On Wed, Oct 11, 2017 at 12:18:30AM +, Kendall Nelson wrote: > > Hello!TC Nomination is now over. The official candidate list is available > > on the election website[0].We now enter the campaigning period where > > candidates and electorate may debate their statements.The election will > > start this Saturday.Thank you,Kendall Nelson (diablo_rojo) > > [0]: http://governance.openstack.org/election/#pike-tc-candidates > > Pike? :) We’re also slightly backlogged on development of better documentation automation. Despite the cosmetics being wrong, this does actually link to the Queens TC list. — Emmet __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open
Tony Breeds wrote: > On Sun, Oct 01, 2017 at 11:26:33PM +, Kendall Nelson wrote: > > Hello Again, > > > > A few corrections from the kickoff email: > > > > Candidates for the Technical Committee Positions: Any Foundation individual > > member can propose their candidacy for an available, directly-elected TC > > seat. (except the seven (7) TC members who were elected for a one-year seat > > in April[3]). > > > > The election will be held from September 29th through to 23:45 October 18th, > > 2017 UTC. PLEASE NOTE, we are discussing adding a few days to the > > nomination period thereby shortening the campaigning period due to the > > lack of updates to the governance page and the delayed kickoff email. > > Please keep an eye out for updates! > > Because of the delay in getting information published the election > officials have decided to extend the nomination period by 2 days, this > has a knock on effect that each deadline is now also bumped: > > > Events Start Date End Date > TC nomination Sep 29, 2017 23:59 UTC Oct 08, 2017 23:45 UTC > TC Campaigning Oct 09, 2017 23:59 UTC Oct 12, 2017 23:45 UTC > TC Election Oct 12, 2017 23:59 UTC Oct 18, 2017 23:45 UTC While all of the prose above is correct, the table does not reflect the extended dates (although we'd be delighted to have nominations well in advance of the dates listed). The updated delayed-two-days dates are: Events Start Date End Date TC nominationSep 29, 2017 23:59 UTC Oct 10, 2017, 23:45 UTC TC Campaigning Oct 11, 2017 23:59 UTC Oct 14, 2017, 23:45 UTC TC Election Oct 14, 2017 23:59 UTC Oct 20, 2017, 23:45 UTC Apologies for the confusion. For those in doubt in the future, the correct current agreed dates are also available from git(1). 1: http://git.openstack.org/cgit/openstack/election/tree/configuration.yaml -- Emmet HIKORY __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][pack-deb][storlets][tacker][telemetry] Last day for PTL candidate announcements
This is the last reminder of the impending conclusion of the PTL candidate announcement period. This is now the last day for nominations. If you want to stand for PTL, follow the posted instructions [1] before 23:45 UTC, 9th August to make sure the community knows your intentions. To ensure your candidacy is merged by the deadline, you may wish to allow some time for reviews after submission. Those four projects still without nominated candidates at the conclusion of this period will be subject to the Technical Committee procedures for leaderless projects [2]. Thank you. -- Emmet HIKORY 1: http://governance.openstack.org/election/#how-to-submit-your-candidacy 2: http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Doc to with pointers on how to review?
Tom Fifield wrote: Just wondering, do we have a document somewhere that educates people on how to do a code review? eg giving a few pointers that reviewers for a particular project normally look for I asked this very question on IRC a few days ago, and was pointed at https://wiki.openstack.org/wiki/ReviewChecklist There are any number of projects that may have specific requirements that aren't documented on that page (please add them), but I found that having read that gave me great confidence to submit more reviews. -- Emmet HIKORY ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
