I would not start with PDE, it is pretty active currently, and I personally would be directly affected as I've opened can of worms with https://bugs.eclipse.org/bugs/show_bug.cgi?id=576736.
Once the initial setup with aggregator is done (which is not yet), I would propose to use eclipse.platform.team or eclipse.platform.ua as a playground. They are really inactive, so no one should be disturbed. But before starting to play with concrete repo at github, wouldn't be a good idea to create a basic *plan* / documentation? Creating new git repository at github & pushing from master is not only work needed to be done here. * How the repo should be named? * Who belongs to the team / how the repo right have to be specified? * How github PR should be validated (manually / automatically / review / whatever)? * How to migrate gerrit validation to PR validation (commit message check, ECA check, API tooling check, patch size check, IP check, whatever else)? * How github PR should be merged (squash is mandatory)? What about patch series? * What happens with gerrit jobs? * How build/test jobs are triggered? * How the PR is linked to issue? * Which bug tracker is setup and how it connects to PR's? * If the bug tracker is the github - how do we migrate existing issues? * Do we "migrate" bugzilla issues for given component to github bug tracker? * Do we "freeze" bugzilla for given component? * How do we map new / old bug ID's (we don't want old/new bug have same numbers I guess)? * How the new workflow looks like for committers / contributors? * Whatever else I've forgot ... Many of items above are generic and you don't need to wait for a concrete repository to move if you want contribute to the github move - start working on answering the questions above, I guess on https://bugs.eclipse.org/bugs/show_bug.cgi?id=577322, or just create a wiki or even github issue to work on that plan. Kind regards, Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov > Gesendet: Dienstag, 18. Januar 2022 um 11:10 Uhr > Von: "Lars Vogel" <lars.vo...@vogella.com> > An: "Eclipse PDE general developers list." <pde-...@eclipse.org> > Betreff: [pde-dev] Migrate PDE to Github? > > Hi, > > as the Eclipse top-level project decided to move to Github, I was > wondering if we can start this for PDE? The pending number of Gerrits > seems small, so this would IMHO a good place to start especially as > m2e and Tycho (which closely relate to PDE) are already on Github and > because PDE is a "leaf" project. > > What do you think? > > Best regards, Lars > > -- > Eclipse Platform project co-lead > CEO vogella GmbH > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: > http://www.vogella.com > _______________________________________________ > pde-dev mailing list > pde-...@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/pde-dev > _______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
