Site Map | --All Pages-- | --Github Commits--, Issues | Possible Initiatives | Open-source Society Project | Main Prototype website | Sub-reddit -- This documentation wiki is under construction
ThinkTank Meetings
- Project Links
- CURRENT LINKS: Performance-Based System for Electing Better Leaders | Citizenship Leadership - Website Functionality
- Often used links: Tasks (to do) ◼List of Page Views
- Redesign Google Doc ◼Website Development Job Description for Redesign
- (Google drive) Prototype links: Prototype Website Dev Job description ◼Screenshots: Home◼Units◼Objectives◼Tasks
- LucidCharts: Process Entity Relationship Diagram ◼Javul Project Lifecycle
- Google Drive link for OSP Project
- Flowchart (under-construction, Diagrams.net) ◼Sub-reddit (forum)
- OLD Team Meeting links: ThinkTank Meetings (wiki) | Project ideas (just a start) (XL) | Asana
This is a ThinkTank for designing a website that helps people solve problems in society and manage their related tasks and goals and get rewarded for it. See Project Overview (Google powerpoint)
- Joy's Ideas: Shared Drive
- Marko Cadsawan's ideas: Marko's Shared GDrive
- Dev's Ideas: Google Drive
- Bilal's ideas: [1]
- Guidelines for Submissions
- Our work every week is focused on the technical side of things: How our website should work, what specific functionality it would provide
- It is difficult to process a lot of theory. Presenting theory is ok, if it can be shown how it can be implemented on our website in a visual way
- Propose what can be done to the current version of the Visual Design (if one is available for that week). Make a Copy of the current design and edit as needed
- Research existing websites and tools to get ideas and see how they can be implemented on our designs
- Propose new/original ideas when possible (ideas don't have to be complete or perfect, they can also just be starting points). Find ideas already implemented by looking at the Prototype links above
- Perfectly ok, in fact you are encouraged to take someone's idea from below and improve it so definitely examine ideas that have been selected before.
- Make a new file for each week
Note: A best attempt is made to select good ideas but some ideas may be missed. If you think something could be very beneficial and needs another look let me know.
Week # | Date | Meeting Minutes | Selected Ideas/Inputs | Plan for next week |
---|---|---|---|---|
1 | Sunday Dec 5, 2021 |
|
Example | Research existing Taxi app related issues and imagine how people online would work through those issues. |
2 | Sunday Dec 12, 2021 |
|
| |
3 | Sunday Dec 19, 2021 |
|
Joy: We can look at your rewards system analysis when we visit this topic later Mark: (1) Interface design effort [4] (2) Object number shown in tables to help identify objects, however this could be placed differently to take less space, or only shown on the Detailed view [1] (3) Gantt chart for Objectives [2] |
Analyze other websites to see how they resolve issues |
4 | Dec 26, 2021 |
Joy: (1) Gantt chart for progress [2] (2) Chat for the team however its already implemented in our Prototype design [2] (3) Tags for issues [1] Mark: (1) Tags for issues [1] |
Start looking at individual Issue pages and taking a close look at what happens there from Issue reporting to resolution and task creation. Focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked | |
5 | Jan 2, 2022 | - | Next week we'll focus on resolving a single issue and look closely at what activity takes place. We look at Issue creation, definition, sub-issues (if any), a 'Resolution Wiki' and how Tasks are defined and linked | |
6 | Jan 9, 2022 | - | (break for next few weeks) | |
7 | Jan 30, 2022 | Looked at work from Jan 9. |
| |
8 | Feb 6, 2022 |
|
| |
9 | Feb 13, 2022 |
|
Mark [PD]: (1) Data Analytics: Page showing analysis of data in the Unit (tasks completed, in progress, analysis of funds etc), and (later feature) allow customization for what to show on home page [4] (2) Add option for Tabbed view of items on home page [3] (3) Add Item number somewhere for easy reference [2] (4) Add total number of items in the table next to Headings eg. Issue (54) [2] (5) Filter and Search bars [2] Joy: (1) Add scrolling for items in the tables [2] (2) show Idea/activity points near User profile icon [2] (3) Search bar [2] (4) Link to Reward System, 'How it Works' kind of link [2] Dev (1) Move out 'completed' task numbers from Analytics [2] (2) show Total tasks completed as separate number [2] (3) Display live view of data (real time updates) [1] (4) Add upvote/downvote for user who upvoted or downvoted a specific issue (? unsure if we should add this) |
Directly edit Issues detail |
10 | Feb 20, 2022 |
Analysis For review: Mark: Issue Page View (updated), Home Page View (updated) - Joy's work (see Analysis and Process at end) - Dev's work |
Dev: Add Upvote/Downvote counter next to the issue (this exists in our Ranking system) [2]. Tags in Issues for skill-matching [2] | For the next few weeks, we will research problem-solving software and tools, any methods they use and see how any of that can be used for our Taxi app business. (some problem-solving theory is ok) |
11 | Feb 27, 2022 | Analysis For review: Problem Solving-- Joy - Dev - Mark (stackexchange) |
Selected Ideas : Joy: 'Resolution wiki' (or issue wiki) could have guided sections for Root Causes. Possibly needs more study [2] -- Mark: (1) Quality control/guided process to help users create higher quality data entries [2]. (2) General process of submitting something and guided through it [1] |
Using Google find as many "problem-solving" software and tools as you can and then if you have time and if that information is available, make a summarized list of their key features and think about how we can use it for our project. Search terms can include alternative words for example problem solving software/tool, solution finding software, problem management software, etc. A small amount of problem-solving theory is ok. |
12 | Mar 6, 2022 | Analysis For review: | Selected Ideas | Plans for next week |
13 | Mar 13, 2022 | Analysis For review: | Selected Ideas | Plans for next week |
14 | Mar 20, 2022 | Analysis For review: | Selected Ideas | Plans for next week |
Tentative Plan for Meetings
Discuss the following topics, create visual designs and decide on functionality:
- Taxi App:
- Home page
- Issue Detail Page
- Problem-solving software
- Task Management (all stages: creation, assignment, completion, evaluation etc)
- Ideas
- Objectives
- Re-assess previous topics and look at the existing system from an over-all view
- Connecting all these: Skill-matching, task skills for searching, recommendations etc
- Reward/Motivational Systems
- Reputation systems (Idea points, Activity points). Also linked to Rewards/Motivational systems
- Decision Making module (community owned businesses and others need this module)
- Interface customization
- Administration (moderation), Interface setup (e.g. Defining types of Issues, tags, categories)
- Unit Generalization/Creation (for other types of units)
- ...