You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ponymail.apache.org by "John D. Ament" <jo...@apache.org> on 2016/06/25 10:51:34 UTC
Fwd: [jira] [Apache Infrastructure] New Podling Parent Request -
PonyMail PPMC
All,
I'll leave this up to the podling to decide how to proceed. Looking at the
project proposal, I'm just covering remaining requested resources. If
they're not needed, that's fine.
I do see a few issues though. Currently, ponymail is the only ASF project
that leverages github issues. The permissions around this seem odd to say
the least. For example, I can comment on tickets, but I cannot do things
like assign.
I asked infra recently on behalf of another incoming podling and the answer
I received was "no". I suspect that ponymail bypassed this because of a)
tight ties between the devs & infra resources and b) the way the project
was imported [looks like it was moved between orgs and not created
externally and pushed].
Ponymail using github issues also sets the precedence that it's OK to do.
I don't believe ASF is currently in a situation to grant this more widely.
Let me know.
John
---------- Forwarded message ---------
From: Daniel Gruno <ji...@apache.org>
Date: Fri, Jun 24, 2016 at 1:29 AM
Subject: [jira] [Apache Infrastructure] New Podling Parent Request -
PonyMail PPMC
To: <jo...@gmail.com>
New comment for the request "New Podling Parent Request - PonyMail PPMC"
with key INFRA-11998 has been added...
*Apache Infrastructure* - New TLP Parent Request
<https://issues.apache.org/jira/servicedesk/customer/portal/1> Reference:
*INFRA-11998*
<https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
New Podling Parent Request - PonyMail PPMC
<https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
Waiting
for Infra
Daniel Gruno Today 01:28
ping? :)
You can view the full request
<https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
Previous activity
Daniel Gruno 01/Jun/16 01:09
Everything but Confluence/JIRA is already set up.
I'm unsure whether the project needs it, but in case it does, we (infra)
would need some preferred instance names for this.
Details
New TLP Name Pony Mail (incubating)
Component/s Confluence, Git, Github, JIRA, Mailing Lists, Website
This message is automatically generated by JIRA Service Desk.
If you think it was sent incorrectly, please contact your JIRA
administrators.
For more information on JIRA Service Desk, see:
http://www.atlassian.com/software/jira/service-desk
Re: Fwd: [jira] [Apache Infrastructure] New Podling Parent Request -
PonyMail PPMC
Posted by "John D. Ament" <jo...@apache.org>.
On Sat, Jun 25, 2016 at 6:53 AM Daniel Gruno <hu...@apache.org> wrote:
> On 06/25/2016 12:51 PM, John D. Ament wrote:
> > All,
> >
> > I'll leave this up to the podling to decide how to proceed. Looking at
> the
> > project proposal, I'm just covering remaining requested resources. If
> > they're not needed, that's fine.
> >
> > I do see a few issues though. Currently, ponymail is the only ASF
> project
> > that leverages github issues. The permissions around this seem odd to
> say
> > the least. For example, I can comment on tickets, but I cannot do things
> > like assign.
> >
> > I asked infra recently on behalf of another incoming podling and the
> answer
> > I received was "no". I suspect that ponymail bypassed this because of a)
> > tight ties between the devs & infra resources and b) the way the project
> > was imported [looks like it was moved between orgs and not created
> > externally and pushed].
> >
> > Ponymail using github issues also sets the precedence that it's OK to do.
> > I don't believe ASF is currently in a situation to grant this more
> widely.
>
> VP Legal has said that GH Issues are fine to use (he was asked on behalf
> of another project at ApacheCon) as long as the replication to mailing
> lists works.
>
Then how do we ensure that there are proper permissions to work with the
issues? In JIRA this is a PMC driven effort, PMC members are in groups that
allow them to do crud operations for other PMC members, committers, and
outside contributors. Is there a ponymail group in the ASF's github
account that has access to maintain these permissions?
>
> With regards,
> Daniel.
>
> >
> > Let me know.
> >
> > John
> >
> > ---------- Forwarded message ---------
> > From: Daniel Gruno <ji...@apache.org>
> > Date: Fri, Jun 24, 2016 at 1:29 AM
> > Subject: [jira] [Apache Infrastructure] New Podling Parent Request -
> > PonyMail PPMC
> > To: <jo...@gmail.com>
> >
> >
> > New comment for the request "New Podling Parent Request - PonyMail PPMC"
> > with key INFRA-11998 has been added...
> > *Apache Infrastructure* - New TLP Parent Request
> > <https://issues.apache.org/jira/servicedesk/customer/portal/1>
> Reference:
> > *INFRA-11998*
> > <
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> > New Podling Parent Request - PonyMail PPMC
> > <
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> > Waiting
> > for Infra
> >
> > Daniel Gruno Today 01:28
> > ping? :)
> > You can view the full request
> > <
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> > Previous activity
> >
> > Daniel Gruno 01/Jun/16 01:09
> > Everything but Confluence/JIRA is already set up.
> > I'm unsure whether the project needs it, but in case it does, we (infra)
> > would need some preferred instance names for this.
> > Details
> > New TLP Name Pony Mail (incubating)
> > Component/s Confluence, Git, Github, JIRA, Mailing Lists, Website
> >
> > This message is automatically generated by JIRA Service Desk.
> > If you think it was sent incorrectly, please contact your JIRA
> > administrators.
> > For more information on JIRA Service Desk, see:
> > http://www.atlassian.com/software/jira/service-desk
> >
>
>
Re: Fwd: [jira] [Apache Infrastructure] New Podling Parent Request -
PonyMail PPMC
Posted by Daniel Gruno <hu...@apache.org>.
On 06/25/2016 12:51 PM, John D. Ament wrote:
> All,
>
> I'll leave this up to the podling to decide how to proceed. Looking at the
> project proposal, I'm just covering remaining requested resources. If
> they're not needed, that's fine.
>
> I do see a few issues though. Currently, ponymail is the only ASF project
> that leverages github issues. The permissions around this seem odd to say
> the least. For example, I can comment on tickets, but I cannot do things
> like assign.
>
> I asked infra recently on behalf of another incoming podling and the answer
> I received was "no". I suspect that ponymail bypassed this because of a)
> tight ties between the devs & infra resources and b) the way the project
> was imported [looks like it was moved between orgs and not created
> externally and pushed].
>
> Ponymail using github issues also sets the precedence that it's OK to do.
> I don't believe ASF is currently in a situation to grant this more widely.
VP Legal has said that GH Issues are fine to use (he was asked on behalf
of another project at ApacheCon) as long as the replication to mailing
lists works.
With regards,
Daniel.
>
> Let me know.
>
> John
>
> ---------- Forwarded message ---------
> From: Daniel Gruno <ji...@apache.org>
> Date: Fri, Jun 24, 2016 at 1:29 AM
> Subject: [jira] [Apache Infrastructure] New Podling Parent Request -
> PonyMail PPMC
> To: <jo...@gmail.com>
>
>
> New comment for the request "New Podling Parent Request - PonyMail PPMC"
> with key INFRA-11998 has been added...
> *Apache Infrastructure* - New TLP Parent Request
> <https://issues.apache.org/jira/servicedesk/customer/portal/1> Reference:
> *INFRA-11998*
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> New Podling Parent Request - PonyMail PPMC
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> Waiting
> for Infra
>
> Daniel Gruno Today 01:28
> ping? :)
> You can view the full request
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11998>
> Previous activity
>
> Daniel Gruno 01/Jun/16 01:09
> Everything but Confluence/JIRA is already set up.
> I'm unsure whether the project needs it, but in case it does, we (infra)
> would need some preferred instance names for this.
> Details
> New TLP Name Pony Mail (incubating)
> Component/s Confluence, Git, Github, JIRA, Mailing Lists, Website
>
> This message is automatically generated by JIRA Service Desk.
> If you think it was sent incorrectly, please contact your JIRA
> administrators.
> For more information on JIRA Service Desk, see:
> http://www.atlassian.com/software/jira/service-desk
>