On 14/09/13 17:06, Alan wrote:
> I think we must find a way to group this, as a category with only one
> item is kindof useless. I think that a category should have 2 to 4/5
> items.
I disagree here. I don't see this work are try only trying to come up
with categories to order a bunch of links. Now I am more trying to
identifying roles or skills, that possible contributors can identify
with, and point them to the relevant tasks. If a role only points to one
task, then that's fine with me. A stronger, but somehow related,
limitation for me would be to stick to a number of roles that good
enough to structure and present our roles.
>>> - Content writer
>>> - Improve documentation
>>> - Translator
>>> - Improve Tails in your own language
>
> I really think we should group these into "Have language skills" or
> something like that.
I disagree, and Fedora also seem to find it important to differentiate
between people who feel like writing things, and people who feel list
translating what is already been written.
>>> - Server administrator
>>> - Setup a BitTorrent seed
>>> - Setup a HTTP mirror
>
> It have been suggested in a previous email to group these two.
>
> We might also want to group the two previous categories (developer and
> administrator) into one "Have computer skills" as you suggested before.
> I'm however unsure whether it would be less appealing to sysadmins.
I'd don't really care about how well this section is classified. We
don't have problems to get mirrors, and people are already pointed to
that page before that and more systematically, from the download page.
> * Have language skills
> - Improve documentation
> - Improve Tails in your own language
>
> * Have computer skills
> - Fix a bug
> - Implement a new feature
> - Setup a mirror
>
> * People Person
> - Spread the word
>
> * Designer
> - Improve the website design -> contribute/how/website
>
> It seems me nice but the to last one-itemed categories.
So I created two mockups which both our proposals on the blueprint. Here
they are:
https://tails.boum.org/blueprint/contribute_section/
Make sure local.css is reloaded.
