Contributors should also be aware that it's not okay to copy/paste content from blogs, tutorials, etc. For this document, everything must be re-written from scratch, and all screen captures, graphics etc. must be of our own making and cc0 (public domain). Anyone not interested in contributing 100% public domain content, should not contribute to this project.
- For a printable book, this sounds like a good idea :D
For a more 'scientific' manual, I think it's not suitable to do this in Scribus, and that we should turn to a proven documentation software.
I'm open to suggestions, as long as it's FLOSS.
Scribus can export to lots of different digital formats as well.
I've heard that Scribus performance drops dramatically with the number of pages. How would you go about translatating the book?
I would have translators do it in Scribus.
I strongly disagree with CC0 - I would only contribute to something that where attribution and copyleft are honored.
Why does content in an inkscape manual need attribution? Contents are more useful if cc0.
It's fine to pull content from properly licenced sources, imho, too.
I disagree. This would create a tangle of licenses and attribution requirements that will make the contents less usable in/by other projects. We should remove the burden of attribution where possible.
There are quick start guides with good licences - this would make the process a lot faster, if it wouldn't need to be written from scratch, but only modified. So yeah, count me out :)
Maren
-C
On Sat, Apr 29, 2017 at 12:01 AM, Maren Hachmann <maren@...3165...> wrote:
Great :)
I think, in this context, it makes sense to also link to the thread on the translators mailing list, where many of us have already been discussing the issue, and started to investigate options.
translator/thread/CAPOH7%3DZn3sWhZ%3D1DDB-1FUp%2BQUZzrLmyy7iOFiL1VcfY0maG9g% 40mail.gmail.com/#msg35807172
Victor (who initiated the thread) has already written about his findings about Sphinx there, and he also linked to a list on github, where different documentation systems are listed (sorry, your latest email is still on my todo list, Victor).
Elisa has mentioned the Booktype instance of flossmanualsfr, as far as I remember.
Regards, Maren
Am 29.04.2017 um 00:17 schrieb Martin Owens:
On Sat, 2017-04-29 at 00:01 +0200, Maren Hachmann wrote:
Would it make sense to use gitlab's new subgroups feature for this?
The inkscape-docs team could be a sub-team of Inkscape, that way. There are only 4 members as of now, so changing wouldn't be so difficult as it might be later on.
Agreed.
I've moved everything around and re-added the members to the group.
Project is now: https://gitlab.com/inkscape/inkscape-docs/manuals Group is now: https://gitlab.com/inkscape/inkscape-docs
Best Regards, Martin Owens
------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel