Support server side / auto conflict resolution
Open
api
feature
roadmap
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
Migrated from the CouchDB Summit 2017 topics.
No comments or description provided. This has come up many times before and isn't trivial for many reasons....comments from @janl or @davisp as to why this hasn't been done yet might be illuminating for others who might try to implement this naively.
Contributor guide
Research direction
No source files, tests, or entry points are named. Start by reading the prior conflict-resolution discussions referenced in the issue and the CouchDB synchronization context, then establish the requirements and constraints. Done criteria are not specified in the issue, so maintainers must define them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100