momack2
commented
5 years ago I think this is a great idea!! A blog that explains what we're trying to do, the research we've done so far, and what our plans are next quarter would be really awesome (but I don't think it needs to be before/concurrent with the npm-on-ipfs post if that's ready first).
Separately (either before or coinciding with this), it'd be great to loop the IPFS captains/WGs more into the work that is being done here as we start planning for the work we need to take on in Q2. It'd be great if there were a video, presentation, or workshop to give the team an overview of the great research that has been happening here and help us chart our course forward to make the most of our eng efforts. Example topics to cover: intro to the package manager use case/market (glossary, categories, goals, etc), what we've learned from research/prototyping so far, the low-hanging fruit we should be pushing on ASAP to make IPFS (more) useful to package managers, the potential trajectories we see for engaging more with this market, what this group is diving into next. Ideally, this should help everyone feel a little closer to the package manager use case, and give folks lots of fodder to answer "what should I work on to drive toward this goal"?
mikeal
andrew
In last weeks Package Management call we discussed, making the work of the Package Managers Working Group public would be a good way to draw people for discussion as well as providing useful documentation for others to reference as well as cementing that Package Management is a key goal for IPFS this year.
I'd also like to get some of the things I've been writing public so that pm maintainers can discuss and contribute async (some of them are in very different timezones and difficult to pin down for calls)
So, what steps should we take to prepare for going public?
Should we announce the working group on the IPFS blog? If so, should it be before or alongside @achingbrain's npm-on-ipfs post?
Do we need a separate section on https://discuss.ipfs.io or should we keep discussion within a GitHub repository issue tracker?
🚢 Ship list
[x] Choose a WG captain (and TPM if different)
[ ] Add intro and call to action to readme
[x] Either publicize or remove two private google docs links from readme
[x] close+delete issues that shouldn't be public
[ ] announcement blog post on https://github.com/ipfs/blog/
[x] Transfer repo to ipfs org
[x] Make this repo public
[x] Add links to package-managers repo and working group in relevant other repositories