intrigeri:
> sajolida wrote (30 Nov 2015 14:43:33 GMT) :
>> I think the hard problem here lies in
>> these pages and do you get from landing on such a page and getting a new
>> contributor on board (introducing, onboarding, etc.), not really in
>> knowing the skill sets that are relevant and pointing to the right team.
>
> I'm not sure this "team" approach matches the reality of how lots of
> our code is maintained.
>
> For a wannabe code contributor, finding what project they have the
> skills to work on is currently very hard.
Ah, so you're referring here more to what's below "Writing code" on the
Mozilla website. Which is then asking for your favorite programming
language and then listing different projects using this language.
Yesterday I didn't pay much attention to this section (as I'm more into
other things myself).
> I've spent countless hours
> extracting e.g. Python tickets in our well stuffed list of "Easy"
> tickets [1] for wannabe contributors who want to do Python.
>
> If those Python coders had been pointed directly (e.g. via a web app)
> to the list of projects (Installer, Greeter, etc.) that we have in
> Python, then I could have spent more time onboarding them, and less
> time doing the skills -> task mapping robot.
>
> I don't know what's the solution to this problem, and I'm sure there
> are better (and cheaper!) solutions than the one I mentioned initially
> in this thread. But it's certainly a problem I've experienced
> a few times :)
>
> [1] https://labs.riseup.net/code/projects/tails/issues?query_id=112
>
> Now I'm going to shut up in this thread. Cheers!
Your last message was useful :)
Ok, so the information mapping that we are missing is which projects do
we have in which programming language, right? Then the formatting (web
app, list, Redmine view, etc.) is a different issue. Because we don't
have this information in Redmine, nor under contribute/how/code, right?
Currently people either have to ask or read the code to know in which
language its written.
