Its one thing to put some code out there, its another thing to get ongoing contributions.Here’s what I’ve learned.
Self-employed for almost two yearsIntroduce selfThanks for inviting to speakSummary…Aim of this talk is to inform you where the ecommerce module is at and give 3 thoughts on working with others on an open source project.
When there’s a bit of interest in a project, someone needs to take the initiative.Encourage people to take the lead.
Modifiers include: tax, shipping, discount
To come:Product reviewsElectronic productsAudit logs
It has been a joy to work with Nicolaas on the projects. I haven’t even met him in person yet!
GitHub or It helps to talk things through over the phone.Google group helps us to resolve things we can’t resolve ourselves.Reqests on forum and from clients get turned into issues on google.
Downsides: discussion takes time, but you can document
Most of this is still under development.Other notable changes:
Making the most of SilverStripe’s strengths.Definitely still on our way there, and appreciate all the help we can get.
Not everything works :S we’re still essentially in beta, and badly wanting to change that.Improvingpayment module
We want more people to be involved to help the project progress.This will vary from project to project.Other people will follow your lead.Ask for code – people may not realise you want their contributions.
We don’t claim to be ecommerce gurus, and welcome the input of those who have been there before.
Why you might consider contributing to an open source project.It may not always work out like that = troll sceince.Open source = money, fun, happiness.
We encourage you to try these out. We’ll be watching their progress to get ideas.
SilverStripe and ecommerce
Jeremy Shipman<br />SilverStripeeCommerceModule<br />
Who am I?<br />Jeremy Shipman<br />Ex-Silverstripe employee<br />Self-employed website developer as ‘Burnbright Websites’<br />Aka ‘Jedateach’ on forums/IRC<br />Twitter: @burnbrightweb<br />
History<br />Built and maintained by SilverStripe<br />Long period of little/no development activity<br />Adopted into the community June 2010<br />Ongoing work since<br />
1. Leadership required<br />Take ownership<br />Manage the project<br />Delegate work to others<br />You don't need to be an expert<br />
The “Team”<br />Primary Maintainers:<br />Jeremy Shipman<br />NicolaasFrancken<br />Other contributions from:<br />Sean Harvey, Romain Louis, IvoBathke, Tony Culshaw<br />Forum posters, dev group participants, ecommerce users<br />
How we’re maintaining it<br />Code + docs + issues on google project<br />Regular contact via Google Talk<br />Used on client projects<br />Monitoring forum discussion<br />Google group discussion<br />
Future plans<br />1.0 …get out of beta!<br />Complete user/dev documentation<br />Unit tests<br />More modules, and payment gateways<br />Out-of-the-box installation<br />SS3<br />
3. Break down barriers to involvement<br />Answer questions – emails, forums<br />Help with problems<br />Provide adequate documentation<br />Don’t worry about giving SVN access<br />Thank for contributions, however small<br />Keep the open source code open source<br />Make it easy to demo, install<br />Ask for code<br />
How you can help<br />Tell us what to do: provide expertise<br />Test the latest code and give feedback<br />Submit feature ideas, issues, patches<br />Write documentation & tests<br />Translation<br />Build sub-modules<br />
You contribute to the project = fun <br />Project needs changes/improvements<br />Project improves = good for everyone<br />Fun, Happiness, and Money!<br />You get work = $$$<br />People recognise your contribution / expertise = happy <br />
Summary<br />Open source needs leadership<br />Working together has valuable benefits<br />Break down barriers to involvement<br />