Thanks for the quick reply and action Raúl. I'm also very happy to help craft such a document. I know that the need and use of being on the ursacomputing org is limited, since the comment bot generally works well, but it still would be nice to have something like that.
Thank you again! -Jon On Tue, May 28, 2024 at 11:22 AM Raúl Cumplido <raulcumpl...@gmail.com> wrote: > Hi Jon, > > From my understanding we currently don't have a written policy for > accessing the crossbow repository but PMCs should be allowed to > request access for them and/or committers. > > I had to ask what happened with your access. It seems it was a mistake > when someone was doing some cleanup on some user accesses. > > In order to avoid those things from happening in the future I will > work on a proposal to have a written policy about how to request > access and when access is removed. > > Regards, > Raúl > > El sáb, 25 may 2024 a las 2:02, Jonathan Keane (<jke...@gmail.com>) > escribió: > > > > Over my time with the project I've had access to the github repository > > ursacomputing/crossbow to be able to manually trigger crossbow jobs. I > find > > it incredibly helpful when working on the extended R CI to be able to > > iterate more quickly than waiting for the comment bot. > > > > But also over the time I've used it I've been removed and then had to ask > > to be readded to the organization at least twice now. > > > > I was recently (15 May) removed from the organization once again. One, is > > it possible to be added back to the repository? And two: what is the > policy > > around who has access and when they get removed? > > > > -Jon >
