All of a sudden my RW access to the website got removed. Can this be reinstated please. Thanks.
On Sat, Jul 9, 2016 at 2:40 PM, Michael Cullum <m...@michaelcullum.com> wrote: > Hi all, > > I've just done a bit of updating with regards to github permissions. Those > who should have access to things (Ping me if you don't): > > > - Every Draft or Review PSR has it's sponsor, editor and coordinator > with write access to php-fig/fig-standards, so long as they are voting > representatives > - We have a website team consisting presently of just Jonathan Reinink > who has access to the website. At the moment this is more of a > discretionary thing for people contributing a lot to the website such as > Jonathan who wrote our current site and helps us [secretaries] out > regularly with frontend and jekyll stuff. > - Secretaries are owners > - Relevant PSR-teams have push access to any particular repos > concerning their PSR e.g. the log and cache interface repos. > > > Should you ever wish to mention PSR's working group [past or present] or > the like, all teams are public and @mention-able by their PSR number e.g. > @php-fig/psr-5 or @php-fig/secretaries. > > I'd also like to extend the privilege of access to php-fig/fig-standards > write access to editors who have been around for a while [around in member > projects, the FIG or the PHP Community], are trusted but are not voting > representatives (e.g. Woody, Matthieu, David and Michael). As the editor > they have (as per the bylaws) the final yes/no for what goes into their > specifications so not giving them push access seems a little odd. All > branches are protected anyway so they cannot force push and any rouge > commits would be noticed very quickly so I see little risk. It would also > increase the usefulness of @mention'ing the teams of PRs as it would always > include the Editor. Are there any objections to this? > > Finally, but most importantly, just a regular reminder to those with > access, and to those just receiving access,* please only ever merge > changes which only concern your own [draft stage] PSR*; any merges to > approved PSRs [typos], the index, licenses or to other PSRs (when the WG is > unable to do so) should be left to secretaries (feel free to highlight us > with @php-fig/secretaries if you feel we've missed something). > > -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to php-fig+unsubscr...@googlegroups.com. > To post to this group, send email to php-fig@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/4d12fd38-bbf5-4163-832e-b3656b083914%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/4d12fd38-bbf5-4163-832e-b3656b083914%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAKxcST_2gDqFrPDsaeW3pgjo2GYSiXV3xg%2BdR5dj-YrDxG8QxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
