Editing Website Functionality

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
[[File:Basic functions.jpg|frame|This diagram shows the basic functionality of the Javul website.]]
[[File:Basic functions.jpg|frame|This diagram shows the basic functionality of the Javul website.]]
The overall concept is similar to that of a project management software (see [https://en.wikipedia.org/wiki/Project_management_software Wikipedia]) which helps people organize their work however we want it to be open-source and offer monetary rewards to those who contribute and keep track of people's reputations.
===Prototype Screenshots===
* (Google drive) [https://drive.google.com/file/d/158viXz3XFK0D-4sfqaFmS0188CI27z0H/view?usp=sharing Home] | [https://drive.google.com/file/d/1l5EV5VCwju15HeIGLHCyQjIAuw6OY5Rb/view?usp=sharing Units] | [https://drive.google.com/file/d/1Mpo0N9eiR2Z-xVEMQ--JoIkp3umLylCu/view?usp=sharing Objectives] | [https://drive.google.com/file/d/1p7jOks6a6A-Ccc8y8NaS0P6KQrJ-PUp0/view?usp=sharing Tasks]


===Units===
===Units===
Line 31: Line 26:
Donations go to Units where they can be used to compensate people who contribute the most. Every Unit home page can have a donate button.
Donations go to Units where they can be used to compensate people who contribute the most. Every Unit home page can have a donate button.


Alternative terms: Project, Group
====Roles====
 
(elaborate..identity management)
 
== Tasks ==
----
'''A task is a unit of work.'''
----
Although tasks are considered to be indivisible units of work, tasks can be composed of other tasks. To each there should exist at least one procedural description; a thorough explanation of the necessary actions that need to be executed in order to complete the task. Defining checkpoints and ways to evaluate the correct execution of a task is important for accountability.
----
;Completion
:Tasks can and should be graded. As an example with three different values: could be better, acceptable (100%), exceptional (110%). This information can be used to define a reputation metric.
----
;Complexity
:A complex task can be a task composed of many sub-tasks or it can be a procedure that requires highly skilled performers.
----
;Recompensation
:The correct execution of a task can be recompensated monetarily, with an increase of reputation or with any other mechanism.
----
''Related concepts: work, procedure, job, accountability''


==Objectives==
==Objectives==
Objectives are top-level goals in a Unit and are a way to group related tasks together. For example the software Atlassian uses the term 'Epic' to describe larger deliverables [https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/ Altassian.com - Issue Types]:
----
: ''In agile development, epics usually represent a significant deliverable, such as a new feature or experience in the software your team develops.''


Without an 'Objective' type of project management component, it would be difficult to organize tasks and track progress on larger goals.
Objectives can also be managed for a person for certain goals that they want to achieve. They can be private or be shared with counselors or the public so others can help in setting new objectives or give feedback. Setting of Objectives could be done according to the [https://en.wikipedia.org/wiki/SMART_criteria SMART criteria]
 
Setting of Objectives could be done according to the [https://en.wikipedia.org/wiki/SMART_criteria SMART criteria]


Initially in addition to an Objective, two terms Ideas and Problems were defined. An Idea was just that - an idea which someone had but there may not be a defined objective for it or a problem associated with it. A Problem was focused on an existing issue or problem. It was thought that having these two additional terms would complicate things when we are looking at big problems that were connected to other problems, ideas or objectives. Using one terms simplifies things. Ideas eventually have to turn into Objectives and Problems usually always have an objective or get an Objective associated with during the course of solving the problem. Having one term also simplifies the implementation in the beginning.
Initially in addition to an Objective, two terms Ideas and Problems were defined. An Idea was just that - an idea which someone had but there may not be a defined objective for it or a problem associated with it. A Problem was focused on an existing issue or problem. It was thought that having these two additional terms would complicate things when we are looking at big problems that were connected to other problems, ideas or objectives. Using one terms simplifies things. Ideas eventually have to turn into Objectives and Problems usually always have an objective or get an Objective associated with during the course of solving the problem. Having one term also simplifies the implementation in the beginning.
----
''Related concepts: mission, goals, ideas''


For personal Units (a low-priority feature to be implemented later), Objectives can also be managed for a person for certain goals that they want to achieve. They can be private or be shared with counselors or the public so others can help in setting new objectives or give feedback.
==Proposals==
 
Alternative terms: Goals, Targets, [https://en.wikipedia.org/wiki/Milestone_(project_management) Milestones]
 
==Ideas==
People can create and discuss new ideas relating to the Unit
 
==Issues==
People can report problems or issues related to the Unit
 
== Tasks ==
A task is a unit of work. Although tasks are considered to be indivisible units of work, tasks can be composed of other tasks. To each there should exist at least one procedural description; a thorough explanation of the necessary actions that need to be executed in order to complete the task. Defining checkpoints and ways to evaluate the correct execution of a task is important for accountability.


;Completion
(any community, corporation, initiative must be democratically governed - elaborate)
Tasks can and should be graded. As an example with three different values: could be better, acceptable (100%), exceptional (110%). This information can be used to define a reputation metric.
(publishing a proposal that gets approved increase in reputation)
----
''Related concepts: governance, voting''


;Complexity
====Treasury====
A complex task can be a task composed of many sub-tasks or it can be a procedure that requires highly skilled performers.


;Compensation
(wip)
:The correct execution of a task can be compensated monetarily, with an increase of reputation or with any other mechanism.
 
''Related concepts: work, procedure, job, accountability''
 
==Treasury==
Every Unit has a treasury or source of funds that can be used by people for re-deeming activity points.
 
==Roles==
Tasks are meant to be open and can be completed by anyone. However there might be some people who are assigned on-going recurring and therefore might have defined 'Roles' relevant to the kinds of tasks they're working on.


==Work Flow==
==Work Flow==
Line 82: Line 76:
General Help, About or FAQ pages about the project can also be managed which provide documentation about the project. In the future we could think of creating options so people can video conference, text or voice chat for discussions. We could use services from external websites such as Google hangouts but it would be integrated with the Javul website in a way to make things convenient.
General Help, About or FAQ pages about the project can also be managed which provide documentation about the project. In the future we could think of creating options so people can video conference, text or voice chat for discussions. We could use services from external websites such as Google hangouts but it would be integrated with the Javul website in a way to make things convenient.


==Differences between the old and new version of the website==
===Other===
{| class="wikitable"
|-
! Feature !! Description !! Reason for adding
|-
| New component 'Ideas' || New ideas can help create tasks for additional features  || Previously we just had issues which are understood to be dealing with existing problems, not new ideas/proposals which are also an important reason for improvement
|-
| Moved United related links || Moving Unit-related links to a row at the top || Have more space for the main core content of a Unit
|-
| New feature 'Active Users' || Active Users (quantity) are shown (logged in is counted as well) and the usernames. These statistics are then used for decision making in the Unit e.g. Task approval || To keep track of active users to help with decision making and also showing how active a Unit is.
|-
| Approval mechanism for Tasks || Previously a task was auto-approved after 7 days if all editors editing it had not approved it. Now an Admin or a user with the 'Task Management' right can approve it. If there's only one or two active users in that task, they can also approve it (see 'Active Users' for detail). || Faster 'approval' process based on Active Users
|-
| Vote weight || Votes of subject-matter experts/active/regular contributors should be more than those of new users ||
|-
| Tasks || Old website: Issues have their own Resolution field and work done for resolving them is not translated into a Task. New website: Should the work for implementing Ideas and Resolving Issues (and completing Objectives) all be directed to the Task management system? ||
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}
 
; Differentiation between Objectives, Issues, Ideas and Tasks
Ideas are for brainstorming and at that time people aren't thinking about the specifics of the task(s) needed to implement an idea. Its a different kind of mental activity.
 
Similarly for Issues we're looking at looking at the Issue in detail, root cause.
 
Converting something into a Task, task bidding, checking what skills are needed to complete the task, task completion and evaluation - those are different stages of the work flow and need a different approach. This is why we need a dedicated task interface just like how Upwork has (which is like Task management but not issue reporting or Idea management)
 
== Improving Government and Leadership ==
The core Unit can also be used for a city, with tags to identify different types of tasks, objectives, issues and ideas. This lets new leaders focus on all the issues for a City in one place and develop their leadership profiles. These profiles can be used to evaluate whether someone would be a good candidate to take part in government activities at higher levels (state/province, national and international). There's more functionality needed for government specific units (e.g. creating/maintaining laws) which will be developed later.
 
==Current Issues==
* Do we need a Decision object? We need to recognize decisions made supported by science, data and research
* ...
 
==Site Administration==
These can be sections in the Javul.org forum
* General Discussion (website functionality and system improvements)
* Conflict Resolution (later)
* Database maintenance for Skills, Areas of Interest, Location
* Report an Issue
* Open Community Business Incubator (for advice and suggestions)


==Links==
===Reputation===
* [https://docs.google.com/document/d/1ehebPoKjbip1DiGWmIuDSKKlZD4bYaRaUgEVEzE1_qc/edit#heading=h.bucnmwf4tft8 Original Job description for Javul.org]
This is to show that project management has similar ways of dividing up a project's tasks to manage its work:
* JIRA. According to Altassian, "Issues are the building blocks" of their project management software. [https://www.atlassian.com/software/jira/guides/getting-started/basics#step-4-create-an-issue more info]
* [https://productschool.com/blog/product-management-2/stories-epics-themes-initiatives-product-manager/ Stories, Epics, Themes and Initiatives for Product Managers] - "Stories, epics, themes and initiatives are the building blocks of great agile product management." (Altassian also talks about these [https://www.atlassian.com/agile/project-management/epics-stories-themes here])
* [https://www.goodday.work/views 20 views] of the GoodDay software to show project management views of different types
* [https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems Comparison of issue-tracking systems]
* [https://en.wikipedia.org/wiki/Task_management Task Management] (Wikipedia)
Please note that all contributions to Javul are considered to be released under the Creative Commons Attribution-ShareAlike (see Javul:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)