do you know what would make the rrp really successful? if you took the idea and put it to your own purposes.
well, here i have a rubric that will help you to do that. fill it out completely and you'll be well on your way to designing your own open & collaborative projects.
for more information on how this was designed, please see the academics section of this website. for help or questions, contact me at rrp@spitfirepress.com
| Title of your project: | |
| foundational questions | |
| Is this a new project or one that will be adapted to the open collaboration
model? |
If this project is an adaptation, why will it benefit from open collaboration? Has it failed under a closed system? Will opening the project prevent future failures? |
| If this project is new, describe why you want to begin it. Do you have the time and skills necessary to manage an Internet-based project? Are you willing to learn new skills or make time if you do not? | |
| Do you believe that you will find an online community that will suit
your project? Do you already have such a group in mind? |
|
| If you have answered these questions and feel that you are ready to undertake an open collaborative project, please continue. If necessary, review your answers above until you are satisfied and then continue. | |
| sharing the source | |
| What is the source code equivalent in this project—its
building blocks? |
|
| What skills are necessary to be able to use this “source”? |
|
| How will it be made available to interested people or
groups? Remember that you should not prohibit other people from making
your source code available if you
follow Open Source licensing guidelines. |
|
| Will it be necessary to create a style guide for changes
and additions to the
building blocks? |
|
| project structure | |
| Will your project have a single leader or a core group? | If so, what is the leader/ core group's primary role and purpose in the project? |
| Will you have clearly defined levels of participation in the project, such as “maintainer” or “contributor” as compared to public users? | If so, what unique privileges and/ or tasks will be granted to users at each level? |
| Will you have additional rules for reviewing and making changes or additions or will these be inherent in the project structure? | |
access |
|
CONSIDER Who SHOULD HAVE access to each of the following parts of your project?
|
Modes of Communication such as newgroups, mailing lists, forums, and bulletin boards. List varying degrees of access for each if applicable. Modes of Information such as FAQ and News web pages and announcement lists. Documentation and Versioning Who documents changes and developments to the project, and who maintains the versioning systems? Building Blocks and Modification Who can make changes and additions to the source-equivalent that is available for distribution. |
Communication
and Information |
|
| What are the primary methods for communications among members of the project's community? | Secondary methods? |
| What are the primary methods for sending information to the project's community? | Secondary methods? |
licensing |
|
| Will you use an Open Source or Open Source-style license to protect and distribute your project? | The Creative Commons provides licenses for use at http://creativecommons.org/license/ |
| Would it be more beneficial for you to write your own license? Do you have the necessary skillls to do so? | |
documentation & versioning |
|
| Develop a numbering system for versioning and a documentation system for changes and additions to the project so that a record may be kept of all changes, additions, and fixes. | |
join
faq
forum
project philosophy
downloads
forum guidelines
community
links
versions
academics
diy