Date
1 - 2 of 2
Github repo organization
|
Jochen Kall
Hi everyone,
Kate and I did a bit of brainstorming how to deal with the our repo problem Problem at hand to recapitulate: Currently we have elisa-tech as central hub for ELISA repos, but since github does not support trees of repositories, this means it will get hard to navigate, this came to our attention in the Automotive WG, since dealing with AGL/Yocto requires several repositories just for one use case demo application, if we expand this will only get worse. · Create elisa-tech suborganizations where appropriate . Naming scheme: "elisa-tech-<NAME> . E.g. Create github.com/elisa-tech-automotive o meta-elisa would relocate there o Code repository for the safety demo app o Additional repos as they become necessary for further usecases/ extensions . Create github.com/elisa-tech-tools o containers, etc. . Create suborganization accounts for the other workgroups when it becomes necessary . Stitch them together via a Wiki from the main Elisa-tech account . That way we keep everything at least kind of centralized without cluttering elisa-tech · Need standardized way of refering to working groups main repos in elisa-tech . Currently we have for instance: "wg-automotive" vs. "Safety_Architecture_WG" . Suggested naming scheme: o wg-<NAME> o use "-" rather than "_" o name of working group first to get repos clustered by sorting o capitalize working group names. · The repo "workgroups" seems to be used differently from the description, and the name is a bit nondescriptive . maybe rename it to something along the lines of "tools-workgroup" or specific to the tools developed within it and move it to elisa-tech-tools · "linux" repo seems to be desserted . Couldn't piece together what this was intended for, but it seems unused . @Shuah Khan can we remove this clone of Linux? · ELISA-White-Papers should be renamed to ELISA-publications · Stitching it all together from the main elisa-tech account . At top level we have working group main repos as we currently do. . We also pin a repo to the top level that explains the project o content in workgroups Link to all sub-accounts Let us know what you think Best regards Jochen On behalf of Toyota. -- Dr. rer. nat. Jochen Kall Functional Safety ITK Engineering GmbH Im Speyerer Tal 6 76761 Rülzheim mailto:jochen.kall@... ______________________________________________________________ ITK Engineering GmbH | Im Speyerer Tal 6 | 76761 Rülzheim Tel.: +49 7272 7703-0 | Fax: +49 7272 7703-100 mailto:info@... | http://www.itk-engineering.de/ Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Dr. Rudolf Maier Geschäftsführung/Executive Board: Michael Englert (Vorsitzender/Chairman), Bernd Gohlicke Sitz der Gesellschaft/Registered Office: 76761 Rülzheim Registergericht/Registered Court: Amtsgericht Landau, HRB 32046 USt.-ID-Nr./VAT-ID-No. DE 813165046 -- Mit freundlichen Grüßen Jochen Kall -- Dr. rer. nat. Jochen Kall Funktionale Sicherheit ITK Engineering GmbH Im Speyerer Tal 6 76761 Rülzheim Tel.: +49 7272 7703-546 Fax: +49 7272 7703-100 Mobil:+491734957776 mailto:jochen.kall@... ( jochen.kall@... ) ______________________________________________________________ ITK Engineering GmbH | Im Speyerer Tal 6 | 76761 Rülzheim Tel.: +49 7272 7703-0 | Fax: +49 7272 7703-100 mailto:info@... ( info@... ) | http://www.itk-engineering.de ( http://www.itk-engineering.de/ ) Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Dr. Rudolf Maier Geschäftsführung/Executive Board: Michael Englert (Vorsitzender/Chairman), Bernd Gohlicke Sitz der Gesellschaft/Registered Office: 76761 Rülzheim Registergericht/Registered Court: Amtsgericht Landau, HRB 32046 USt.-ID-Nr./VAT-ID-No. DE 813165046 |
|
|
|
Hello Jochen, Kate,
toggle quoted message
Show quoted text
some feedback inline. Best regards, Philipp --- Philipp Ahmann Manager Engineering Software System 1 (ADITG/ESS1) Tel. +49 5121 49 6918 Mobile +49 172 1576941 Data protection information: We use your contact information and e-mail communication to process your inquiry and for internal and possibly tax documentation purposes. A passing on to third parties takes place only as far as this is necessary for the execution of your inquiry or we are legally obligated to it. -----Original Message-----Beside the part "capitalize working group names" I agree. I see no enhanced readability (actually for me pure capital letters makes it harder to read) and with the wg-<name> it will be structured enough. But this is just taste. So I am good with both at the end. · The repo "workgroups" seems to be used differently from the description,Sounds good. This repo will remain in the top level elisa-tech account, right? · Stitching it all together from the main elisa-tech accountI like this approach, especially due to keeping a wg-<name> top repo in elisa-tech and not have a sub group by default allows us to scale. If a group grows, there is way to separate out in a sub-account, but nobody has to start this way. Thanks for this proposal
|
|
|