Log in to discuss and edit this issue
For change to be implemented through grassroots action, plans must be divided into work that individual people can do. Tasks are how Magnova does that. Projects address Issues, and Tasks make up Projects.
This Issue page will document the motivators for dividing work into Tasks, the features that Tasks should have, and the progress that's been made so far.
Much action is done around the world for the betterment of the community. But much of the energy and time spent is directed at the symptoms of systemic problems, rather than the causes. Additionally, many organizations have to reinvent the wheel to form their local chapter of operations. Our economy requires most people to spend most of their labor at jobs, which perform little to no social good in many cases. It is altogether rather inefficient. By providing an open-access, crowdsourced tool for creating clear action plans, a single self-management structure can be deployed by people all around the world. It also provides a platform for existing nonprofits to publicize opportunities for direct action in their own campaigns.
There are a variety of kinds of task that need to be done. Some tasks only need to be done once. Others may repeat, or need to be performed by each person getting involved in a project. Some may need to be performed in tandem with others. Certain tasks must precede others. A good Task management software should allow for all kinds of tasks and relationships between tasks to be represented. There should be flexibility for tasks to change from one form to another.
Presently, Tasks can be created, edited, and deleted on Magnova and store a few data, such as the name, completion requirements, description, what project they belong to, and the user who created it.
Magnova is open source and forever free. If you'd like to learn about how we implement Tasks, check out the:
Magnova will eventually provide the ability to create Local Projects out of Project templates, and that process will involve cloning all of that Project's Tasks as Local Tasks. Some analysis is needed to determine the best data structure for a Task template, and how Local Tasks will relate to their templates. Tasks will be able to relate to one another. UI improvements will be made to view tasks in different ways.
The Magnova community says the following issues give rise to Task. Addressing this issue could be accomplished by dealing with the following sub-issues. (Registered users can upvote/downvote these connections.)
The following projects have been created by the Magnova community to address this issue. (Registered users can upvote/downvote which projects they want to see implemented.)
Is Task affecting your community? Issue pages, like the one you're on now, are ideal for talking about general problems. Each Issue can be deployed to a Location to create a "Local Issue" page, where users can measure an Issue's impact on that Location, and discuss things that are particular to the community.
None identified yet! Registered users can identify new Local Issues.
This QR code links to this page. Print stickers, add it to fliers, or chalk it onto your driveway.