Phonon: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(Convert ExpressionEngine links)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Cleanup | reason=Auto-imported from ExpressionEngine.}}
[[Category:Developing_Qt]]
[[Category:Developing_Qt]]


Line 9: Line 11:
* 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? ("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)
* CLA required? ([http://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt#Moving_an_existing_project_to_the_Qt_Project apparently so] but better to check … ossi will talk with lars)
* figure out what to do with l10n
* figure out what to do with l10n
  <code><tsdgeos> i see two problems
  <code><tsdgeos> i see two problems

Latest revision as of 15:08, 4 March 2015

This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

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 but better to check … ossi will talk with lars)
  • figure out what to do with l10n
<tsdgeos> i see two problems
 <tsdgeos> first, qt-project won't accept scripty raw commiting into the project
 <tsdgeos> second, making it happen means adding more code than then i have to maintain
 
 <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
 
 <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?