Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-18 Thread Jeremy Stanley
On 2018-06-18 11:54:00 -0700 (-0700), Kendall Nelson wrote:
[...]
> I'm 100% in agreement with Doug and Tony about not giving more work to
> election officials. Speaking as an election official, its already tedious
> and one more thing to keep track of (even if its automated) is not
> something I would wish on future election officials.

Yep, TC member hat off and election official hat on for a moment,
the proposed changes (there's a similar one for showing the TC
member E-mail addresses) just involve us copying over one piece of
additional information we already have in the election data so is
really no increased burden in that regard.
-- 
Jeremy Stanley


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


Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-18 Thread Kendall Nelson
On Sun, Jun 17, 2018 at 5:49 PM Tony Breeds  wrote:

> On Fri, Jun 15, 2018 at 03:05:51PM -0400, Doug Hellmann wrote:
> > Excerpts from Jean-Philippe Evrard's message of 2018-06-15 17:37:02
> +0200:
> > > > Not sure it'd help but one option we do is to create aliases based on
> > > > the title.  Though since the PTLs don't have addresses on the
> openstack
> > > > domain an alias may not make as much sense, it'd have to be a full
> > > > account forward.  It's useful for centralized spam filtering.
> > >
> > > I foresee this:
> > > 1) We create an alias  to PTL email
> > > 2) PTL think that kind of emails are worth sharing with a team to
> balance work
> > > 3) We now have a project mailing list
> > > 4) People stop using openstack-dev lists.
> > >
> > > But that's maybe me...
> > >
> >
> > Yeah, setting all of that up feels like it would just be something
> > else we would have to remember to do every time we have an election.
> > I'm trying to reduce the number those kinds of tasks we have, so
> > let's not add a new one.
>
> While I'm not sure that JP's scenario would eventuate I am against
> adding the aliases and adding additional work for the election
> officials.  It's not that this would be terribly hard to automate it
> just seems like duplication of data/effort whereas the change under
> review is pretty straight forward.
>

I'm 100% in agreement with Doug and Tony about not giving more work to
election officials. Speaking as an election official, its already tedious
and one more thing to keep track of (even if its automated) is not
something I would wish on future election officials.

-Kendall (diablo_rojo)


>
> Yours Tony.
> __
> 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] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-17 Thread Tony Breeds
On Fri, Jun 15, 2018 at 03:05:51PM -0400, Doug Hellmann wrote:
> Excerpts from Jean-Philippe Evrard's message of 2018-06-15 17:37:02 +0200:
> > > Not sure it'd help but one option we do is to create aliases based on
> > > the title.  Though since the PTLs don't have addresses on the openstack
> > > domain an alias may not make as much sense, it'd have to be a full
> > > account forward.  It's useful for centralized spam filtering.
> > 
> > I foresee this:
> > 1) We create an alias  to PTL email
> > 2) PTL think that kind of emails are worth sharing with a team to balance 
> > work
> > 3) We now have a project mailing list
> > 4) People stop using openstack-dev lists.
> > 
> > But that's maybe me...
> > 
> 
> Yeah, setting all of that up feels like it would just be something
> else we would have to remember to do every time we have an election.
> I'm trying to reduce the number those kinds of tasks we have, so
> let's not add a new one.

While I'm not sure that JP's scenario would eventuate I am against
adding the aliases and adding additional work for the election
officials.  It's not that this would be terribly hard to automate it
just seems like duplication of data/effort whereas the change under
review is pretty straight forward.

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


Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Doug Hellmann
Excerpts from Jean-Philippe Evrard's message of 2018-06-15 17:37:02 +0200:
> > Not sure it'd help but one option we do is to create aliases based on
> > the title.  Though since the PTLs don't have addresses on the openstack
> > domain an alias may not make as much sense, it'd have to be a full
> > account forward.  It's useful for centralized spam filtering.
> 
> I foresee this:
> 1) We create an alias  to PTL email
> 2) PTL think that kind of emails are worth sharing with a team to balance work
> 3) We now have a project mailing list
> 4) People stop using openstack-dev lists.
> 
> But that's maybe me...
> 

Yeah, setting all of that up feels like it would just be something
else we would have to remember to do every time we have an election.
I'm trying to reduce the number those kinds of tasks we have, so
let's not add a new one.

Doug

