Establish project management process about projects HOT 6 CLOSED

With regard to documenting this process, see #7 (comment), where I explained to @m52go how things are designed to work in a nutshell.

from projects.

@bisq-network/team-leads, I've just fleshed out the description of this issue into a complete project proposal. It's rather meta, as this (first) project is about establishing a project management process, but you'll get the idea. The next step is to discuss this with the larger @bisq-network/dao team, so I'd appreciate your feedback on this as quickly as possible here as comments or in teamleads chat. At this point I'm just looking for any strong objections. If none, we can broaden the communication asap. Thanks.

from projects.

With bisq-network/admin#41, I've fleshed out the remaining tasks for this project and represented them on the dedicated project board at https://github.com/orgs/bisq-network/projects/8. I've removed all the checkboxes from the Tasks section of the description above and simply linked to the project board.

As a general note on the emerging process here, I have a feeling this (dedicated boards per project) is going to be my preferred approach as opposed to maintaining long lists of task checkboxes and bidirectional issue references in each project issue's description. Depends on how complex the project is, but in my experience, most have merited a board by the time the project is really in full swing.

from projects.

As per bisq-network/admin#48, I've just significantly revised the description of this project, simplifying it, removing unnecessary aspects, and referring to relevant sections of the newly-published https://bisq.wiki/Project_management article where appropriate.

from projects.

I've just updated the description to reflect current project status; bisq-network/proposals#182 has just been accepted, meaning that this process is "officially" adopted now. The dev calls proposed at bisq-network/proposals#231 can be used to implement the (bi-)weekly project reviews and really drive the project management process.

from projects.

Closing as delivered, with a couple caveats:

• The project review process is not yet locked in. As mentioned above, we're planning to use the new dev calls to implement this, but discussions are still underway as to exactly how this will go
• I've crossed out a couple tasks regarding folding in feedback to the process after two cycles of having it in the wild. This is because we've already had the process out there for more than two cycles, and it's clear that feedback and refinements will be an ongoing process.

In any case, all tasks on the associated project board are now complete. The infrastructure and process is out there, folks know about it, links exist in places that new contributors can easily discover the process, and now it's about making good use of it and refining it over time.

Also note that it is not yet clear who will "own" the process going forward. Discussions are underway now to eliminate the project management committee (@bisq-network/pmc) and replace it with a simple 'maintainer' role, but this has not yet been done.

from projects.