Commit Access

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

David E Jones


Ean Schuessler wrote:

> On Tuesday 11 September 2007 03:22:24 am David E Jones wrote:
>> Ummm... not sure where this idea came from...
>>
>> Neither "David" nor "Undersun" (now part of Hotwax Media) nor any other
>> person or organization are some central source of resources or driving
>> force for the project. OFBiz is overseen by a PMC (project management
>> committee) but everything that goes into OFBiz is contributed by users.
>>
>> So no, this would never work. There is no central organization to pull
>> stuff into the project, just users to push stuff into the project. That's
>> the WHOLE point of a community driven project that facilitates
>> collaboration.
>>
>> Of course, this is also impossible with current forks like opentaps and
>> Neogia because they specifically structure their licensing and copyright
>> ownership so that it is impossible to bring the contributions back into
>> OFBiz.
> [snip]
>> I don't think people understand just how incorrect and harmful to the
>> project this sort of thought is. If it isn't community driven people and
>> organizations won't be as interested in contributing and the whole project
>> will fall apart. It's a vicious and damaging lie! For anyone thinking this
>> please check your facts and motives!
>
> Don't be so defensive! There is a big difference between a vicious lie and a
> widespread misconception. Hotwax has more committers than anyone else so its
> easy to see why people might think something like this. If I was a
> dangerously motivated liar I would do more than simply state the obvious!
>
> Anyway, my main point was about the benefit of using a more modern and
> distributed source management system for things that aren't ready to go into
> SVN. Brainfood would rather make extensive changes to our local repository
> and pool them up into change sets that go to mainstream. Repeated merges
> where portions have been partially applied in multiple paths of development
> isn't a workflow that is well supported by SVN but is easy (or way easier,
> anyway) under GIT and Mercurial.
>
> ps. Check your facts and motives before calling someone a vicious, damaging
> liar.

Now who's being defensive? ;) And what I wrote wasn't even a reply to your email...

Whatever the case, I stated the lie and then said it was such, I wasn't quoting from anyone, though I think the reply was to Jonathon and we have a nice long history and being harsh with each other (again ;) ). It's great to have you around Jonathon, you bring up lots of good issues in these little high level threads.

There is some good stuff in what you're saying Ean, and I totally agree that different people and organizations will find different ways of collaborating with the community that works best for them. I'm just trying to describe and encourage (like in the contributors best practices page) the ones that seem to result in the most contributions coming into the project AND the most benefit and feedback going back to the contributor.

My perception is definitely limited though, and I know it very well, so for whatever anyone is doing if it's working well for you then there's no reason to change. If it's not working so well then I invite people to take a look at stuff that will help them, but that may not seem so obvious, and may in fact seem like a waste of time, and that is trying to get as much as possible into the open source project and collaborating with others in the community as you do so (well, that's the short/simple version, more verbose in the contributors best practices page).

-David

Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

Ean Schuessler
On Tuesday 11 September 2007 06:23:36 pm David E Jones wrote:

> Now who's being defensive? ;) And what I wrote wasn't even a reply to your
> email...
>
> Whatever the case, I stated the lie and then said it was such, I wasn't
> quoting from anyone, though I think the reply was to Jonathon and we have a
> nice long history and being harsh with each other (again ;) ). It's great
> to have you around Jonathon, you bring up lots of good issues in these
> little high level threads.
>
> There is some good stuff in what you're saying Ean, and I totally agree
> that different people and organizations will find different ways of
> collaborating with the community that works best for them. I'm just trying
> to describe and encourage (like in the contributors best practices page)
> the ones that seem to result in the most contributions coming into the
> project AND the most benefit and feedback going back to the contributor.
>
> My perception is definitely limited though, and I know it very well, so for
> whatever anyone is doing if it's working well for you then there's no
> reason to change. If it's not working so well then I invite people to take
> a look at stuff that will help them, but that may not seem so obvious, and
> may in fact seem like a waste of time, and that is trying to get as much as
> possible into the open source project and collaborating with others in the
> community as you do so (well, that's the short/simple version, more verbose
> in the contributors best practices page).

You know perfectly well that I can't resist toying with something as
incindiary as the phrase "a vicious damaging lie".  After all, Debian is my
alma mater. TINC!

--
Ean Schuessler, CTO
[hidden email]
214-720-0700 x 315
Brainfood, Inc.
http://www.brainfood.com
Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

David E Jones


Ean Schuessler wrote:

