Loomio
Mon 18 Sep 2017

OCP dev roadmap

BH
Bob Haugen Public Seen by 489

This is a discussion to write up a roadmap for OCP development and propose it for a consensus-style vote.

We want to consider a list of roadmap-level deliverables that provide value, for the next 3 months. ("roadmap-level" we can work out together in practice.)

BH

Bob Haugen Mon 18 Sep 2017

Here's my very rough idea of three components for a roadmap (not the whole roadmap):
Now:
* Keep process planning and logging working in the OCP Work app until the Kamasi app (new kanban-card-style OCP UI) is ready to take over work planning and logging. Bob will fix bugs. No other new features will be added.
* Work on the Kamasi app features for process planning and logging. Bernini and Lynn will focus on that, with help from Bob and Pospi.
* Plan a method for importing work records from Gitlab to OCP. Ale and Ivan Esperanto will work on that, with help from Lynn.

Please correct any errrors.

BH

Bob Haugen Mon 18 Sep 2017

Should also add something about a testing group.

LF

Lynn Foster Mon 18 Sep 2017

Other possibilities:
* Decide requirements and create feature for levels of segregation of resource types and recipes, to support group operations in a broad heterogeneous network.
* Test the budget/income distribution feature for FairCoop requirements, and improve if needed.
* Add feature for participants to approve time logged by other participants.

Also people should add what is appropriate for BotC and CoopShares, as well as what is still needed for FairCoin.

BH

Bob Haugen Mon 18 Sep 2017

I think somebody should add something about how the General App taxonomy will be developed and agreed upon. I proposed that Bumbum use the work app in testocp to experiment with after Kamasi takes over process planning and logging, but I have no idea what he and others might think about that.

LF

Lynn Foster Mon 18 Sep 2017

From Xavi in the wekan:
* Cooperative providers bill collection
* Map chip-chap's multi-currency transfers in OCP as exchanges.
* Integrate new chip-chap user form in multi-currency app.

These might be too detailed, maybe something like:
* Complete chip-chap integration.

(I don't know what the first one even is.)

???

LF

Lynn Foster Mon 18 Sep 2017

I expect that after the first deliverable of the Kamasi process planning logging, we can expect some level of additional work based on feedback. Focus might be on coordinating work, per the summercamp. This could be a separate bullet point for after the first deliverable, but within 3 months.

AF

Ale Fernandez Mon 18 Sep 2017

About the testing group, a pad with more detail is at https://board.net/p/OCPtesters but here is a summary of the proposal for this group:

  • The group will take on testing tasks, testing new features and reported errors in the use of OCP.
  • Tasks will be prioritised and planned during a weekly scrum meeting.
  • Displayed text corrections and translations will also be run.
  • This group will connect with faircoop tech, communication, welcome, circular economy, and management, to agree and manage the use and implementation of OCP in the faircoop ecology.
  • The tester group will support developers, and end users.

We propose this for 3 months, with 2 part time coordinators - maro and ale, and an open team able to take on work on a task basis. After these 3 months, OCP should already be in use within faircoop and we can reassess the workload.

So how about the overall team? As well as the people working on this already, if santi can take care of the blockchain and server care, dion (catalan/peruvian django dev) can take on a couple of tasks, I can (ale) figure out how to change text and do simple fixes, then we still need someone with django and blockchain skills who can take on xavip's tasks, and another person - or group - able to take on a more end user support and fixing role. In terms of people, we need this to happen as soon as possible.

This means according to the open coop work process which we worked through at faircoop's summer camp, OCP devs would have 2 more people, and the tester group would be maybe the full time equivalent of 1 coordinator and 3 testers working on a task basis.

AF

Ale Fernandez Mon 18 Sep 2017

The "bill collectors" one is about identifying what money belongs to who and automatically making payments, from what I understand of that task. I made a comment in it trying to clarify a bit.

I

ivan Tue 19 Sep 2017

Here another proposal to add to this roadmap, I would like to arrive at the end of this 3 months with a detailed collaboration guidelines / readme / branching model up & running for the projects I am working at (kamasi at the moment)

BH

Bob Haugen Wed 20 Sep 2017

Combined roadmap, from the comments above and below:

OCP+Kamasi:

  • Keep process planning and logging working in the OCP Work app until the Kamasi app (new kanban-card-style OCP UI) is ready to take over work planning and logging. Bob will fix bugs. No other new features will be added.
  • Work on the Kamasi app features for process planning and logging. Bernini and Lynn will focus on that, with help from Bob and Pospi.
  • Plan a method for importing work records from Gitlab to OCP. Ale and Ivan Esperanto will work on that, with help from Lynn.
  • Test and improve as needed value distribution according to logged work.
  • In 3 months develop detailed collaboration guidelines / readme / branching model for kamasi.
  • Unassigned work, needing more programmers:
    • Cooperative providers bill collection ( identifying what money belongs to who and automatically making payments).
    • Complete chip-chap integration.
  • Unknown plans and status:
    • Bank of the Commons

Coopshares:

tl;dr

As first step we (Victor, Lynn, Me with the contribution of Dyne and thomas) will define the overall architecture of coopshares app and based on the result we will define a project kanban board (in github, untill kamasi will be ready)
Full version

Related to Coopshares in our last meeting we decided as first step to define the general architecture of the web app. We will try to reuse as many part as we can of kamasi on the front end. I suggested to think about coopshares firstly as an agnostic exchange webapp, and in a second moment customize it towards the shares type of resources exchange, in order to build at the same time a reusable component for the open app ecosystem. OCP is needed to handle agent login and data and resources exchanges, all of that through a graphql layer. But in order to be more clear about timeline, amount of works and skills needed we need to study better the functionalities of the app and all the different part to integrate together.

Testing group:

  • The group will take on testing tasks, testing new features and reported errors in the use of OCP.
  • Tasks will be prioritised and planned during a weekly scrum meeting.
  • Displayed text corrections and translations will also be run.
  • This group will connect with faircoop tech, communication, welcome, circular economy, and management, to agree and manage the use and implementation of OCP in the faircoop ecology.
  • The tester group will support developers, and end users.
  • We propose this for 3 months, with 2 part time coordinators - maro and ale, and an open team able to take on work on a task basis. After these 3 months, OCP should already be in use within faircoop and we can reassess the workload.

Overall:
* Need more programmers with Django and blockchain skills.

Please help correct and complete.

I

ivan Thu 21 Sep 2017

Coopshares Update

tl;dr

  • As first step we (Victor, Lynn, Me with the contribution of Dyne and thomas) will define the overall architecture of coopshares app and based on the result we will define a project kanban board (in github, untill kamasi will be ready)

Full version

Related to Coopshares in our last meeting we decided as first step to define the general architecture of the web app. We will try to reuse as many part as we can of kamasi on the front end. I suggested to think about coopshares firstly as an agnostic exchange webapp, and in a second moment customize it towards the shares type of resources exchange, in order to build at the same time a reusable component for the open app ecosystem. OCP is needed to handle agent login and data and resources exchanges, all of that through a graphql layer. But in order to be more clear about timeline, amount of works and skills needed we need to study better the functionalities of the app and all the different part to integrate together.

BH

Bob Haugen Thu 21 Sep 2017