That all makes perfect sense to me, Ken. Thanks for the update.
-Steve
> -Original Message-
> From: Ken Giusti [mailto:kgiu...@redhat.com]
> Sent: Thursday, December 10, 2009 10:39 AM
> To: dev@qpid.apache.org
> Subject: Re: [QMF] public github repo for QMFv2 api work
&g
Hi all - thanks for all the feedback.
I didn't explain my main motivation for setting up the github repo: backups. I
wanted some safe place to put the code in case my dog eats my laptop (again).
Getting scm functionality, and doing it all in the open in a way that people
can easily play with
On Wed, 2009-12-09 at 20:25 +, Robert Greig wrote:
> > I think the safest option is to expose your work through a series of JIRA's.
> > If we need to make the code available immediately and/or collaborate
> > with others we could create a branch.
> > You could work off the branch and then Ted c
Robert Greig wrote:
2009/12/9 Carl Trieloff :
In the ASF, unfortunately to give commit rights to anything we need to get
through the
committer nomination and vote process.
Do you (or anyone else) know what the rationale for this is?
Main thing is infra does not want to deal with hig
inal Message-
> From: Robert Greig [mailto:robert.j.gr...@gmail.com]
> Sent: 09 December 2009 20:25
> To: dev@qpid.apache.org
> Subject: Re: [QMF] public github repo for QMFv2 api work
>
> Is it not possible for us to create a branch and give Ken commit
> rights *only* to the branch? As long
> -Original Message-
> From: Robert Greig [mailto:robert.j.gr...@gmail.com]
> Sent: Wednesday, December 09, 2009 3:25 PM
> To: dev@qpid.apache.org
> Subject: Re: [QMF] public github repo for QMFv2 api work
>
>
> > I think the safest option is to expose your
2009/12/9 Carl Trieloff :
> In the ASF, unfortunately to give commit rights to anything we need to get
> through the
> committer nomination and vote process.
Do you (or anyone else) know what the rationale for this is?
Thanks,
Robert
-
Robert Greig wrote:
I think the safest option is to expose your work through a series of JIRA's.
If we need to make the code available immediately and/or collaborate
with others we could create a branch.
You could work off the branch and then Ted could apply the patches as
an when they are made a
> I think the safest option is to expose your work through a series of JIRA's.
> If we need to make the code available immediately and/or collaborate
> with others we could create a branch.
> You could work off the branch and then Ted could apply the patches as
> an when they are made available.
I
Ken I appreciate your effort in making the development process as open
as possible.
But I agree with Steve about the licensing issues.
I think the safest option is to expose your work through a series of JIRA's.
If we need to make the code available immediately and/or collaborate
with others we co
Hi Ken,
> -Original Message-
> From: Ken Giusti [mailto:kgiu...@redhat.com]
> Sent: Wednesday, December 09, 2009 9:00 AM
> To: dev
> Subject: [QMF] public github repo for QMFv2 api work
>
>
> Hi all,
>
> Just fyi - I've set up a public git repo at github so I can
> develop the QMFv2 A
11 matches
Mail list logo
