1.
Community Engagement Sander van der Waal Development Officer - OSS Watch http://www.oss-watch.ac.uk [email_address]

2.
Agenda <ul><li>OSS Watch

3.
Engagement with Hadoop

4.
Community

5.
Shameless plug </li></ul>

6.
About OSS Watch http://www.oss-watch.ac.uk

7.
OSS Watch – what we do <ul><li>Advice on all things open source

8.
Services </li><ul><li>Consultancy, events, presentations, community development </li></ul><li>Publications </li><ul><li>Briefing notes, surveys, case studies, blog posts </li></ul><li>Free to UK Higher and Further Education </li></ul>

9.
Engagement with Hadoop How many of you have experienced these issues with Hadoop? <ul><li>Deployment issues

10.
Applying it to a specific use case

11.
Customising locally </li></ul>

12.
Engagement with Hadoop How many of you are engaging with the Hadoop community to solve your problems? <ul><li>Ask on the mailing list

13.
Contribute your solution

14.
Customisation / new functionality </li></ul>

15.
&quot;The real value of open source software is that it allows communities to work together and solve problems&quot; - Irving Wladawsky-Berger, Head of IBM's e-business on demand initiative http://www.itconversations.com/shows/detail495.html Community

16.
Who is this “community”? <ul><li>Users </li><ul><li>Students, researchers , Institutional IT staff, Commercial IT staff </li></ul><li>Contributors </li><ul><li>Students, researchers , Institutional IT staff, Commercial IT staff </li></ul><li>Maintainers </li><ul><li>Students, researchers, Institutional IT staff, Commercial IT staff </li></ul></ul>

17.
Why does this community care? <ul><li>Open source is driven by user need </li><ul><li>Without user feedback the project is blind </li></ul><li>Assisting users ensures the user community expands </li><ul><li>A large user community becomes self supporting </li></ul><li>Some users become contributors

18.
Some contributors become maintainers

19.
Users = sustainability </li></ul>

20.
Long term sustainability <ul><li>It's all about the users </li><ul><li>no users means no contributors

21.
no contributors means no developers

22.
no developers means no development

23.
no development means no future prospect of attracting users </li></ul><li>No users means no business opportunities

24.
No business justification means no development

25.
No users means no project </li></ul>

26.
Engaging with the community Evangelism Requirements Support Bugs Use Documentation Design Code Contribute Strategy Legal Oversight Manage

27.
Community only needs four tools <ul><li>Coordination through collaboration </li><ul><li>Web site </li><ul><ul><li>http://hadoop.apache.org or http://hadoop.a.o/sub_project </li></ul></ul><li>Communication </li><ul><ul><li>Hadoop mailing lists </li></ul></ul><li>Issue Tracker </li><ul><ul><li>http://issues.apache.org/jira/browse/HADOOP </li></ul></ul><li>Version Control </li><ul><ul><li>Publicly accessible Subversion repository </li></ul></ul></ul></ul>

28.
Mailing Lists / Forums <ul><li>Asynchronous (Supports geographic distribution)

29.
Decision making

30.
Problem solving

31.
Support

32.
Project Memory (Archives) </li><ul><li>Don't repeat yourself

33.
Don't forget why a decision was made

34.
Prior art record </li></ul></ul>

35.
Communications (forums / mailing lists) <ul><li>New user support </li><ul><li>Installation

36.
Customisation

37.
Course development

38.
Course delivery </li></ul><li>Developer support </li><ul><li>Design

39.
Implementation </li></ul><li>Maintainers </li><ul><li>Strategy

40.
Legal </li></ul></ul>

41.
Issue Tracker <ul><li>Project planning </li><ul><li>What will be done

42.
What may be done

43.
What will not be done </li></ul></ul><ul><li>IPR management </li><ul><li>Who contributed what </li></ul></ul>

44.
Benefits - Long term sustainability <ul><li>Do you have skill retention plans? </li><ul><li>“We've just lost our team for the second time in a year” </li></ul><li>Do you have local customisations? </li><ul><li>Are they compatible with future version of Hadoop? </li></ul><li>Can you upgrade quickly and cheaply? </li><ul><li>“ we made a decision not to upgrade”

45.
“ we tried to upgrade but....” </li></ul></ul>

46.
Local specialisation <ul><li>Engaging with external community extends and preserves project memory beyond internal staff

47.
Allowing local installations to diverge from new developments can be dangerous

48.
Local customisations should be contributed back

49.
It's cheaper for you and helps secure the future of the project </li></ul>

50.
What about regional communities? <ul><li>Sub-optimal as limited expertise </li><ul><li>May not contain Hadoop committers </li></ul><li>Can be more “comfortable”

51.
Makes physical meetings easier

52.
Can be effective “first level support” </li><ul><li>But be aware of allowing bad practice to go unchecked </li></ul></ul>

53.
Regional support caveats <ul><li>Public archives of lists

54.
Open subscription </li><ul><li>Encourage commercial participants </li></ul><li>If regional expertise is unsure defer to the official project support

55.
Don't duplicate effort </li><ul><li>Point to and contribute to central resources </li></ul></ul>

56.
Shameless plug: OSS Watch Conference <ul><li>TransferSummit/UK 2010

57.
24/25 June 2010 - Keble College, Oxford

58.
Open innovation / Case studies / Business and Community

59.
Improve collaboration between academia and business </li></ul>http://www.transfersummit.com

60.
Shameless plug: OSS Watch BarCamp <ul><li>26 June 2010 – University Club, Oxford

61.
Interactive informal discussions and meetups

62.
Find out about each other's OSS projects

63.
BarCamp >> active participation encouraged </li></ul>

64.
Come along! <ul><li>http://www.oss-watch.ac.uk

65.
[email_address] </li></ul>