You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 8, 2023. It is now read-only.
Other than a bit of rewording (I've got a PR incoming on that front), the main things we need to do to the PM document are to
add good, concrete examples
tweak it to work as a clear, straightforward guide that people can rely on and refer to
define roles clearly
Rather than cooking those up in the abstract, I propose that @em-ly, @whyrusleeping and I try applying this model, as it's expressed in the document right now, to go-ipfs. That will let us
figure out what's confusing or unclear in the document
sort out an iplementation of the mechanics -- translating this model into real, working GH issues, milestones, roadmap, waffle board, etc (inspired by existing examples in js-ipfs and orbit)
identify good examples to explain the model
I'm suggesting go-ipfs as the starting point because
Its waffle board as-is seems to be the closest reflection of a "middle of the road" implementation of mechanics (though some tweaks still necessary)
Getting the PM process and roles right for go-ipfs will free up @jbenet's time
It lets us experiment with the distinction between responsibilities of a Project Lead (@whyrusleeping), Project Manager (@em-ly) and Product Owner (@jbenet) so that we can represent it accurately in the PM document.
It lets us revisit the go-ipfs roadmap & milestones for Q3 while we figure out the mechanics for expressing the Project Roadmap
Other than a bit of rewording (I've got a PR incoming on that front), the main things we need to do to the PM document are to
Rather than cooking those up in the abstract, I propose that @em-ly, @whyrusleeping and I try applying this model, as it's expressed in the document right now, to go-ipfs. That will let us
I'm suggesting go-ipfs as the starting point because
Whaddaya think?
cc @haadcode @diasdavid @RichardLitt