Development/Gerrit: Difference between revisions
| Line 17: | Line 17: | ||
** tosky? | ** tosky? | ||
** ossi? | ** ossi? | ||
** Who else? Register at Gerrit, send a mail to [mailto: | ** Who else? Register at Gerrit, send a mail to [mailto:jkt@flaska.net jkt] and I'll make it happen. | ||
* Implement the CI | * Implement the CI | ||
** Jenkins, its job builder, zuul,... | ** Jenkins, its job builder, zuul,... | ||
** Tool idea: run krazy over submitted patches before committing and inform committer about possible changes | ** Tool idea: run krazy over submitted patches before committing and inform committer about possible changes | ||
Revision as of 19:57, 7 September 2014
Gerrit runs at [1], use your KDE Identity to login in and don't forget to upload your SSH keys (bugreport).
BoF at Akademy
Someone suggested to use Frameworks Meeting (Room 1 - September 9th, afternoon).
Also the PIM one (Room 4 - September 9th, morning)
TODO list
- Documentation: Write a howto for users/developers
- Define how to get support
- sysadmin's tickets?
- gerrit admins have to be able to read these
- anything which needs hard-core stuff like recreating the whole VM: a sysadmin should file a ticket at CESNET's XIFI support.
- sysadmin's tickets?
- give access to further admins
- frederik gladhorn?
- tosky?
- ossi?
- Who else? Register at Gerrit, send a mail to jkt and I'll make it happen.
- Implement the CI
- Jenkins, its job builder, zuul,...
- Tool idea: run krazy over submitted patches before committing and inform committer about possible changes