Preparing for the Eclipse initial contribution
19 views
Skip to first unread message
Julien Ponge
Jun 22, 2015, 4:53:35 AM6/22/15
to golo...@googlegroups.com
Hi everyone,
As you know by now, Golo is now an incubating Eclipse Technology project [1].
Now that the project has been created, we are still waiting on all committers to have their paperwork in place, after which they’ll appear at [1]. Note that if you are one of the committers and had sent your paperwork in advance you may need to send it again, because well… at that time the EMO (Eclipse Management Organisation) perhaps did not knew anything about you :-)
According to the development process at [2], the next step for us is to propose an initial contribution of the code base. I have started work at [3] to prepare the code base. This includes a switch to the Eclipse Public License, fixing the headers, various files etc.
This initial contribution will be IP-checked and it will form the basis for a new repository that will be hosted on Github under the Eclipse organisation. In practice this also means that the whole Git history will be reset, and that the `golo-lang/golo-lang` repository will be transferred to Eclipse.
In any case we will keep a public frozen reference fork at github/dynamid, and all of your forks are copies anyway.
Another thing to keep in mind is that while we will use GitHub instead of a Git repository at the Eclipse Foundation, we will not be able to use GitHub issues (but pull-requests yes, just like before). Instead we will need to use the Eclipse Bugzilla [4], and we will have to move issues there.
If you have a few minutes to spare, it would be very helpful if you could consider looking at [3] and help us prepare a suitable initial contribution according to the rules [2].
There is a last decision to be made: we need a cutoff date to freeze our current repository, and after which no more commits or pull-requests will be accepted until we have the code at Eclipse.
How about this Friday 26th? There no big hurry so if you have a PR that you would like to pass before the cutoff we can shift.
Of course this would break pull-requests, especially since Git history is going to be reset, but as a minor relief we have been authorised to enter incubation without refactoring all packages to org.eclipse.* yet, so a simple rebase onto the new repo master branche shall be just fine.
Last but not least, this mailing-list will probably become (even more) useless after the switch, since we’ll have to make discussions on the Foundation lists :-) I’ll see to keep the Gitter.im chat, but we’ll have to make more use of lists.
Cheers
[1] https://projects.eclipse.org/projects/technology.golo
[2] https://eclipse.org/projects/dev_process/development_process.php
[3] https://github.com/golo-lang/golo-lang/pull/283
[4] https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Golo
- Julien
As you know by now, Golo is now an incubating Eclipse Technology project [1].
Now that the project has been created, we are still waiting on all committers to have their paperwork in place, after which they’ll appear at [1]. Note that if you are one of the committers and had sent your paperwork in advance you may need to send it again, because well… at that time the EMO (Eclipse Management Organisation) perhaps did not knew anything about you :-)
According to the development process at [2], the next step for us is to propose an initial contribution of the code base. I have started work at [3] to prepare the code base. This includes a switch to the Eclipse Public License, fixing the headers, various files etc.
This initial contribution will be IP-checked and it will form the basis for a new repository that will be hosted on Github under the Eclipse organisation. In practice this also means that the whole Git history will be reset, and that the `golo-lang/golo-lang` repository will be transferred to Eclipse.
In any case we will keep a public frozen reference fork at github/dynamid, and all of your forks are copies anyway.
Another thing to keep in mind is that while we will use GitHub instead of a Git repository at the Eclipse Foundation, we will not be able to use GitHub issues (but pull-requests yes, just like before). Instead we will need to use the Eclipse Bugzilla [4], and we will have to move issues there.
If you have a few minutes to spare, it would be very helpful if you could consider looking at [3] and help us prepare a suitable initial contribution according to the rules [2].
There is a last decision to be made: we need a cutoff date to freeze our current repository, and after which no more commits or pull-requests will be accepted until we have the code at Eclipse.
How about this Friday 26th? There no big hurry so if you have a PR that you would like to pass before the cutoff we can shift.
Of course this would break pull-requests, especially since Git history is going to be reset, but as a minor relief we have been authorised to enter incubation without refactoring all packages to org.eclipse.* yet, so a simple rebase onto the new repo master branche shall be just fine.
Last but not least, this mailing-list will probably become (even more) useless after the switch, since we’ll have to make discussions on the Foundation lists :-) I’ll see to keep the Gitter.im chat, but we’ll have to make more use of lists.
Cheers
[1] https://projects.eclipse.org/projects/technology.golo
[2] https://eclipse.org/projects/dev_process/development_process.php
[3] https://github.com/golo-lang/golo-lang/pull/283
[4] https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Golo
- Julien
Thierry Chantier
Jun 22, 2015, 11:07:58 AM6/22/15
to Julien Ponge, golo...@googlegroups.com
to be sure paperwork has been received and processed, could we check that our name is added to http://projects.eclipse.org/projects/technology.golo/who
or is it something unrelated?Julien Ponge
Jun 22, 2015, 12:22:41 PM6/22/15
to Thierry Chantier, golo...@googlegroups.com
Yes, or perhaps just contact emo at eclipse to check :-)
Julien Ponge
Jun 23, 2015, 10:51:25 AM6/23/15
to golo...@googlegroups.com
Julien Ponge
Jun 23, 2015, 4:28:28 PM6/23/15
to golo...@googlegroups.com
Hi everyone,
The project is fully provisioned now. I also think that the initial contribution branch is ok, too.
At the moment the plan is to make the initial contribution request + repo freeze this Friday. We can make it earlier if the people with open pull-requests (Yannick, Daniel) wave the green flag :-)
- Julien
The project is fully provisioned now. I also think that the initial contribution branch is ok, too.
At the moment the plan is to make the initial contribution request + repo freeze this Friday. We can make it earlier if the people with open pull-requests (Yannick, Daniel) wave the green flag :-)
- Julien
Thierry Chantier
Jun 25, 2015, 11:03:07 AM6/25/15
to golo...@googlegroups.com
if like me you missed the Individual Committer Questionnaire because you thought that it was the same as Eclipse CLA form, your paperwork will not be processed.
go to http://portal.eclipse.org/ and fill the form here.
by the way, there is additionnal info on the status of your accountgo to http://portal.eclipse.org/ and fill the form here.
To view this discussion on the web visit https://groups.google.com/d/msgid/golo-lang/06252ACC-7E59-47BC-BE4E-6615DE5793DD%40insa-lyon.fr.--
You received this message because you are subscribed to the Google Groups "golo-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golo-lang+...@googlegroups.com.
To post to this group, send email to golo...@googlegroups.com.
Visit this group at http://groups.google.com/group/golo-lang.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages