Re: [Math] Feature development model: pull request?

2016-04-11 Thread Gilles
Hello. On Mon, 11 Apr 2016 08:04:54 -0400, Rob Tompkins wrote: All, I was thinking about this some over the weekend. How many of the contributors (those without commit access to the apache repository), do you think, will be accessing and submitting code via GitHub pull request? I ask because

Re: [Math] Feature development model: pull request?

2016-04-11 Thread Rob Tompkins
All, I was thinking about this some over the weekend. How many of the contributors (those without commit access to the apache repository), do you think, will be accessing and submitting code via GitHub pull request? I ask because GitHub offers a template mechanism for pull requests.

Re: [Math] Feature development model: pull request?

2016-04-08 Thread Gilles
On Fri, 08 Apr 2016 16:18:25 +0200, Gilles 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 that would explain which steps the

Re: [Math] Feature development model: pull request?

2016-04-08 Thread Gilles
Hi. I'm not fluent enough in "git" and never used "Github", so most of what you write below is not at all clear to me. Also, I'm not sure that we talk from the same basis. Just to be sure: Commons Math is not hosted at "Github"; the "Github" site is merely a "one-way" mirror. Committers must

Re: [Math] Feature development model: pull request?

2016-04-08 Thread Rob Tompkins
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

[Math] Feature development model: pull request?

2016-04-08 Thread Gilles
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 that would explain which steps the contributor and committer must follow (i.e. one, simple,