Thanks for the post, JoshStrobl !
So right now it's arguable we're in major flux and the method of contribution is largely unknown - which is usually considered a bad thing. On the other hand - I consider this a good thing as it allows us to actually define it now.
Our intent is to move everything to GitHub to PRs. Regarding documentation - ideally I would've liked it integrated into the main website but as you say, it needs to be translatable. The current iteration of the website is going to be "just enough" to allow a switch away from Hugo while importing all the original Hugo content.
I believe we'll want translations stored into a DB, likely using a gettext model, and have the frontend fetch the right language.
JoshStrobl If a user is not multi-lingual (or does not feel their language skills are sufficient to contribute in that manner), what ways would you like to see engagement
Honestly at this point - involving one self in in the feedback loop. Tighter communications. The priority at this minute is to get us to a point where initial packaging is possible for all contributors, so we can fix any early format/process issues.
JoshStrobl What are the current best ways for technical users to get involved? What language skills are needed and what would you say are the best resources for learning them?
For the low level bits? Dlang - might be worth checking the D playground or our repos for inspiration.
Higher up? Be creative and diversify!
JoshStrobl What is the status of running SerpentOS in an isolated environment?
This has actually worked for a long time we just don't do it as we're more interested in the infra. You can "run" Serpent OS chroots and namespaces they're just not entirely awesome.. 🙂
JoshStrobl What is the current status of packaging within SerpentOS? If there are any blockers for contributing packaging files, what are those? (I know Summit and the build infra is one of the biggest ones, but is that the sole blocker?)
Basically just the infra and shift to GitHub. Tis all 😁
JoshStrobl Post-GA what are the expected largest hurdles to growing the userbase that technical users can help to overcome?
Documentation, translations, robustifying the code and extensive testing, hardware enabling..etc =) (Also, packaging the stuff we NEED)