TL;DR We need a project management tool in order to asynchronously coordinate amongst different teams, to reduce duplication of effort, and allow anyone to easily jump on board to contribute to Yearn. If others feel that they agree, the next step is to decide on closed source services vs open source. I’m a fan of the latter for the reasons described below due to considerations of cost, vendor lock-in, and contributing back to the open-source ecosystem.
(Copying the below from discord)
I’m not sure if this has been answered already or posted about but do we have a semi-organized Todo List / Kanban board for everything that is currently going on? We often get a lot of similar suggestions (which is great!) but it would be even better if we can get everyone on the “same page” in more ways than one, where we can expand on topics rather than post similar variations of the same.
(I know there are some hackmd docs floating around but the PM in me knows a quick visual map of what we are working on, what we’re blocked on, what’s in the pipeline etc can provide us with outsized benefits)
Not sure how others feel re: tooling but I would be open to trying open-source tools especially if it creates a feedback loop wherein it creates value for the OSS ecosystem(whether financial or direct code contributions, one coming to mind being Kanboard (it is self-hosted and we won’t run into issues regarding cost/user/month). As an aside as I find it a shame there isn’t a true open source/decentralized standard for project/product management(gitcoin grants when?). That said, the functionality of such tools should not compromise our ability to coordinate/deliver and as such we should strike a good balance so I’m definitely interested to hear what others have to say (if this means that the core teams find it easier to work using established/traditional tools such as Trello/Asana then I’m all for it too, just want to ensure everyone who wants to contribute can while minimizing our costs of operations).
I think the community as a whole has shown they are very committed to help so my philosophy has always been, whether professionally or personally, to facilitate this and then get out of the way.
Our imperative should be to make it as easy for anyone, technical or not, to contribute to the Yearn ecosystem. Ideally, I envision Yearn to be the “alien dreadnought” of DAOs, where emergent behavior arises to grow Yearn and its environment (recursively) in ways we could not imagine.
Having worked as a Product/Program/Project Manager for a number of years in companies ranging from stealth mode 5 person startups to larger corporations, I can say from experience that adequate communication between teams/areas of responsibility has been one of the major keys to maintaining or increasing forward velocity while maintaining quality(and most of all keeping everyone happy & engaged). While we have not yet begun to experience true growing pains I am beginning to see signs of it on the forums(great ideas that dead end and get buried, duplicated work, people wanting to contribute but not knowing where to start, etc).
As we grow and consequently develop ad-hoc organizational strategies, we may inadvertently silo ourselves preventing cross-pollination/diffusion across our various ‘subdivisions’. Transparency is paramount, especially so in nascent fluid/flat DAO-democracies as everyone is understandably skeptical of any impositions of power and influence which could undermine. This is a good thing. We can empower all the members of our DAO by providing a structure by which we all understand the direction we are heading and maybe in doing so can also find gaps others didn’t see.
Anyone joining our community should immediately be able to dive in and begin contributing without needing to read hundreds of pages of forum posts to know if they are duplicating effort or if it’s something that hasn’t be mentioned before.
So with all this fluff aside here are some options (I have no affiliation to the projects mentioned):
- Closed Source: Trello, Asana, Pivotal , Jira
- Familiar, have polished UIs, and bug free so contributors can hit the ground running
- Cost usually is $/user/month which limits our contributor pool
- User board limitations based on cost which then limits who can
- Open Source: Kanboard / Wekan (others?)
- Prevent vendor lock-in
- Own our data
- Contribute to Open Source (wait are these pros beginning to sound familiar)
- “Free” (no user costs only those for self hosting until a decentralized solution comes along hint hint)
- Extensible / Customizable with benefits that spill over to overall OSS community
- Operational overhead: We need to self-host / some maintenance / time needed there. Anyone have a spare server?
- Not as feature-filled as other commercial platforms
Middle ground: Zenhub Extension but this requires creating additional github repos/granting permissions we likely wouldn’t comfortable with.
In any case, having the most pertinent information allows us to push in the same direction regardless what solution we choose. In the spirit of open source and supporting the ethos which continues to drive us forward, I’m leaning towards an open-source solution such as Kanboard (https://kanboard.org/), docs (https://docs.kanboard.org/en/latest/user_guide/index.html) as it has an extensible interface (via plugins Kanboard Plugins) which means we can customize it to our heart’s content. If the theme has you down we can make our own or use this one GitHub - kenlog/Nebula: Modern theme for kanboard + syntax highlighting for Markdown code 💨 . I’m not married to it though and would be more than happy to hear what everyone else thinks but I do think we should consider this sooner rather than later.