flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject Re: [DISCUSS] How do we want to handle Whiteboard?
Date Mon, 08 Apr 2013 21:03:23 GMT
I would say, at the moment they want to contribute, it means they accept the 
contributor license agreement, maybe indicating it in the README would be 
sufficient but I'm not sure.

-Fred

-----Message d'origine----- 
From: Om
Sent: Monday, April 08, 2013 10:31 PM
To: Alex Harui
Cc: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?

On Apr 8, 2013 12:00 PM, "Alex Harui" <aharui@adobe.com> wrote:
>
> I'm ok with a couple of folks trying it in order to see if it can satisfy
everyone and Apache.
>
> I'm not sure we need a gate but maybe I'm missing something.
>
>

I meant the contributor licence agreement.  How do we do this for JIRA
patches today?  Is it an implicit agreement?  I am wondering if adding a
note in the main Github page would be sufficient?

Thanks,
Om

>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Om <bigosmallm@gmail.com> wrote:
>
>
> On Mon, Apr 8, 2013 at 11:30 AM, Frédéric THOMAS <webdoublefx@hotmail.com
>wrote:
>
> > Hi Om,
> >
> > Actually, that seems good.
> >
> > I just wonder if it will be possible to configure the email to send
> > directly in the commit@f.a.o
> >
> > So, it would mean you would open this account, give us the password and
> > then we would add our rsa and  finally each one can create it's repo ?
> >
> > -Fred
> >
> >
> The way I would do it is to create an Organization account on GitHub,
share
> the login details with private@flex.apache.org.   Then, any committer who
> wants to create a whiteboard can send an email on private@flex.a.o.  We
add
> the committer's github id as part of our organization account.  We both
can
> perhaps play with the settings to see how best we can get this done.
>
> And another thing I want to try to do is to put a Apache V2 licencse
> agreement gate before someone can send a 'Pull request' to an official
> whiteboard github project.  I am not sure if GitHub supports such
> functionality, but given their support for third-party APIs, I imagine we
> can write a script for this ourselves.
>
> Thanks,
> Om
>
>
> > -----Message d'origine----- From: Om
> > Sent: Monday, April 08, 2013 8:13 PM
> > To: dev@flex.apache.org
> > Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
> >
> >
> > Maybe we can try the whiteboard@github option for a few months and see
how
> > it works out?  Like the move from SVN to Git, there are always going to
be
> > some issues and we cannot think of all of them upfront and have
> > documentation ready.  The only way to find out of this will work is to
just
> > do it and squash issues as they come along.  We timecap the effort and
see
> > if we can solve issues to the satisfaction of the PMC, Infra, etc.
> >
> > I think a poll/vote would be more useful at the end of the experiment,
not
> > before.  We dont want another round of
> > "github-supporters-need-to-**answer-this-question-**immediately" after
we
> > decide to use github and start facing issues.
> >
> > Thanks,
> > Om
> >
> > On Mon, Apr 8, 2013 at 11:00 AM, Om <bigosmallm@gmail.com> wrote:
> >
> >
> >>
> >> On Mon, Apr 8, 2013 at 10:47 AM, Alex Harui <aharui@adobe.com> wrote:
> >>
> >>
> >>>
> >>>
> >>> On 4/8/13 9:49 AM, "Michael A. Labriola" <labriola@digitalprimates.net
>
> >>> wrote:
> >>>
> >>> >> I don't think it would be possible to use github for the "official"
> >>> >> whiteboards as it brings up a number of issues for infra and the
ASF
> >>> >> ie knowing who contributed, licensing issues etc etc basically
the
> >>> >> normal issues for bit of donated code.
> >>> >>
> >>> >
> >>> > Ultimately I think github is the way to go. If that can't work, the
> >>> other
> >>> > choice is for infra to create a repo per committer (github model).
>
> >>> Git's
> >>> > strength is that of a distributed version control system. We keep
> >>> trying to
> >>> > centralize it. The whiteboard don't belong in the same repo as the
core
> >>> code
> >>> > in the git model IMO.
> >>> >
> >>> > Regarding official whiteboards and github, its interesting. In some
> >>> ways, IMO,
> >>> > it's better for the ASF. In this way nothing enters an ASF repo
until
> >>> > it
> >>> > officially becomes part of the project and its better for me as I
can
> >>> quickly
> >>> > play and just commit code without worrying about headers, etc. Then
we
> >>> deal
> >>> > with those things prior to an import.
> >>> >
> >>> > Mike
> >>> >
> >>> I think Greg's point about working in the "open" is the critical
factor.
> >>> How can we find out what other committers are doing if we use GitHub?
Can
> >>> we get change notifications on the dev list?
> >>>
> >>>
> >> GitHub supports organizations (free for open source orgs) using which
we
> >> can configure notifications to be sent to any email alias/list we
choose.
> >>
> >>
> >>
> >>> Otherwise, I think the boundary is at the committer/non-committer
level.
> >>>  As
> >>> a committer you will be working in Git on an Apache Server and you
should
> >>> always be careful about what you are doing, if you are not a
committer,
> >>> you
> >>> can work with the Git mirrors and do whatever you want and generate a
> >>> pull
> >>> request and then a committer has to review.
> >>>
> >>
> >>
> >>
> >>
> >>
> > 


Mime
View raw message