On 01/16/2013 06:05 AM, Victor Berchet wrote:
There are two major things that IMO can be improved here:
- define plans - this has been discussed before in the serie[6] and
above so I won't discuss it again,
- have a better predictability on the available development resources
- As Fabien said[7]: "How would you put a plan together without
knowing who will be able to help? That sounds impossible to me"
Fabien is true, most Symfony contributors are volunteer who submit PRs
on an availability basis and it makes putting a plan together very hard.
This is a problem of any open source project; it's a big one for Drupal
where we have lots of cats going in different directions who don't like
to be herded. :-) Drupal 8 is the first release we've had anything even
resembling quasi-formal roadmaps, and the results have been... mixed.
One solution that should be worth exploring is to create a "Symfony
association" - Typo3[8] and Drupal[9] have such associations. The goal
of the association would be to do some fund raising in order to be
able to hire some developers to work on the Symfony framework - I
don't exactly know the goal of either the Typo3 or Drupal associations
but I would like to hear form them.
It could be more than fund raising only. The association should accept
donations from individuals or companies (same as the different levels
of membership on the Typo3 association homepage) or ask "big" users to
have some part-time dedicated resources working on some important
features / fixes / documentation chapters.
To be clear, the Drupal Association does not direct, manage, or
influence Drupal development. It supports the community in doing so by
holding events, keeping the servers and website running, etc. Its bylaws
expressly forbid hiring devs to work on Drupal. It does employ people
to work on Drupal.org, who in the course of such work often work on
modules that are publicly available, but that's no different than any
other Drupal-using site. What you propose here has been discussed from
time to time in the Drupal community, but always in the context of
someone other than the Drupal Association doing it, and it's never
really come to anything.
There are a number of Drupal companies that have people that work either
part time or full time on Drupal or certain contributed modules, but
those are by far the exception. Acquia is the most notable of them, but
not the only, and Acquia's position in Drupal is not the same as
Sensio's position in Symfony. It's the biggest fish in the pond, not
the fish that runs the pond.
Disclaimer: I am currently an Advisor to the Drupal Association, after
spending about 4 years on the Board of Directors.
I cannot speak for the Typo3 Association as I've never worked with them.
--Larry Garfield
--
--
If you want to report a vulnerability issue on Symfony, please read the
procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
