You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "John D. Ament" <jo...@apache.org> on 2016/06/25 11:27:36 UTC
Resolution on Github Issues
All,
In talking with the PonyMail podling, I was informed that VP Legal approved
using GIthub Issues for projects. Seeing as how this was a legal approval,
I was wondering what other steps need to be done, if any, to make this open
to others.
John
Re: Resolution on Github Issues
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Jim Jagielski wrote on 6/29/16 1:32 PM:
> Recall that issue trackers have not been, traditionally, held under
> the requirement of being under ASF infra nor infra control. If people
> wish to use external, 3rd party issue/bug trackers, they are taking
> on the risks themselves, as far as SLAs, historical access, etc...
Can we please document the hard functional requirements that either
board, VP Legal, or the IPMC have for such services, so it's a little
clearer to projects what choices are allowable?
Obviously infra only supports specific services on ASF hardware/clouds,
so projects will also have to be aware about maintenance, admin
assistance, etc. for any such non-ASF run services.
- Shane
>
>> On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
>>
>> I think John is talking about
>> https://github.com/apache/incubator-ponymail/issues used instead of
>> ASF-hosted Jira/Bugzilla - source code is still maintained
>> git.apache.org as the main repository, with just mirroring to GitHub
>> and the usual Pull Request notifications.
>>
>>
>> The GitHub Issues of Ponymail are mirrored to
>> https://lists.apache.org/list.html?dev@ponymail.apache.org but you
>> would have to use GH infrastructure to manage the issues (e.g.
>> new/assign/close).
>>
>> See legal discussion on
>> https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
>> contribute" should be covered - so legally it's "OK".
>>
>>
>> But then the question is if other ASF projects can also choose to use
>> GitHub Issues for their issue tracking.
>>
>>
>> I think this raises wider questions for policy and community and
>> should be discussed on general@incubator and/or community@apache
>> rather than at legal-discuss.
>>
>> On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com> wrote:
>>> I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF\u2019s git or svn repositories.
>>>
>>> Ralph
>>>
>>>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
>>>>
>>>> All,
>>>>
>>>> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
>>>>
>>>> John
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>
>>
>>
>>
>> --
>> Stian Soiland-Reyes
>> Apache Taverna (incubating), Apache Commons
>> http://orcid.org/0000-0001-9842-9718
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Resolution on Github Issues
Posted by Chris Mattmann <ma...@apache.org>.
One thing I just want to pipe up here and re-iterate. Software
artifacts include more than just code. Having just the code
here as a requirement is incomplete without additional artifacts
including issue trackers, wikis, etc., seems incomplete and also
seems to produce undue burden and potential risk.
Having the ability at a minimum to have an archive copy/hot
backup of issues, wikis, etc., with the provenance of who is doing
what (similar to code) should also be something we consider.
Cheers,
Chris
On 6/29/16, 10:06 PM, "Greg Stein" <gs...@gmail.com> wrote:
>Heck, back in the day, mod_python continued with external mailing lists, even after becoming part of the HTTPD project. We only ever really cared about the source code being at the ASF.
>
>
>(nowadays, it seems we want mail archives here)
>
>
>On Wed, Jun 29, 2016 at 12:32 PM, Jim Jagielski
><ji...@jagunet.com> wrote:
>
>Recall that issue trackers have not been, traditionally, held under
>the requirement of being under ASF infra nor infra control. If people
>wish to use external, 3rd party issue/bug trackers, they are taking
>on the risks themselves, as far as SLAs, historical access, etc...
>
>> On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
>>
>> I think John is talking about
>>
>https://github.com/apache/incubator-ponymail/issues <https://github.com/apache/incubator-ponymail/issues> used instead of
>> ASF-hosted Jira/Bugzilla - source code is still maintained
>> git.apache.org <http://git.apache.org> as the main repository, with just mirroring to GitHub
>> and the usual Pull Request notifications.
>>
>>
>> The GitHub Issues of Ponymail are mirrored to
>>
>https://lists.apache.org/list.html?dev@ponymail.apache.org <ht...@ponymail.apache.org> but you
>> would have to use GH infrastructure to manage the issues (e.g.
>> new/assign/close).
>>
>> See legal discussion on
>>
>https://issues.apache.org/jira/browse/LEGAL-249 <https://issues.apache.org/jira/browse/LEGAL-249> - the "intention to
>> contribute" should be covered - so legally it's "OK".
>>
>>
>> But then the question is if other ASF projects can also choose to use
>> GitHub Issues for their issue tracking.
>>
>>
>> I think this raises wider questions for policy and community and
>> should be discussed on general@incubator and/or community@apache
>> rather than at legal-discuss.
>>
>> On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com> wrote:
>>> I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF’s git or svn repositories.
>>>
>>> Ralph
>>>
>>>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
>>>>
>>>> All,
>>>>
>>>> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
>>>>
>>>> John
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>legal-discuss-unsubscribe@apache.org <ma...@apache.org>
>>> For additional commands, e-mail:
>legal-discuss-help@apache.org <ma...@apache.org>
>>>
>>
>>
>>
>> --
>> Stian Soiland-Reyes
>> Apache Taverna (incubating), Apache Commons
>>
>http://orcid.org/0000-0001-9842-9718 <http://orcid.org/0000-0001-9842-9718>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail:
>legal-discuss-help@apache.org <ma...@apache.org>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>For additional commands, e-mail: legal-discuss-help@apache.org
>
>
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Resolution on Github Issues
Posted by Greg Stein <gs...@gmail.com>.
Not sure when/how, but I think it makes sense: we want a historical and
permanent archive of the *decision-making process* of our projects, and
that process (by definition) occurs on our mailing lists.
On Thu, Jun 30, 2016 at 6:26 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> I think having Email here was formalized/standardized when we
> were looking at using OmniTI and Circonous (sp??) as a replacement
> for our Email infra...
> > On Jun 30, 2016, at 1:06 AM, Greg Stein <gs...@gmail.com> wrote:
> >
> > Heck, back in the day, mod_python continued with external mailing lists,
> even after becoming part of the HTTPD project. We only ever really cared
> about the source code being at the ASF.
> >
> > (nowadays, it seems we want mail archives here)
> >
> > On Wed, Jun 29, 2016 at 12:32 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> > Recall that issue trackers have not been, traditionally, held under
> > the requirement of being under ASF infra nor infra control. If people
> > wish to use external, 3rd party issue/bug trackers, they are taking
> > on the risks themselves, as far as SLAs, historical access, etc...
> >
> > > On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
> > >
> > > I think John is talking about
> > > https://github.com/apache/incubator-ponymail/issues used instead of
> > > ASF-hosted Jira/Bugzilla - source code is still maintained
> > > git.apache.org as the main repository, with just mirroring to GitHub
> > > and the usual Pull Request notifications.
> > >
> > >
> > > The GitHub Issues of Ponymail are mirrored to
> > > https://lists.apache.org/list.html?dev@ponymail.apache.org but you
> > > would have to use GH infrastructure to manage the issues (e.g.
> > > new/assign/close).
> > >
> > > See legal discussion on
> > > https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
> > > contribute" should be covered - so legally it's "OK".
> > >
> > >
> > > But then the question is if other ASF projects can also choose to use
> > > GitHub Issues for their issue tracking.
> > >
> > >
> > > I think this raises wider questions for policy and community and
> > > should be discussed on general@incubator and/or community@apache
> > > rather than at legal-discuss.
> > >
> > > On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com>
> wrote:
> > >> I am sure Jim can speak for himself, but given the recent discussions
> I have been watching Github has not been approved to replace the ASF’s git
> or svn repositories.
> > >>
> > >> Ralph
> > >>
> > >>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org>
> wrote:
> > >>>
> > >>> All,
> > >>>
> > >>> In talking with the PonyMail podling, I was informed that VP Legal
> approved using GIthub Issues for projects. Seeing as how this was a legal
> approval, I was wondering what other steps need to be done, if any, to make
> this open to others.
> > >>>
> > >>> John
> > >>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > >> For additional commands, e-mail: legal-discuss-help@apache.org
> > >>
> > >
> > >
> > >
> > > --
> > > Stian Soiland-Reyes
> > > Apache Taverna (incubating), Apache Commons
> > > http://orcid.org/0000-0001-9842-9718
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > > For additional commands, e-mail: legal-discuss-help@apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > For additional commands, e-mail: legal-discuss-help@apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
Re: Resolution on Github Issues
Posted by Jim Jagielski <ji...@jaguNET.com>.
I think having Email here was formalized/standardized when we
were looking at using OmniTI and Circonous (sp??) as a replacement
for our Email infra...
> On Jun 30, 2016, at 1:06 AM, Greg Stein <gs...@gmail.com> wrote:
>
> Heck, back in the day, mod_python continued with external mailing lists, even after becoming part of the HTTPD project. We only ever really cared about the source code being at the ASF.
>
> (nowadays, it seems we want mail archives here)
>
> On Wed, Jun 29, 2016 at 12:32 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> Recall that issue trackers have not been, traditionally, held under
> the requirement of being under ASF infra nor infra control. If people
> wish to use external, 3rd party issue/bug trackers, they are taking
> on the risks themselves, as far as SLAs, historical access, etc...
>
> > On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
> >
> > I think John is talking about
> > https://github.com/apache/incubator-ponymail/issues used instead of
> > ASF-hosted Jira/Bugzilla - source code is still maintained
> > git.apache.org as the main repository, with just mirroring to GitHub
> > and the usual Pull Request notifications.
> >
> >
> > The GitHub Issues of Ponymail are mirrored to
> > https://lists.apache.org/list.html?dev@ponymail.apache.org but you
> > would have to use GH infrastructure to manage the issues (e.g.
> > new/assign/close).
> >
> > See legal discussion on
> > https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
> > contribute" should be covered - so legally it's "OK".
> >
> >
> > But then the question is if other ASF projects can also choose to use
> > GitHub Issues for their issue tracking.
> >
> >
> > I think this raises wider questions for policy and community and
> > should be discussed on general@incubator and/or community@apache
> > rather than at legal-discuss.
> >
> > On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com> wrote:
> >> I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF’s git or svn repositories.
> >>
> >> Ralph
> >>
> >>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
> >>>
> >>> All,
> >>>
> >>> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
> >>>
> >>> John
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> >> For additional commands, e-mail: legal-discuss-help@apache.org
> >>
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > Apache Taverna (incubating), Apache Commons
> > http://orcid.org/0000-0001-9842-9718
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > For additional commands, e-mail: legal-discuss-help@apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Resolution on Github Issues
Posted by Greg Stein <gs...@gmail.com>.
Heck, back in the day, mod_python continued with external mailing lists,
even after becoming part of the HTTPD project. We only ever really cared
about the source code being at the ASF.
(nowadays, it seems we want mail archives here)
On Wed, Jun 29, 2016 at 12:32 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> Recall that issue trackers have not been, traditionally, held under
> the requirement of being under ASF infra nor infra control. If people
> wish to use external, 3rd party issue/bug trackers, they are taking
> on the risks themselves, as far as SLAs, historical access, etc...
>
> > On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org>
> wrote:
> >
> > I think John is talking about
> > https://github.com/apache/incubator-ponymail/issues used instead of
> > ASF-hosted Jira/Bugzilla - source code is still maintained
> > git.apache.org as the main repository, with just mirroring to GitHub
> > and the usual Pull Request notifications.
> >
> >
> > The GitHub Issues of Ponymail are mirrored to
> > https://lists.apache.org/list.html?dev@ponymail.apache.org but you
> > would have to use GH infrastructure to manage the issues (e.g.
> > new/assign/close).
> >
> > See legal discussion on
> > https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
> > contribute" should be covered - so legally it's "OK".
> >
> >
> > But then the question is if other ASF projects can also choose to use
> > GitHub Issues for their issue tracking.
> >
> >
> > I think this raises wider questions for policy and community and
> > should be discussed on general@incubator and/or community@apache
> > rather than at legal-discuss.
> >
> > On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >> I am sure Jim can speak for himself, but given the recent discussions I
> have been watching Github has not been approved to replace the ASF’s git or
> svn repositories.
> >>
> >> Ralph
> >>
> >>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org>
> wrote:
> >>>
> >>> All,
> >>>
> >>> In talking with the PonyMail podling, I was informed that VP Legal
> approved using GIthub Issues for projects. Seeing as how this was a legal
> approval, I was wondering what other steps need to be done, if any, to make
> this open to others.
> >>>
> >>> John
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> >> For additional commands, e-mail: legal-discuss-help@apache.org
> >>
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > Apache Taverna (incubating), Apache Commons
> > http://orcid.org/0000-0001-9842-9718
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > For additional commands, e-mail: legal-discuss-help@apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
Re: Resolution on Github Issues
Posted by Jim Jagielski <ji...@jaguNET.com>.
Recall that issue trackers have not been, traditionally, held under
the requirement of being under ASF infra nor infra control. If people
wish to use external, 3rd party issue/bug trackers, they are taking
on the risks themselves, as far as SLAs, historical access, etc...
> On Jun 27, 2016, at 6:10 AM, Stian Soiland-Reyes <st...@apache.org> wrote:
>
> I think John is talking about
> https://github.com/apache/incubator-ponymail/issues used instead of
> ASF-hosted Jira/Bugzilla - source code is still maintained
> git.apache.org as the main repository, with just mirroring to GitHub
> and the usual Pull Request notifications.
>
>
> The GitHub Issues of Ponymail are mirrored to
> https://lists.apache.org/list.html?dev@ponymail.apache.org but you
> would have to use GH infrastructure to manage the issues (e.g.
> new/assign/close).
>
> See legal discussion on
> https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
> contribute" should be covered - so legally it's "OK".
>
>
> But then the question is if other ASF projects can also choose to use
> GitHub Issues for their issue tracking.
>
>
> I think this raises wider questions for policy and community and
> should be discussed on general@incubator and/or community@apache
> rather than at legal-discuss.
>
> On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com> wrote:
>> I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF’s git or svn repositories.
>>
>> Ralph
>>
>>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
>>>
>>> All,
>>>
>>> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
>>>
>>> John
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons
> http://orcid.org/0000-0001-9842-9718
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Resolution on Github Issues
Posted by Stian Soiland-Reyes <st...@apache.org>.
I think John is talking about
https://github.com/apache/incubator-ponymail/issues used instead of
ASF-hosted Jira/Bugzilla - source code is still maintained
git.apache.org as the main repository, with just mirroring to GitHub
and the usual Pull Request notifications.
The GitHub Issues of Ponymail are mirrored to
https://lists.apache.org/list.html?dev@ponymail.apache.org but you
would have to use GH infrastructure to manage the issues (e.g.
new/assign/close).
See legal discussion on
https://issues.apache.org/jira/browse/LEGAL-249 - the "intention to
contribute" should be covered - so legally it's "OK".
But then the question is if other ASF projects can also choose to use
GitHub Issues for their issue tracking.
I think this raises wider questions for policy and community and
should be discussed on general@incubator and/or community@apache
rather than at legal-discuss.
On 26 June 2016 at 19:51, Ralph Goers <ra...@dslextreme.com> wrote:
> I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF’s git or svn repositories.
>
> Ralph
>
>> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
>>
>> All,
>>
>> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
>>
>> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/0000-0001-9842-9718
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Resolution on Github Issues
Posted by Ralph Goers <ra...@dslextreme.com>.
I am sure Jim can speak for himself, but given the recent discussions I have been watching Github has not been approved to replace the ASF’s git or svn repositories.
Ralph
> On Jun 25, 2016, at 4:27 AM, John D. Ament <jo...@apache.org> wrote:
>
> All,
>
> In talking with the PonyMail podling, I was informed that VP Legal approved using GIthub Issues for projects. Seeing as how this was a legal approval, I was wondering what other steps need to be done, if any, to make this open to others.
>
> John
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org