Typical in other projects is this: Code resides in Apache git There is a mirror in Github Issues are logged at https://issues.apache.org/jira/projects/CRAIL <https://issues.apache.org/jira/projects/CRAIL> Github has a facility for logging issues, but Apache projects do not use that facility. Contributors log a JIRA case, use the JIRA issue as the prefix for the commit comment, then make a pull request at https://github.com/apache/incubator-crail/pulls <https://github.com/apache/incubator-crail/pulls> Committers take those pull requests and commit them to ASF git with a comment “Close #NNN” to close the PR, where NNN is the number of the pull request Within a few seconds they appear in the Github mirror
The pull request is important. It indicates that the the contributor intends to contribute the IP, and owns the IP they are contributing. (Some projects attach patches to to JIRA cases, but in my opinion patches are harder to manage.) “How do I contribute to Crail?” is a very reasonable question. Can the Crail project decide a policy, and document it on (say) http://crail.incubator.apache.org/community/ <http://crail.incubator.apache.org/community/>. I have logged https://issues.apache.org/jira/browse/CRAIL-5 <https://issues.apache.org/jira/browse/CRAIL-5> for this. Julian > On Jan 29, 2018, at 3:33 AM, Animesh Trivedi <[email protected]> > wrote: > > Hi all, > > How we do manage external code contributions? Should we still be opening > pull requests and issues at https://github.com/apache/incubator-crail ? > > What is the accepted way for Apache projects? > -- > Animesh
