Hi Turbine developers,

as Turbine and Fulcrum projects are now mostly with Git and synced in 
GitHub, PRs are enabled by default and we may encounter more code patches 
this way now than before. 

How should we handle it? IMO as we're not a very big project, I'd suggest 
that any committer or PMC member could merge the PR, but she/he should 
leave a short comment and after that, 
if nobody from PMC or any committer does complain within a certain time, I 
would say about 24 to 48 hours, it could/will be merged. 

Of course, this "decision" is just a best-case statement - hopefully not 
resulting in more work to do, e.g to fix unexpected code incomings. 

But I think most of the time PRs are valuable, if not important and an 
excellent communication channel ! 

We could go even one step further to consider inviting any person, who has 
been the author of a merged PR, to become a committer - ?!

Best regards, Georg

P.S. It may be, that there already a project or an Apache rule exists, but 
I am not aware of it - ..?

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to