Begin forwarded message:From: John Malconian <malc@indexdata.com>Subject: Re: Fwd: Today's AgendaDate: July 19, 2018 at 11:05:28 AM EDTTo: Mike Gorrell <mdg@indexdata.com>Cc: Jakub Skoczen <jakub@indexdata.com>(CC'ed Jakub in case he something to add)
There is no real formal documented process around this. Also, I removed the Frontside employee's access (he had access to four repositories).
I'm stingy about adding folks to folio-org and granting write access to repositories. It's typically done on an "as needed" basis. By default, folio-org members can create new repos (but not delete them) and have read access to all repos. Membership is typically granted to ID, OLE, and third-parties contracted to work on this project - Frontside, Stacks, Qulto, EPAM, etc. Further breakdown of write access to individual repositories is as follows:
The "stripes" team which consists of ID and OLE members with a couple of outliers including some key folks from EBSCO. They are given access to all Stripes/UI related projects. I may have also made an exception for Charles from Frontside.
"'foliodev-core" team which consists of ID and OLE members and some key contributors from EBSCO. They are given write access to all backend FOLIO modules.
There is an 'okapi' team which is given write access to the Okapi repo. This team consists of only a handful of people.
Third-parties like Frontside, Stacks, Qulto, EBSCO, EPAM, etc have their own teams and are given write access to repos on an as-needed basis or on a repo-by-repo basis, sometimes as individual accounts rather than entire team access.
There are other teams like 'DevOps' and so forth but the one listed above are the major ones.
John
On 7/19/18 7:17 AM, Mike Gorrell wrote:
John, is there a document somewhere that lists how our permissions to Github work for FOLIO? If not, is it “simple” enough to explain to me?
-mdg
Begin forwarded message:
From: Jakub Skoczen <jakub@indexdata.com>
Subject: Re: Today's Agenda
Date: July 19, 2018 at 7:12:40 AM EDT
We should revoke his membership in groups that have direct write access to FOLIO repos. He is of course welcome to continue contributing through a standard GH model (fork + PR). Do you know his nickname?
On Wed, Jul 18, 2018 at 4:29 PM Mark Veksler <mveksler@ebsco.com> wrote:
sort of a last minute request... but ( could we also talk about what to do with terminated employees who worked on FOLIO and have github access. SHould it be revoked or not? Scratching my head since its an open source project and, in theory, they should retain their access whether they are terminated or not?
In case you're wondering, it was a Frontside employee who was terminated.
On 7/18/18, 10:04 AM, "tech-council@ole-lists.openlibraryfoundation.org on behalf of Mike Gorrell" <tech-council@ole-lists.openlibraryfoundation.org on behalf of mdg@indexdata.com> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Please see today’s agenda. We won’t have Jakub in attendance, FYI.
https://wiki.folio.org/display/TC/20180718+-+July+18%2C+2018+-+Technical+Council+Meeting+Notes
-mdg
To unsubscribe from this list please go to http://archives.simplelists.com
To unsubscribe from this list please go to http://archives.simplelists.com
--
--Regards,Jakub SkoczenTo unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=SeK0ArgpLZB2ijVHc1q8eivZ4CXy8J2w