Hey Gilles, Having been thinking about these sorts of ideas considerably in my day job, it might be worth considering adding some status checks for formatting. These aren’t too difficult to implement, but do require some mechanics.
Its mainly having github POST to some configured url, and having some flavor of script run and POST several varieties of statuses back to the git commit hash. Further, the public github has the mechanics in place to provide a pull request template that provides some assistance with this formatting. > On Apr 8, 2016, at 10:18 AM, Gilles <gil...@harfang.homelinux.org> wrote: > > Hello. > > Struggling with how to share non-committer contributions: > https://issues.apache.org/jira/browse/MATH-1290 > > At some point, we should have a paragraph in > doc/development/development.howto.txt I would suggest using a CONTRIBUTING.md at the root of the project, as this seems to be a de facto standard for github projects, simply for the ease of creating a nicely formatted page which is versionable along with the code. All the best, -Rob > that would explain which steps the contributor and committer must > follow (i.e. one, simple, fool-proof, way) in order to, respectively, > create and merge a pull request. > > > Thanks, > Gilles > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
