> I like GitHub for it's good community integration - just mention somebody or link it in another issue/PR and everything will automatically be referenced; pretty neat. Take a look at https://issues.apache.org/jira/projects/SPARK/issues/SPARK-14220?filter=allopenissues
BTW Spark is also "complex" multi-language project. They also had problems with long running builds and test jobs On Mon, Jun 11, 2018 at 5:23 PM, Marco de Abreu < marco.g.ab...@googlemail.com> wrote: > Thanks for this detailed description! > > I think GitHub and JIRA are a good thing to co-exist. GitHub for issues and > JIRA for action items (as a result of the issues). I like GitHub for it's > good community integration - just mention somebody or link it in another > issue/PR and everything will automatically be referenced; pretty neat. > > How about you set up a personal instance of JIRA (let us know if the public > ones differ too much from the one we're running under Apache) and play > around a bit? We can then review the setup and migrate the necessary > changes after everything looks good. But sure, if anybody at @dev has > further experience, I'd love to see them involved. > > -Marco > > On Mon, Jun 11, 2018 at 7:22 AM Yasser Zamani <yasserzam...@apache.org> > wrote: > > > > > > > On 6/11/2018 6:32 PM, Sebastian wrote: > > > Looks like they also don't handle the committer nomination process > > > correctly ... > > > > > > "If you are interested in becoming a Weex committer, contact any > > > existing committer and we will help you go through the invitation > > process." > > > > Yes you're absolutely right. Contributors wouldn't ask for this, > > instead, they will be nominated. In some cases like this [1] we're > > better than Weex :) > > > > [1] https://cwiki.apache.org/confluence/display/MXNET/ > Becoming+a+Committer > > >
