Le 04/09/2013 05:57, Chris Johnston a écrit :
On 09/03/2013 04:20 PM, Jan Friberg wrote:

     I'd love to see some discussion around this. The Ubuntu community has
     always worked hard to be inclusive of all kinds of contributions,
     Ubuntu Membership is open to everyone: artists, translators, folks
     running Ubuntu events, everyone contributing anything to Ubuntu and
     the community! In fact, developers have their own track to go through
     to get developer access to the project and that's separate from
     regular membership and only really adds on developer-specific
     privileges. Is there something about the process for Ubuntu Membership
     that translators find unfair, or do they feel like they don't qualify?

     Beyond membership, do you have ideas on how to specifically gratify
     translators?

     Thanks for the feedback! :)


I think it's an attitude in the community, not only in Ubuntu but in the
Linux community in general. Developers and graphic artist has always
created cool stuff while translators just write what some one else
already written in another language.
So how do we make the translator to be a cool guy? I have no good ideas
yet, but we are thinking about it in my team.

About membership in general. I asked in our forum about how many was
applying for membership or thinking of starting to apply. So far 1
person has shown any interest.
I hate to say this. But the interest for Ubuntu and/or Linux is
declining fast in Sweden. And I see this even in my team.





     Do you have any specific ideas for tools? Between the Ubuntu wiki,
     mailing lists and loco.ubuntu.com <http://loco.ubuntu.com> the
     California team hasn't felt a
     huge need for our own website - all our website does is provide a
     convenient URL for people to start off with, from there they are
     linked off to the other pages, we don't actually host any content on
     it. Makes it much easier to maintain and we don't have a major problem
     if folks leave :) We also use social media a fair amount to get
     announcements out beyond just our mailing list, the access to these
     accounts is shared between a few trusted community members so no one
     person has control of everything.

     I do acknowledge that as an English-speaking team we have an advantage
     here, our team doesn't need to host local support forums and similar
     but I thought there were localized spaces for many of the LoCo tools
     being provided already. If not, perhaps that's a good discussion to
     have - what tools do non-English teams need in the community that are
     currently not being internationalized? What steps need to be taken to
     do a better job of providing these things? I've found Canonical to be
     much easier to work with when you approach them with specific plans
     that include needs and goals.

Ok, my team might be special and I don't know all the history behind it.
But we have our domain on a members private server. It host 1 drupal
portal, 1 forum, 2 wikis. Most informations in the wikis are outdated
about the year 2010, except comment fields that are daily filled with spam.

So what you describe with the California team is what I like us to be.
But the lack of guidance and rules made the team do some bad mistakes in
the start up.

A new team should get a rulebook that say; Use this tools first like
mailing lists, loco.ubuntu.com <http://loco.ubuntu.com>, wiki.ubuntu.com
<http://wiki.ubuntu.com> and if that is not enough to cover your need
you use this forum software with this style sheet, this portal software
with this style sheet and so on.
DO NOT INVENT YOUR OWN STUFF!

Then I can turn to another team and ask them question how to set up and
run things because they use the same tools as me.

People are eager to start up things in the beginning, but when the work
get overwhelming we end up with outdated information ans systems.




All of that information already exists.

http://loco.ubuntu.com/about-loco/setup/

cJ


Hi,

This guide is a very good starting point to create a LoCoTeam and let it know how to have tools and resources to organise the first members of the team.

But these resources have some defaults. They are not for users.
- IRC : who use this old communication tool ? lot of people (young ones, not technical ones) are not at ease with this tool. They join, they ask something, they leave.
 - Launchpad : well, it's a developer tool… not for users.
- Mailing Lists : like IRC, but a bit easier, people already know emails can take time to have an answer. Lot of people don't understand how mailing lists work and they think it's a newsletter.
 - ubuntu forums : ok, that one is for users ;)
- wiki page : this wiki is for ubuntu teams, just for presentation, and a bit of organisation.

And, of course, all of this is in english only… clearly not for foreign language users.

LoCoTeams (and non-english ones in particular), when they grow, they want to offer more to the users in their country. They need new tools for that. And There is no guide, no resources, nothing to help them make the right choices, to have some unity on the tools they use and the templates.

Yes, I'm exaggerating a bit, there is some wiki page who talk about these tools, https://wiki.ubuntu.com/LoCoCreatingWebsite .

Perhap's we can highlight this a bit more, creating a new page on the loco portal or the wiki, something like "locoteam growth" presenting some good practice on what tools they can add to help them : - social network accounts, groups, pages to let users know what you are doing, create events,… - a team blog to talk about your activities and to have some static pages on how to join the team or ubuntu teams and how to contribute - if you want to do language support, start with a forum or an askubuntu like tool, continue with a wiki if needed (harder to keep up to date)
 - if you have some bloggers talking about ubuntu, create a planet
 - …

Philippe


--
loco-contacts mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/loco-contacts

Reply via email to