mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco de Abreu <>
Subject Re: Vote to stop using JIRA
Date Sun, 10 Jun 2018 00:23:06 GMT
Thanks a lot, this sounds like a good start. We definitely do not want to
re-invent the wheel - if there's some setup we can copy, I'd love to do
that as well!

Something we need is the possibility to have projects with subtasks and the
ability for any contributor (not committer) to contribute to these
projects. This could be adding tasks, changing the state of a task, maybe
even labelling and other things you usually do if you work on systems like
a Kanban-board. We want to give contributors the possibility to manage a
project entirely on their own without much involvement of committers.


On Sat, Jun 9, 2018 at 5:32 PM Yasser Zamani <>

> On 6/9/2018 5:01 PM, Marco de Abreu wrote:
> > Would you mind creating a proposal document at
> > [1], describing what you would have in mind and how project planning,
> > -management, development, planning, third-party-engagements and other
> > things you can think of would look like then?
> Yes of course. However, I think we don't have to reinvent the wheel. I'm
> almost sure there are projects in Apache (either incubating or not)
> which have similar general properties like MXNet. e.g. from Apache
> reports, we can see which incubating (or not) project has a lot of
> monthly revolutionary changes or issues while needs several different
> contribution expertise. Then I can see how they work :)
> At Apache we aren't alone. If we couldn't find any doc via above, then
> we have Apache Incubating Experts [1]. They're here and are experts for
> such situations. I can ask them for any clues.
> But firstly let list what are problems: (I added following which I think
> summarizes them via reading all of this thread)
> 1) It seems JIRA causes overhead works while makes it harder to new
> contributors to file an issue.
> 2) We don't have a document about how to manage a project using Apache
> INFRA with these properties: has a lot of monthly revolutionary changes
> and issues. needs several different contribution expertise e.g. C++,
> Scala, Python and etc. has a lot of concurrent committers working on
> different aspects and so may have no time to review others.
> contributions have different skill levels but their management is flat
> and not modular.
> @dev could you please update/delete or add to these if is needed? then
> when completed, I can research or discuss them with experts mentioned :)
> Thanks in advance!
> [1]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message