Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incubation] How do we move github repos from our organisation to the Eclipse organisation?

There's all sorts of "have to" with Eclipse projects. But we do try to be flexible within the principles that guide us.

The Eclipse IP Policy basically makes it very difficult to import the history of a project. Strictly speaking, the Eclipse IP Team would have to pour through every change in the history to preserve it and we just don't have the bandwidth for that. Besides, history tends to include things like license changes and the licenses that were used before even a valid license change exercise might not be permissible.

So as it stands, we do need to squash the history one way or another. One way is to leave the history behind and start fresh from a snapshot in the Eclipse Project's git repository. We do also have a means of obscuring the history in a hidden branch.

There's more here: https://wiki.eclipse.org/GitHub

Wayne

On Tue, Oct 3, 2017 at 12:04 PM, Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxx> wrote:
From my experience there's no "have to" in Eclipse, only guidelines and best practices. If you have special needs or concerns, you should discuss with your Eclipse mentor and seek the best for both your project and the Eclipse foundation. They are very flexible, don't be afraid to express your concerns if you think the default isn't convenient for you.

Ondro

2017-10-03 8:54 GMT-07:00 Stephane Epardaud <stef@xxxxxxxxxxx>:

What? We were told we had to squash history when moving…


On 03/10/17 17:51, Ondrej Mihályi wrote:
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 <kopp.dev@xxxxxxxxx>:
Hi Stephane,

2017-10-03 13:14 GMT+02:00 Stephane Epardaud <stef@xxxxxxxxxxx>:

> 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
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation



_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation


_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation



_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top