We are pleased to announce the addition of Jorge Calas Lozano to the core team. Here at the Spree project we all call him Calás because that is user name in IRC. Calás has been contributing to the Spree projects since the very early days. He is responsible for much of the early work in making Spree i18n friendly using the Globalite plugin and many other related improvements. Calás has rejoined the Spree project recently and has been providing a ton of great fixes and patches. He’s also now a full time member of the Rails Dog team so we’re going to keep him busy on Spree work 24/7.
This is probably also a good opportunity to talk a bit about the criteria for becoming a core member.
- Sustained Commitment to the General Project – Core members need to demonstrate a commitment to the overall well being of the project (not just fixing or contributing in areas that are specific to their needs.) Examples of this include: Answering questions on #spree and spree-user, contributing/fixing documentation and helping with releases. We also look for members whose interest lasts beyond a short period of time. Lots of people contribute actively to Spree for a month or two and then fade away. That’s certainly fine – we appreciate all levels of contribution. Core members, however, tend to stick around for longer.
- Demonstrated Communication and Decision Making Skills – Spree is now a very big project with hundreds of real world deployments. It is important that major changes to Spree are only done after consultation with other core members and the community. Core members will be presented with all sorts of patches and feature enhancements. They need to be able to ask themselves if this represents a major change to how things are done in the current code. We have a pretty good system for making these kinds of decisions already, new core members need to become familiar with how these kinds of decisions are made and learn to make the same types of judgements as the existing core team.
- Treat Other Community Members with Respect – Treating people with respect is probably the most important of all the rules. I list it last only because it should be obvious and its also relatively easy to do. The power of open source comes is in the collective efforts of the community. Everyone’s ideas and work should be treated with respect.
Much of the core team now works for Rails Dog. Working for our company is not a requirement for core team membership, nor does it ensure that you will be offered membership. We have over ten different people working for Rails Dog right now and only four of them are on the core team.
Hopefully this clears up any questions people might have as to how the project is run and how these decisions are made.