nextcloud / nextcloud/integration_dropbox
Lacking documentation explaining what tool actually does
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Does it preserve the folder structure?
Does it copy the files or move them (i.e. are the files left behind for data safety)?
Is there a post-transfer verification process that is run, perhaps doing a hash of each file, providing confidence that the files have been transferred correctly without me having to do that for 127,947 different files manually?
Does it preserve the file version history for each file so previous versions can be recovered on Nextcloud, once Dropbox is retired?
Having something that describes what the tool does (and does not do) would lend confidence to those who want to entrust their data to it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Dropbox integration's documented or observable transfer behavior, focusing on folder structure, copy versus move semantics, post-transfer verification, and file version history. Done means user-facing documentation clearly answers each question and explains what the tool does and does not preserve.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100