[rust-dev] Mentoring + E-easy
Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
I'd definitely be in support of the change to easy tagging - I've seen quute a few issues where I've thought 'I could do this' but then realized I have no idea where to start. On 2013-11-26 12:59 AM, Corey Richardson co...@octayn.net wrote: Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
agree ! - Gaetan 2013/11/26 Brandon Sanderson singingb...@gmail.com I'd definitely be in support of the change to easy tagging - I've seen quute a few issues where I've thought 'I could do this' but then realized I have no idea where to start. On 2013-11-26 12:59 AM, Corey Richardson co...@octayn.net wrote: Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
On 11/26/2013 10:03 AM, Brandon Sanderson wrote: I'd definitely be in support of the change to easy tagging - I've seen quute a few issues where I've thought 'I could do this' but then realized I have no idea where to start. On 2013-11-26 12:59 AM, Corey Richardson co...@octayn.net wrote: Same for me. Even if it's obviously easy, even trivial, (1) there are usually some annoying, unknown points of the lang itself involved (2) we don't know the code base! People seem never to take the latter point into account when tagging the difficulty level of an issue to be solved, while in fact it is the main barrier; not the difficulty of correcting the issue itself. A trivial, 3 min, correction can require weeks of discovering, understanding, digesting, the relevant parts of the code base. Side-note: as a consequence, un-quality, in particular un-clarity, of a code base is for me the blocker #1 to participation. A possible good side-effect to this mentoring project is that it may help improve code clarity and overall quality: novices will stump on numerous code issues, and mentors themselves will feel uneasy when having to explain bad parts of the code. == amelioration Denis ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
It would be great if these bugs could be indexed by Bugsahoy: http://www.joshmatthews.net/bugsahoy/ This is the search system we use in Mozilla to lead contributors towards mentored tasks, so that would only make sense. Cheers, David On 11/26/13 9:58 AM, Corey Richardson wrote: Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev -- David Rajchenbach-Teller, PhD Performance Team, Mozilla ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
I strongly support this kind of human to human interaction. When arriving in a new project, there is a lot things to know that is not properly described in a proper document, set of general rules, etc. Things like how to handle this error situation, or weird error message from the compiler. I don't want to annoy the mailing list with obvious error message, trivial situations. I think we can learn a lot from well organised documentation, but talking to someone who already know is extremely valuable. - Gaetan 2013/11/26 David Rajchenbach-Teller dtel...@mozilla.com It would be great if these bugs could be indexed by Bugsahoy: http://www.joshmatthews.net/bugsahoy/ This is the search system we use in Mozilla to lead contributors towards mentored tasks, so that would only make sense. Cheers, David On 11/26/13 9:58 AM, Corey Richardson wrote: Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev -- David Rajchenbach-Teller, PhD Performance Team, Mozilla ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Mentoring + E-easy
This sounds like a very appealing option for someone like myself who is looking to contribute but lacks experience and know-how. I'll be following this thread and am encouraged by the willingness of developers to bring on new members. On Tue, Nov 26, 2013 at 5:07 AM, Gaetan gae...@xeberon.net wrote: I strongly support this kind of human to human interaction. When arriving in a new project, there is a lot things to know that is not properly described in a proper document, set of general rules, etc. Things like how to handle this error situation, or weird error message from the compiler. I don't want to annoy the mailing list with obvious error message, trivial situations. I think we can learn a lot from well organised documentation, but talking to someone who already know is extremely valuable. - Gaetan 2013/11/26 David Rajchenbach-Teller dtel...@mozilla.com It would be great if these bugs could be indexed by Bugsahoy: http://www.joshmatthews.net/bugsahoy/ This is the search system we use in Mozilla to lead contributors towards mentored tasks, so that would only make sense. Cheers, David On 11/26/13 9:58 AM, Corey Richardson wrote: Hey fellow Rusties, We have a fair number of new contributors, and my devious mind wonders how we can get more. My first thought was a new tag, E-mentored, where someone can volunteer to mentor someone through an E-easy issue. It's a very lightweight, non-formal process, and can hopefully give some more guidance to people who come into #rust asking for a good issue to get started with. This is intended for brand-new contributors, whereas I feel E-easy is a teeny bit misused. I also propose that, when tagging an issue as E-easy, a comment describing the nature of the fix and where (file + function ideal) one would look to start the fix. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev -- David Rajchenbach-Teller, PhD Performance Team, Mozilla ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
