2009/12/8 Rafael Schloming <[email protected]>

> A number of recent threads have made it clear that we have a fair amount of
> unspoken etiquette about how we do things around here, and the fact that it
> is unspoken can be confusing to newcomers and old-timers alike.
>
> Looking at a few other apache project web sites, they often seem to have a
> page or two devoted to documenting their project etiquette. I think this
> would be a good thing for us to have as well, and I've taken the liberty of
> trying to seed this effort with some content.
>
> I think there are some obvious places where it would make sense to
> formalize some of this etiquette into some lightweight process, e.g. having
> maintainers files in svn, having a sandbox for new code contributions, etc,
> however this text is *not* intended to be a proposal for that sort of thing,
> merely an attempt to put into words what I believe most of us consider to be
> the status quo wrt the unspoken etiquette of the project.
>
> Of course the problem with unspoken etiquette is that we might not all have
> the same concept of what it actually is, so please let me know if you
> disagree with something I've written or you think something important is
> missing.
>
> --Rafael
>

All this sounds very sensible to me; and there's nothing I can immediately
think of that I would like to add.

Having this on a "Getting Involved" section of the website, along, perhaps,
with a list of the "Big Ideas" people are currently working on would seem to
make a lot of sense...

-- Rob

Reply via email to