|
Hi all,
yesterday the code repositories were moved to the newly created https://github.com/eclipse-viatra Github organization, and the old repository is already read-only. The issues will be moved soon as well, in
the meantime, please consider the issue/pr functiionality on github not yet available.
If you are a committer and have already added your Github account, as asked in my previous email, you should have received an invitation to the organization, please accept it. If you have not received an invitation, please add your Github account on your
Eclipse Foundation account on https://accounts.eclipse.org
Thanks,
Zoltán
![]() |
|
|
|
Zoltán Ujhelyi, PhD |
|
Solution Architect |
|
|
E: zoltan.ujhelyi@xxxxxxxxxxxxxxxx |
|
A: Hungary H-1072 Budapest, Rákóczi út 36. |
|
|
|
|
|
On 17 Oct 2023, at 10:45, Zoltán Ujhelyi <zoltan.ujhelyi@xxxxxxxxxxxxxxxx> wrote:
Hi all,
concerning this migration request, I suggest the following strategy going forward:
-
Given the https://git.eclipse.org/c/viatra/org.eclipse.viatra2.vpm.git/ repository had not been touched in about ten years, we should use this opportunity to archive
it (together with the corresponding Bugzilla component (https://bugs.eclipse.org/bugs/buglist.cgi?component=VPM%20%28Archive%29&list_id=21373810&order=Importance&product=Viatra&query_format=advanced).
-
We should migrate the remaining three repositories to separate Github repositories and keep the current structure intact.
-
We should ask to migrate the existing Bugzilla issues to the Github repositories, if possible, splitting them by Bugzilla components:
-
Examples -> org.eclipse.viatra.examples.git
-
Obfuscator -> org.eclipse.viatra.modelobfuscator.git
-
Any other -> org.eclipse.viatra.git
-
After the migration, we should migrate the developer contents from https://wiki.eclipse.org/VIATRA to the appropriate Github repository wikis. The user documentation
is already present in the repositories in Asciidoc format.
I am prepared to coordinate the migration from the project side, but I'd like to ask you the following things:
-
If you have any issues or requests regarding the timing, please share them this week. We are offered the move on February 15th, 2024, but we could ask for a different
schedule if necessary.
-
If you have any suggestions or concerns about the points above, please share them this week.
-
If you are a committer or plan to contribute to the code base, you can prepare for the migration by adding your existing Github username to your Eclipse Foundation
account at https://accounts.eclipse.org. This field is used now to give committers access to the website repository of the project and will be used for getting access to the migrated repositories.
-
Finally, we have a few unmerged Gerrit changes: https://git.eclipse.org/r/#/q/status:open+projects:viatra. We should look at them and merge or abandon them before
the migration. If you feel responsible for one or more of them, feel free to go about them. Regardless, I will review them as time allows and contact the owners or reviewers as necessary. In such cases, please try to respond promptly.
Thanks for your cooperation,
Zoltán
![]() |
|
|
|
Zoltán Ujhelyi, PhD |
|
Solution Architect |
|
|
E: zoltan.ujhelyi@xxxxxxxxxxxxxxxx |
|
A: Hungary H-1072 Budapest, Rákóczi út 36. |
|
|
|
|
|
On 12 Oct 2023, at 21:39, webmaster--- via viatra-dev <viatra-dev@xxxxxxxxxxx> wrote:
Hello,
As you may be aware the Foundation is working on deprecating its Gerrit instance[1]. To that end we transferred project website repositories to Gitlab/Github last year just to get projects familiar with the basic process.
In keeping with our planned timeline we have begun selecting 15-20 projects per quarter that will have their code repositories moved in the following quarter, and as you may have guessed your project has been selected as part of next quarters moves.
We’ve filed an issue(https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3818) to track the details and conversation between the Webmaster team and the project, so please take this opportunity to discuss what timing works best for you, what should happen
to your bugs(if any), and let us know on the above issue.
Want to move sooner than our default schedule of next quarter? Please comment on the issue and we’ll do our best to accommodate your timing.
If we don’t hear back from you by the due date for the above issue, we’ll work with the Foundations project team to determine if your project is still active. Active but unresponsive projects will be moved to the Foundations Gitlab instance by default. Inactive
projects will be scheduled for termination review.
If you have any questions feel free to ask Webmaster via the above issue.
-Matt.
[1]https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan
_______________________________________________
viatra-dev mailing list
viatra-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/viatra-dev
|
