[OPEN-ILS-DOCUMENTATION] Need help with proofreading some EG 2.4 documentation

[Yamil Suarez]

On Aug 6, 2013, at 11:03 AM, Dan Scott <dan at coffeecode.net> wrote:
> 
> Crazy idea to avoid bottlenecking, depending on how many files we're
> talking about: 
> 
> 1. Push the draft docs into a git working "collab" branch
> 
> 2. Put up a wiki page linking to each file (git version and HTML
> version), and let people edit the wiki to show that they're working on /
> have finished proofreading each file.
> 
> 3a. If the proofreader also has the skills to push changes to git,
> then they can push their changes to the collab branch
> 
> 3b. Otherwise, they could add comments to the wiki page to indicate
> where changes need to happen, and then someone who may not be yboston
> would be able to make those changes
> 
> Seem doable?
> _______________________________________________
> OPEN-ILS-DOCUMENTATION mailing list
> OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation


For the record, I have about 28 individual Asciidoc files with 28 matching HTML files (plus images).

I don't know if this approach will be worth it if I only have one or two people helping me, compared to the time it will take me to set it up. Also, I will probably be the only one that is using Git in this group. I am still a Git newbie, and it is great to see ways that source control can be leveraged, while taking advantage of current community practices, to make our lives easier. I will keep this approach in mind for future use. 

Does that make sense?

Thanks,
Yamil