Repository navigation
Replies: 3 comments 13 replies
|
Or use docuwiki? Available in deb and rpm from default repos. |
I meant option 3 to somewhat imply updating the wiki engine as UseMod seems to be very niche, I would call it's syntax "Sondergurke", and it doesn't seem to be developed any further. Decades ago I preferred to deploy MoinMoin, but that seems to be stuck on python 2.7, so clearly a no-go. Docuwiki seems nice, I can convert the UseMod-Wiki syntax to markdown with some fidelity (see github pages link above), and pandoc could convert markdown to docuwiki, so that path should be viable in principle. |
|
I would suggest ikiwiki though. |
|
Forum infra is at capacity till bot issue is solved, forum admins are still work in progress on that... I think the docs fit as the place to move what's of value in the wiki, having a single source of knowledge is better than two, from a user stand point in their mind "I need know something linuxcnc" = "look at the docs", the docs get updated trough here where we review and keep an eye on things, I am currently splitting efforts trough github+docs+forum+Discord/IRC, I really don't need a +wiki in there ;-) I'm for 1, plus move things of value to the docs, which are now searchable and can get maintained trough github already, and may also get translated for our non-english speaking friends. |
A WikiWikiWeb as it was invented https://wiki.c2.com/?WelcomeVisitors should be a low-friction place where users can share information. Key innovations were that everybody can edit and that hyperlinks are generated automatically for WikiWikiWords. As we have somewhat traditional "reference-manual"-style documentation, github issues/discussions and a web forum, it is unclear what place a wiki could serve. IMO it could still be useful, e.g. as a staging area for tutorials, to hold curated condensed info that doesn't fit in a refman, stuff people nowadays put in github "gists", meeting minutes, meeting coordination and other collaborative stuff. But then somebody would have to do that. Github issues/discussions and the forum easily get sidetracked, AI wall-of-text threads don't make it easier to follow stuff. In it's current somewhat non-functional state where you have to go through multiple hoops like manual URL editing and getting info from @andypugh on how to edit the wiki it is not surprising that content is stale. I agree if you come to www.linuxcnc.org with a blank slate it is kinda hard do figure everything out. (RTAI/Preempt-RT/Bookworm/Trixe/multiple GUIs/Mesa/Ethercat/Steppers to just name a few confusing items). A "Getting Started" Tutorial should not be in the wiki, that should probably be linked prominently from the frontpage of www.linuxcnc.org, and live in the documentation section. |
You really think a non reviewed/curated wiki, where anyone can share information low-friction, will not get the AI wall-of-text treatment today and in years to come? IMO if the objective is to create a place where only humans can post, then you have to have friction, there is no way around it, unless I'm missing something... |
|
The "wiki" concept as it was invented 1995 clearly is outdated and wouldn't work like that any more. Even the original C2 wiki is in archive-mode, as are numerous other wikis of the past (e.g. python wiki). The "wall of text" is really useful if you want to deep dive, but can be a bit intimidating and hard to navigate for human users that research a specific issue. OTOH users nowadays will ask their stochastic parrot anyways, that can digest "walls of text", that kind of "dalectic" will make something like a wiki even more unnecessary. |
|
Moving the entire old wiki data into the docs would be a good idea. But it needs to become easier to read and updated where necessary. The "wall of text" is symptomatic for many docs. It is fine if you have the time and will to go through it all. However, organisation is a key that allows you to navigate the wall. Asking your digital parrot to stochastically reproduce some kind of derivative will be used, yes, but it still does not give you the correct information in the way you need it, which you discover when your finger is lying on the floor because the parrot told you to cut it off. |
This prompted me to write: Which isn't really what you were asking about, and needs some work, but the current docs / web page do rather assume that everyone knows what LinuxCNC is. The number of queries about how to use it for DNC or with a GRBL system suggest that is not the case. |
|
There is some stuff on the Wiki that is useful, and only on the wiki. Also: |
|
The contributed components could be put into their own github repository or in github gists or something like that. Minimum software versions should probably go into developer docs. |
Yeah, a repo would be nice. It would effectively be similar to the "Voron Mods" folder in the voron repos or an "Awesome C++" repo, but it would be for "Awesome LinuxCNC Components" (or whatever you guys want to name it). Minimum versions should already be in dev documentation. |
Uh oh!
There was an error while loading. Please reload this page.
There is a long standing problem with https access to wiki.linuxcnc.org and several attempts to resolve that always ran into roadblocks. http seems to work fine. Also there is the question about the wiki software (www.usemod.org).
As more and more browsers default to https and nobody seems to have administrative access to dreamhost to enable a letsencrypt certificate, I see the following options:
As nobody seems to add or modify content in the wiki (the process to do so currently is very awkward, logins etc... don't work AFAIK) and the stuff that is in there is outdated, option 1) would not be that catastrophic as it sounds.
Remains point 3)
I see a few possibilities:
Options github and forum would take care of the login situation, although there doesn't seem to be a widely used wiki plugin for joomla and the github wiki isn't really a wiki neither.
All reactions