osdev wiki dedicated git resource

[ajxs]

This is just a thought I had.
When supplying code snippets for wiki articles and tutorials, the wiki provides adequate facilities. However there are times where authors have had to provide entire source files one after another in a single article, this is obviously not ideal. In some other cases authors have provided links to external git repositories to provide more complete examples.
I was thinking that it might be an idea to create a central git repository or account on a VCS hosting service ( github, gitlab, etc ) to be used as a central repository for examples used in the wiki.
In many cases I find it much easier to pore through source code in my own editor than read it online, so being able to check out resources and examples I'm studying is much easier. There is definitely a small administrative overhead, but I think there's some benefits.

[Solar]

I do not see where this would be helpful.

Either your source is open; then you usually already have it residing in a publically accessible repository.

Or your source isn't open. Then there's already places like Pastebin.

Creating / checking into a repository for the sole purpose of posting to OSDev sounds like a pretty nuisance for me. I also take exception at Git being considered some kind of "gold standard" of VCS. It isn't.

[ajxs]

Either your source is open; then you usually already have it residing in a publically accessible repository.
Or your source isn't open. Then there's already places like Pastebin.
Creating / checking into a repository for the sole purpose of posting to OSDev sounds like a pretty nuisance for me.

I didn't intend to introduce any new methodology for posting code to the wiki or sharing user projects. My idea was intended to address the cases where users are already linking external repositories to the wiki. Commonly this contains supplementary code. Or fully assembled examples in the case of the 'Bare Bones' series of articles. My thinking was that it would bring the code provided under shared control, which might help avoid 404's in the case that the hosting user removes their work, or allow for the code to evolve with the associated osdev wiki article.

There's currently only a few wiki pages I could find that link to examples hosted as online source control resources. I should have checked before posting the topic, but you can see them below:

• https://wiki.osdev.org/Bare_Bones

• https://wiki.osdev.org/C_Sharp_Bare_Bones

• https://wiki.osdev.org/Ada_Bare_bones

• https://wiki.osdev.org/Meaty_Skeleton

• https://wiki.osdev.org/ARM_Integrator-CP_IRQTimerPICTasksMMAndMods

• https://wiki.osdev.org/ARM_Integrator-CP_ITPTMME_Phase2

• https://wiki.osdev.org/Ada_Kalinda

I'll admit a few of these are a little obscure.

I also take exception at Git being considered some kind of "gold standard" of VCS. It isn't.

You can have this argument with someone else, I'm not interested. I could possibly have used a more generic term in the title, but I think the word 'git' in the title conveys the point adequately.

My original thought was that a central repository would help for users to make corrections and improvement to supplemental code provided for the wiki. Such as that linked to by many of the 'bare bones' articles above. I guess that might be out of the scope of the wiki, and creating a pull request or similar to the repo and updating the wiki might be a bit onerous.
I'm not too upset about this if others aren't interested, it was just an idea! I'm willing to leave the idea here if no one else thinks this resource can be useful.

[eekee]

It might be more appropriate to create sub-pages for the code. That way, anyone with a wiki account can edit them without additional tools. It wouldn't help with viewing code in your editor, but that would be eased if code fields had a button to copy the text. Or if some automation was added to, say, pull all the code from all the sub-pages of an article and present it as files in zip or tar.

More strongly, I'm recently finding Git culture with all its forking to be a real nuisance. This isn't just Git; it could happen with any other DVCS, but Git is where the culture is. I can't find things for all the worthless abandoned forks on Github. The other day I was looking for the fix to Jonesforth to make it run on modern Linux, but I couldn't find it amongst all the abandoned unfixed forks. Also, pull requests are too much beaurocracy for me, making much more work than just fixing the code.