Proposal: Add Decentralized Data Stewardship WG #353
Conversation
This PR adds a new working group called Decentralized Data Stewardship. This will hold the work that @flyingzumwalt , @michellebrous and I are doing around supporting user research, collaborations, and products that deal with data management on the decentralized web. Some examples include: - Participating in groups such as [Data Together](https://datatogether.org/) - Conducting [user research around managing large volumes of data](https://github.com/ipfs/user-research/tree/master/large-volumes) on IPFS - Supporting collaborations between IPFS and community members who need to manage large volumes of data @steverichmond requested this PR several days ago, and I know @flyingzumwalt was intending on submitting it, but got pulled into other things. Please consider this a first draft that I'm sure @flyingzumwalt will have edits to, but at least the 'placeholder' is there for the Q4 OKR process.
TEAM_STRUCTURES.md
Outdated
| @@ -194,6 +195,20 @@ The IPFS Cluster Working Group is the team implementing IPFS Cluster. | |||
| - Design and implement IPFS Cluster. | |||
| - Provide knowledge and APIs that organizations with large data sets can use. | |||
|
|
|||
| ### Decentralized Data Stewardship | |||
|
|
|||
| - **Coordination**: Soon(tm) | |||
There was a problem hiding this comment.
can we have this repo before merging?
There was a problem hiding this comment.
It sounds like we should resolve the naming conversation above before we create the repo, but I'm happy to have this ASAP. I don't have permissions to create new repos, so when we align on a name, someone else will need to create the repo for me.
If possible (not sure how fine-grained org controls are in GitHub), since I'm going to be the Captain, it would be great to have top-level control of that particular repo once it's created.
There was a problem hiding this comment.
Repo created: https://github.com/ipfs/decentralized-data-stewardship
Made you an Admin of the repo and a Maintainer of a newly created team https://github.com/orgs/ipfs/teams/decentralized-data-stewardship/members
There was a problem hiding this comment.
Also got you a shine tab on the OKR spreadsheet for next quarter! https://docs.google.com/spreadsheets/d/139lROP7-Ee4M4S7A_IO4iIgSgugYm7dct620LYnalII/edit#gid=1521120849
TEAM_STRUCTURES.md
Outdated
| @@ -194,6 +195,20 @@ The IPFS Cluster Working Group is the team implementing IPFS Cluster. | |||
| - Design and implement IPFS Cluster. | |||
| - Provide knowledge and APIs that organizations with large data sets can use. | |||
|
|
|||
| ### Decentralized Data Stewardship | |||
There was a problem hiding this comment.
Stewardshipthe job of supervising or taking care of something, such as an organization or property.
Do we actually want to name it Stewardship? I'm concerned that people in the community might read it as "the IPFS WG that archives and manages datasets" in the same way that https://github.com/ipfs/archives was seen in the past as the "effort to archive and manage all the datasets on IPFS"
There was a problem hiding this comment.
I think people's confusion around IPFS repos and initiatives doesn't come down to choice of name. For example, my experience with /archives is that the README purpose isn't especially clear (to me, as an outsider), so I followed the README instructions to look at the issues to understand ongoing work. Then, my read of the issues led me to believe that /archives is exactly what you say it was not meant to be: PL's effort to archive datasets on IPFS. Changing the WG name only would not help clarify this misunderstanding; it is a layered communication problem.
So, I don't think naming this WG Stewardship will confuse people if we're clear in its home repo about scope and purpose, and make sure to edit that README as the project evolves (and when/if we hear feedback that certain terminology is unclear).
As for the selection for that word specifically, it is meant to reflect the WG's focus on understanding and supporting how people might take care of data over time on distributed networks, within contexts of:
- the need to manage data as mutable, connected, findable assets
- the reality that on the decentralized web, data will be managed with groups of people, and groups of organizations, both of whom will need policy layers to support human consensus on top of IPFS trustless systems
Is there another way to name the WG that you think is clearer @diasdavid ?
There was a problem hiding this comment.
Let's move forward with the Stewardship word for now and change later if it becomes an issue
👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽 Congratulations \o/
|
This PR adds a new working group called Decentralized Data Stewardship. This will hold the work that @flyingzumwalt , @michellebrous and I are doing around supporting user research, collaborations, and products that deal with data management on the decentralized web. Some examples include:
I would be the Captain, with @flyingzumwalt advising as needed.
@diasdavid requested this PR several days ago, and I know @flyingzumwalt was intending on submitting it, but got pulled into other things. Please consider this a first draft that I'm sure @flyingzumwalt will have edits to, but at least this 'placeholder' is here for the Q4 OKR process.