CC to translate-pootle, for more input On 12/08/2006, at 6:03 AM, Dwayne Bailey wrote:
> On Fri, 2006-08-11 at 23:37 +0930, Clytie Siddall wrote: >> >> I think I've mentioned this before, but just in case... ;) >> >> From the translator point of view, it would definitely help if we >> could have cross-Pootle logins as an option. I know Drupal does this. >> >> That would mean that I could try to login at the Creative Commons >> Pootle by using: >> >> "[EMAIL PROTECTED]" >> (my current password) >> >> and _if_ CC had enabled that option, I would be able to login, and >> wouldn't have to register yet again at yet another website. >> >> What do you think? It's another barrier removed, and strengthens the >> sense of a Pootle community. >> >> One useful security step would be to assess hardworking Pootlers as >> eligible for this cross-Pootle login, if enabled. Then it wouldn't >> apply to just anyone who registers with any Pootle. It would be for >> the real community, the people who do the work. > > I've always liked this idea, but have never been sure how we would do > it. Do we share rights, how do you tell a hard working Pootler from a > slacker. I think quite a few admins would be unhappy with the idea that enabling the cross-Pootle login meant _anyone_ who registered with a Pootle could login to their site. However, they would be interested in it giving them easier access to the hardworking translators. I think we can assess hard-working translators as people who are regularly active, we could set a limit, say contributing to a certain number of strings per month, so it's not a one-off. If you stop contributing, you lose your cross-Pootle login. We would need a central database, I suppose, where user data were kept. For those of us already registered with more than one Pootle, the full name acts as a filter. So I'm registered as "Clytie Siddall" with each Pootle, with the same email address, so my data from each Pootle should be filtered together. I don't think the email address itself would make a good primary filter, because people often have different email addresses for different projects or situations. This would also act as an incentive to keep active on Pootle. :) The number of strings per month doesn't need to be anything large, even 10 is useful, because it filters out the people who simply don't do any regular work, and the monthly aspect filters out those who don't persevere. It also filters out people who don't always have enough time, but they can renew it when they participate again. Actually, a central database of translators like this would have more than one use. It would mean that new projects using Pootle could contact translators listed in the database, who have indicated in their Prefs. that they are willing to be contacted for other projects. It would be useful for stats. It would put translators in touch with each other, if that was what they chose (option: I would like to be contacted by other people translating into my language): like a forum, Pootle can have its private message or chat service (Jabber). This helps with some important issues: how translators get to know about projects needing work, how projects find translators, and how teams find new translators and mutual support. > > I guess allowing people to login they simply get the rights of a > default > login or something less. We could probably achieve this with XML-RPC. > Then each site treats this person as a user with a qualified name and > manages him/her with that name. > > Could be easier then I expected. I suppose registering and logging in implies some effort. But I think a filter on actual contribution would be useful. > > The hard part might be if we wanted to share things like team > memberships and stuff... But the first part seems plausable. I think the team/project level can be another filter, activated by options. "Do you want to extend your membership of the Vietnamese team to other Pootles translating into your language?" "Do you want to extend your membership of the Gnome project to other Pootles translating this project?" (the second less likely, as it duplicates effort, but it might also detect duplication and bring resources together). Extending membership would not be automatic, but it would mean, for example, that a Vietnamese translator I've never heard of, working on a Pootle I don't even know, possibly one mostly offline in country Vietnam, ticks this option, and when her [1] server is lucky enough to get online one day, her contact details and request are sent to me. Then I can contact her, and we can choose to work together! I can offer her some support, and more networking. :)) Making these things optional means people actually have to choose them (not default, more effort), and admins of Pootles, teams and projects also get to choose whom they accept. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] or his, or him etc. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
