Hello. Sorry for the very delayed response. I agree with everything you said. See below.
On 06/24/2017 03:21 AM, Sébastien Blaisot wrote: > Having the manual in a separate github project doesn't help to sync code > merge and manual update. > > Other projects manage this by asking contributors in PR to update manual > before accepting merge. > No manual update, no code merge. (at least for each code change that > change the interface or behaviour) > > is it possible to move the manual inside the same github project ? Yes, it is. I figure making it a subdirectory of the root would make the most sense. (The only thing I wonder is if doing so will complicate distro packaging, where they may think that Sphinx and Graphviz are required to build Mixxx itself.) So let's review and merge the four pending PRs against the manual repo, then we can add it to the main one and delete the separate one. https://github.com/mixxxdj/manual/pulls Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
