And finally, we need to think about the OS development.
Image creation --------------
At the moment, aTc somehow creates images out of somewhere... but not anywhere public.
So everything for that needs to be setup on our GIT as well.
aTc, now that you have more experience with building the Debian stuff, maybe you could let me know here how many gits and what gits we need.
Basically, it should be similar to the old Pandora OS, where I can just trigger an OS image creation process on the server and a few minutes later, we have a brand new, fresh image.
Ideally, the build process should update all gits, compile and add the kernel, etc.
Also, what else do we need? Do we need one GIT for each debian package we build and provide? (for example, meta-packages, our own config setups and daemons, the gl-wrapper, etc.) or can that be handled with one GIT where we have subdirectories for the packages?
What would be better and cleaner?
What do you need me to do to set it up properly? Anyone who wants to help (and can help) aTc here?
Issues tracker / organization -----------------------------
As our OS has nothing to do with the Letux setup, I'd like to use our own system (GitLab?) and issues tracker on our server.
I guess more devs can help with stuff for the OS (optimized configs, daemons, etc.) than for the kernel as well.
--- Mit freundlichen Grüßen,
Michael Mrozek
----------------------- OpenPandora GmbH Geschäftsführer: Michael Mrozek
Schäffbräustr. 11 85049 Ingolstadt Deutschland Tel.: 0841 / 990 5548 http://www.openpandora.de/ HRB 4879, Amtsgericht Ingolstadt ----------------------- eMail: mrozek@openpandora.org