[Internals] Secretary & 4 Core Committee Nominations Open
Alessandro Lai
Hi all,
The nominations for 4 Core Committee seats and one Secretary position are open; sorry for the delay of this announcement, but I was away from a keyboard for the holidays, and I'm excited to perform my first official duty as a Secretary! I would also like to take the time to thank Michael (whose term as a Secretary is now ending) for such a speedy onboarding for us two newly elected Secretaries, and for the enormous work that he has accomplished in the last two years in our transition to the FIG 3.0. Thanks also to the four CC members whose terms are ending also.
Below are some practical details and FAQs.
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.
If you would like to nominate someone, please get in touch with them and speak with them about it first. But please do actively seek out people you think should be on the Core Committee to nominate them, don't wait for them to ask you to nominate them.
If you would like to stand/accept a nomination, please contact the seating secretaries (me, Michael or Margaret) to find out a bit about what the relative role entails. You may seek a nomination any way you wish (requesting on the mailing list, asking individuals in private, etc.).
A list of nominees will be maintained here . Remember that the nomination must be accepted to be valid, so please ensure that you confirm your nomination if you wish to and someone nominates you.
Nominations close on the 11th January 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 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 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 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?
1st January: Nominations open
11th January: Nominations close
12th January: Election voting begins
26th January: voting ends
28th January: 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.
Alessandro Lai
Stefano Torresi
As I feel I can still give valuable contributions to the processes that will produce current and future proposals, I'd like to stand for re-election as a member of the Core Committee.
I hope the group will accept my re-candidacy.
Cheers, and happy 2018!
Last but not least, spread the word! Please retweet this: https://twitter.com/phpfig/status/947969054043762689 and actively search people that could be nominated!
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/e31ec564-c79b-48aa-bcba-037e14278263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Alessandro Lai
Il giorno martedì 2 gennaio 2018 00:11:02 UTC+1, Alessandro Lai ha scritto:
Chris Tankersley
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/632d1e9c-1868-4f80-9674-31a70eab7d6c%40googlegroups.com.
Ben Marks
Chris Tankersley
I am glad to say that I am Chris Tankersley’s sponsor on behalf of Magento.
--
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+unsubscribe@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/3464af7e-f076-4c14-9fb0-a9ed1c74fdae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.