[Secretary nomination] Michael Cullum

[Larry Garfield]

I hereby nominate Michael Cullum (m...@michaelcullum.com) for the position
of FIG Secretary.

Michael has been an active participant in FIG for years, moreso than
many of our voting representatives. :-) He until recently was the
editor of PSR-12. Previously, he started and for a time maintained an
index of all past FIG votes and who voted what, entirely as a
volunteer. That's the sort of pedantic record keeping that I want to
see in the Secretary's seat.

--
--Larry Garfield

[Michael Cullum]

Thanks for the nomination Larry. After a brief IRC discussion about how to handle nominations those present thought it would make sense for posted nominations to be 'accepted' by the nominee then confirmed by the person running the election (Korvin in this instance) so leading on from that so I this email can be considered my accepting of the nomination.

A quick word about me for those of you who don't know me. As Larry said I've been involved with the FIG for varying degrees for a number of years now and I did used to maintain a large sheet of the all the voting (You can still view it here: https://goo.gl/pn67Jv). More recently I've been involved as editor of PSR-12 and I've also helped out with numerous other efforts to clean things up (including bylaw revisions) such as the recent translation vote and writing up the changes discussed at various conferences into the bylaws for the introduction of this position. Outside of the FIG I recently founded a PHP User Group, am an organiser of the PHP South Coast Conference and I work on phpBB. If you'd like to know more about me or have any questions then please don't hesitate to drop me an email directly, tweet to me (I've put a link in my email signature of this email) or of course ask here.

Thanks!

--

Michael C

https://twitter.com/michaelcullumuk

--
--Larry Garfield

--
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/568AF6B8.7050502%40garfieldtech.com.
For more options, visit https://groups.google.com/d/optout.

[Paul M. Jones]

> On Jan 4, 2016, at 17:37, Michael Cullum <m...@michaelcullum.com> wrote:
>
> Thanks for the nomination Larry. After a brief IRC discussion about how to handle nominations those present thought it would make sense for posted nominations to be 'accepted' by the nominee then confirmed by the person running the election (Korvin in this instance) so leading on from that so I this email can be considered my accepting of the nomination.

Cullum appears to be against freedom of speech, and as such is unsuitable for this position. His neutrality is suspect.



--
Paul M. Jones
pmjo...@gmail.com
http://paul-m-jones.com

Modernizing Legacy Applications in PHP
https://leanpub.com/mlaphp

Solving the N+1 Problem in PHP
https://leanpub.com/sn1php

[Christopher Pitt]

Paul, not everyone can tell when you're joking. This runs the risk of distracting from the point of this topic.

[Paul M. Jones]

> On Jan 4, 2016, at 21:10, Christopher Pitt <cgp...@gmail.com> wrote:
>
> Paul, not everyone can tell when you're joking. This runs the risk of distracting from the point of this topic.

Not joking. Cullum needs to learn what it means to be "the offender" and presumed guilty. Cf. the contemptible code-of-conduct RFC, and his commentary on it here: <http://news.php.net/php.internals/90040>

Apparently he can't bear opposing views, and I am offended.

[Christopher Pitt]

Paul, that is not even remotely applicable to this thread. It's not even a part of the same organisation. Please don't discuss PHP internals stuff here.

[Paul M. Jones]

> On Jan 4, 2016, at 21:50, Christopher Pitt <cgp...@gmail.com> wrote:
>
> Paul, that is not even remotely applicable to this thread. It's not even a part of the same organisation. Please don't discuss PHP internals stuff here.

The COC under consideration apparently applies everywhere. If it gets accepted, get used to it.

[Christopher Pitt]

Be that as it may, the CoC does not enforce the remediation of conflicts to happen outside the organisation adopting the CoC. If the conflict happens between PHP internals members, the conflict is resolved inside PHP internals. Not here or in a court of law or on the moon. It is not yet accepted which makes this doubly irrelevant for discussion here.

Please voice any concerns with the nomination (respectfully if you please) and leave it to the voting members to  cast their votes for the nomination.

I know you as a consummate professional, and implore you to return to that professionalism with regards to this conversation.

[Alexander Makarov]

Count me as +1.

[Gary Hockin]

I'm sorry Paul, I think that you are absolutely out of order in your comments here. You are allowed to disagree with people's views, but you should afford that person the courtesy and respect that you would expect to be extended yourself if someone disagrees with you. Your abrupt tone, use of Michael's surname and general abruptness and rudeness offends me greatly.

I have no desire to turn this whole thread into an argument - you are more than entitled to the opinion, but please, I'm asking you as someone I consider a friend, please be nicer when making your point. This list has no place for this kind of attitude.

Peace Out

G

--
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/BF7DAE2E-CAB7-4DCD-9A3E-5B82CDE21F17%40gmail.com.

[Korvin Szanto]

This nomination has been received.

I just wanted to say that after having the pleasure to work closely with Michael recently, there's no one I'd consider more suited for this position. Michael is a very driven member of the community who has proven that he has a level head and the determination to complete the tasks that he sets out to accomplish. He is pretty much active in every discussion and in my experience is always available and ready to help if you need him. 

A huge +1 for Michael from me and the concrete5 community!

Best wishes,

Korvin

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAAueXOXqH6iYHu%3DFhK9VNXO%3DYVC%3DdkEzn1S0mCAkjVysJWdrPQ%40mail.gmail.com.

[Paul M. Jones]

> On Jan 5, 2016, at 05:52, Gary Hockin <ga...@hock.in> wrote:
>
> I'm sorry Paul, I think that you are absolutely out of order in your comments here.

Seeing as he has apologized for his misuse of the phrase "the offender" regarding the proposed speech code under consideration, I retract my comment.

> You are allowed to disagree with people's views, but you should afford that person the courtesy and respect that you would expect to be extended yourself if someone disagrees with you. Your abrupt tone, use of Michael's surname and general abruptness and rudeness offends me greatly.

Yes, speech-policing is an ugly business. If you didn't like that very gentle example, I hope you would be against the COC as presented; if it passes, it will metastasize to PHP-FIG sooner rather than later.

> I have no desire to turn this whole thread into an argument - you are more than entitled to the opinion, but please, I'm asking you as someone I consider a friend, please be nicer when making your point.

Speech police are not "nice." The COC will give you plenty of them.

> This list has no place for this kind of attitude.

I agree, which is why I hope everyone here is against the COC as presented.

[Christopher Pitt]

Paul, I'm not sure how much more clearly or politely I can request this. PHP-FIG is not the place to discuss PHP internals RFC's. You are derailing a nominations thread with personal grievances and I would kindly request that you stop. I am confident you would tell me to shut up if I started derailing FIG threads with irrelevant grievances about my perceived problems with somebody's framework, or some other problem I have with somebody. 

Let's keep the focus on PHP-FIG in the PHP-FIG mailing list. If we ever get a CoC topic, for PHP-FIG discussion, then it would be appropriate to discuss these things here. Only then.

[William Durand]

I second that.

--

William

On 06 Jan 2016, at 00:52, Christopher Pitt <cgp...@gmail.com> wrote:

Paul, I'm not sure how much more clearly or politely I can request this. PHP-FIG is not the place to discuss PHP internals RFC's. You are derailing a nominations thread with personal grievances and I would kindly request that you stop. I am confident you would tell me to shut up if I started derailing FIG threads with irrelevant grievances about my perceived problems with somebody's framework, or some other problem I have with somebody. 

Let's keep the focus on PHP-FIG in the PHP-FIG mailing list. If we ever get a CoC topic, for PHP-FIG discussion, then it would be appropriate to discuss these things here. Only then.

--

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/04678386-00bf-43e3-9ab1-92de3914f96d%40googlegroups.com.

[Paul M. Jones]

> On Jan 5, 2016, at 17:52, Christopher Pitt <cgp...@gmail.com> wrote:
>
> You are derailing a nominations thread with personal grievances and I would kindly request that you stop.

Ahead of you. I'm done; the example has been presented.

[Andrew Carter]

I've known Michael for a while now and can confirm that he is a very suitable candidate for this position.

His valuable input to this group is obvious to all those who read this mailing list. He also has an in depth working knowledge of the bylaws and processes.

Andrew