Sustainable open source contributions in your business
summary
Company policy sets 32 billable hours so one weekday is reserved for nonbillable work and explicit rules like the 20% rule let teams spend one day a week on maintenance, docs and bug fixes; engineers contribute to concrete projects such as phpunit and phpdocumentor, run events (Wecamp, conference.online) and invoice higher rates so four billable days pay for the fifth. Success requires full stakeholder buy in, realistic pricing and reserves; without those contributions stop when sales demand full capacity.
AI-written summary · about
chapters (4)
related talks
44mSustainable open source contributions in your business
40mSustainable open source contributions in your business
23mOpen Source Contribution Policies that Don't Suck
49mOpen Source At Work - How Contribute On The Clock
22mDaunting to Doable: How Institutions can encourage Open Source Contributions
32mOpen Source: When Nights & Weekends Are Not Enough
25mOpen Source Corporate Sustainability – Models to Consider
41mHow Your Company Can Help Sustain Open Source
