I nominate Margaret Staples for another Secretary term, if she's willing. CRB
On Mon, Apr 8, 2019, 05:56 Alessandro Lai <alessandro.la...@gmail.com> wrote: > Hello everyone, > May is approaching, and since it's the designated month for the next > election cycle, we need to get started on nominations! > > This time we have 5 seats up which are expiring: > > Secretary: > - Margaret Staples (@dead_lugosi) > > Core Committee: > - Beau Simensen (@beausimensen) > - Larry Garfield (@Crell) > - Matthew Weier O’Phinney (@mwop) > - Sara Golemon (@SaraMG) > > We also have one CC member who wants to step down, Lukas Kahwe Smith, due > to lack of time to dedicate to the role. > > I would like to take the chance to thank all of them for their help and > work inside the PHP-FIG during their terms. Thank you! > > ==================== > > Ok, now it's nominations time! If you are willing to step up for this > election cycle, even for those that are seeking to be re-elected, please > seek a nomination as required by our bylaws: > https://www.php-fig.org/bylaws/elections-and-vacancies/#nomination > > If you're interested but you want more details on the roles, look up to > the bylaws and feel free to contact one of the secretaries or the current > CC members. > *Anyone can be nominated*, including the five persons with expiring > terms, any Secretaries or project representatives, or any person which > would like to be more involved with the FIG. > *ONLY Member projects and Secretaries may nominate*, without any limit, > to be CC or Secretary candidates. > > *Nominations close on May 5th at 23:59 UTC.* > > *FAQs:* > > *What does the role of a CC member entail?* > To quote the Bylaws: > > “The Core Committee is a twelve (12) member board of individuals > recognized for their technical skill and expertise. The Core Committee is > responsible for final decisions regarding what specifications PHP-FIG will > consider and those that are approved. The Core Committee is responsible for > ensuring a high level of quality and consistency amongst all published > specifications, and that all relevant perspectives and use cases are given > due consideration.” > > The core committee acts as a steering group and handles all entrance votes > and, after being completed by working groups, has the final acceptance vote > on new PSRs and is responsible for making sure specifications meet the > technical direction of the PHP-FIG, are of good quality, and have taken > relevant stakeholders into account. The core committee is expected to be > able to keep an eye on what is going on in the PHP-FIG. While this doesn't > mean reading every mailing list post or every GitHub issue, this does mean > having a general awareness of what is going on and regular activity is > expected (e.g. they should be voting on every core committee two-week vote > unless there are particular circumstances preventing them from doing so). > > > *What does the role of a Secretary entail?* > The full role can be read from the bylaws here: > http://www.php-fig.org/bylaws/mission-and-structure/#secretaries > > Between the three secretaries they handle all the administration that goes > on with the FIG such as votes, the website, GitHub as well as also being > responsible for moderation of FIG mediums and representing the PHP-FIG to > the wider PHP community. Feel free to reach out to any of the seating > Secretaries if you would like to know more about the role. > > > *What does a Core Committee member look like?* > The idea of the core committee is that it should reflect a cross section > of the PHP ecosystem and community. > > This means it's important to have a range of people including (but not > requiring or limited to) those with experience relating to things such as: > - Large & small framework maintenance > - Library maintenance > - Consumer package maintenance (by consumer package I mean CMS, blogs, > forums, etc.) > - HTTP and non-HTTP based PHP > - Legacy and modern projects > - PHP internals > - Specific topics such as Async and Security > > However, it is important to note that you are voting for people, not > projects, so please do not vote in people because they are the lead on > 'Project X'; but rather you might vote for them because they have > experience as a framework maintainer or legacy project maintainer and > therefore have a different view on things. CC members should be > representing the opinion of the wider PHP ecosystem and community as CC > members, not of projects they are affiliated with, and some will likely not > be affiliated with any project at all. Furthermore, this should not become > a popularity contest of 'who is the most well known' but who would make the > most well-balanced core committee that accurately represents the interests > of you, the member projects and wider PHP community. > > > *What's the timetable?* > April 8th: Nominations open > May 5th: Nominations close > May 6th: Election voting begins > May 19th: voting ends > May 26th: new CC members and new Secretary take post > > *Election Process Summary* > After nominations close then voting will start. Votes are expressed as an > ordered list, not as single votes, so you don't have to pick a single > favorite, but just rate in order of your preference. Member projects can > vote, as can any community member judged to have participated actively in > the FIG (there are subjective and objective tests for this in the bylaws, > which will be taken care of by the seating Secretaries). After the voting > closes and results are officially announced by me, the newly elected will > take post. Voting is done through STV, as per our bylaws. > > For more information please read the bylaws or the FIG 3.0 TL;DR. > > Thanks! > > Alessandro Lai > PHP-FIG Secretary > > -- > 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/27b3aa8d-886b-478d-a067-5fba78373a64%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/27b3aa8d-886b-478d-a067-5fba78373a64%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/CANsgjnsmd90BG5xA_GSXzw4YFi8o1qg94wqwgCTSe%2BXq6zf20Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
