On Feb 8, 2014, at 2:11 AM, eh...@mytime.com wrote: > I see this on the agenda: > >> Handling github issues: create more E-Easy? And how should people 'claim' >> them and get them 'fixed/closed'? > > It's not mentioned again though. I'd like to know about the "claiming" > process in particular. The last couple of times I started trying to implement > something in Servo, someone had started working on it unbeknownst to me. > That, combined with my major Rust noobishness has been a little demotivating.
I apologize for your bad experience trying to contribute a fix for a first issue! If you're looking for a straightforward first one, I just added one: https://github.com/mozilla/servo/issues/1641 In the future, please comment in the issue first (just say, "can I take this?"). One of us will definitely respond quickly and the comment will hopefully serve as a warning to anyone else looking at it. It will also ensure that we comment on whether anything has changed with the issue, as the Servo codebase changes quickly. One of our biggest challenges using GitHub (there are many - https://github.com/mozilla/servo/wiki/Github-challenges ) is that GitHub doesn't allow us to assign issues to non-members or for people to claim them easily. We also have a "good problem" that when we create approachable E-Easy issues, contributors fix them more rapidly than we can write them up. We didn't get around to talking about the E-Easy issues in the meeting because we had pretty low attendance at the Servo meeting this week due to travel schedules and time zones of most of the core team members, so I didn't think it made a lot of sense for Patrick and I to just chat about it :-) Thanks for your interest in Servo! - Lars _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
