KDE Core/Platform 11/Eliminating Duplication With Qt: Difference between revisions
< KDE Core | Platform 11
(Created page with ' == Notes == * A Good Thing (TM), lt's do it * Must start now to get what we need into Qt5 or will miss the chance * Freeze kdelibs4, but not too hard may need changes or can b...') |
(→Notes) |
||
| Line 10: | Line 10: | ||
** Create list of known contributors who have/will agree to Qt license so we can reuse their code if appropriate (will still need explicit agreement per contribution?) | ** Create list of known contributors who have/will agree to Qt license so we can reuse their code if appropriate (will still need explicit agreement per contribution?) | ||
** Need to be very careful don't copy code of those who oppose code donations | ** Need to be very careful don't copy code of those who oppose code donations | ||
* Much depends on success of OpenGov | |||
* All contributions from KDE must be seen as for better of Qt not just KDE, we need to be pragmatic | |||
* If get in early with quality contributions can establish position of trust and authority | |||
* Start small with some test cases to prove process, gain trust: | |||
** KUrl/QUrl - Very simple case with minimal change required | |||
** KLineEdit/QLineEdit(?) - More involved case | |||
** QDateTime - Test for working with Qt Brisbane to develop common requirements | |||
** Printing - Big test case for major changes + maintainership | |||
Revision as of 08:24, 3 June 2011
Notes
- A Good Thing (TM), lt's do it
- Must start now to get what we need into Qt5 or will miss the chance
- Freeze kdelibs4, but not too hard may need changes or can backport some KDE5 stuff
- Licence:
- Need review by eV lawyers to reassure contributors they don't lose rights, are fully informed of consequences, start asap as may take time
- Create list of known contributors who have/will agree to Qt license so we can reuse their code if appropriate (will still need explicit agreement per contribution?)
- Need to be very careful don't copy code of those who oppose code donations
- Much depends on success of OpenGov
- All contributions from KDE must be seen as for better of Qt not just KDE, we need to be pragmatic
- If get in early with quality contributions can establish position of trust and authority
- Start small with some test cases to prove process, gain trust:
- KUrl/QUrl - Very simple case with minimal change required
- KLineEdit/QLineEdit(?) - More involved case
- QDateTime - Test for working with Qt Brisbane to develop common requirements
- Printing - Big test case for major changes + maintainership