> On Tuesday 11 September 2007 06:23:36 pm David E Jones wrote:
>> Now who's being defensive? ;) And what I wrote wasn't even a reply to your
>> email...
>>
>> Whatever the case, I stated the lie and then said it was such, I wasn't
>> quoting from anyone, though I think the reply was to Jonathon and we have a
>> nice long history and being harsh with each other (again ;) ). It's great
>> to have you around Jonathon, you bring up lots of good issues in these
>> little high level threads.
>>
>> There is some good stuff in what you're saying Ean, and I totally agree
>> that different people and organizations will find different ways of
>> collaborating with the community that works best for them. I'm just trying
>> to describe and encourage (like in the contributors best practices page)
>> the ones that seem to result in the most contributions coming into the
>> project AND the most benefit and feedback going back to the contributor.
>>
>> My perception is definitely limited though, and I know it very well, so for
>> whatever anyone is doing if it's working well for you then there's no
>> reason to change. If it's not working so well then I invite people to take
>> a look at stuff that will help them, but that may not seem so obvious, and
>> may in fact seem like a waste of time, and that is trying to get as much as
>> possible into the open source project and collaborating with others in the
>> community as you do so (well, that's the short/simple version, more verbose
>> in the contributors best practices page).
>
> You know perfectly well that I can't resist toying with something as
> incindiary as the phrase "a vicious damaging lie".  After all, Debian is my
> alma mater. TINC!

:)

-David
Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

jonwimp
In reply to this post by David E Jones
 > Whatever the case, I stated the lie and then said it was such, I wasn't
 > quoting from anyone, though I think the reply was to Jonathon and we
 > have a nice long history and being harsh with each other (again ;) ).

Discussions! Those were discussions! We need brutally honest discussions. That, or we can dance
around in misunderstanding for years. I like drawing bee-lines towards absolutely clear
understanding (even if it means being stung big time), but that's just me.

 > It's great to have you around Jonathon, you bring up lots of good issues
 > in these little high level threads.

:) Not so great to have me around when I'm being slave-driven by a difficult employer, with no
room to stretch my legs and creativity.

Very OT here. Seems money and pride motives are strong divisive factors. We need more love going
around in the world. :) I'll stop short of discussing religion here.

Perhaps some day, none of us will need to work for a living. I believe that may drastically raise
productivity (and love)?

Jonathon

David E Jones wrote:

>
>
> Ean Schuessler wrote:
>> On Tuesday 11 September 2007 03:22:24 am David E Jones wrote:
>>> Ummm... not sure where this idea came from...
>>>
>>> Neither "David" nor "Undersun" (now part of Hotwax Media) nor any other
>>> person or organization are some central source of resources or driving
>>> force for the project. OFBiz is overseen by a PMC (project management
>>> committee) but everything that goes into OFBiz is contributed by users.
>>>
>>> So no, this would never work. There is no central organization to pull
>>> stuff into the project, just users to push stuff into the project.
>>> That's
>>> the WHOLE point of a community driven project that facilitates
>>> collaboration.
>>>
>>> Of course, this is also impossible with current forks like opentaps and
>>> Neogia because they specifically structure their licensing and copyright
>>> ownership so that it is impossible to bring the contributions back into
>>> OFBiz.
>> [snip]
>>> I don't think people understand just how incorrect and harmful to the
>>> project this sort of thought is. If it isn't community driven people and
>>> organizations won't be as interested in contributing and the whole
>>> project
>>> will fall apart. It's a vicious and damaging lie! For anyone thinking
>>> this
>>> please check your facts and motives!
>>
>> Don't be so defensive! There is a big difference between a vicious lie
>> and a widespread misconception. Hotwax has more committers than anyone
>> else so its easy to see why people might think something like this. If
>> I was a dangerously motivated liar I would do more than simply state
>> the obvious!
>>
>> Anyway, my main point was about the benefit of using a more modern and
>> distributed source management system for things that aren't ready to
>> go into SVN. Brainfood would rather make extensive changes to our
>> local repository and pool them up into change sets that go to
>> mainstream. Repeated merges where portions have been partially applied
>> in multiple paths of development isn't a workflow that is well
>> supported by SVN but is easy (or way easier, anyway) under GIT and
>> Mercurial.
>>
>> ps. Check your facts and motives before calling someone a vicious,
>> damaging liar.
>
> Now who's being defensive? ;) And what I wrote wasn't even a reply to
> your email...
>
> Whatever the case, I stated the lie and then said it was such, I wasn't
> quoting from anyone, though I think the reply was to Jonathon and we
> have a nice long history and being harsh with each other (again ;) ).
> It's great to have you around Jonathon, you bring up lots of good issues
> in these little high level threads.
>
> There is some good stuff in what you're saying Ean, and I totally agree
> that different people and organizations will find different ways of
> collaborating with the community that works best for them. I'm just
> trying to describe and encourage (like in the contributors best
> practices page) the ones that seem to result in the most contributions
> coming into the project AND the most benefit and feedback going back to
> the contributor.
>
> My perception is definitely limited though, and I know it very well, so
> for whatever anyone is doing if it's working well for you then there's
> no reason to change. If it's not working so well then I invite people to
> take a look at stuff that will help them, but that may not seem so
> obvious, and may in fact seem like a waste of time, and that is trying
> to get as much as possible into the open source project and
> collaborating with others in the community as you do so (well, that's
> the short/simple version, more verbose in the contributors best
> practices page).
>
> -David
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

