Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ipfs-inactive/package-managers
[ARCHIVED] 📦 IPFS Package Managers Task Force
https://github.com/ipfs-inactive/package-managers
ipfs package-management working-group
Last synced: 16 days ago
JSON representation
[ARCHIVED] 📦 IPFS Package Managers Task Force
- Host: GitHub
- URL: https://github.com/ipfs-inactive/package-managers
- Owner: ipfs-inactive
- License: mit
- Archived: true
- Created: 2019-02-12T16:57:00.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-04-16T09:53:04.000Z (over 4 years ago)
- Last Synced: 2024-08-16T16:22:30.172Z (4 months ago)
- Topics: ipfs, package-management, working-group
- Homepage:
- Size: 9.89 MB
- Stars: 98
- Watchers: 27
- Forks: 11
- Open Issues: 34
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## This repository has been archived!
*This IPFS-related repository has been archived, and all issues are therefore frozen*. If you want to ask a question or open/continue a discussion related to this repo, please visit the [official IPFS forums](https://discuss.ipfs.io).
We archive repos for one or more of the following reasons:
- Code or content is unmaintained, and therefore might be broken
- Content is outdated, and therefore may mislead readers
- Code or content evolved into something else and/or has lived on in a different place
- The repository or project is not active in general
Please note that in order to keep the primary IPFS GitHub org tidy, most archived repos are moved into the [ipfs-inactive](https://github.com/ipfs-inactive) org.
If you feel this repo should **not** be archived (or portions of it should be moved to a non-archived repo), please [reach out](https://ipfs.io/help) and let us know. Archiving can always be reversed if needed.
---
[](https://protocol.ai/)
[](http://ipfs.io/)
[](http://webchat.freenode.net/?channels=%23ipfs-package-managers)
## Status: INACTIVE
In 2019, this working group focused on making IPFS a usable platform for package managers. The working group has been spun down in favor of focusing on improving the core protocol but this repo still contains quite a few important learnings and experiments.
In this group, we:
* Surveyed known package managers - https://github.com/ipfs/package-managers/tree/master/package-managers
* Experimented with running package managers on IPFS to understand the relevent pain-points: https://github.com/ipfs/package-managers/issues?q=is%3Aissue+is%3Aopen+label%3A%22Type%3A+Experiment%22.
* Did a ton of user research - https://github.com/ipfs/package-managers/tree/master/docs
* Improved bitswap performance (in go-ipfs) - https://github.com/ipfs/go-bitswap/pull/189
* More than doubled initial ipfs add performance (in go-ipfs) - https://github.com/ipfs/go-ipfs/issues/6775
* Added file modes and modification time support to the IPFS spec - https://github.com/ipfs/specs/blob/master/UNIXFS.md#metadata
* Explored ways to improve how go-ipfs mounts /ipfs and /ipns as a local filesystems - https://github.com/ipfs/go-ipfs/pull/6612
## Why are package managers important to the future of IPFS?
- IPFS is *very close* to becoming a great tool to solve real problems for package manager users, package publishers, and package manager maintainers! Plus, closing those gaps will make IPFS better for everyone while giving the IPFS community a yardstick for how to measure our success in the future.
- Package manager maintainers and consumers are an important demographic to IPFS' future: developers who may not be IPFS pros yet, but who can get excited and engaged about IPFS in its current state, enabling everyone to help IPFS improve both on existing fronts and in problem areas we haven't yet envisioned
- Introducing IPFS tooling and support can create direct value and impact in the overall package manager ecosystem by saving developers time and empowering resilient development experiences for developers using IPFS or IPFS-powered tools and registries.
## Goals for IPFS and package managers
1. Get the package manager maintainer community excited about the benefits of using IPFS in their ecosystems
2. Demonstrate to package consumers that IPFS is _holistically better_ than current centralized package managers (this may mean parity on some use cases, but significantly better on others)
3. Increase awareness and engagement with IPFS (either to build new tools, or contribute directly) among package manager users/package publishers
## Non-goals
- Become the sole centralized maintainers of large new package manager infrastructure
- Hack together a demo to “subvert” package manager maintainers or “steal control” from package creators
- Implement YAPM (yet another package manager)
## Starter reading
There's a wealth of research, analysis and other tasty info to be found in the [docs directory](docs), but if you're just getting started with package managers and IPFS, you may want to start with these:
- [Package management glossary](docs/glossary.md)
- [Package manager categories](docs/categories.md)
- [Problems with current-state package managers that IPFS can help solve](docs/problems.md)
- [How IPFS concepts map to package manager concepts](docs/concepts.md)
- [IPFS Package Manager Upgrade Paths slide deck](docs/ipfs-package-managers-upgrade-paths.pdf)
- [Finding the best abstractions for talking about package managers](docs/abstractions.md)
- [Tactical tree for implementing IPFS in a package manager](docs/tree.md)
- [Package manager (pre-IPFS) pain points, sorted by user type](https://app.mural.co/t/protocollabs6957/m/protocollabs6957/1557168696127/577c9453a3c51199c8163cf0fe5701294e55f99b)
- [Package manager goals in the 2019 IPFS roadmap](https://github.com/ipfs/roadmap#-package-managers-d1-e5-i3)
- [Directory of existing package managers](package-managers) with notes on language, categorization, clients and more
## Current IPFS integrations
These package managers already have some form of IPFS integration underway. If you're a package manager maintainer and want to be in this list, please reach out. :smile:
- [dpkg](package-managers/dpkg.md#existing-ipfs-support)
- [f-droid](package-managers/f-droid.md#existing-ipfs-support)
- [go](package-managers/go.md#existing-ipfs-support)
- [guix](package-managers/guix.md#existing-ipfs-support)
- [homebrew](package-managers/homebrew.md#existing-ipfs-support)
- [nix](package-managers/nix.md#existing-ipfs-support)
- [npm](package-managers/npm.md#existing-ipfs-support)
- [ports](package-managers/ports.md#existing-ipfs-support)
- [pypi](package-managers/pypi.md#existing-ipfs-support)
- [rpm](package-managers/rpm.md#existing-ipfs-support)
- [rubygems](package-managers/rubygems.md#existing-ipfs-support)
- [wapm](package-managers/wapm.md#existing-ipfs-support)
## Blockers
There are still some [current issues with IPFS](docs/blockers.md) that are limiting package manager adoption today.
## Package Manager Maintainer Service Blueprint
[Video walkthrough](https://drive.google.com/a/protocol.ai/file/d/1CJUTzuN7QcsA0QBKMNEcTtNBdNps7uyH/view?usp=sharing)
## License
All documents are licensed under the [CC-BY-SA 3.0](https://ipfs.io/ipfs/QmVreNvKsQmQZ83T86cWSjPu2vR3yZHGPm5jnxFuunEB9u) license © 2019 Protocol Labs Inc. Any code is under an [MIT license](LICENSE).