sillsdev / sillsdev/languageforge-lexbox
Create instructions for admins about resetting Language Forge projects
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
I recently spent some time dealing with a project that had been reset on Language Depot, but the users on Language Forge continued adding entries to the project after it had been reset, not knowing that the Language Forge copy of the project would also need to be deleted & re-created in order to sync. I was able to get that sorted out with no loss of user data, but it took me about 3 hours total to do so.
I wonder if we should write some instructions for admins who are doing a project reset, saying "If there's a Language Forge project involved, make sure the user knows they'll need to delete and re-create the Language Forge project". Because it's possible that the LD admins are communicating the need for starting over with FLEx but not with Language Forge.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or documentation entry point is named. Start by verifying the Language Depot reset and Language Forge delete-and-re-create workflow described in the issue; done means admins and users have clear instructions explaining the required action to preserve synchronization and avoid continued work in the reset project.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100