Skip to content

Latest commit

 

History

History
71 lines (52 loc) · 3.23 KB

index.md

File metadata and controls

71 lines (52 loc) · 3.23 KB
layout title
default
FriendsOfSymfony

FriendsOfSymfony

FriendsOfSymfony started as a group of people collaborating on the knpLabs UserBundle that felt it would be nice to have a vendor namespace to use for this and future Bundles that are maintained together, which has since led to the creation of several popular Bundles.

How do I get in touch?

Several of us hang out in the #symfony IRC channel on freenode. There is also the [email protected]. Finally if you want to ask for a vote (for example to propose a new topic) create a ticket on the friendsofsymfony.github.com repository

I want to join!

Generally we are open to anyone joining if there is enough overlap in interest with the other members. The point is to enable collaboration among most of the members.

If there isn't enough overlap with the existing members, just create a new vendor namespace and invite others to join.

Also the idea is to keep the numbers of members somewhat manageable so that its easy to keep everyone in the loop so that there is no need to have complex organizational structures.

Again vendor namespaces are free, so no reason to create complexity by trying to do everything in one vendor namespace, after all then there wouldn't be a need for vendor namespaces to begin with.

So this is some sort of elitist club?

Not at all. Again keeping the number of members small is just for practical purposes not because we want to exclude others or lack respect for other developers.

Actually we do expect that other vendor namespaces will appear with their own way of working and their own focus topics which some of us will want to join as well.

We love collaboration! :)

So are there any rules?

Not many and really the idea is to just talk to all the other members when in doubt and get agreement.

  • New Bundles should be relevant for at least half of the existing members
  • Adding a Bundle means that you are ok with all members messing with it
  • Obvious stuff can be committed without review
  • Non obvious stuff should try to get review from at least one more member
  • Try to use feature branches for larger changes

Slides