I think JIRA/Github are suitable candidates.
It will require to decide on some way to tag these items so a convenient
filter can produce the desired list (otherwise it will be hidden between
lots of JIRAs and no use for anyone)

What I personally like about the Wiki option, is that maintaining my list
of items will involve only a single page (no mouse clicks); in contrast to
JIRA where I'll need to create items and maintain each item in a separate
page (many mouse clicks). I'm also more of a list-of-open-bullets guy than
a table-with-fixed-columns guy when it comes to viewing information.

On the other hand JIRA gives more power when it comes to stuff like
order-by filter-by and etc.

Ultimately, it's a question of which tool most people imagine will be
convenient for them to update and view.

On Thu, May 25, 2017 at 7:02 PM, Dave Neuman <[email protected]> wrote:

> I am probably opening a can of worms that I don't know if I want to open,
> but can't we just use Jira for this (and Github once we move there)?  If
> someone is working on something it should be in Jira as an issue that
> assigned to that person.  From there you can see who is working on what.
> It's not going to be perfect, and everything is not always going to be in
> there, but it should be good enough IMO.  I think that would be a better
> solution than relying on people to keep a wiki up to date.
>
> On Thu, May 25, 2017 at 9:54 AM, Durfey, Ryan <[email protected]>
> wrote:
>
> > I am +1 on this.  This dovetails well with the idea of a high-level
> > roadmap illustrating active areas of work.
> >
> > I am open to ideas on what tool to use.  I agree with Shmulik we could
> > make this work in the wiki if needed.
> >
> > Ryan Durfey    M | 303-524-5099
> > CDN Support (24x7): 866-405-2993 or [email protected]<mailto:
> > [email protected]>
> >
> >
> > From: Shmulik Asafi <[email protected]>
> > Reply-To: "[email protected]" <
> > [email protected]>
> > Date: Wednesday, May 24, 2017 at 11:54 PM
> > To: "[email protected]" <
> > [email protected]>
> > Subject: TC Contributers to Publish list of Planned/WIP Items for Better
> > Community Sync
> >
> > Hi All,
> >
> > During the summit I've suggested to a few people that maybe each TC
> > contributer should publish a list of the items she's working on presently
> > and planning to work on in the near future.
> >
> > The goal is to share what "major stuff" is going to happen in the project
> > (e.g. Jeff's work on Localized/Edge Traffic Routing; Derek's work on
> > Delivery Service configuration; Dave/Matt's work on Lua scripts; etc.).
> >
> > I think this is very little effort by each contributer and will allow us
> to
> > be much more synced, make it possible to engage with existing efforts and
> > provide a platform to detect conflicting/duplicated efforts. I also think
> > this can be a first baby step towards building a roadmap in the long
> term.
> >
> > The few people I talked with seemed open to this idea. I hope others will
> > feel the same.
> >
> > I think Wiki pages is the best place for this, but it can also be in
> > JIRA/Git, or whatever appropriate tools Apache provides (it would also be
> > cool if we could make RSS feed no changes).
> >
> > What do you think?
> >
> > If all support, I'd be happy to create the "framework" for this in
> whatever
> > tool we choose.
> >
> > Thanks!
> >
> > --
> > *Shmulik Asafi*
> > Qwilt | Work: +972-72-2221692 <+972%2072-222-1692>| Mobile:
> > +972-54-6581595
> > <+972%2054-658-1595>| [email protected]<mailto:[email protected]> <
> > [email protected]<mailto:[email protected]>>
> >
> >
>



-- 
*Shmulik Asafi*
Qwilt | Work: +972-72-2221692| Mobile: +972-54-6581595| [email protected]
<[email protected]>

Reply via email to