Free project

From Wowwiki
Jump to: navigation, search
THIS IS AN OLD PAGE just kept for historial purposes

See relating

Free project is any project that has more than 50% of relating love.


This page shows definitions and metrics coding the some or less present freedom in relating, and use those standards for the accepting, labelling and hierarchizing of projects in comunaction (also useable for any other initiatives).

We already have the shareful standards for productive offers that could also be used for labelling your project planned goods as shareful project. However, we felt the need of a deeper and more specific standard and meassurers for what and how much freedom a project is offering to the outer world.

Free projects standards should hot the actual projects' management in an interesting way by provoking in them the debate of adding some piece of the protocols (i.e. for improving their accesibility, for publishing and categorizing tasks, etc)

Comunaction interpretation

Comunaction helps developing projects with some minimum degree of freedom (50% or more) through the promotion of their tasks aggregating and federatings for them being done easier anytime or in crowded comunathons. Comunaction also develops free projects funding with action, crowdfunding, directed barter, conventional money and/or the sharing of assets through further interpreted corporate models such as the jobs or the shops ones that any of their local comunas are implementing.

Below you find a broader protocol estating some general operating principles for a free project. It should help meassuring whether your project is interested in being free or not. For a more detailed qualification, you should use lovics.


Free project is for people lovely participating in planned productions.


Objectives (also named as aims, purposes, goals) are the mid-long term purposes that the project wants to achieve and the reason for it being initiated.

Free projects Objectives should be defined as accurately as posible unless the project states as an Objective not to define that sub-objective if that is not conflicting with the previously already defined Objectives.

Privacy issues

The project should provide ways for assignees and members remaining anonymous to the public, while being contactable and traceable.

Members critical mass and hierarchy

The project hasn't a members critical mass or if it has, it has published that and the reason for a posible future merging, forking or disolution when that would be reached (see more: infinity group)

The Project has specified and available the method for new entries, exits and the privileges from members (i. e. vetos' rights, exclusive duties, quality voting, etc) if any, their temporality and the way for getting those temporary privileges.

Decission and proposals

Everyone who has read the project objectives can propose whatever.

New decisions made out of proposals will need to be included in the Objectives definition, at the public tasks' public listing and communicated to the members if-as they have choosed.

A member can transfer his-her vote at all or for some specific issue to another member.

In the case of a technical draw at a non polytelic problem, the resolution should be choosen according to the one who better analizes the pros and the cons of his-her and the other's proposal.

The project could specify further policy on minimums for blocking proposals and quorum needed for those.


The project is or is willing to welcome and/or participate in more global (as in territory and thematic scope) and/or local networks.

Tasks creation and management

The tasks are the the short term or regular things that have to be done for maintaining and getting closer to the project Objectives.

Tasks are created by the people's suggestions and have to comply with the project Objectives. The new proposals for project tasks can be done by anyone through all posible ways at cost on request, starting by adding in the tasks listing the need of a more proper communicating of new tasks (i.e. e-form, paper writing, voice, etc) if the project is not yet offering such facilities.

Project members have the rigth to see and be directly informed of new tasks suggestions and refuse them to be added to the tasks list.

The free project is or tends to manage tasks according to:

  1. Minimizing tasks' dependency on specific assignees.
  2. Categorize tasks
    1. Minimize the basic tasks for doing more developmental tasks.
    2. All tasks are public tasks

Tasks categorization

Categorizing tasks should provide guidance for volunteers and clarity to the project way of doing.

Accepted and refused tasks

  1. Active tasks. Action proposals that have been aproved as maintaining or developing the project.
    1. Assigned task. Assignee could drop her assignation anytime and should inform the public about their volunteering scheduling and should work on standarizing the practices for doings the specific task (i.e. protocols, forms, roadmap in case the crowd comes, etc).
    2. Unassigned tasks. Doings aproved by the project but without any volunteer willing to be assigned yet.
    3. Postponed tasks
  2. Closed tasks
    1. Done tasks are tasks that acomplished what its own objectives
    2. Postponed tasks are task that was active that now it is not because is being reviewed
    3. Cancelled tasks are deleted tasks from the tasks list because there has been a change in the project objectives

Regular tasks

Regular tasks are the doings that anyone can do with requesting permission to the project that nor needed to be published as projects tasks. (i.e. tell a mate about the project, link us, send us cheers, etc)

Basic and development tasks

  1. Basic tasks are what have to be done for maintain the project alive.
  2. Developmental tasks are the tasks that are getting closer to achieve the Objectives.

Public and private tasks

  1. Public tasks is a listing of things that need to be done inside a group - project - community for improving it according to their objectives which everyone, being a member or not, is allowed unrestrictedly to do it - them. Public tasks listing should be available to the public in all posible ways at cost on request.
  1. Private tasks. Tasks just available to be a assigned to some member of the project.
  2. Not published tasks. Just visible for members

Tasks priority

The tasks priority level could come as a result of the group strategy specification process. That specified priority should be used just an additional advice, and should never be used for difficulting volunteering working on low priority or unassigned tasks.

Tasks assignation and cancellation

Assignees should propose to get on the task.If there is a concurrent competing case for being a task assignee, the task(s) should be assigned to the one who is less engaged in other project's tasks already; less fees is asking for; has a higher restorative status in the project; has more available time and-or resources for accomplishing or managing it the quicker or; has suggested the task.

When a task that is being commited or coordinated by some volunteer is willing to be cancelled o postponed, the information has to be provided to the commiter or coordinator prior cancellation or postponing for him/her being able to discuss that. Once a final decission of refusing or closing a task is reached, the arguments for deciding that should be provided to the public and kept documented during a reasonable time.

Criticism publicity

Complaints about posible uncompliances with the free project's terms, objectives or proposed strategies have to be directed to the responsible of the conflicting content (or to the thread she opened). In case of not reaching an agreement the issue should be resolved with alternative dispute resolution mediation methodologies directed by other members that both parts agree to, before trying to raise the issue in a project voting session.


The project could punish, by discounting or ending members' rights, any behauviour that conflicts with the free project's terms and-or with the free project's Objectives.

The project has a restorative member's status defined policy, at cost on request, which should contain information about penalties for hipothetical damages.

Fundraising and paying

The free project accepts any kind of donations in goods (including money$) and-or in whichever (skilled) time from anyone anonimously or not.

The project could specify methods of paying fees to tasks assignees in a regular or punctual way in the freest currency possible.


The free project's disolution should be communicated the earlier to all their members when the free project's tasks are not being done by their assigned members.

The free project's ownership should pass to the one that better preserve the project as free project.


  • Create new project. Admins accept members personal classified offers (for fundraising for the project).
  1. (x)Admins should aprove new members
  2. (x)Use group's own currency. [00] Credit limit
  3. (x)Admins can move credit: (x)within project, ()externally
  4. (x)Members can move credit: (x)within project, ()externally
  5. Discount [00] member credits per [week, month, year]
  6. Categories / tags per type of activity (Housing, Transport, ...).
  7. Viewable by: ()
  8. Veto by: ()Single member, ()Admins, ()10%, ()+50%
  9. Add [membername] as admin
  10. Create subproject
    1. Admins can:
  11. Move project to subproject
  12. Move subproject to project
  13. ...
  14. Add task
    1. Add category
    2. Add threshold
    3. ...
    4. Join task
    5. ...
  15. Users donate to categories

  • Projects' listings. Search / Order by:
  1. Sooner completed
  2. Started
  3. Sooner started
  4. More members
  5. More activity
  6. More recent activity

See also