On Sun, Sep 1, 2013 at 3:16 AM, Jan Friberg <j...@janfriberg.nu> wrote: > Language is important > In my mind translation is the most important work that can be done in the > LoCo:s today. But the translators don't have the same status as the > developers. Without the translators work people will not use the developers > software, no matter how good the software is. So we need to gratify the > translators somehow.
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! :) > We need some more leadership and guidance. And tools to work with. People > join the LoCo and build things and then leave the project. We are ending up > in a chaos. > LoCo's have different platforms, different styles so you can't see we are a > community and we can't support ourself because we all use different tools. Do you have any specific ideas for tools? Between the Ubuntu wiki, mailing lists and 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. > Give us information early > I don't say Canonical should trust us with company secrets. But as an > example, Ubuntu Edge, if Canonical just told me something big is going to > happen on ubuntu.com on Friday, I could have informed about it, made the > interest bigger and the LoCo had got some credit to get information about > what is happening deep inside the Ubuntu project. Speaking with my Community Council hat on for a moment, we have been working with Canonical this year to improve this. So far they've started off by being more forthcoming with the CC about upcoming announcements so at least *some* community members can answer questions immediately, and through that we've worked to make sure other councils who need to know about upcoming announcements are also given a heads up. Eventually I would like to see some of this expanded to LoCos, I absolutely agree that more knowledge about things like Ubuntu Edge the LoCos could have been quite effective in helping promote it in their own areas. It is hard though, the press loves big announcements and press coverage is super valuable too! -- Elizabeth Krumbach Joseph || Lyz || pleia2 http://www.princessleia.com -- loco-contacts mailing list loco-contacts@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/loco-contacts
