I don't mean to slow anyone's roll here. But wouldn't it make more sense to put any kind of energy towards documentation into the much discussed, direly needed, user-focused, step by step manual? Rather than starting from scratch on a whole different kind of project?
There are many books out there already, which amount to a series of tutorials. It's not a bad thing. I just think this kind of project is better suited for a single author, or maybe a small team. And I think the project needs the manual much, more more than the community needs another book of tutorials. As far as I understand, all that's needed is an English translation of...well I can't find a link to the French version. Here's a link to whatever has been translated already: https://fr.flossmanuals.net/start-with-inkscape/introduction/ Once we have the translation, we'll be off and running to update and finish it! By the way, is there anything those of us who can't translate, can do, to help the translators? And won't such a new book of tutorials have to be published? A big obstacle to writing any book is getting it published. You almost have to have an invitation from a publisher to be certain a book will get published. Or publish it yourself, which is not easy eitiher. Just my opinion :-) brynn -----Original Message----- From: Maren Hachmann Sent: Friday, April 28, 2017 4:01 PM To: Inkscape-Docs ; Inkscape Devel List Subject: Re: [Inkscape-devel] Any chance we can make some docs material? (targeting the moon) 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. Maren > Am 28.04.2017 um 16:14 schrieb Martin Owens: >> On Fri, 2017-04-28 at 12:39 +0100, C R wrote: >>> I'd love to quit my job and just do docs. :) Unfortunately, that's >>> what it would probably take to get docs going to the extent we'd >>> like. >>> It's been discussed before, but never gone anywhere because of lack >>> of time/hands involved. >>> >>> Yes, we should use Scribus to do it. In fact, it should probably be a >>> github project to attract contributors. This way we can patch what >>> needs to be patched when stuff changes in subsequent releases. >> >> Sounds like you have a solid step one Chris. >> >> Here's the inkscape-docs group on gitlab, EVERYONE should join, there >> should be a button to join: >> >> https://gitlab.com/inkscape-docs >> >> And here's the new book/manual/docs project where files can be put: >> >> https://gitlab.com/inkscape/manuals >> >> I recommend using the wiki attached to the project to plan the >> adventure slowly. Add a bit at a time and don't rush to have something >> "complete" but have something small produced. >> >> 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-de...@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> > ------------------------------------------------------------------------------ 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
