Topic: Making the most of the Kete project : community, resources and collaboration.
Topic type:
A discussion topic about the Kete.net Community outlining how it works currently, the problems which are on the horizon, and outlining a possible way forward.
Introduction
The key premise with an Open Source community is that we all contribute to the project. Open Source – Open Spirited. So we need to each contribute what we can to the project.
The domain name: old.kete.net.nz is available for anyone wishing to use it, for example http://otaki.old.kete.net.nz etc
Kete.net site
The Kete Community has a website for sharing information and resources : http://old.kete.net.nz :
- Documentation and instructions
- The code for download
- Themes for customizing your Kete
- Links to an online shop with kete merchandise
- Logo: couple of versions on the kete.net site
- Progress and method reports
- A forum for discussing issues
- Advanced training modules
- Forum for discussion and sharing learning
The site had 1942 unique visitors to the site last month and there have been 42 code checkouts from around the world including Australia, Italy, USA, Japan, China, Netherlands, France, Germany and Canada.
Background
Horowhenua Library Trust developed and gave away the source code for anyone to use but holds the copyright, plus the copyright of all enhancements since in exchange for giving the source code.
Horowhenua Library Trust is a registered charitable trust, a Council Controlled Organisation, and is audited by Auditors Office annually. It comprises a board of 5 Trustees appointed by Council to run the library:
- Sharon Crosbie – Chair
- George Sue JP – Deputy
- Heather Birrell, Alan Smith JP and Bob Wright.
Issues
- How do we coordinate development of the codebase?
- Who should hold the copyright?
- Who decides what enhancements will be Kete core-code and what should be optional / enhancements?
- Who defends the founding principles of Kete project, or decides when they should be modified or abandoned? ie by the people for the people, plain English, intuitive and easy to use, simple, etc
- Where is the line between commercial relationships and the project management ie Katipo and a Kete Client and HLT ?
- How will we fund the work required to maintaining the cohesion of the project ie maintaining the codebase, developing releases etc? HLT have done it to date.
- How often should the Kete Community Meetings be held? Should they be held? Locations? Format? Cost?
Collaboration
The key premise with an Open Source community is that we all contribute to the project. Open Source – Open Spirited. So we need to each contribute what we can to the project. We are happy to give Kete away for free but we would love it if in return we could be helped with the costs of supporting the project.
I would love to see a Kete organisation of some sort formed to:
- Collect an annual subscription / donation to fund things which benefit us all including enhancements, managing the code base, developing releases. Maybe a donation with a sliding scale of amounts in relation to how big the organisation is: $5,000 pa - down to $500 pa.
- Seek funding from external sources to further the Kete project ie Eastern and Central Community Trust, etc.
- Set priorities for the development path of the main branch.
- Coordinate collaborative funding for enhancement work which is over and above the cost of maintaining the codebase.
- Facilitate Kete Community Meetings.
- Promotion and marketing