Coop Platform rebuild: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Project | {{Project | ||
|Name= | |Name=Coop Platform rebuild | ||
|Owner=André Fincato | |Owner=André Fincato | ||
|Budget=Stimuleringsfonds | |Budget=Stimuleringsfonds | ||
|Categories=100% Development Program | |Categories=100% Development Program | ||
}} | }} | ||
The project | == Intro == | ||
The software built by James for the coop platform has shown very interesting features and a good workflow to organize H&D yearly budget into a more approachable format. | |||
The experimentation done by running it on a private Ethereum-based blockchain was at the same time useful in terms of how to “vote“ on a project proposal, as well as full of complications. | |||
== Proposal == | |||
While keeping all the core ideas from the original project, this re-implementation aims to start with a simpler setup (eg no blockchain as database, but a more canonical posgresql), a more solid user interface and better integration with the wiki. | |||
In parallel, an ongoing research track on co-op structures will be developed, both to inform the design of the new coop software as well as the general internal workflows of the group. | |||
Later on, a private blockchain could be re-introduced as part of going experimentation with coop models. | |||
Software stack: | |||
* <code>golang</code> for the backend (opportunity to learn new lang) | |||
* <code>posgresql</code> for the database | |||
* <code>python</code> for the frontend, or possibly <code>javascript</code> (it depends how the UI works) | |||
=== Participants === | |||
* André | |||
* Karl (interfacemaken) | |||
* … | |||
=== Work outline === | |||
Research and Design: | |||
* outline of previous workflow (from coop platform) together with current one | |||
* definition of general, agreed upon, workflow amongst all coop members | |||
** what does a user need to do to propose a project? | |||
** how does a user vote on a project? | |||
Backend: | |||
* setup of database | |||
* building of necessary functions based on agreed upon workflow | |||
* setup of APIs for frontend to interact with | |||
* login system | |||
* notification system? eg | |||
** when a new project has been added | |||
** or approved | |||
** or proposed but never reached enough votes after x amount of time | |||
Frontend: | |||
* design of user interface | |||
* building of necessary functions to talk with backend | |||
* actual UI implementation | |||
* login system | |||
== Budget == | |||
… | |||
Latest revision as of 12:08, 6 January 2021
| Coop Platform rebuild | |
|---|---|
| Name | Coop Platform rebuild |
| Owner | André Fincato |
| Hours | [[]] |
| Budget | Stimuleringsfonds |
| Categories | 100% Development Program |
| Period | [[]] |
Intro
The software built by James for the coop platform has shown very interesting features and a good workflow to organize H&D yearly budget into a more approachable format.
The experimentation done by running it on a private Ethereum-based blockchain was at the same time useful in terms of how to “vote“ on a project proposal, as well as full of complications.
Proposal
While keeping all the core ideas from the original project, this re-implementation aims to start with a simpler setup (eg no blockchain as database, but a more canonical posgresql), a more solid user interface and better integration with the wiki.
In parallel, an ongoing research track on co-op structures will be developed, both to inform the design of the new coop software as well as the general internal workflows of the group.
Later on, a private blockchain could be re-introduced as part of going experimentation with coop models.
Software stack:
golangfor the backend (opportunity to learn new lang)posgresqlfor the databasepythonfor the frontend, or possiblyjavascript(it depends how the UI works)
Participants
- André
- Karl (interfacemaken)
- …
Work outline
Research and Design:
- outline of previous workflow (from coop platform) together with current one
- definition of general, agreed upon, workflow amongst all coop members
- what does a user need to do to propose a project?
- how does a user vote on a project?
Backend:
- setup of database
- building of necessary functions based on agreed upon workflow
- setup of APIs for frontend to interact with
- login system
- notification system? eg
- when a new project has been added
- or approved
- or proposed but never reached enough votes after x amount of time
Frontend:
- design of user interface
- building of necessary functions to talk with backend
- actual UI implementation
- login system
Budget
…