commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From __matthewHawthorne <>
Subject Re: [vsf] sandbox etiquette
Date Wed, 26 Nov 2003 21:37:56 GMT
I was in a similar situation a few weeks ago with [sql].

Here's some words of wisdom from

"The right thing to do is to ask on the list or talk to the owners of 
the component (see the STATUS file) before diving in. The owners may not 
be still subscribed to the commons-dev list and so you might need to 
contact them directly."

After that, if you don't hear any responses, I would imagine that you 
could go ahead start working on it.  You may want to check the Gump 
stats to see what other projects depend on it, depending on the type of 
changes you are making.

Anyone else been in this situation?  It's undesirable to step on 
someone's toes, but even less desirable to let good projects die...

Gary Gregory wrote:
> Hello,
> I know the sandbox is "open" to all Commons committer (I am one [lang],
> [codec]) but I'd like to know if there is any etiquette as to committing to
> a specific sandbox  project, in this case, I want to fix a bug in VFS and
> perhaps update build.xml.
> ?
> Thanks,
> Gary

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message