Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hudson-ci/community meetings/nextAgenda"
(→Agenda) |
|||
| Line 8: | Line 8: | ||
*3.0.0M0 Release! | *3.0.0M0 Release! | ||
| + | ** Henrik: Plugin testing effort, and coordinated contact with plugin owners of plugins with problems? | ||
*Eclipse Move progress | *Eclipse Move progress | ||
| − | *Website | + | **Website |
| − | *Wiki | + | **Wiki |
| − | *Initial Code Contribution | + | **Initial Code Contribution |
| − | *Issues migration | + | **Issues migration |
| − | *Release plans and version numbers | + | **Release plans and version numbers |
| − | *Machine Provisioning | + | **Machine Provisioning (henrik: 1:How do we manage this machine e.g. add Hudson on Hudson jobs, 2: Any chance a Sonar installation will fit on there?) |
''Suggested by Winston'' | ''Suggested by Winston'' | ||
| − | *Non Eclipse committer contribution process (raised by Henrik) | + | * Non Eclipse committer contribution process (raised by Henrik) |
| + | * Nominating Henrik for Technical Leadership role to support Hudson plugins. | ||
''Suggested by Henrik '' | ''Suggested by Henrik '' | ||
| Line 24: | Line 26: | ||
*The Hudson book is a fine user manual, but it lacks advanced topics such as plugin development. Would it be better to create a new book like "Hudson Advanced topics"/"Hudson plugin development" or is it better to expand the current book ? (personally I think there might be value in splitting in to a user manual and a developer manual) see http://wiki.eclipse.org/Hudson-ci/Planning/Hudson_Book_Ideas | *The Hudson book is a fine user manual, but it lacks advanced topics such as plugin development. Would it be better to create a new book like "Hudson Advanced topics"/"Hudson plugin development" or is it better to expand the current book ? (personally I think there might be value in splitting in to a user manual and a developer manual) see http://wiki.eclipse.org/Hudson-ci/Planning/Hudson_Book_Ideas | ||
*How does one contribute to the book(s) including getting review of submitted content? | *How does one contribute to the book(s) including getting review of submitted content? | ||
| + | * Status of Gerrit workflow for non-committer contributions to eclipse parts? | ||
= Minutes = | = Minutes = | ||
''To Follow'' | ''To Follow'' | ||
Revision as of 17:06, 19 January 2012
| Hudson Continuous Integration Server | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source |
|
Community Meeting 23-Jan-2012 |
|---|
Agenda
Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:
Suggested by Susan
- 3.0.0M0 Release!
- Henrik: Plugin testing effort, and coordinated contact with plugin owners of plugins with problems?
- Eclipse Move progress
- Website
- Wiki
- Initial Code Contribution
- Issues migration
- Release plans and version numbers
- Machine Provisioning (henrik: 1:How do we manage this machine e.g. add Hudson on Hudson jobs, 2: Any chance a Sonar installation will fit on there?)
Suggested by Winston
- Non Eclipse committer contribution process (raised by Henrik)
- Nominating Henrik for Technical Leadership role to support Hudson plugins.
Suggested by Henrik
- The Hudson book is a fine user manual, but it lacks advanced topics such as plugin development. Would it be better to create a new book like "Hudson Advanced topics"/"Hudson plugin development" or is it better to expand the current book ? (personally I think there might be value in splitting in to a user manual and a developer manual) see http://wiki.eclipse.org/Hudson-ci/Planning/Hudson_Book_Ideas
- How does one contribute to the book(s) including getting review of submitted content?
- Status of Gerrit workflow for non-committer contributions to eclipse parts?
Minutes
To Follow