There's lots about this discussion that dismays me. But alas, I'll focus on making this better. I suggest we look to other open source projects for guidance and examples of successful processes. I'd throw Linux Kernel and Chromium as examples of modern collaborative workflows. Each assigns Code Reviewers/Approvers for various specialty areas. On Linux, lines are drawn by CPU architecture, or File System, or Scheduler, or Driver, etc. On Chromium, similarly, CPU arch, JS Standard Libs, OS, etc. In this way, a contributor sends a patch (or a pull request since both use git) to the appropriate Approver for Review by attaching the code to a Bug Report or Issue. If the patch is a Approved, then the Approver sends it up the chain for integration into the mainline. On Chromium, there's usually multiple Approvers per area.
How I see this working for FreeDOS, you assign Approvers for the Kernel, BASE, UTIL, etc. Say, in BASE, there's FreeCOM, which is super important, so it could have its own Approvers. Just a thought. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
