Missing eclipse-qvto
Please create the wiki repo for QVTo. (NOthing listed on PMI page.)
Activity
mentioned in issue #4083
Wiki repos on both Gitlab and Github are generally co-located with code repositories, so they don't tend to be 'independent'. That doesn't mean they can't be, only that it's not the default workflow.
If qvto has a code repository at say: gitlab.eclipse.org/eclipse/qvto/org.eclipse.qvtd , you can create the associated wiki repository by browsing to the repo, and clicking 'Plan -> wiki' in the left hand nav bar. Then just click on 'create your first page' button, add some text(hello world?) and click save at the bottom of the page. That will init the wiki repository(with a name of gitlab.eclipse.org/eclipse/qvto/org.eclipse.qvto.wiki) and you can then clone it and interact with it like a normal git repo.
If the project would like the wiki content to be co-located with the website content repos, that's up to them, but I think it would be better associated with the project code itself.
Part of the issue here is that both qvto(and qvtd(#4083)) appear to still be running on our Gerrit instance so they don't have an actual 'home' on either Gitlab or Github as the code repos haven't been moved yet.
That is because as sub-projects of MMT they look like MMT repos(from a filesystem perspective) and since MMT hasn't been moved yet either, these projects went unnoticed. I've broken them out in our tracking doc so we can add them to the list of projects to be moved.PLs or interested committers(with a +1 from the PL) are free to request(via a helpdesk ticket) their project be moved to either Gitlab or Github before it becomes one of the projects we pick to move in any given quarter. We'll do our best to accommodate the projects desired timing.
As so often I am confused. I expect my four projects to be similar. There is an https://github.com/eclipse-ocl/ocl-website so I just ask for the same for QVTo (and QVTd and MoDisco).
Code is highly synchronized with SimRel and only updated by committers.
Wiki is ad hoc and may be edited by non-committers.
I cannot see why Wiki and code could be in the same repo.
Documentation is more synchronized and more likely to be by committers so why is the website separate?
There is an https://github.com/eclipse-ocl/ocl-website so I just ask for the same for QVTd (and QVTo and MoDisco).
The websites for QVTo, QVTd were simply links to projects.eclipse.org, and so they were replaced with static redirects. If you're planning on creating web content for these projects, I'm happy to create the appropriate organizations and repos for you.
For the Modisco website, it was moved into the Eclipse organization on Github, rather than it's own organization because of how early in this transition it was moved(OCL was moved later), so we should correct that when the code repository moves, or we can do it now if you like.
In order for everyone to familiarize themselves with how Gitlab/Github function, we elected to move the project websites before the code as that was deemed to be lower risk. Since then our workflow has been to move 15-20 random projects per quarter to Gitlab/Github, with the goal of having all projects moved before the shutdown of our Gerrit instance.
If you don't want to wait until we get to your project(s), just file an issue here requesting the move and we'll do our best to work with your timing. We can repurpose this issue for that work if you like.
Wiki is ad hoc and may be edited by non-committers.
While true, in practice the wiki pages for any project are maintained(or not) by the relevant project.
I cannot see why Wiki and code could be in the same repo.
I think my use of 'co-located' may be at issue here. I didn't mean 'co-located' as 'the wiki is located within the project code repository', but as 'the wiki is located next to the project code repository'.
Part of the confusion is that from the Gitlab/Github web-uis it sure looks like the wiki is within the associated code repo, but in reality it's a separate repo(That any committer on the project can create/init via the web UI).
Developers, projects and users seem to prefer this appearance of tighter integration between their code and documentation.
Documentation is more synchronized and more likely to be by >committers so why is the website separate?
Projects are free to make their documentation available via their websites, integrated within the code repositories, as a separate repository, or a 'co-located' wiki as they like.
Traditionally project websites have been a bit of a mix of marketing and documentation, but the trend seems to be moving these sites towards more of a marketing/community building approach with the documentation elsewhere.
mentioned in issue #3816 (closed)
I've created an initial wiki page for QVTo here: https://github.com/eclipse-qvto/org.eclipse.qvto/wiki and updated the PMI to point there.
The project team can add/import content as they like.
