[SANDBOX] policy question (was Re: [VFS][PATCH] make it compile)

[Stefan Bodewig <bo...@apache.org>]

Hi all,

since I have karma for the sandbox, I could easily apply the patch
myself.  On the other hand I do not plan to get involved with VFS
beyond making it compile right now, so it feel wrong to add myself to
the status file and commit away.

Should I commit it without adding myself to the status file or should
I simply wait until the patch gets applied by one of the people listed
there?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [SANDBOX] policy question

[Stefan Bodewig <bo...@apache.org>]

On Tue, 2 Mar 2004, Henri Yandell <ba...@generationjava.com> wrote:

> I don't bother to add to the status file as I consider this kind of
> thing to be Commons development and not VFS specific stuff.

OK, thanks to you three.  I've committed the patch.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [SANDBOX] policy question (was Re: [VFS][PATCH] make it compile)

[Tim O'Brien <to...@discursive.com>]

On Tue, 2 Mar 2004, Henri Yandell wrote:
> I don't bother to add to the status file as I consider this kind of thing
> to be Commons development and not VFS specific stuff.
> 
> It's a bit rude of me, but no one has complained at me yet for barging
> into their project to fix some typo or move docs around.

I don't consider that rude at all - I consider that right.

Too much "turf" in the Commons - I think this is the main reason why 
projects stagnate.  People assume that "somebody else" is taking care of 
project X - I've found that they usually are not.

If there is a project with shotty documentation or typos, the expectation
should be that it can be fixed by *anyone* with commit rights.  Broken
windows should be fixed by whomever has the itch and the karma, if another
committer doesn't like a change then -1 it. 





---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [SANDBOX] policy question (was Re: [VFS][PATCH] make it compile)

[Henri Yandell <ba...@generationjava.com>]

I don't bother to add to the status file as I consider this kind of thing
to be Commons development and not VFS specific stuff.

It's a bit rude of me, but no one has complained at me yet for barging
into their project to fix some typo or move docs around.

Hen

On Tue, 2 Mar 2004, matthew.hawthorne wrote:

> Stefan Bodewig wrote:
> > since I have karma for the sandbox, I could easily apply the patch
> > myself.  On the other hand I do not plan to get involved with VFS
> > beyond making it compile right now, so it feel wrong to add myself to
> > the status file and commit away.
> >
> > Should I commit it without adding myself to the status file or should
> > I simply wait until the patch gets applied by one of the people listed
> > there?
>
>
> I say go ahead and commit.  Since this is a unique situation, adding
> yourself to the status file is probably still good practice, but not a
> necessity.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Re: [SANDBOX] policy question (was Re: [VFS][PATCH] make it compile)

["matthew.hawthorne" <ma...@apache.org>]

Stefan Bodewig wrote:
> since I have karma for the sandbox, I could easily apply the patch
> myself.  On the other hand I do not plan to get involved with VFS
> beyond making it compile right now, so it feel wrong to add myself to
> the status file and commit away.
> 
> Should I commit it without adding myself to the status file or should
> I simply wait until the patch gets applied by one of the people listed
> there?


I say go ahead and commit.  Since this is a unique situation, adding
yourself to the status file is probably still good practice, but not a 
necessity.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org