1. Sorry! That was honestly the best slide you’re going to see in this talk.
4. Usage Statistics
5. What do we use jQuery for?• Used across Aol for cross-browser DOM manipulation, animation & effects.• Occasionally combined with projects like Backbone, JMVC, KnockoutJS etc.• We use it in Agora,VIVAD and other projects
6. What does the project offer?• jQuery (core)• jQueryUI• jQuery Mobile• Sizzle• QUnit
7. Some interesting facts• jQuery is now almost completely community-driven.• John Resig is still actively involved in managing releases, project direction.• Some businesses provide OSS hours to staff just to work on projects like jQuery (eg. Bocoup)
8. Organisation structure• Executive board• Voting members - primarily U.S based, handle voting on donation fund usage• Sub-teams - Developers that: • Write patches for core • Review bugs/triage and document • Design, handle operations and more.
9. My involvement• Core bug triage team• API/Documentation team• jQuery Learning site team• Evangelism & Teaching
10. Bug Triage • Evaluate jQuery core bugs based on merit. Put together test cases if needed • Establish whether breakage is due to a recent change and if so what • Cross-browser test to conﬁrm which browsers are effected • Discuss issues with team • If possible, suggest patches
11. Team achievements • Churned through 10-15 tickets a day for jQuery 1.4.3 • For 1.4.4 - 1.5.2 we heavily worked to keep this pace up • It’s now rare that a ticket isn’t reviewed within 2 days of submission (1.7)
12. Voting on features • Done before work is begun on a new major version • Community interested in HTML5 support, modular builds & more
13. Pros of getting involved• Lets you give something ‘back’ to the community• Contributing encourages you to ﬁll in gaps in your knowledge• Great way to learn and get to vote on features before they land in a release• Opportunity to learn how a large open- source project works day to day
14. Challenges• Time - how do you get involved around work? isn’t it difﬁcult?• How to spread yourself across projects• Time-zones - if they’re based in the U.S. How do you make that work for you?
15. More Challenges• Consistent availability - Do OSS projects care?• Paid work vs open-source work - do you consider the opportunity enough?• Level of skill - important to ensure you know what you’re doing.
16. Conclusions• There are 100s of really interesting OSS projects out there• You *don’t* need to have hours of free time each week to get involved. Just knowledge and an interest.• Give it a try! It’s worth the experience and the community loves all the help it can get.