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 "Platform-releng/Migration To GitHub"
(Created page with "This page is meant to capture ideas, concerns, evaluations, experimentations... that can help the Platform project in moving to GitHub. == Goal == Attract more contributors...") |
|||
Line 28: | Line 28: | ||
* PMI info needs to be changed | * PMI info needs to be changed | ||
* ... [Please add more missing items] ... | * ... [Please add more missing items] ... | ||
+ | |||
+ | |||
+ | |||
+ | [[Category:Eclipse_Platform_Releng| ]] |
Revision as of 12:25, 10 March 2021
This page is meant to capture ideas, concerns, evaluations, experimentations... that can help the Platform project in moving to GitHub.
Goal
Attract more contributors by using a more known workflow on a popular Platform
Concerns
Moving to GitHub is an opportunity but also has drawbacks:
- GitHub code review is not perceived by some committers as good as Gerrit
- GitHub issue tracker is not perceived by some committers as usable at the scale of Platform project (lack of depends on/blocks/clone relations, difficulty to list attachements, linked patches...)
- The process for contributing to Eclipse project via GitHub is currently cumbersome and not productive enough for new contributors (Signed-Off-By requirement cause a lot of noisy descripton and some contributions are abandoned)
- ... [Please add more missing items] ...
What needs to be done?
Generally
- Build scripts need to be able to manipulate (add tag to) GitHub repositories
- ... [Please add more missing items] ...
For each repository
- Some GitHub actions and/or Jenkinsfile need to be added to trigger CI builds
- The aggregator repository needs to change its submodule reference
- The build scripts need to add tags to the GitHub repo
- PMI info needs to be changed
- ... [Please add more missing items] ...