Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
7 Lessons learned from running an open source p...
Search
gregbell
April 25, 2012
Technology
3
330
7 Lessons learned from running an open source project.
A 1 minute lightning talk at RailsConf 2012. Seriously 1 minute was way too short.
gregbell
April 25, 2012
Tweet
Share
Other Decks in Technology
See All in Technology
AWS 怖い話 WAF編 @fillz_noh #AWSStartup #AWSStartup_Kansai
fillznoh
0
130
QuickSight SPICE の効果的な運用戦略~S3 + Athena 構成での実践ノウハウ~/quicksight-spice-s3-athena-best-practices
emiki
0
300
AI Ready API ─ AI時代に求められるAPI設計とは?/ AI-Ready API - Designing MCP and APIs in the AI Era
yokawasa
15
4.5k
Autify Company Deck
autifyhq
2
44k
Four Keysから始める信頼性の改善 - SRE NEXT 2025
ozakikota
0
420
MCP とマネージド PaaS で実現する大規模 AI アプリケーションの高速開発
nahokoxxx
1
560
助けて! XからWaylandに移行しないと新しいGNOMEが使えなくなっちゃう 2025-07-12
nobutomurata
2
210
スタックチャン家庭用アシスタントへの道
kanekoh
0
130
(HackFes)米国国防総省のDevSecOpsライフサイクルをAWSのセキュリティサービスとOSSで実現
syoshie
5
490
AIコードアシスタントとiOS開発
jollyjoester
0
180
AWS Well-Architected から考えるオブザーバビリティの勘所 / Considering the Essentials of Observability from AWS Well-Architected
sms_tech
1
550
データ駆動経営の道しるべ:プロダクト開発指標の戦略的活用法
ham0215
2
150
Featured
See All Featured
Rebuilding a faster, lazier Slack
samanthasiow
83
9.1k
Being A Developer After 40
akosma
90
590k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
248
1.3M
The Pragmatic Product Professional
lauravandoore
35
6.7k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
980
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.5k
Git: the NoSQL Database
bkeepers
PRO
430
65k
Visualization
eitanlees
146
16k
RailsConf 2023
tenderlove
30
1.1k
Optimizing for Happiness
mojombo
379
70k
The Art of Programming - Codeland 2020
erikaheidi
54
13k
Testing 201, or: Great Expectations
jmmastey
43
7.6k
Transcript
Lessons learned from running an open source project. 7
@gregbell
None
None
#1: Don’t use this button
#2: Travis is Awesome
#3: Don’t forget Design & User Experience
#4: Depend on Less
Write Half as Many Features and Twice as Much Documentation
#5:
#6: Build a community
#7: Just make it happen