Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Where does our content go when the wiki goes?
I've completed the migration of the wiki content, including all pages under the following categories: https://wiki.eclipse.org/Category:Architecture_Council, https://wiki.eclipse.org/Category:Architecture_Council_Committer_Resources and https://wiki.eclipse.org/Category:Architecture_Council_Meeting_Minutes) to gitlab: https://gitlab.eclipse.org/groups/eclipsefdn-ac/-/wikis/

Notably, the meeting notes are now located at https://gitlab.eclipse.org/groups/eclipsefdn-ac/-/wikis/Meetings/Meeting_Notes

The content is editable online and is backed by a Git repository. For more information, please refer to the git access page https://gitlab.eclipse.org/groups/eclipsefdn-ac/-/wikis/git_access if you prefer working directly with the repository.

I've performed minimal sanitization, but please note that some links are broken, images have not been copied, and some content may be outdated. However, it's a good starting point.

Cheers,

Mikaël Barbero 
Head of Security | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration



On 11 Apr 2024 at 18:14:57, Jay Jay Billings via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
Like you and Jonah, I never found the GitLab or GitHub wikis to be worth much. Personally, I'm fine with (and prefer) using individual markdown files in a GitLab project. Plain text, uniquely addressable, scalable, well tracked, easy to edit from anything, /and exceptionally well rendered... the list goes on.

jm2c,
Jay

On Thu, Apr 11, 2024 at 12:08 PM Wayne Beaton via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
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.

Wayne

On 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


--
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

Back to the top