mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hen <bay...@apache.org>
Subject Re: [DISCUSSION] Initial draft for MXNet roadmap
Date Tue, 10 Jul 2018 20:51:57 GMT
Roadmaps are interesting in a project with a high level of commit-in-dayjob
employment.

Some opinions for my part:

* Roadmaps should be release and not time based. We might have an intent to
release every X months but the roadmap should still be focused on that
release rather than the X months.
** The exception is operational items. Fixing CI, updating website etc; for
these I would have an Operational section and indicate priority and/or
whether they affect release.
* Roadmaps should be wishlists. Items for the V.Next release would either
be Required or Nice to Have. Nice to Haves can (and should) be punted to
the next release by the RM if the Requireds are all resolved.
* Items can be identified as someone having an intent to work on. For
example, as Steffen manages various folk contributing to MXNet, I imagine
he has particular contributions he would like them to work on and is making
time available in the day for that to happen. Ideally the folk he manages
would note that they have the intent rather than it being a borglike
'Amazon' next to it.
** It's important to leave lots of open work, including small items.
** It's important not to continually punt Nice to Haves small items to the
next release. ie: At the start of the roadmap there are a bunch of newbie
items, and then as you get to release stage the existing committers take
care of a large chunk of newbie items.

My tuppence :)

Hen



On Wed, Jul 4, 2018 at 11:05 AM, Steffen Rochel <steffenrochel@gmail.com>
wrote:

> As a project contributor, I published an initial draft for MXNet roadmap
> at  https://cwiki.apache.org/confluence/display/MXNET/MXNet+Roadmap
> The initial draft is based on offline discussion with various contributors
> and committers including Mu, Junyuan and AWS developer community.
>
> Please review and suggest changes and enhancements.
> Please also review https://spark.apache.org/improvement-proposals.html and
> share your thoughts if the project should adopt a similar process or
> suggest something you think is more appropriate.
>
> Regards,
> Steffen
>

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