The first thing I did when I started building Savoir was not to write code, but to plan my sprints with a tool called Codetree. I highly recommend them by the way, if you're looking for a good GitHub powered project management tool. I planned my entire feature set through epics, and I would break things down into smaller issues on a bi-weekly basis. I personally really like working in more structured environments.... - Source: dev.to / over 1 year ago

Very much agree, most projects I work on these days have components in multiple repositories and trying to coordinate work among them is challenging. We use Github Issues as a source of truth but have resorted to using third-party software on top of them to help get a bigger-picture view. Currently we're using Codetree: https://codetree.com/. - Source: Hacker News / almost 3 years ago

I'm thinking of using some bug bounty type of services to speed up bugfixes and adding new features, anyone has experience with it? I mean services like https://www.bountysource.com/ , https://gitpay.me/ or https://issuehunt.io/. Source: almost 3 years ago

I don't think we have a good model for monetary rewards for maintenance. If Haskell.org was providing support contracts covering a wide range of libraries, I would guess a lot of companies would use the option. However, signing a support contract with a maintainer of every dependency I have is infeasible. Things like Gitpay (bounties for PRs) have been tried time and again, and they never take off. Source: about 3 years ago

Donate to the project, start a company employing devs, buy support from Canonical or RedHat or SuSE, pay for issues to be fixed through GitPay or BountySource. Source: about 3 years ago