BE engineer + TW time to work on Git LFS docs
Problem to solve
We have at least two pages about Git LFS. Both are old, crusty, and need significant work. I would like to make these better, but need help from an engineer to do so. @ashmckenzie has expressed some interest, and I think it's better to request a small percentage of his time rather than ask him to fit in this work around scoped / planned work.
Further details
The pages:
- User doc: https://docs.gitlab.com/ee/topics/git/lfs/
- Administrator doc: https://docs.gitlab.com/ee/administration/lfs/index.html
Amy can clean up the administrator doc to bring it up to current style expectations. The changes to the user doc are harder. It should consist of a set of subheadings, each containing steps for the user to complete. In broad strokes:
- configure your project
- configure the destination for the files - whether that's "configure your GitLab server for Git LFS" or "configure your external storage"
- install the client locally
- ???
- PROFIT!
The catch: Amy doesn't know what each of those subheadings should contain. Ash apparently does!
Proposal
Amy to get a percentage of Ash's time to set up a demo / test project using Git LFS that stays as close to real-world conditions as possible. As we work through each major chunk of work (the numbered list), polish and publish that subheading. Even if we don't complete the review of the page in a single milestone, every bit of cleanup helps. The page is currently in a state that I'm amazed anyone has EVER set up Git LFS successfully.