Versions Compared

Old Version 1

changes.mady.by.user Jeremiah Foster

Saved on

compared with

New Version 2

changes.mady.by.user Gunnar Andersson (old account, disabled)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: A few spelling fixes and clarify public membership

...

The target date is to be fully migrated from our current repo to the new GitHub by July 1st 2016 and it looks like we can make that target. Lot's Lots of folks are involved and many repos have been migrated. The process is fairly easy, with some caveats of course. You can follow this issue tracker for more recent status.

...

These repos are going to get mirrored on a new server. That work has begun with the installation of equipment in JLR's Portland facility and the hiring of a dedicated GENIVI IT person. That person will be joining the Tools Team meetings so you can send questions to the Tools Team should you have them, though hopefully I can answer questions here as well. The repos will be switched to "read only" so that we do not get updates to separate git repos. New development should happen at GitHub, the old repos remain only to provide a link that provides source code for older versions of the GENIVI Compliance Specification and for convenience for automated software builds. As we turn the git repos from write to read only, we'll also be deactivating the public ssh keys associated with the accounts on the repositories. This is for security purposes.

How do we mark

...

GitHub projects as being part of GENIVI?

When repos are put onto GENIVI's GitHub account they automatically become part of the GENIVI GitHub space as it were. This is reflected in the URL for example, as well as other places: https://github.com/GENIVI/capic-poc Everything under https://github.com/GENIVI/ is part of GENIVI. 

...

It might be nice if you made your membership in the GENIVI GitHub account organization 'public'  – currently they're all private which makes them invisible to team non-members. – it is by default private when you are added as a member in the GENIVI Organization in GitHub.  Making the association public makes your belonging to GENIVI visible on your personal GitHub page.  Also, adding two factor authentication is a good idea for protecting both your account and GENIVI. Add an avatar as well to easily identify contributors.