Frameworks/Meetings/201409Akademy: Difference between revisions
< Frameworks | Meetings
→Agenda: Gerrit |
No edit summary |
||
| Line 3: | Line 3: | ||
Hosted by Kevin Ottens and the KDE Frameworks crew. | Hosted by Kevin Ottens and the KDE Frameworks crew. | ||
Notes taken during the meeting on [https://notes.kde.org/p/frameworks-bof-akademy-2014 etherpad] | Notes taken during the meeting on [https://notes.kde.org/p/frameworks-bof-akademy-2014 etherpad] (not really, network not stable enough). | ||
== Agenda == | == Agenda == | ||
| Line 29: | Line 29: | ||
** Windows installers | ** Windows installers | ||
** i18n status | ** i18n status | ||
== Meeting Notes == | |||
=== Branch Policy === | |||
There is no branch, everything happens in master. | |||
Feature branches: Should be very short lived, if they live longer than 2-3 weeks look at splitting them into smaller changes. Might not be best suited for ReviewBoard review, alternative review approaches are allowed. Rebase/split into independent commits is possible, force pushing is currently disabled on the main repos (possible on personal clones, or with new branches). | |||
Lack of long term stable branches caused concerns from packagers initially, try it nevertheless for now and see how well it works. | |||
to be continued... | |||
Revision as of 12:25, 9 September 2014
Akademy 2014 Frameworks BoF
Hosted by Kevin Ottens and the KDE Frameworks crew.
Notes taken during the meeting on etherpad (not really, network not stable enough).
Agenda
- Practices topics
- Branch policy
- Commit hooks and reviews -- want to use Gerrit?
- Getting more tests
- Licence Policy - would it be useful to allow code from Qt into KF5?
- Tooling and platforms topics
- Developer story / SDK
- Android support
- Non-Linux CI support
- Documentation/Book status?
- frameworks.kde.org website for PR and point of contact?
- Technical topics
- libkonq
- sycoca replacement
- kdepimlibs
- Accessibility
- kglobalaccel runtime parts in kglobalaccel itself?
- Windows installers
- i18n status
Meeting Notes
Branch Policy
There is no branch, everything happens in master.
Feature branches: Should be very short lived, if they live longer than 2-3 weeks look at splitting them into smaller changes. Might not be best suited for ReviewBoard review, alternative review approaches are allowed. Rebase/split into independent commits is possible, force pushing is currently disabled on the main repos (possible on personal clones, or with new branches).
Lack of long term stable branches caused concerns from packagers initially, try it nevertheless for now and see how well it works.
to be continued...