Of course it is. The question is only if they can get support for the migration So their migration is not a dedicated topic for the Docs meeting. Just finding out if someone can support them. Maybe @jflory7 can indicate what type of support they need?
I maybe caused a misunderstanding: I just added the link because Justin mentioned this point in that ticket. The pagure ticket/issue in general is not related to Docs.
Yes, I would like to create a kind of archive page as part of our team page to document where to find those old docs. Some of these old docs seems to be useful after an update (and spares the effort of creating a complete new doc).
I think I need about 2 weeks after we have a stg branch ready.
At the end, we should completely remove the old docs web in docs.fp.o tree and also remove the link from our landing page, but retain the repos and pdf files.
@heidal to write a draft about usage of GitLab web IDE for content contribution.
A closing note and appeal
It would be really helpful if we all used a constant IRC nick name that is identical or at least very similar to the nick name here on discussion as well as matrix. And maybe a nick that is easy to type and not long. This would greatly simplify and improve the comprehensibility of arguments and plans over the months.
Yes, although I rather think we should split the page, it will be too long otherwise. Then there would be a separate new page, with a title “Using the GitLab web IDE” or something like that (i.e. a new adoc).
Unfortunately, I haven’t gotten around to creating a feature branch and posting my suggestions for an expanded outline. I hope to be able to do that in the next 2 days.