Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Social-value motivations > Platform-centric demos #4

Open
benhylau opened this issue Mar 27, 2019 · 7 comments
Open

Social-value motivations > Platform-centric demos #4

benhylau opened this issue Mar 27, 2019 · 7 comments
Labels
Discussion Topic An idea you'd like to discuss here to maybe form a project or extend into Camp

Comments

@benhylau
Copy link
Member

I would personally like to see more projects that start from social-value motivations over platform-centric demos. For example...

Platform-centric:

Deploy this application across the network to provide distributed storage.

Social-value motivated:

Using distributed storage systems, install nodes on the local network and map the physical and virtual infrastructures, followed by a discussion session about community governance models that ensure local ownership and digital sovereignty.

I think the latter example provides more opportunity for bidirectional learning across disciplines and specialities.

@benhylau benhylau added the Discussion Topic An idea you'd like to discuss here to maybe form a project or extend into Camp label Mar 27, 2019
@alexalekseyenko
Copy link
Collaborator

To that end, do you think it would be useful to define some capabilities that we'd likely want to have as a community? For example:

  • Chat/broadcast to transmit messages to those who could benefit from them
  • Schedule to let organizers communicate the days' activities
  • Map to display points of interest

Or to list some topics we'd like to explore? Such as:

  • Community governance models that ensure local ownership and digital sovereignty
  • Considerations for designing mesh network infrastructure
  • Designing applications for limited connectivity environments

If you think it would be useful to have such lists, would this be the best place to construct them?

@amaliejames
Copy link

I agree that a community board for those kinds of lists would be helpful! For example, we intend to use camp as a real world test to see what happens if network falls out of sync with the internet in a low connectivity environment. Would be awesome to find folks who are curious about similar questions to connect with!

@benhylau
Copy link
Member Author

@alexalekseyenko oops just saw your message, sorry I missed it before.

Capabilities

Chat/broadcast to transmit messages to those who could benefit from them

For example, GUN #2 SSB #6 Cabal #7 are all related to the same thread.

Topics

I think #12 is one of these topics


My thinking is to use the Issues board on this repository as the place to advertise things and store discussion summaries (but perhaps there are better tools for a "community board"?) and use #dweb-camp-2019-apps:matrix.org as a place for synchronous discussions?

How about posting chat handles in Issues like...

If you are interested to discuss more, ping me on #dweb-camp-2019-apps:matrix.org, I am @benhylau:tomesh.net!

I can make an Issue template to help with this, or create new Issues tags like Capabilities and Topics?

Thoughts? @alexalekseyenko @amaliejames @amberinitiative @ArtsEd4All

@alexalekseyenko
Copy link
Collaborator

No problem. Thank you for following up.

I did notice that there were multiple issues regarding chat, and I thought that might be an indication that high level planning would be useful. Namely, there are probably some basic things we can anticipate people needing, like chat, or an up-to-date schedule, and it would be good to have at least one solution working and tested well in advance.

GitHub Issues are great for tracking individual work items, but I'm not sure that they provide a good high level overview of the situation (in that way that lengthy lists of things usually don't). To that end, I think it could be helpful to synthesize that information and to add it to the README.

What that might look like:

Applications

Chat

SSB at a minimum link to relevant issue
Other options in the works links to other issues

Schedule

GitHub README at a minimum link to page
Other options in the works links if there are any

Map

Does this even make sense? link to discussion issue

@benhylau
Copy link
Member Author

benhylau commented May 2, 2019

@alexalekseyenko I sent a PR using new labels to group. That is perhaps not as detailed as your example above (e.g. doesn't really summarize the current status of each category). Do you think we should be more explicit?

Also invited you as collaborator to this repo if you'd like to be more involved with the curation :)

@benhylau
Copy link
Member Author

benhylau commented May 2, 2019

@amaliejames would a posting of something like Explore sync behaviour of distributed protocols under poor connectivity environments to the Discussion Topic label be sufficient to attract people to that interest?

@alexalekseyenko
Copy link
Collaborator

@benhylau Thank you for adding this to the page. It feels like a more gentle introduction to what's happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Topic An idea you'd like to discuss here to maybe form a project or extend into Camp
Projects
None yet
Development

No branches or pull requests

3 participants