Feature development tracker
The core developers are unlikely to step through solutions outside paid support, but if you can phrase questions in a general way and lots of people vote them up, the chance goes up a tutorial could be made at some point.
- Complex written tutorials take about an hour to make.
- Step-through videos take about 5 times longer to make than they are in length, e.g. a 12 minute video would take about 1 hour to make.
How is Composr developed?Composr is a community project, with ocProducts Ltd ensuring a balanced quality product is delivered for free to all users. Most core developers work directly for ocProducts Ltd, which was founded out of passion for the project goals and for Open Source, but external contributors are just as welcome.
Development generally moves forward by incorporating advancements made for commercial Composr projects, and features directly sponsored. ocProducts generally spends more time on client work than is directly funded, in order to implement things in a reusable way so that everyone benefits – and each new client benefits from all the work done before.
Before you make requests, it's a good idea to check they aren't already made, and that you are only posting something generic enough to be useful for 15% of users or higher. Be aware that money may be needed in some cases to get traction on things (looks at the stats below to see how much has already been contributed, but why the developers do need to get most future development funded). Ideas are always extremely welcome regardless, even if only for inspiration or to help us all see the path ahead.
The story so far
(The figures above are calculated by Ohloh and represent normal costs from programmers with only average skillz. In most cases we've been smart enough to get things done on more cromulent figures.)See who's getting all the credit
Where do the cost estimates come from?
The hourly development time is estimated, then cost is calculated at the minimum ocProducts Ltd support cost of 33 GBP/hour.
So where does this figure come from?
ocProducts is based in the UK, where the average programmer salary is roughly 38,000 GBP/year (17% less than what programmers in the USA are paid, on average). This is higher than UK average salary due to the amount of advanced education and experience required to become good.
It generally is accepted it costs about 130% salary for a company to maintain an employee (the actual salary, plus office costs, additional tax, insurance, etc).
There are about 235 working days per year in the UK (after taking out weekends and holiday entitlements).
That can be brought to about 220 working days after considering the need for regular training (even if that just means reading blogs and books), sick leave, and various other kinds of regular overhead.
There are 8 working hours per day.
There is only about 80% efficiency in working hours when you consider the fixed costs of maintaining Composr and legal costs (which we seek to spread over a few employees), and variable costs such as hiring, accountancy, preparing and delivering work, negotiation, general management, and normal human things like having chats, going to the toilet and having snack breaks.
38,000 × 1.3 ÷ 8 ÷ 220 ÷ 0.8
That comes down to 35 GBP per hour (a small loss), and that's for a company not seeking to make a profit to grow or to re-pay early-stage R&D investments with ROI. Fortunately we're in a cheaper part of the UK, so the salaries are below national averages, we are passionate about our work, and that we don't normally operate on this bare-minimum rate for the majority of our business.
Now a short rant…
Unfortunately we are regularly asked to work for much less than our rates (few people know how it is calculated and how skilled the work is, and it seems expensive when comparing to other things, especially in today's global economy). Very regularly we are asked to work even for free, or people assume we'll have no life and work evenings and weekends. Sometimes we're fine about this, if it's something we're already passionate about, but in most cases, we're already really over-stretched. We're a professional project, not volunteer run – which is reflected in the quality of Composr.
So I hope it is clear why we have developed quite a tough defensive approach to asking that our rates are met for individual Composr service-requests we receive. It's also hard for us just to make accurate cost estimations for the work we do (we're constantly exposed to risk of not getting paid) and to make sure a flow of work keeps coming in.