Re: [Savannah-hackers-public] Code of conduct

[Sylvain Beucler]

Hey,

On Tue, Apr 20, 2010 at 11:47:45PM +0200, Alex Fernandez wrote:
> Hi Sylvain,
> 
> On Tue, Apr 20, 2010 at 1:56 AM, Sylvain Beucler <address@hidden> wrote:
> > As you may have seen, I wrote a "code of conduct" for Savannah
> > Hackers.
> 
> Thanks to your advice, I am wearing my new @gnu.org address for this
> mail. I will try to remember to use it for official communications.
> 
> > http://savannah.gnu.org/maintenance/CodeOfConduct
> >
> > It includes a rationale about why it's interesting to have such a
> > document.
> >
> > What do you think?
> 
> It is great, and very nicely expressed. There are a couple of
> additional points I have been thinking of:
> 
> * We are here to solve problems, not to create or magnify them, and to
> help people. Any compliance issues that we encounter need to be solved
> in the way that best benefits both parties.
> 
> * As a corollary, admin privileges should only be used to solve
> project problems at the request of developers.

This sounds like re-explaining the last point.  I think it's better
to improve it rather than adding separate points.


> * If you force the situation (for example threatening the project with
> removal) you are incorporating two new outcomes into the picture: that
> project maintainers decide to leave, or that you have to shut down the
> project. In both cases everyone loses: the project loses an excellent
> host, the developers will likely reject anything that comes from
> @gnu.org from now on, and Savannah loses a project.
> 
> Feel free to add them, rephrase them or ignore them. I don't want to
> preach as I have not been here long and all of you know more about
> admin'ing than I do, but I do think that keeping these two points in
> mind can be helpful. They have been useful to me in my day job :D

I'd like to avoid a page bloat, so it gives the general points (not
too specific) and is quick to read.

Try to keep this in mind if you modify the page, otherwise there may
be additional advices for project reviews on the related wiki pages.

-- 
Sylvain