| Re: [eclipse.org-architecture-council] Where does our content go when the wiki goes? |
We might want to consider migrating some subset of the content to keep current.FWIW, some of the content in the Eclipse Project Handbook was based on content migrated from the wiki. I exported the content in Wikimedia markup, and used pandoc to convert it to AsciiDoc to provide a starting point. pandoc also supports Markdown.My experience with the wiki support in GitLab has been disappointing to date. I've found that just pushing markdown files to the Git repository works great. GitLab (and GitHub) does a very good job of rendering Markdown. I did this, for example with the SBOM repository.WayneOn Thu, 11 Apr 2024 at 11:30, Jay Jay Billings via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:_______________________________________________Everyone,We discussed wiki migration during the AC meeting today. Where should we host our content when the wiki goes away?Wayne proposed that we use a GitLab project, which I think is a good idea. Are there any other suggestions?Jay
--Jay Jay Billings, Ph.D.
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
--_______________________________________________Wayne Beaton
Director of Open Source Projects | Eclipse Foundation
My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours.
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council