Re: [Inkscape-docs] [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-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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
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.
https://sourceforge.net/p/inkscape/mailman/inkscape-translator/thread/CAPOH7...
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
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-devel@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-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, 2017-04-29 at 07:19 -0600, brynn wrote:
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/
No, that's not licensed. We can't and shouldn't use it until it has a known and open license.
Unfortunately there are going to be lots of good resources that we just can't use.
But you can use "the idea" of the content. So having similar sections and covering similar ground.
Best Regards, Martin Owens
I agree with Brynn. We should first focus in create the official/original doc of Inkscape on Gitlab and then try to do this hard copy book to sell in the inkscape store.
I just wanted to gather the opinions of you guys if more or less following the index of a 3rd party material is a good idea or at least a good place to start. We don't have to copy it topic by topic but we could inspire ourselves in it.
Cheers,
--Victor Westmann
2017-04-29 6:19 GMT-07:00 brynn <brynn@...78...>:
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/st art-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-devel@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-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (4)
-
brynn -
Maren Hachmann -
Martin Owens -
Victor Westmann