Greetings all, I just sent out invitations to github.com/spdx to all users who have commit access to one or more repos on the git.spdx.org repo and are not already a member of github.com/spdx. If you are a committer and are not already a member and did not receive an invitation, please email me.
I will update the permissions to the corresponding repositories once we stop mirroring from git.spdx.org. Gary > -----Original Message----- > From: Philippe Ombredanne [mailto:[email protected]] > Sent: Friday, December 2, 2016 9:33 AM > To: Gary O'Neall > Cc: Kate Stewart; [email protected] > Subject: Re: Using github and not http://git.spdx.org as primary for SPDX > python tools > > On Fri, Dec 2, 2016 at 6:17 PM, <[email protected]> wrote: > > Hi Philippe, > > > > There are a few things we need to do to make the complete transition. > > There are some repos which are on git.spdx.org that need to be moved to > github. > > There are also some users who have commit access to git.spdx.org that > > do not have commit access on github. > > The simplest is to ask their Github username on this list or a private email > and then send an invite. > If they do not reply then this might not be a big issue for them? > > > I am also thinking we may want create some kind of README or pointer > > to github for those still looking at git.spdx.org. Any ideas on what > > to do here would be appreciated. > > This is easy: once the mirroring is removed, I can just push a commit that > explains that the repo has moved to Github in a file called > MOVED_TO_GITHUB_SPDX.txt and in that same commit delete all files (the history > would still have them for the posterity) or just update the README and leave > everything else as-is. > > > For Python, we have the original GSoC student Ahmed with commit access > > - do you think we need to reach out to him to get him access to the > > new repo (I'll need to dig up his email address)? > > Ahmed has been quiet for a while so I would not bother. > If he shows up we can grant him access or his github user is ah450 so you > could send an invite too. > But since he not active it might be best to just do nothing until he wakes up. > > > Kate and Philippe - > > > > We can probably move things incrementally - python and SPDX tools > > first since they are already setup with all committers on github with > > the possible exception of Ahmed. Any reason to wait on these to > > repos? Philippe or I should be able to disable the mirroring. I > > would then remove all commit access on SPDX.org to prevent any accidental > commits. > > This works for me alright. > > You should go head with the the Go tools too and grant me access on Github as > I mentored the initial contribution. There will be some minor issues with Go > import namespacing but they will be easy enough to fix. > > -- > Cordially > Philippe Ombredanne > > +1 650 799 0949 | [email protected] > DejaCode : What's in your code?! at http://www.dejacode.com nexB Inc. at > http://www.nexb.com _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
