Community
Participate
Working Groups
Hi, With the removal of all the useless mid-level "container" projects from the modeling project (like Modeling.M2T), can you move the Acceleo project in the bugzilla from a simple M2T component to a real Product. This will have several advantages for the Acceleo project: - Even as the leader of the Acceleo project, I cannot edit the Acceleo versions or milestones since I would need to be a committer of the empty M2T project. - The Acceleo project could have its own components - We won't be able to share the versions and milestones of others M2T subprojects like Xpand or Jet I just need the creation of an "Acceleo" Product in the bugzilla under the "Modeling" Classification with the components "Core", "Documentation", "Eclipse Integration", "Releng", "User Interface" and the rights, as the leader of the project, to edit components, versions and milestones from the bugzilla manager (https://dev.eclipse.org/committers/bugs/bugz_manager.php). It may be the good time for the creation of an Acceleo inbox email for the bugzilla assignee instead of relying on the m2t-mtl email with "acceleo-inbox@eclipse.org" instead of "m2t.mtl-inbox@eclipse.org". Regards, Stephane Begaudeau, Obeo
cc'ing EMO and the IP team. -M.
(In reply to Eclipse Webmaster from comment #1) > cc'ing EMO and the IP team. +1 Makes sense to me.
Committer legal paperwork has been checked - no barriers to moving the committers... I'll move the related IPzilla CQs when the project has been moved. Over to Matt (Webmaster). Cheers, Sharon Intellectual Property
Just to be clear, Stephane are you looking to just move within Bugzilla or move out of M2T entirely? -M.
(In reply to Eclipse Webmaster from comment #4) > Just to be clear, Stephane are you looking to just move within Bugzilla or > move out of M2T entirely? > > -M. Moving out of the M2T Bugzilla component to have our own Acceleo component would give us way more options to manage the project. What would be the impact of moving out of M2T entirely? Would that mean that things like our Git repository (http://git.eclipse.org/c/m2t/org.eclipse.acceleo.git) and our update sites would change? (http://download.eclipse.org/modeling/m2t/acceleo/updates/releases). If the Eclipse Foundation wants to clean things by removing this empty M2T components entirely, we would adapt quite easily but contrary to the situation on the Eclipse Bugzilla, the impact of being under the M2T component for our Git repository or our update sites is negligible for us or our community. I don't thing that we need to change anything except the bugzilla, except if I am missing something.
(In reply to Stephane Begaudeau from comment #5) > What would be the impact of moving out of M2T entirely? Would that mean that > things like our Git repository > (http://git.eclipse.org/c/m2t/org.eclipse.acceleo.git) and our update sites > would change? > (http://download.eclipse.org/modeling/m2t/acceleo/updates/releases). These could stay as they are. We have been moving projects to a "flat" model, however. I would encourage you to consider migrating from /m2t/acceleo/* to /acceleo/*. You can maintain both for a period of time of your choosing. Or you can just leave everything under /m2t/acceleo/*, but this will get stranger over time. > If the Eclipse Foundation wants to clean things by removing this empty M2T > components entirely, we would adapt quite easily but contrary to the > situation on the Eclipse Bugzilla, the impact of being under the M2T > component for our Git repository or our update sites is negligible for us or > our community. For completeness, the Modeling PMC decided that it wanted to get rid of the container projects and flatten out the project structure. The review for that has already occurred, as has some of the work. https://wiki.eclipse.org/Modeling/project_termination_review_2012 If you have questions about the restructuring review, you should ask the PMC. > I don't thing that we need to change anything except the bugzilla, except if > I am missing something. The project id will change from modeling.m2t.acceleo to modeling.acceleo. That will change things like the URL for the IP Log generator; that id is also used in IPZilla. You can also make the downloads/git changes I mentioned above if you choose, but that's not necessary if it's too onerous.
Ok then let's go for it, let's migrate everything from /m2t/acceleo/* to /acceleo/* (project id, etc).
Ok here is the list of changes you need to make your committers(and community) aware of: Downloads: https://download.eclipse.org/acceleo Archives: https://archive.eclipse.org/acceleo Bugs: Modeling -> Acceleo . I've created a generic inbox(acceleo-inbox) and made it the assignee for the 'core' component. All of the bugs that belonged to Modeling->M2T->Acceleo have been moved to this new component and the default assignee has been updated where it was previously assigned to the m2t default inbox. Group: modeling.acceleo Git URL: ssh://commiter_id@git.eclipse.org/gitroot/acceleo/org.eclipse.acceleo.git I've left your 'current' repo in place but changed the owner to root pending your confirmation that the 'new' repo is working. Once I have that I'll remove the old one. IPZilla: I've asked EMO IP to take care of this. Have I missed anything? -M.
I've updated the project record in the PMI. Both of these URLs point to the project. https://projects.eclipse.org/projects/modeling.acceleo https://projects.eclipse.org/projects/modeling.m2t.acceleo Since this is bigger than the Bugzilla presence of the project, I've renamed and moved the bug.
(In reply to Eclipse Webmaster from comment #8) > Git URL: > > ssh://commiter_id@git.eclipse.org/gitroot/acceleo/org.eclipse.acceleo.git > > I've left your 'current' repo in place but changed the owner to root pending > your confirmation that the 'new' repo is working. Once I have that I'll > remove the old one. > > Have I missed anything? > > -M. Regarding the new URL of the Git repository, it does not seems to be "visible" from our Hudson instance. Log: https://hudson.eclipse.org/acceleo/job/acceleo-master/415/console Fetching changes from the remote Git repository Fetching upstream changes from git://git.eclipse.org/gitroot/acceleo/org.eclipse.acceleo.git ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Error performing command: git fetch -t git://git.eclipse.org/gitroot/acceleo/org.eclipse.acceleo.git +refs/heads/*:refs/remotes/origin/* Command "git fetch -t git://git.eclipse.org/gitroot/acceleo/org.eclipse.acceleo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: fatal: The remote end hung up unexpectedly The new Git repository is not visible on the list of Eclipse.org repositories (http://git.eclipse.org/c/?q=acceleo), is it normal? Only the one under m2t is visible. On Gerrit, I only see the Acceleo m2t project (https://git.eclipse.org/r/#/admin/projects/?filter=acceleo), is it normal too?
IPzilla CQs have been moved to modeling.acceleo! Thanks, Sharon
I think we're done!
I can't push any commit anymore even after changing my remote urls into ssh://git.eclipse.org:29418/gitroot/acceleo/org.eclipse.acceleo.git I get : " fatal: Project not found: gitroot/acceleo/org.eclipse.acceleo fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists " Looks like the gerrit is in a weird state, I can only find this project by typing "acceleo" and it points to the old one. https://git.eclipse.org/r/#/admin/projects/m2t/org.eclipse.acceleo
(In reply to Cedric Brun from comment #13) > I can't push any commit anymore even after changing my remote urls into > ssh://git.eclipse.org:29418/gitroot/acceleo/org.eclipse.acceleo.git > > I get : > " > fatal: Project not found: gitroot/acceleo/org.eclipse.acceleo > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > and the repository exists > " > > Looks like the gerrit is in a weird state, I can only find this project by > typing "acceleo" and it points to the old one. > > https://git.eclipse.org/r/#/admin/projects/m2t/org.eclipse.acceleo Webmaster, please help.
The correct URL should be: git clone ssh://tha@git.eclipse.org:29418/acceleo/org.eclipse.acceleo Notice the missing "/gitroot" part, it is not needed for Gerrit repos. Also Gerrit wasn't updated to know that acceleo was moved out of m2t and into acceleo directory so that's why Gerrit did not recognize that it exists. I ran the necessary Gerrit updates and ensured the new group is configured with permissions to push to the repos. Cedric, can you try again after fixing your URLs and let me know if you still have issues?
It works, thanks !
