> > > > > - It should at least exist an additional field for the mail address. > Since > > > > we are (still) tied to google for authentication, you don't want > necessarily > > > > take the google registered address for the commit message. > > > > > > Use a google account for your preferred email address. I think it is > the > > > best way to do it as this will ensure we will have a valid address. > > > > I think this could be another quite substantial barrier for contribution > at all. > > Too bad for them. At some point, we must realize that people who are > nitpicking to contribute, are losing but not the project. If you can fix > an issue and you don't do it, it is bad for you not for us. > > its actually bad for both, because the issue remains unfixed and the issue is what is being remained... The current contribution process seems very intransparent and it is not easy to see which party allowed for which change and who actually merged it. please dont get me as a fashion victim, but i think here the role of the interface can not be overestimated...
> I found another point to add: > > > > - It should be able to work on a tree of repos (this being a feature of > the > > current setup and not being possible on github AFAIK). > http://git-scm.com/book/en/v2/Git-Tools-Submodules would this be an option? > > Such cases are for big changes (so out of cusual contributor) and we > already have a good workflow for that for the core developers. > > -- > Given the given example, "just a typo in a label", here, remains a wrong label, unless you do things like search in code on github: p.e.: https://github.com/tryton/trytond/search?utf8=%E2%9C%93&q=imprimer&type=Code which doesnt require for a core developer to waste valuable time... best regards, simon
