hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suraj Menon <surajsme...@apache.org>
Subject Re: [DISCUSS] Community Policies to prevent conflicts
Date Fri, 15 Mar 2013 15:49:45 GMT
+1 Thank you for the information Edward and we start afresh. I think things
should be lot simpler within a small team like ours. I am touching on
topics related to code and commit protocol here.

We are trying to get a resolution on three points and the voting could be
done in appropriate channel. Let me know if this is the correct place to do
the votings.
- Voting for/against "Review then commit" policy
- Voting for an appropriate time window that a committer can assume silence
as a +1 on his patch.
- Voting for whether a commit should reflect documentation on Wiki.


On Fri, Mar 15, 2013 at 12:08 AM, Edward J. Yoon <edwardyoon@apache.org>wrote:

> Hey all,
> We are seeing some conflicts between committers (especially me and
> Thomas?) and a growing number of somewhat arrogant, self-centred
> actions. However, I believe that all began with misunderstandings,
> misreadings, and insufficient discussions, (we didn't mean it). Let's
> don't argue anymore since everyone has different sides.
> Here's my suggestions:
> 1. The RoadMap should be discussed on dev@ and all decisions should be
> described on Wiki[1].
> 2. Observance of HowToCommit[2] is required of every committers.
> We might want to edit some plans/policies of RoadMap and HowToCommit.
> Please feel free to edit them.
> And, 3. Discussion in very polite terms.
> My only worry is whether we can be able to follow HowToCommit process
> everytime. As you know we're only have 3 active committers (= PMCs).
> Any other ideas?
> 1. http://wiki.apache.org/hama/RoadMap
> 2. http://wiki.apache.org/hama/HowToCommit
> --
> Best Regards, Edward J. Yoon
> @eddieyoon

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message