Phonon: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
* 3 repos (phonon, phonon-gstreamer, phonon-vlc) | * 3 repos (phonon, phonon-gstreamer, phonon-vlc) | ||
** current qtphonon becomes branch of new phonon, to retain its history | ** current qtphonon becomes branch of new phonon, to retain its history | ||
* CLA required? ( | * CLA required? ("apparently so":http://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt#Moving_an_existing_project_to_the_Qt_Project but better to check … ossi will talk with lars) | ||
* figure out what to do with l10n<br /> <code> | * figure out what to do with l10n<br /> <code><tsdgeos> i see two problems<br /> <tsdgeos> first, qt-project won't accept scripty raw commiting into the project<br /> <tsdgeos> second, making it happen means adding more code than then i have to maintain<br /> …<br /> <ossi|tt> apachepanda: ok, let's assume it's static for now. we could have one scripty commit per release. that's doable with little effort if albert lets script push into some discardable repo anywhere<br /> …<br /> <ossi|tt> apachepanda: well, you can actually have it cleanly … don't put the i18n into the desktop files, but let the code tr() the fetched strings with the actual catalog</code> | ||
* figure out what to do with deprecated repos on git.kde.org (KDE needs a policy for deprecated git repos…) | * figure out what to do with deprecated repos on git.kde.org (KDE needs a policy for deprecated git repos…) | ||
Revision as of 14:38, 24 February 2015
Phonon
Move Phonon to Qt Project
TODO
- 3 repos (phonon, phonon-gstreamer, phonon-vlc)
- current qtphonon becomes branch of new phonon, to retain its history
- CLA required? ("apparently so":http://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt#Moving_an_existing_project_to_the_Qt_Project but better to check … ossi will talk with lars)
- figure out what to do with l10n
<tsdgeos> i see two problems<br /> <tsdgeos> first, qt-project won't accept scripty raw commiting into the project<br /> <tsdgeos> second, making it happen means adding more code than then i have to maintain<br /> …<br /> <ossi|tt> apachepanda: ok, let's assume it's static for now. we could have one scripty commit per release. that's doable with little effort if albert lets script push into some discardable repo anywhere<br /> …<br /> <ossi|tt> apachepanda: well, you can actually have it cleanly … don't put the i18n into the desktop files, but let the code tr() the fetched strings with the actual catalog
- figure out what to do with deprecated repos on git.kde.org (KDE needs a policy for deprecated git repos…)
- API documentation hosting? (ask mariusg and troubalex)
- Move wiki content?
- If so: move wiki content!
- Move bugs? how?