One bit I find hard about open-source projects is figuring out what is happening right now. For example, I don't think like people from wg-rls-2.0 understand what I am working on right now.
Is it a good idea to make immediate work more visible? Is there an off-the-meta-wg-shelf solution for this?
I imagining creating a free-form paper document, editable by anyone, where anybody can say (if they wish) "hey, I am working on this area right now", and link this doc from the wg page.
There's nothing documented or recommended in the compiler-team repo about that sort of thing though.
I'm not sure how @nikomatsakis is documenting and keeping track of #t-compiler/wg-traits's sprint tasks.
Ok, I guess it doesn't hurt to try the paper doc thing: https://paper.dropbox.com/doc/RLS-2.0-work-list--AZ3BgHKKCtqszbsi3gi6sjchAQ-42vbnxzuKq2lKwW0mkn8Y
How do people know how to find the paper doc?
I'd think a good solution would be effectively a blog. Each team can post to it with status updates.
(Also lets you compare the WGs and see who publishes more often ;-))
It has been linked from the compiler-team repository where all the working group details live.
@davidtwco how do people find that? :-) Everything is a discoverability problem
Niko has discussed a blog for the compiler team in the “announcing updates” topic in this stream.
I think we’re going to want to focus on discoverability at some point, but making sure the working groups are all ticking away successfully before we do that probably makes some sense.
Oh certainly; I don't mean to suggest any priority order here