Hi, On Mon, Sep 26, 2016 at 08:13:56PM -0500, Lars Bergstrom wrote:
> Are you saying that you'd like to see something between > https://github.com/servo/servo/wiki/Roadmap, which gives what people > are working on for the rest of the quarter, and the "next week" > section of the status reporting? > > Or are you saying that part of the problem is that we're not really > capturing the "next week" details well enough so that, e.g., you know > that Vlad's going to be looking into ipc-channel Windows support and > might need your feedback? A bit of both I guess?... To be honest, I'm not quite sure myself what I'm asking for exactly. As an outside contributors, usually it's not important to me who exactly is working on what exactly at what exact moment: but I'd like to have a rough idea what areas are seeing work currently or in the near future; what major changes are coming up; and also what things are being considered. The meeting notes used to cover much of the "considered" part. TWiS somewhat covers "currently", but only for ongoing things. The status updates somewhat cover currently/upcoming, but too incomplete, too fine-grained, and too short a time frame. The quaterly planning covers upcoming, but at too high a level, and last I checked, also very incomplete. What I'd really love to see, would be something in between all these I guess -- but I frankly don't know in what form... > BTW, I am full-time and I can't keep up with the IRC channel either. > And I (we) shouldn't! If IRC becomes a substitute for GitHub issues > and the mailing list, then it will crowd out both volunteers and > contributors who are not in the "right" timezone. Actually I think GitHub is in a similar position as IRC: while timezones are less of a concern, it's probably not feasible to follow all relevant repositories either... > I try to make sure that people don't make *decisions* on IRC, as > that's a pretty nasty community anti-pattern, but I'm sure I've done > it myself and should definitely be called out when I do that. That's certainly important for major, cross-cutting decisions; but people are constantly making "smaller" decisions on the spot -- and that's OK I'd say. The issue is *communicating* when these things are happening... -antrik- _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
