Hey folks,
Just saw the "Fedorahosted-sunset" announcement yesterday, and I have a question/problem. The Spacewalk project moved its code to github a while back, but https://fedorahosted.org/spacewalk/wiki is still the primary source of info for the Spacewalk community. Suggestions for what to do with/about our entire (large, heavily used) Trac instance?
Help?
Grant Gainey
On 8 September 2016 at 09:54, Grant Gainey ggainey@redhat.com wrote:
Hey folks,
Just saw the "Fedorahosted-sunset" announcement yesterday, and I have a question/problem. The Spacewalk project moved its code to github a while back, but https://fedorahosted.org/spacewalk/wiki is still the primary source of info for the Spacewalk community. Suggestions for what to do with/about our entire (large, heavily used) Trac instance?
My initial thought would be the following:
I would look at taking the pages and importing them into the github as part of the project with the markup being markdown. I expect that users will find it less confusing than having to jump back and forth between sites to get items.
However that is just an initial thought which needs feedback also.
Help?
Grant Gainey
Grant Gainey Principal Software Engineer, Red Hat Satellite _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproje...
Stephen John Smoogen píše v Čt 08. 09. 2016 v 10:21 -0400:
On 8 September 2016 at 09:54, Grant Gainey ggainey@redhat.com wrote:
Hey folks,
Just saw the "Fedorahosted-sunset" announcement yesterday, and I have a question/problem. The Spacewalk project moved its code to github a while back, but https://fedorahosted.org/spacewalk/wiki is still the primary source of info for the Spacewalk community. Suggestions for what to do with/about our entire (large, heavily used) Trac instance?
My initial thought would be the following:
I would look at taking the pages and importing them into the github as part of the project with the markup being markdown. I expect that users will find it less confusing than having to jump back and forth between sites to get items.
However that is just an initial thought which needs feedback also.
GitHub can provide a wiki for each project, so you could actually do this and still have nice display on web. GitHub help has fairly good page on cloning the wiki git repo: https://help.github.com/articles/adding-and-editing-wiki-pages-locally/
Help?
Grant Gainey
Grant Gainey Principal Software Engineer, Red Hat Satellite _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fe doraproject.org
Stephen John Smoogen píše v Čt 08. 09. 2016 v 10:21 -0400:
GitHub can provide a wiki for each project, so you could actually do this and still have nice display on web. GitHub help has fairly good page on cloning the wiki git repo: https://help.github.com/articles/adding-and-editing-wiki-pages-locally/
The problem isn't editing the wiki once we're on GitHub - it's trying not to lose 8 years of history while getting there in the first place. Also, all the trac-to-markdown tools I've found a) do an 'ok'-ish job, and b) only care about the most-current-version. I hate losing history.
G
"GG" == Grant Gainey ggainey@redhat.com writes:
GG> The problem isn't editing the wiki once we're on GitHub - it's GG> trying not to lose 8 years of history while getting there in the GG> first place.
Extract each version as a separate page, convert to markdown (as well as you can) and commit that? It should be easily scriptable, but I don't know if github exposes its wiki as a git tree like pagure does with tickets or docs.
- J<
I would look at taking the pages and importing them into the github as part of the project with the markup being markdown. I expect that users will find it less confusing than having to jump back and forth between sites to get items.
I generally concur - but we've been dealing with that since we moved the code to GitHub in the first place, a couple years back.
However that is just an initial thought which needs feedback also.
Yeah - I'm just looking for ideas at this point.
G
On Thu, 08 Sep 2016 17:25:04 -0000 "Grant Gainey" ggainey@redhat.com wrote:
I would look at taking the pages and importing them into the github as part of the project with the markup being markdown. I expect that users will find it less confusing than having to jump back and forth between sites to get items.
I generally concur - but we've been dealing with that since we moved the code to GitHub in the first place, a couple years back.
However that is just an initial thought which needs feedback also.
Yeah - I'm just looking for ideas at this point.
Another thought would be to convert them to a doc and use a pagure doc repo. For example:
https://docs.pagure.org/pagure/usage/using_doc.html
So, anyone with commit there could update things and you can use sphinx to make it look nice, and you can use PR's if you want to update things.
But thats another site, and probibly similar to markdown on github.
Another possible option might be readthedocs: https://readthedocs.org/ Lots of projects use that and you can hook it into github pretty easily.
kevin
infrastructure@lists.fedoraproject.org
-
Grant Gainey -
Jason L Tibbitts III -
Kevin Fenzi -
Lubomír Sedlář -
Stephen John Smoogen