> 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.
No need to apologize, nobody is at fault here. I will try commenting next time before I do anything. As for that issue, looks like somebody has already gotten to it! I'll look for something else I can do. > 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. That is a good problem to have! But this makes me think that going for E-Easy issues are also more likely to result in conflicts. Even if I comment, someone else may have started working on the issue without having commented, and I have no control over that. Eg, I see no comment from saneyuki on that issue you pointed out prior to his PR. If I asked you if it's cool to start working on, you may say that it is. In the meantime, saneyuki has already started without your knowledge or mine and we both end up repeating each others' work regardless. Hopefully that's rare, and I'm sorry I have no solution to offer myself, short of lobbying GitHub to allow issue assignment to non-members. _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
