Increasing community developer contributions in Launchpad Translations

Registered by David Planella on 2009-11-05

This specification aims to define a plan in which we raise awareness on developer community participation to Launchpad Translations, those contributions are increased, and they provide a path for an easier process to future contributions.

Blueprint information

Status:
Complete
Approver:
David Planella
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
David Planella
Definition:
Obsolete
Series goal:
None
Implementation:
Deferred
Milestone target:
milestone icon later
Completed by
David Planella on 2010-05-21

Related branches

Sprints

Whiteboard

Work items:
[danilo] Provide a list of trivial bugs (https://bugs.launchpad.net/rosetta/+bugs?field.tag=trivial): DONE
[dpm] add more information to https://wiki.ubuntu.com/Launchpad about developing Launchpad Translations: TODO
[dpm] Help organizing an Ubuntu Developer Week session with the Launchpad devs about developing for Launchpad Translations (proposed session, henninge and adiroiban will be running it): DONE
[dpm] Review documentation on Launchpad Translations development on lp.dev with danilo: POSTPONED
[adiroiban] Fix a bug/add a new feature (not something big) to Launchpad Translations: DONE
[adiroiban] After fixing the bug, make a BIG announcement and encourage new developers. Let them know that this can be done ... and it is not that hard: TODO
[danilo] Help adiroiban to install lp.dev and then add last-updated column into the +templates page: DONE
[adiroiban] Do a write up of how it went, and what it involved: TODO
[akgraner] Send an e-mail to dpm on getting the word out on UWN, Fridge, Full Circle Magazine, Ubuntu User, etc: DONE
[dpm] Work with akgraner on an interview or series of interviews on developing for Launchpad Translations: POSTPONED
[dpm] Contact the user who fixed the first bug in Launchpad Translations to see whether he'd be interested in participating in this round of interviews: POSTPONED
[dpm] Talk to mrevell about developer documentation on lp.dev and spreading the word on blog.launchpad.net: POSTPONED
[dpm] Follow up the discussion on letting users know how blueprints should only be used for features the community want to implement themselves, talk with danilo: POSTPONED

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.