Issues Tree

[abitrolly]

I would like to link see my funded issues as a tree.

First, other people could see the main issue that I am trying to solve. Many issues are interconnected, so it is useful to see the root cause or how deep is the rabbit hole.

Second, other people can co-fund the issues. Not only the one on the surface, but also the one that are below. People should be able to pour additional tokens into the tree for the same distribution or adjust it before hitting the final button. Foundations and companies account that can back specific trees with real compensation that people with expertise to create trees can't provide.

Third, exporting this tree will allow people to extract more useful stats and insights.

[owocki]

thanks for the feedback @abitrolly !

when you say "see as a tree", im having a hard time visualizing it. i'm also curious if all the information one would need to generate this information is available straight away on github. would you be able to take 3 minutes in draw.io and mock up what you're talking about ?

[PixelantDesign]

great idea!

[abitrolly]

@owocki indented list is okay for the start. For example

• Webpack bundle failing at CID: Unexpected token: name (CID) multiformats/js-cid#38 (failure to build project)
  • Does not work with UglifyJS version 2 ipfs/js-ipfs#938 (comment) (real cause that needs to be fixed)
    • and on the issue above you will find the rest of the tree that needs to be be merged

[vs77bb]

@abitrolly This is very interesting. I like the specific point that we should incentivize community contributors to post $5-10 intial bounties, with the thought that this initial bounty might incentivize others to meaningfully contribute to the pot (including those with Foundation-level backing).

In current time, the $5-10 bounty usually struggles to incentivize people by itself.