Future of bpkg #122

As I look through the issues, the open pull requests, and the overall state of bpkg, I wonder: Where to from here?

This project was able to see some corporate sponsorship through committed hours, but those days are long gone, and it has become difficult to give the much deserved attention to bpkg over the years. I find myself with new energy and time to be able to commit again.

Issues I think that should initially be addressed:

• Test coverage - Test your code #72
• Use shellcheck - Code quality #78
• Migrate from package.json to bpkg.json (with backwards compatibility - we did something similar with clibs) - Add support for bpkg.json, next to package.json. #124
• Make installation easier
• Make publishing easier
• User guides
  • Best practices
  • Pitfalls

I'd love some thoughts or feedback from anyone interested in seeing this move forward ❤️