-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #607 from ipfs/damedoteth-patch-1
Create 2023-introducing-the-ecosystem-working-group.md
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
title: Introducing the IPFS Ecosystem Working Group | ||
description: 'Nurturing a vibrant and sustainable IPFS ecosystem.' | ||
author: The Ecosystem Working Group | ||
date: 2023-09-05 | ||
permalink: '/2023-introducing-the-ecosystem-working-group/' | ||
header_image: '' | ||
tags: | ||
- 'Ecosystem' | ||
- 'Working Group' | ||
--- | ||
|
||
Since its initial release over 9 years ago, IPFS has been stewarded by a variety of teams and individual contributors, both within and outside of Protocol Labs. More recently though, it has lacked a dedicated team focused on nothing other than the success of the IPFS ecosystem. It is with this reality in mind that we are excited to announce the formation of **the brand new IPFS Ecosystem Working Group!** | ||
|
||
At launch, the IPFS Ecosystem WG consists of Protocol Labs employees, but we are forming with the explicit purpose of spinning out into our own independent entity over the coming months. We believe that this working group and its autonomy will be critical in helping propel IPFS toward a better and even brighter future. | ||
|
||
Initially, we have four core goals: | ||
|
||
1. Foster a thriving ecosystem by advocating for IPFS, | ||
2. Build bridges between IPFS and other ecosystems that could benefit from content addressing, | ||
3. Grow the community and develop strong and durable community ownership of the IPFS project as a public good, and | ||
4. Spin out from Protocol Labs into a self-sustaining organization that can support the IPFS community and build robust, effective governance for the protocol. | ||
|
||
The future of IPFS requires greater degrees of decentralization, so you can expect other IPFS-focused teams to begin spinning out from Protocol Labs in the future as well. | ||
|
||
As we continue to make progress towards these goals, we will provide updates and work in the open so as to keep the entire community in-the-loop with what we’re doing. A thriving ecosystem requires care and attention, and we believe that this new initiative and nimble team will be able to deliver on exactly that. But our work is only part of the story: community ownership means that your voice as IPFS users, operators, or contributors needs to be heard just as much as ours. | ||
|
||
**Have comments, questions, or concerns?** Please join us in discussion in the comments section below, via the [Ecosystem section of the IPFS Forums](https://discuss.ipfs.tech/c/communities/ecosystem/15), or the various chat links that follow – together let’s work on making IPFS thrive! | ||
|
||
[Forums](https://discuss.ipfs.tech/c/communities/ecosystem/15) | [Discord](https://discord.com/channels/806902334369824788/1146489977174233098) | [Slack](https://filecoinproject.slack.com/archives/C05PGBP697E) | [Matrix](https://app.element.io/#/room/#ipfs-ecosystem:ipfs.io) |