COVESA project/repository life cycle

[erikbosch]

We have a lot of repositories in https://github.com/orgs/COVESA/repositories. What is our general governance model for them? Do we have any? Or where should it rather be defined? Some ideas:

• There shall be at least one active maintainer (person with write rights) per repository
• This shall be documented (in wiki?)
• The maintainer(s) shall address (respond) to all issues/pull-requests within no more than 3 months (preferably faster, but we shall accept that some stable projects work at slow pace)
• Releases/Tags shall typically be created on at least yearly basis if pull requests have been merged.
• If there is no maintainer the repository shall be archived in the long term
• We shall have a process for archiving repos, e.g. if we identify a possibly dormant repo, create an issue asking for volunteers for the maintainer role, or asking if someone is actively using the repository. If no-one responds within 12-months the project will be archived (set to read-only)

Discussion:

• Adnan: We could review the list of repositories and see which repositories that we consider to be in scope of the Data Expert Group
• Stephen: We had archiving process when we were GENIVI. Companies can be reluctant to archive projects.
• Erik: I assume we are "governance body" of at least VSS and VSC repo, but who is "governance body" for the rest of the repos.

[erikbosch]

Draft created at https://wiki.covesa.global/display/WIK4/Repositories+under+governance+of+Data+Expert+Group

We need to discuss if we would like to "control" also others, but if so we need to discuss how to bring them in to the Data Expert group. First step would be for someone with COVESA generic admin access to contact all with admin/maintainer/write-access in those repositories and ask for their current way of working.

[erikbosch]

Think we can close this, no active work