Open-source Society Project: Difference between revisions

From Javul
Jump to navigation Jump to search
Line 24: Line 24:
** Rate issue importance: Low, Medium (default), High: Weighted average (need to create method of calculator for 1 to 10 for importance): 1, 5, 10 for low, medium, high
** Rate issue importance: Low, Medium (default), High: Weighted average (need to create method of calculator for 1 to 10 for importance): 1, 5, 10 for low, medium, high
* Sort issues by type (if people are interested in issues of a certain type). Possibly let people create custom views in which they can customize their dashboard and only see what they want to see
* Sort issues by type (if people are interested in issues of a certain type). Possibly let people create custom views in which they can customize their dashboard and only see what they want to see
* Meeting  
* Meeting functionality
 
* Global action rate limit depending on activity points
* Global action rate limit depending on activity points



Revision as of 05:51, 4 January 2022

This is the home page for the Open-source Society project.

Project Links

Software Requirements (additional)

These are the ideas that we are coming up with as we work through our weekly meetings:

  • Home pages of Units should be customizable e.g. re-order and collapse components as needed
  • Social media share function (twitter, facebook)
  • Show related and Linked objects (for all objects)
  • Importance level -> change to 'Priority'
  • All posts (Issues, Objectives, Tasks) should have a box for OP's comments, as well as the wiki entry which can be edited by all. The wiki part can be called 'Issue Wiki' etc
  • Issue editing:
    • Issue default sort: by Priority
    • 'Issue Wiki' (for describing the issue) and 'Resolution wiki' (for working towards a solution). 'Tasks Wiki'- duplicate object shown separately in the Tasks table
    • Issue can be 'Mark as Verified' by a minimum of 3 people (or one third of the total active users for last month etc, round up to 1 at least)
    • Issue then becomes locked
    • Editing the locked issue requires 50 activity points and System will give a warning: "Warning, this issue has been marked as Verified. Editing it will unverify the issue and re-start the verification process. Are you sure you want to edit it?"
    • Issue then becomes unverified and can be edited
    • Rate issue importance: Low, Medium (default), High: Weighted average (need to create method of calculator for 1 to 10 for importance): 1, 5, 10 for low, medium, high
  • Sort issues by type (if people are interested in issues of a certain type). Possibly let people create custom views in which they can customize their dashboard and only see what they want to see
  • Meeting functionality
  • Global action rate limit depending on activity points
For later development / lower priority

These can be implemented if these problems are encountered.

  • Reporting functions:
    • Report this (for: spam, conflict of interest, misleading data and science, other terms of abuse)
    • If an Issue is reported, a mediation group can analyze the report and reject the issue or archive it etc (reporting requires some points)
  • Request responses/feedback/answers for objects that haven't gotten a response (or system highlights 'high priority' objects that havent gotten a response etc)
  • Rewards have an expiration (as observed in StackExchange) to provide motivation for people to respond (e.g. bonus rewards have a timer on them). Search on this for more info.
  • Gantt Charts (some open-source solutions available here)
  • Specific chat and meeting organization for objects (issues, tasks etc)
To-do
  • Make block diagrams /flowcharts for various processes in our project (Issue reporting, resolution, Task creation to completion, Objectives management)
Suggestions but these features already exist
  • Treasury View (already exists)
    • Log of debits/credits (already exists)
  • File attachments for objects
Links

Older Material

Selection Process

Recruitment

The goal is to find students with the appropriate backgrounds. Our methods can include:

1. Contacting teachers teaching these programs to see if they can put us in touch with their students. The programs can include:

  • community development
  • problem-solving (any students who have studied one or more courses for this)
  • hire college students directly who have studied these kinds of courses

Sample searches:

2. Finding people on forums about problem solving or community development e.g.:

3. Searching for student hiring/internship websites where an ad could be posted

4. Searching for groups of students on social media (facebook)

5. We can also search directly for resumes mentioning the above

Approach/Selection

  • Informational slides (to send to teachers)
  • Initial questionnaire