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

Public "PR" mechanism #42

Closed
parkan opened this issue Oct 12, 2016 · 4 comments
Closed

Public "PR" mechanism #42

parkan opened this issue Oct 12, 2016 · 4 comments

Comments

@parkan
Copy link
Contributor

parkan commented Oct 12, 2016

This is one potential mechanism for data set aggregation: prompt a remote operator to merge in some statements from your node. Can probably take the form of a web UI that shows the changeset (+ potentially any conflicts) and lets the user merge that set through the normal mechanisms.

This is a nice, shareable way to get users to interact with the system and potentially supplements whatever other aggregation mechanisms we choose to use.

Complements #23 for less trusted sources.

@parkan parkan modified the milestones: V3, V4 Oct 12, 2016
@denisnazarov
Copy link
Contributor

I like this idea 👍

@parkan
Copy link
Contributor Author

parkan commented Oct 12, 2016

Semantics of whether or not this crosses namespace boundary is tbd

@vyzo what do you think?

@vyzo
Copy link
Contributor

vyzo commented Oct 13, 2016

Maybe we can do that, but it may better belong to aleph in terms of UX.

@parkan
Copy link
Contributor Author

parkan commented Oct 13, 2016

Agreed, gonna move to that repo 😄

@parkan parkan closed this as completed Oct 13, 2016
@parkan parkan removed this from the V4 milestone Oct 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants