You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juneau.apache.org by James Bognar <ja...@salesforce.com> on 2016/06/28 13:47:14 UTC
Fwd: Juneau Project Bootstrap
My $.02.
Using GitHub Issues sounds appealing. But something feels strange about
using GitHub for bugs but not SCM.
I'm leaning slightly towards using GitHub Issues. GitHub seems to be
taking over the world. But I don't feel strongly about it since I'm really
unfamiliar with either right now. I'll be okay with whatever the community
decides.
---------- Forwarded message ----------
From: Stian Soiland-Reyes <st...@apache.org>
Date: Tue, Jun 28, 2016 at 9:05 AM
Subject: Re: Juneau Project Bootstrap
To: private@juneau.incubator.apache.org
Cc: Peter Haumer <ph...@us.ibm.com>, "craig.russell@oracle.com" <
craig.russell@oracle.com>, Craig Chaney <cc...@salesforce.com>, "John D.
Ament" <jo...@apache.org>, James Bognar <ja...@salesforce.com>,
david.goddard@uk.ibm.com, Brian Laskey <bl...@us.ibm.com>, Min Idzelis <
midzelis@salesforce.com>
Let's continue this discussion on dev@juneau.incubator.apache.org. (you can
sign up before you have signed ICLA and get @apache.org address)
On 28 Jun 2016 6:46 a.m., "Jochen Wiedmann" <jo...@gmail.com>
wrote:
>
>
> On Mon, Jun 27, 2016 at 10:45 PM, Peter Haumer <ph...@us.ibm.com> wrote:
>
>> Hello.
>> Speaking of tools, can we continue developing on GitHub and then push
>> commits over in batch to the Apache Git for releases?
>>
>> I see on the incubator page that there is an entry for using JIRA, which
>> is a commercially licensed product and a direct competitor to the product
>> in which this library was originally developed. Is using that really
>> required or can we continue with GitHub issues as well?
>>
>> AFAIK, Infra is still only supporting ASF Git as the primary repository,
> and Git as a mirror. I believe, this is, what John requested.
>
> I think, this means, that you will be required to download pull requests
> from GitHub as a file before applying them. However, that inconvenience
> should be acceptable, IMO.
>
> As an exception from that rule. I have read, just yesterday, that it
> should now be acceptable, if Juneau decides *not* to use the ASF Jira for
> bug reports, and use GitHub issues instead. My personal impression is, that
> this wouldn't really be an advantage, because tool support for Jira is much
> better than for Github. OTOH, GitHub might be more attractive for users.
>
> Again, John should be able to tell about details.
>
> Jochen
>
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
>
--
James Bognar
Re: Juneau Project Bootstrap
Posted by James Bognar <ja...@salesforce.com>.
Yea...I realized that as soon as I hit submit. Can't take back emails :-(
On Tue, Jun 28, 2016 at 11:34 AM, Jochen Wiedmann <jochen.wiedmann@gmail.com
> wrote:
> On Tue, Jun 28, 2016 at 3:51 PM, James Bognar
> <ja...@salesforce.com> wrote:
> > My vote:
> >
> > [0] - No preference either way.
>
>
> You should start the vote by a formal announcement. This is done by
> sending a mail with the subject "[VOTE] What it is about" to the
> dev@mailing list. Your announcement should contain, in particular
>
> a) The possible options.
> b) Which votes will are binding. (Usually, and in this case, all
> committers. The exception are release votes, where only PMC members
> have a binding vote.)
> c) Whether a quorum is required. (In the case of a release vote, three
> binding affirmative votes are required.)
> d) How long the vote is open.(Votes, that are incoming later on, may
> be discarded.)
>
> Jochen
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
--
James Bognar
Re: Juneau Project Bootstrap
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Jun 28, 2016 at 3:51 PM, James Bognar
<ja...@salesforce.com> wrote:
> My vote:
>
> [0] - No preference either way.
You should start the vote by a formal announcement. This is done by
sending a mail with the subject "[VOTE] What it is about" to the
dev@mailing list. Your announcement should contain, in particular
a) The possible options.
b) Which votes will are binding. (Usually, and in this case, all
committers. The exception are release votes, where only PMC members
have a binding vote.)
c) Whether a quorum is required. (In the case of a release vote, three
binding affirmative votes are required.)
d) How long the vote is open.(Votes, that are incoming later on, may
be discarded.)
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
Re: Juneau Project Bootstrap
Posted by James Bognar <ja...@salesforce.com>.
My vote:
[0] - No preference either way.
On Tue, Jun 28, 2016 at 9:50 AM, Jochen Wiedmann <jo...@gmail.com>
wrote:
> It's definitely a matter of preference. How about a vote?
>
>
> On Tue, Jun 28, 2016 at 3:47 PM, James Bognar
> <ja...@salesforce.com> wrote:
> > My $.02.
> >
> > Using GitHub Issues sounds appealing. But something feels strange about
> > using GitHub for bugs but not SCM.
> >
> > I'm leaning slightly towards using GitHub Issues. GitHub seems to be
> > taking over the world. But I don't feel strongly about it since I'm
> really
> > unfamiliar with either right now. I'll be okay with whatever the
> community
> > decides.
> >
> >
> > ---------- Forwarded message ----------
> > From: Stian Soiland-Reyes <st...@apache.org>
> > Date: Tue, Jun 28, 2016 at 9:05 AM
> > Subject: Re: Juneau Project Bootstrap
> > To: private@juneau.incubator.apache.org
> > Cc: Peter Haumer <ph...@us.ibm.com>, "craig.russell@oracle.com" <
> > craig.russell@oracle.com>, Craig Chaney <cc...@salesforce.com>, "John
> D.
> > Ament" <jo...@apache.org>, James Bognar <
> james.bognar@salesforce.com>,
> > david.goddard@uk.ibm.com, Brian Laskey <bl...@us.ibm.com>, Min
> Idzelis <
> > midzelis@salesforce.com>
> >
> >
> > Let's continue this discussion on dev@juneau.incubator.apache.org. (you
> can
> > sign up before you have signed ICLA and get @apache.org address)
> >
> > On 28 Jun 2016 6:46 a.m., "Jochen Wiedmann" <jo...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On Mon, Jun 27, 2016 at 10:45 PM, Peter Haumer <ph...@us.ibm.com>
> wrote:
> >>
> >>> Hello.
> >>> Speaking of tools, can we continue developing on GitHub and then push
> >>> commits over in batch to the Apache Git for releases?
> >>>
> >>> I see on the incubator page that there is an entry for using JIRA,
> which
> >>> is a commercially licensed product and a direct competitor to the
> product
> >>> in which this library was originally developed. Is using that really
> >>> required or can we continue with GitHub issues as well?
> >>>
> >>> AFAIK, Infra is still only supporting ASF Git as the primary
> repository,
> >> and Git as a mirror. I believe, this is, what John requested.
> >>
> >> I think, this means, that you will be required to download pull requests
> >> from GitHub as a file before applying them. However, that inconvenience
> >> should be acceptable, IMO.
> >>
> >> As an exception from that rule. I have read, just yesterday, that it
> >> should now be acceptable, if Juneau decides *not* to use the ASF Jira
> for
> >> bug reports, and use GitHub issues instead. My personal impression is,
> that
> >> this wouldn't really be an advantage, because tool support for Jira is
> much
> >> better than for Github. OTOH, GitHub might be more attractive for users.
> >>
> >> Again, John should be able to tell about details.
> >>
> >> Jochen
> >>
> >>
> >>
> >>
> >> --
> >> The next time you hear: "Don't reinvent the wheel!"
> >>
> >>
> >>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >>
> >>
> >
> >
> > --
> > James Bognar
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
--
James Bognar
Re: Juneau Project Bootstrap
Posted by Jochen Wiedmann <jo...@gmail.com>.
It's definitely a matter of preference. How about a vote?
On Tue, Jun 28, 2016 at 3:47 PM, James Bognar
<ja...@salesforce.com> wrote:
> My $.02.
>
> Using GitHub Issues sounds appealing. But something feels strange about
> using GitHub for bugs but not SCM.
>
> I'm leaning slightly towards using GitHub Issues. GitHub seems to be
> taking over the world. But I don't feel strongly about it since I'm really
> unfamiliar with either right now. I'll be okay with whatever the community
> decides.
>
>
> ---------- Forwarded message ----------
> From: Stian Soiland-Reyes <st...@apache.org>
> Date: Tue, Jun 28, 2016 at 9:05 AM
> Subject: Re: Juneau Project Bootstrap
> To: private@juneau.incubator.apache.org
> Cc: Peter Haumer <ph...@us.ibm.com>, "craig.russell@oracle.com" <
> craig.russell@oracle.com>, Craig Chaney <cc...@salesforce.com>, "John D.
> Ament" <jo...@apache.org>, James Bognar <ja...@salesforce.com>,
> david.goddard@uk.ibm.com, Brian Laskey <bl...@us.ibm.com>, Min Idzelis <
> midzelis@salesforce.com>
>
>
> Let's continue this discussion on dev@juneau.incubator.apache.org. (you can
> sign up before you have signed ICLA and get @apache.org address)
>
> On 28 Jun 2016 6:46 a.m., "Jochen Wiedmann" <jo...@gmail.com>
> wrote:
>
>>
>>
>> On Mon, Jun 27, 2016 at 10:45 PM, Peter Haumer <ph...@us.ibm.com> wrote:
>>
>>> Hello.
>>> Speaking of tools, can we continue developing on GitHub and then push
>>> commits over in batch to the Apache Git for releases?
>>>
>>> I see on the incubator page that there is an entry for using JIRA, which
>>> is a commercially licensed product and a direct competitor to the product
>>> in which this library was originally developed. Is using that really
>>> required or can we continue with GitHub issues as well?
>>>
>>> AFAIK, Infra is still only supporting ASF Git as the primary repository,
>> and Git as a mirror. I believe, this is, what John requested.
>>
>> I think, this means, that you will be required to download pull requests
>> from GitHub as a file before applying them. However, that inconvenience
>> should be acceptable, IMO.
>>
>> As an exception from that rule. I have read, just yesterday, that it
>> should now be acceptable, if Juneau decides *not* to use the ASF Jira for
>> bug reports, and use GitHub issues instead. My personal impression is, that
>> this wouldn't really be an advantage, because tool support for Jira is much
>> better than for Github. OTOH, GitHub might be more attractive for users.
>>
>> Again, John should be able to tell about details.
>>
>> Jochen
>>
>>
>>
>>
>> --
>> The next time you hear: "Don't reinvent the wheel!"
>>
>>
>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>>
>>
>
>
> --
> James Bognar
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg