I'll reply here, Massimo can chime in and correct me at will. There are 2 main repo, one on google code, the other one in github. Massimo keep both in sync all times (a few glitches here and there pop up but those count as exceptions (e.g. at most once a month) and are fixed ASAP).
Until a few months back, if you wanted to contribute you'd pick the trunk version, do your own things and send a patch via email to Massimo. He applies those patches generally within a week (if not the same day). If you have an issue, you can as well open an issue on google code and attach a patch. Now that the github repo is being used for a while (and has CI hooked up) the best way is to fork the github trunk, open a feature branch on your repo, do your own things, possibly squelch commits messages, open a Pull Request and wait for it to be merged (here too, if not within the day, in a week at top). If they are ready to be merged (i.e. you make sure the patch can be merged as a fast-forward one) bonus points. If your PR includes tests (see gluon/tests) you get additional bonus points :-P. Then you maintain your own fork in sync with the "upstream master", think about another feature (or issue to be fixed), spawn another branch from master, and reopen another PR. If a guide is needed I can provide the steps to "be a good web2py contributor using git on github". Niphlod -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
