Goals / Ideas
Created by Caroline Meeks, last modified by Nima Mazloumi 26 Apr 2007, at 05:16 PM
Goals
- Adoption
- Recognized as a Web 2.0 Leader
- Documentation
- Training/ Learning Curve
- Brand recognition (OpenACS/dotLRN)
- Missing Functionality
- Consolidating Functionality
- Developer Collaboration
Ideas & Votes
| Marketing | 18 |
| Top 10 Hall of Shame of Packages / Bugs | 5 |
| Better categorization of Bugs | 5 |
| Only include modules of certain quality in future releases | 19 |
Incentive to announce code and/or allow charge of code | 10 |
| How to behave - when modifying code | 5 |
| Process for submitting & processing patches | 9 |
| Move official documentation to Wiki | 15 |
| Small chunks of advice / code , recipes | 5 |
| Create a way to contribute learning material, presentation, marketing material | 13 |
| Clean frontpage / website for .LRN / Openacs | 16 |
| OpenACS book | 16 |
| Move to sourceforge | 17 |
| Move to a non viral license like BSD | 2 |
Notes
What are you working on?
- fix package per page
- create a "twitter" type page where you write what you are doing
- PO Client and Security service
- auto search of forums & wiki
Pimping the websites
- different sections for different persons (developers, users, ...)
- e-learning course on how to work with the toolkit, curriculum integration
