GENIVI is now COVESA 
A number of activities are under way to transfer IT infrastructure
to the domain : covesa.global
The process of migrating Git repositories will start NEXT WEEK.
Please read this email carefully!
Git repositories will be reviewed. Projects that are active and relevant
to the COVESA scope of work will be moved from the GENIVI GitHub
account to the COVESA GitHub account. The GENIVI account will remain for a
while, but projects need to transfer their activity and update git-remotes
and other URLs accordingly, since it will go away at some point in the
What to do depends on how the project is categorized.
Here are project categories to use and to discuss with project
maintainers as needed:
A1) Projects in this category are considered relevant for further
development within the scope of COVESA. These will be transferred over to
COVESA's GitHub account and thus get a new upstream URL. The GENIVI copy
will be set to read-only for the time period that the GENIVI account
remains. This will be done in collaboration with maintainers, HOWEVER,
do not wait. If you are maintaining a repository I expect you to be
proactive and contact me to negotiate any details, as needed.
A2) This category is like A1 but the project will remain active and
writable at the GENIVI URL while we take some more time to plan a migration
strategy together with the maintainers.
B) Projects in category B will be marked as no longer maintained and set to
read-only. These will remain readable to allow all users and downstream
projects to use the existing URLs for a while. There will be a clear
notice that if further development is desired, then the project should be
forked and maintained at a new location.
C) Repositories in category C could be immediately deleted. These are
typically repositories that have little to no content, negligible value at
this point or are covered through other means such as documents that have
been moved out of Git and kept elsewhere.
As always with open-source projects, it is possible to revisit the strategy
and change it. For example, if there is someone who very much would like to
pick up and activate a project placed in category B, and also wish that we
help find hosting for it under COVESA, then you can contact me about this,
and we can discuss it. Users are free to step up and become maintainers.
Maintainers can also express their desire, whatever it may be, and we can
What to expect next: I will send the proposal for categories/actions for
each repository for you to review. This will then be implemented QUICKLY
after that, so be proactive.
** MAINTAINERS! ** At minimum, keep the conversation open by replying to
me personally (not to mailing list) to say you have read THIS email. Do not
wait for the proposal. If I do not hear from you, your project might
falsely be considered unmaintained.
Thanks to all in advance for your support in this activity!
COVESA - The Connected Vehicle Systems Alliance