Re: [openstack-dev] Election Season, PTL and TC September/October 2016
On 16-09-13 10:23 AM, Anita Kuno wrote: On 16-09-13 09:52 AM, Nate Johnston wrote: On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: Lastly, election officials are also reachable through the #openstack-election Freenode channel. I wonder if it's worth having all conversations in #openstack-dev? There are pros and cons to both. Having a single purpose election channel certainly make it easy to spot election activity Using openstack-dev increases the possibility of braoder reach. I don't have a strong opionion either way. Yours Tony. No strong opinion either, but I agree openstack-dev would get more visiblity. Sean (smcginnis) I am fine with #openstack-dev if that is the consensus choice, but we may also want to list the direct contact info for the election officers Officials, not officers. The role is to administrate as an appointee of the technical committee, not police. so that people can ping directly in case their query happens to get lost. The conversation can then come back to #openstack-dev, but then you would know you had someone's attention. Well the method of communication up until now has been using the -dev mailing list with an invitation to email the election officials directly for private matters. That way communication reaches the broadest audience and is time insensitive. Correction, timezone insensitive. The fact that email is time sensitive is also one of the features for using it. Thanks, Anita. My experience is that has worked well in the past. Thank you, Anita. But this is my first time helping out on an OpenStack election, so I may be a bit paranoid about missing something. --N. __ 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 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] Election Season, PTL and TC September/October 2016
On 16-09-13 09:52 AM, Nate Johnston wrote: On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: Lastly, election officials are also reachable through the #openstack-election Freenode channel. I wonder if it's worth having all conversations in #openstack-dev? There are pros and cons to both. Having a single purpose election channel certainly make it easy to spot election activity Using openstack-dev increases the possibility of braoder reach. I don't have a strong opionion either way. Yours Tony. No strong opinion either, but I agree openstack-dev would get more visiblity. Sean (smcginnis) I am fine with #openstack-dev if that is the consensus choice, but we may also want to list the direct contact info for the election officers Officials, not officers. The role is to administrate as an appointee of the technical committee, not police. so that people can ping directly in case their query happens to get lost. The conversation can then come back to #openstack-dev, but then you would know you had someone's attention. Well the method of communication up until now has been using the -dev mailing list with an invitation to email the election officials directly for private matters. That way communication reaches the broadest audience and is time insensitive. My experience is that has worked well in the past. Thank you, Anita. But this is my first time helping out on an OpenStack election, so I may be a bit paranoid about missing something. --N. __ 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 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] Election Season, PTL and TC September/October 2016
On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: > On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > > > Lastly, election officials are also reachable through the > > > #openstack-election Freenode channel. > > > > I wonder if it's worth having all conversations in #openstack-dev? > > > > There are pros and cons to both. > > > > Having a single purpose election channel certainly make it easy to spot > > election activity > > Using openstack-dev increases the possibility of braoder reach. > > > > I don't have a strong opionion either way. > > > > Yours Tony. > > No strong opinion either, but I agree openstack-dev would get more > visiblity. > > Sean (smcginnis) I am fine with #openstack-dev if that is the consensus choice, but we may also want to list the direct contact info for the election officers so that people can ping directly in case their query happens to get lost. The conversation can then come back to #openstack-dev, but then you would know you had someone's attention. But this is my first time helping out on an OpenStack election, so I may be a bit paranoid about missing something. --N. __ 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] Election Season, PTL and TC September/October 2016
On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > Lastly, election officials are also reachable through the > > #openstack-election Freenode channel. > > I wonder if it's worth having all conversations in #openstack-dev? > > There are pros and cons to both. > > Having a single purpose election channel certainly make it easy to spot > election activity > Using openstack-dev increases the possibility of braoder reach. > > I don't have a strong opionion either way. > > Yours Tony. No strong opinion either, but I agree openstack-dev would get more visiblity. Sean (smcginnis) > __ > 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 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] Election Season, PTL and TC September/October 2016
Tony Breeds wrote: > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > >> Lastly, election officials are also reachable through the >> #openstack-election Freenode channel. > > I wonder if it's worth having all conversations in #openstack-dev? > > There are pros and cons to both. > > Having a single purpose election channel certainly make it easy to spot > election activity > Using openstack-dev increases the possibility of braoder reach. > > I don't have a strong opionion either way. At the very least it should happen in a logged channel. I think reusing #openstack-dev for this is fine -- it's an activity that is limited in time (so doesn't need a permanent channel) and -dev is pretty inactive those days. -- Thierry Carrez (ttx) signature.asc Description: OpenPGP digital signature __ 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] Election Season, PTL and TC September/October 2016
On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > Lastly, election officials are also reachable through the > #openstack-election Freenode channel. I wonder if it's worth having all conversations in #openstack-dev? There are pros and cons to both. Having a single purpose election channel certainly make it easy to spot election activity Using openstack-dev increases the possibility of braoder reach. I don't have a strong opionion either way. Yours Tony. signature.asc Description: PGP signature __ 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 and TC September/October 2016
Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware, in the PTL elections if the program only has one candidate, that candidate is acclaimed 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 myself Tristan Cacqueray (tristanC) email: tdecacqu at redhat dot com, Tony Breed (tonyb) email: tony at bakeyournoodle dot com and Nate Johnston (njohnston), openstacknate at gmail dot com so that we may address your concerns. Lastly, election officials are also reachable through the #openstack-election Freenode channel. Thank you, -Tristan signature.asc Description: OpenPGP digital signature __ 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
