I suggest add/remove collaborators is always done as a distinct PR that
ONLY adds/removes collaborators.

That eliminates a need for redundant emails to this list that are no
different than the PR itself.

On Wed, Mar 22, 2023 at 12:41 PM Steve Lawrence <[email protected]>
wrote:

> Since this only grants access to GitHub issues and wiki (is that true?),
> maybe we follow a similar policy that we use for Jira or Confluence?
> Which is users just ask on the dev list and provide their username, and
> then a comitter/PMC can grant the access. In this case granting the
> access is via a code change/PR instead of a config change.
>
> I'm not sure it needs to be any more complex than that, but I think it's
> good to require the requests be done publicly so others are aware when
> access changes are made.
>
>
> On 2023-03-22 12:30 PM, Shearer, Davin wrote:
> > There is a file called .asf.yaml that has a stanza where collaborators
> can be added (or removed).   Since updates to .asf.yaml requires review by
> at least 2 other Apache members before merging into main, is that
> sufficient, or are there additional requirements for adding collaborators
> aside from the 2 green checks and the merge?  Do we need any other rules
> beyond that?
> >
> > Thanks!
> >
> > Davin Shearer
> > Senior Principal Engineer
> > Concurrent Technologies Corporation (CTC)
> > 8539 Corridor Drive
> > Savage, MD 20763
> > Office: (301) 543-3905
> > [email protected]<mailto:[email protected]>
> > [cid110391*[email protected]]
> >
> > www.ctc.com<http://www.ctc.com/>
> [cid110391*[email protected]] <
> https://facebook.com/ConcurrentTechnologiesCorporation>
> [cid110391*[email protected]] <
> https://www.linkedin.com/company/concurrent-technologies-corporation>
> [cid110391*[email protected]] <
> https://twitter.com/ConcurrentTech>
> [cid110391*[email protected]] <
> https://www.youtube.com/c/ConcurrentTechnologiesCorporation>
> >
> >
> > -----------------------------------------------------------------
> > This message and any files transmitted within are intended
> > solely for the addressee or its representative and may contain
> > company proprietary information.  If you are not the intended
> > recipient, notify the sender immediately and delete this
> > message.  Publication, reproduction, forwarding, or content
> > disclosure is prohibited without the consent of the original
> > sender and may be unlawful.
> >
> > Concurrent Technologies Corporation and its Affiliates.
> > www.ctc.com  1-800-282-4392
> > -----------------------------------------------------------------
>
>

Reply via email to