I guess so, this ("documenting how to contribute") has been raised up once
or twice already but until now there have been no "fixed rules".
On Friday, September 27, 2013 8:58:40 PM UTC+2, Michele Comitini wrote:
>
> Massimo, Niphlod
> can we add those instructions to the book? A chapter "Contributing to
> web2py" can be helpful, don't you think?
>
>
>
> 2013/9/27 Niphlod <[email protected] <javascript:>>
>
>> in addition to joining the developers group, there are some (absolutely
>> not required, but good to have) main ideas to follow (it's how currently
>> most of contributors are dealing with PR):
>> - github is preferred for their PR system
>> - make your patch on a topic branch against current master trunk
>> - it should be a patch that can be fast-forwarded (i.e. merged
>> automatically in current master)
>> - composed of a single commit (unless the patch is long and needs
>> specific commit "comments" to track it later)
>> - commit message **should** include a "thanks to @someone" if it was
>> someone else that pointed out the bug or raised the request for the feature
>> - if the commit contains a new feature it should come with the relative
>> tests (unittest in gluon/tests)
>>
>> I have another one, but it seems that I'm the only one (would be good if
>> we agree on something consistent):
>> - every bug-fixing commit should come from a branch named
>> "issue/number_of_the_issue_on_google_code" (like issue/1684)
>> - every enhancement commit should come in a branch named
>> "enhancement/title_of_the_enhancement" (like enhancement/trapped_links)
>>
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
