2011/6/23 Larry Garfield <la...@garfieldtech.com>: > I agree that part is uncomfortably vague. To use me as an example, I've > been on this list for a few years, post periodically but not > super-frequently, and haven't written any C code for PHP itself. However, > I'm one of only two people from the Drupal project I know of on this list. > While I'm not the project lead (he isn't on this list), I'm one of the > leading developers, such as it is in an amorphous project like Drupal. That > probably makes me the closest there is to a Drupal "representative" to this > list, given that Drupal doesn't officialize much of anything. :-) > > I'm sure there are other projects with a vested interest whose people don't > know C well enough to engage in most conversations on this frequently busy > list. So... would we get a say or not? :-) > > --Larry Garfield > > On 06/21/2011 03:52 PM, Pierre Joye wrote: >> >> We thought there was no need to over regulate this part. >> >> It is something like mentors, if you just come in, post a couple of >> times or daily but nobody can second you and you lead zero OSS >> project, then the chance that you can vote will be rather low. Your >> option? Contribute! :-) >> >> On Tue, Jun 21, 2011 at 5:57 PM, Arvids Godjuks >> <arvids.godj...@gmail.com> wrote: >>> >>> That really neads clearing, because if i understand correctly, I should >>> get >>> ability to vote (userland developer activly reading the list and writing >>> to >>> list on some maters). So the question - do i get a vote ability? :-) >>> 21.06.2011 17:36 пользователь "Philip Olson"<phi...@roshambo.org> >>> написал:
Whilst it may be democratic to allow 1 person 1 vote, I would honestly hope that my vote, as a non-core developer, would count less then say, Zeev or Rasmus. Simply because my bread and butter is NOT in the core and my understanding of the finer points may (and in all honestly will be) lost to me. Until I can prove to the community a clear understanding and provable technical ability to affect core without completely breaking everything, then it would be unfair to "pollute" the vote, but my vote should still be recorded at a secondary level. Maybe as an interested party. The main vote has to be amongst those capable of effecting the change. At least in principle by having php-src karma if a major language change or pecl karma for pecl+core related changes. Maybe there should be some different voting criteria, or the ability to create a specific voting criteria per vote. Internal only (something that won't affect userland code - a new memory manager or a significant change in internal mechanisms) Affects PECL (a change in the core that will have an impact on multiple PECL extensions) Userland Change (something that will alter an existing feature - obviously, this could be a BC). Userland Enhancement / New Feature (something that will work in a new version of PHP - possible name collision to existing userland code). -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
