Re: [soa-pmc] Approval: Usage of GitHub

[Oliver Kopp <kopp.dev@xxxxxxxxx>]

Dear Adrian,

I'm closely following
https://bugs.eclipse.org/bugs/show_bug.cgi?id=481771 and the
discussion going on at "eclipse.org-project-leadership", subject "Use
of GitHub Issues by Eclipse Projects". Julien Ponge summarized the
arguments for GitHub Issues pretty well. Also the mail by Mickael
Istria (GitHub culture) offers a good thought!

The usage of GitHub issues has been approved by the Board meeting
beginning of November. And it seems to be allowed that "projects [...]
host their day-to-day development at GitHub". However, the concrete
process is currently unclear to me. What I got from the emails is that
I have to ask my PMC and then move forward.

I am  not aware of a list of projects using GitHub, but
https://projects.eclipse.org/projects/technology.golo is heading for
it (GitHub issues) and Jetty seems to head forward to it
(http://www.eclipse.org/jetty/documentation/current/contributing-patches.html
-> Contributing via GitHub PullRequests).

On the one hand, I am very well aware that Eclipse will last longer
than GitHub and thus durability is a very valuable good (Mike:
"preserve freedom of action"). On the other hand, GitHub is used by
many projects and it's easy and known to developers. Although Bugzilla
will be developed further, I really like the GitHub worklfow (PRs;
especially easy reviewing of contributions) more than the gerrit or
bugzilla one.

With the main source of information being GitHub, I hope to attract
more contributors to Winery.

BTW: I also read about the "CLA check hook" and have to investigate
that further.

Cheers,

Oliver

2016-01-05 9:41 GMT+01:00 Mos, Adrian <adrian.mos@xxxxxxxxxxxxxx>:
> Hi Oliver,
>
> Happy New Year. Sorry for the slow reply, I was away on holidays. I think
> it¹s fine to use Github for issue tracking but I admit I¹m not sure about
> the restŠ
> Can you explain why you would like to use GitHub for everything else? Is
> it because you want to give access to external committers that are not
> part of Eclipse? Is it for visibility?
>
> I¹m adding Wayne to the discussion as he¹s much more knowledgeable about
> the Eclipse regulations, in case he wants to add something.
>
> Thanks,
> Adrian.
>
> On 22/12/15 11:36, "soa-pmc-bounces@xxxxxxxxxxx on behalf of Oliver Kopp"
> <soa-pmc-bounces@xxxxxxxxxxx on behalf of kopp.dev@xxxxxxxxx> wrote:
>
>>Dear PMC,
>>
>>2015 ends and Winery is getting traction again.
>>
>>I would like to use GitHub for Winery development. As far as I
>>understood the discussion on "eclipse.org-project-leadership", I have
>>to get PMC approval for using GitHub issues instead of BugZilla
>>issues. Therefore:
>>
>>Question A: Dear PMC, May I use GitHub issues for Winery? I know that
>>I have to clarify the details with EMO.
>>
>>
>>In case, I discover the other processes to file appropriate requests,
>>I'm also seeking approval for
>> * releases
>> * wiki
>> * git repository
>> * pull requests
>>
>>Therefore,
>>
>>Question B: Dear PMC, May I use a GitHub git repository as primary git
>>repository for Winery? I know that I have to clarify the details with
>>EMO.
>>
>>The concrete repository is not yet fixed. I have to clarify whether
>>https://github.com/winery/winery/ is OK or if I have to move to
>>https://github.com/eclipse/winery/
>>
>>
>>Question C: Dear PMC, May I use a GitHub wiki associated with a GitHub
>>git repository (see Question B) as Wiki for Winery? I know that I have
>>to clarify the details with EMO.
>>
>>Question D: Dear PMC, May I use the GitHub releases (at the repo
>>approved at Question B) to do releases for Winery? I know that I have
>>to clarify the details with EMO.
>>
>>Question E: Dear PMC, May I use GitHub's pull requests for Winery? I
>>know that I have to clarify the details with EMO.
>>
>>
>>Cheers,
>>
>>Oliver
>>_______________________________________________
>>soa-pmc mailing list
>>soa-pmc@xxxxxxxxxxx
>>To change your delivery options, retrieve your password, or unsubscribe
>>from this list, visit
>>https://dev.eclipse.org/mailman/listinfo/soa-pmc
>
> _______________________________________________
> soa-pmc mailing list
> soa-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/soa-pmc