Jacques Le Roux
Administrator
About GIT and other alike tools : I just want to remind people interested about legal issues when it comes to merge with Apache
trunk (yes it's not HotWax trunk, but I'm sure nobody overlooked that ;o). We had already some discussion last year. This link may
help http://www.nabble.com/forum/Search.jtp?local=y&forum=2740&query=%22joint+work%22. And I can provide you some more if you
want...

Maybe this  discussion is not closed ?

Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

Jacopo Cappellato
In reply to this post by Adrian Crum
Adrian,

the vote passed a few days ago and you should now have commit privileges
to the Webtools and Example components.

Jacopo

Adrian Crum wrote:

> Now that this thread has made the rounds for a few weeks, can we get
> back to the original subject? I need commit access to framework/webtools
> and framework/example. Please.
>
> :D
>
> -Adrian
>
> David E Jones wrote:
>
>>
>>
>> Ean Schuessler wrote:
>>
>>> On Monday 10 September 2007 07:23:36 pm David E Jones wrote:
>>>
>>>>> As a committer, I would like to do more to get the patches in Jira fed
>>>>> into the project - but there are only so many hours in the day. I know
>>>>> other committers are in the same position. Sometimes you just have
>>>>> to be
>>>>> patient.
>>>>
>>>> Be patient... or do something about it!
>>>>
>>>> Like Adrian did...
>>>
>>>
>>> I believe Adam had commit access at one time but no longer does. Do
>>> something about it!
>>>
>>> :-D
>>
>>
>> touché.
>>
>> It would be great to have Adam involved again, and his contributions
>> from before really made a difference.
>>
>> There is a bar to make it over for new committers and for previous
>> committers it would obviously be lower, but the same stuff applies in
>> general:
>>
>> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices
>> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities 
>>
>>
>> -David
>>


Reply | Threaded
Open this post in threaded view
|

Re: Commit Access

Adrian Crum
Thank you Jacopo!

Jacopo Cappellato wrote:

> Adrian,
>
> the vote passed a few days ago and you should now have commit privileges
> to the Webtools and Example components.
>
> Jacopo
>
> Adrian Crum wrote:
>
>> Now that this thread has made the rounds for a few weeks, can we get
>> back to the original subject? I need commit access to
>> framework/webtools and framework/example. Please.
>>
>> :D
>>
>> -Adrian
>>
>> David E Jones wrote:
>>
>>>
>>>
>>> Ean Schuessler wrote:
>>>
>>>> On Monday 10 September 2007 07:23:36 pm David E Jones wrote:
>>>>
>>>>>> As a committer, I would like to do more to get the patches in Jira
>>>>>> fed
>>>>>> into the project - but there are only so many hours in the day. I
>>>>>> know
>>>>>> other committers are in the same position. Sometimes you just have
>>>>>> to be
>>>>>> patient.
>>>>>
>>>>>
>>>>> Be patient... or do something about it!
>>>>>
>>>>> Like Adrian did...
>>>>
>>>>
>>>>
>>>> I believe Adam had commit access at one time but no longer does. Do
>>>> something about it!
>>>>
>>>> :-D
>>>
>>>
>>>
>>> touché.
>>>
>>> It would be great to have Adam involved again, and his contributions
>>> from before really made a difference.
>>>
>>> There is a bar to make it over for new committers and for previous
>>> committers it would obviously be lower, but the same stuff applies in
>>> general:
>>>
>>> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices
>>> http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities 
>>>
>>>
>>> -David
>>>
>
>
>

12