Hello,
As previously mentioned, a dvcs might benefit this project, and also
svn is too slow so we need a new vcs.
If there is no objection, I proposed that we can prepare to migrate to git.
The migration won't be done before pootle integration with git gets
done; otherwise this will break translation workflow.
Here are the things we need to prepare for the migration:

1. A list of acount name and real name <E-mail> mapping. Something like this:
    pcmanx = Hong Jen Yee <[email protected]>
    jserv = Jim Huang <[email protected]>
    juergenhoetzel = Jürgen Hötzel <...>
    ....

    We already have a list of devs on
https://sourceforge.net/project/admin/project_membership.php?group_id=180858
    but we still need the E-mail address and real names of the
contributors to complete this mapping.

2. All translators should get registered on brother's pootle server
<http://pootle.lxde.bsnet.se/> or Transifex.net
<http://www.transifex.net/>. In the future translation will be done
trough those services and direct full access to all git repos will be
limited to core developers who writes source code only for security
reasons.

3. Pootle server and transifex.net service should be set up to handle
git pull/push correctly.

After those things get prepared, we can migrate to git cleanly. If
there is any objection, feel free to leave your comment.

Bonus: maybe we can have some git hooks to sync changes in git to svn
repo? Is this possible?

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list

Reply via email to