Hi, On Jul 21, 2024, at 7:35 AM, Jim Hall via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote:
I probably have access to do that too. (I wrote my email at 11pm, too tired to try it out .. and fix it if I messed something up.)
But I'll let Jerome do it (if he doesn't mind) to make sure all the options are set right.
I don’t mind. I’m more familiar with setting the stuff up on GitLab.
I agree with you about pushing directly rather than pull requests, and using the unstable branch. Good ideas.
I also have a bunch of docs to put in right away. For a start, I'll add condensed how-tos based on the articles I've written for OpenSource and elsewhere.
Maybe a main docs group with sub-projects would be better.
Like the other groups (Base, Devel, etc) there can be a “documentation” (docs/) group. Then under that projects like Books, How-To…
Even Books could be a sub-group under Docs, with each book being its own sub-project. But, it might be better to just keep them in one project. Then all the books would be together and pulled as one project.
The FreeDOS books will go in here too, including an update for Why We Love FreeDOS (someone requested edits to their contribution, this is a good opportunity to move it at the same time). I'll have to look at how to organize them, so that might be lower on the list than the other how-to docs.
> Am 21.07.2024 um 06:08 schrieb Jim Hall via Freedos-devel <freedos-devel@lists.sourceforge.net>:
>
> What do we need to do next to set up a "Documentation" subproject
> (shared subdirectory) at https://gitlab.com/FreeDOS where we can start
> working on documentation?
I think only Jerome has the permissions to create the repository under the Gitlab FreeDOS organisation. So first step would be that he creates the repo and assigns some permissions to us.
For simplicity I suggest that we will push directly to this repo instead of everyone forking it and creating somewhat labour intensive merge requests.
For some packages, there is an unstable branch. I recommend to also use this for checking in documentation. We can then transfer articles we are satisfied with to the main branch, which can then be converted to HTML by a workflow and put somewhere on a HTTP server.
For the start I would like to write some guides how to cross-compile to the DOS target from different operating systems and compilers. Documentation for the latest tools (GCC-IA16, OpenWatcom v2 on Mac, Linux) seems to be a little sparse.
Bernd
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
|
