As an Eclipse MicroProfile commiter, I know there are 2 options to create a
github repo at Eclipse

 - create a new empty repo based on Eclipse template (EPL license file,
etc.)
 - migrate an existing repo under the Eclipse github org, preserving
history, issues and everything else

As an example of the second option, have a look at
https://github.com/eclipse/microprofile-config - it was migrated under
eclipse org this year, but there are still issues and commits dated to 2016
- everything was preserved from day 1.

So I wouldn't be afraid of losing history.

Ondro

2017-10-03 5:04 GMT-07:00 Oliver Kopp <[email protected]>:

> Hi Stephane,
>
> 2017-10-03 13:14 GMT+02:00 Stephane Epardaud <[email protected]>:
>
> > As part of the Ceylon move to Eclipse, we have to move our github repos
> to
> > the Eclipse organisation. I understand we have to delete history, so
> we'll
> > need to first force-push a blank history to our current repo, delete all
> > branches and tags,
>
> Yes. You might want to add the tag "initial-code-contribution" as tag.
> I used "Initial Code Contribution - CQ 7916" at the first commit to
> ensure proper referencing to IPZilla.
>
> I also agree that an BugZilla issue is the best way to move forward.
>
> Cheers,
>
> Oliver
> _______________________________________________
> incubation mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/incubation
>
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

Reply via email to