__
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] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Jean-Philippe Evrard
> Not sure it'd help but one option we do is to create aliases based on
> the title.  Though since the PTLs don't have addresses on the openstack
> domain an alias may not make as much sense, it'd have to be a full
> account forward.  It's useful for centralized spam filtering.

I foresee this:
1) We create an alias  to PTL email
2) PTL think that kind of emails are worth sharing with a team to balance work
3) We now have a project mailing list
4) People stop using openstack-dev lists.

But that's maybe me...

__
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] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Matthew Thode
On 18-06-15 15:29:07, Jeremy Stanley wrote:
> On 2018-06-15 10:23:36 -0500 (-0500), Matthew Thode wrote:
> [...]
> > Not sure it'd help but one option we do is to create aliases based
> > on the title.  Though since the PTLs don't have addresses on the
> > openstack domain an alias may not make as much sense, it'd have to
> > be a full account forward.  It's useful for centralized spam
> > filtering.
> 
> I'm not personally comfortable having someone else decide for me
> what is or isn't spam, and I doubt I'm alone in that.
> -- 
> Jeremy Stanley

That makes sense, it'd only be for openstack ptl emails, still makes
sense.

-- 
Matthew Thode (prometheanfire)


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


Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Jeremy Stanley
On 2018-06-15 10:23:36 -0500 (-0500), Matthew Thode wrote:
[...]
> Not sure it'd help but one option we do is to create aliases based
> on the title.  Though since the PTLs don't have addresses on the
> openstack domain an alias may not make as much sense, it'd have to
> be a full account forward.  It's useful for centralized spam
> filtering.

I'm not personally comfortable having someone else decide for me
what is or isn't spam, and I doubt I'm alone in that.
-- 
Jeremy Stanley


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


Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Matthew Thode
On 18-06-15 15:00:50, Jeremy Stanley wrote:
> Governance tooling change https://review.openstack.org/575554 is
> currently up for review to start displaying current PTL E-mail
> addresses on the team specific pages linked from the projects index
> https://governance.openstack.org/tc/reference/projects/ page.
> 
> Since https://review.openstack.org/234420 merged a few years ago
> we've been tracking PTL E-mail addresses in the structured data from
> which we generate those pages, but the Sphinx extension we're using
> was never amended to include them. Having somewhere consistent to
> point members of the community who need to reach out to the PTL of a
> team in private (and may not have easy access or comfort to do so via
> IRC privmsg) would be useful. Right now we're stuck telling people
> to dig around in a YAML file for them, which is not an especially
> friendly answer.
> 
> A knee-jerk reaction any time E-mail addresses get displayed
> somewhere new is that it's going to increase the amount of spam
> those addresses receive. Keep in mind that we've been publishing all
> of them on a Web page for years now, just one which is only
> convenient for spammers and not one which is convenient for people
> who might have a legitimate need to contact our PTLs.
> -- 
> Jeremy Stanley

Not sure it'd help but one option we do is to create aliases based on
the title.  Though since the PTLs don't have addresses on the openstack
domain an alias may not make as much sense, it'd have to be a full
account forward.  It's useful for centralized spam filtering.

-- 
Matthew Thode (prometheanfire)


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] [tc] [ptl] PTL E-mail addresses on rendered team pages

2018-06-15 Thread Jeremy Stanley
Governance tooling change https://review.openstack.org/575554 is
currently up for review to start displaying current PTL E-mail
addresses on the team specific pages linked from the projects index
https://governance.openstack.org/tc/reference/projects/ page.

Since https://review.openstack.org/234420 merged a few years ago
we've been tracking PTL E-mail addresses in the structured data from
which we generate those pages, but the Sphinx extension we're using
was never amended to include them. Having somewhere consistent to
point members of the community who need to reach out to the PTL of a
team in private (and may not have easy access or comfort to do so via
IRC privmsg) would be useful. Right now we're stuck telling people
to dig around in a YAML file for them, which is not an especially
friendly answer.

A knee-jerk reaction any time E-mail addresses get displayed
somewhere new is that it's going to increase the amount of spam
those addresses receive. Keep in mind that we've been publishing all
of them on a Web page for years now, just one which is only
convenient for spammers and not one which is convenient for people
who might have a legitimate need to contact our PTLs.
-- 
Jeremy Stanley


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