Re: [Inkscape-docs] [Inkscape-devel] License for the new manual

[Victor Westmann]

We really need to start working on it.

We need to have the official, original docs for Inkscape the sooner the
better. ;-)

Cheers,



--Victor Westmann

2017-05-10 16:18 GMT-07:00 Maren Hachmann :

> Sorry, I think I need to explain and ask one last question:
>
> I asked for CC-By, because that allows the licence to be changed when
> you make derivatives, and because it wasn't clear yet which licence we
> might want to use in the end, and because this wasn't my decision to make.
>
> Martin, you took it on you to count the votes. I think CC0 is out of the
> question by now. What is the current status?
>
> (Mc asked about CC-By, I think. I bet CR would prefer CC-By to CC-By-SA,
> from what I read.)
>
> Do people now just want to go with CC-By, either because they like it
> most, or to just 'be done' with it and start working? (I'd like to have
> some kind of final decision).
>
> Maren
>
> Am 10.05.2017 um 03:44 schrieb Victor Westmann:
> > Blessed be the LORD! ;-)
> >
> > Yay! +1
> >
> >
> >
> > --Victor Westmann
> >
> > 2017-05-09 18:43 GMT-07:00 brynn  >>:
> >
> > Yay!  Glad to have that settled  :-D
> >
> > Thanks Maren!
> >
> > -Original Message-
> > From: Maren Hachmann
> > Sent: Tuesday, May 09, 2017 4:37 PM
> > To: inkscape-de...@lists.sourceforge.net
> > 
> > Subject: Re: [Inkscape-devel] License for the new manual
> >
> > Update: I got a reply from Hinerangi, and she wrote:
> >
> > "I'm OK to relicense it to whatever you guys need (I guess the
> original
> > author also needs to be OK, if translations are considered a derived
> > work...). "
> >
> > So the 'Get started with Inkscape' book on flossmanualsfr.net
> >  is now
> > officially CC-By.
> >
> > Maren
> >
> > (The below licence request with the 'SA' was an inadvertant
> mistake... I
> > didn't want to determine or change the licence before an official
> > decision has been made. Fortunately, I got it right in the private
> mail
> > to her.)
> >
> > Am 06.05.2017 um 00:03 schrieb Maren Hachmann:
> > > Am 05.05.2017 um 19:57 schrieb Sylvain Chiron:
> > >> Le 05/05/2017 à 16:18, Maren Hachmann a écrit :
> > >>> Merci! :D (was Hinerangi's consent required?)
> > >>
> > >> I think she translated the first four chapters, so I’d say yes.
> > >>
> > >> Here is offered the opportunity for her to oppose.
> > >
> > > - Actually, she would need to consent, not be given opportunity to
> > oppose.
> > >
> > > Hinerangi, in case you haven't gotten the full info:
> > > We're asking you if you would be okay with the licence of your
> > > translated chapters in the linked book to be changed from GPL to
> > CC-By-SA.
> > >
> > > This is so the book can become part of a new manual effort for
> > Inkscape.
> > >
> > > Please let us know as soon as possible :)
> > >
> > > Thank you,
> > >  Maren
> > >
> > >> https://fr.flossmanuals.net/start-with-inkscape/about-this-book/
> > 
> > >>
> > >> Regards,
> > >> --
> > >> Sylvain
> > >>
> > >
> > >
> > >
> > 
> --
> > > 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
> > 
> > 

Re: [Inkscape-docs] [Inkscape-devel] Any chance we can make some docs material? (targeting the moon)

[Maren Hachmann]

@jazznico: Is there a way to transfer books between the French
flossmanuals site and the English one? I.e. would it be possible to
export and import a book? Or would it be possible to have a language
selection menu on flossmanualsfr instead, with English available for
selection? This would make it easier for our international editors to
deal with the interface.

Hi Brynn,

thanks for taking a closer look! (I'm so glad someone was able to take
the time for this.)

FLOSS is the abbreviation for 'Free/Libre Open Source Software'.
The websites are flossmanualsfr.net / flossmanuals.net respectively.
They allow for collaborative writing of manuals for FLOSS.

I fully understand the need for a WYSIWYG editor. The one from Booktype
is quite okay. Where it lacks is when you want to insert a file or image
- because you need to upload it first, then you need to find out that
the link to it that you need to enter in the insertion dialog is
'/static/filename.ext'. That's more difficult than it would need to be
(but you can use the same image file on different pages this way).

(Btw. what do you think of helping with the translation by making sure
that all images get uploaded? When I copy-paste from the French book, I
get all the images, but they are just links to the original book, not
part of the one I'm editing. And it takes quite some time to rename the
files to something English,  upload, add a useful placeholder text and
then exchange the links. I'd prefer to spend that time on translating.)

About the 'location', I've had this silly idea:

As a first step, we create/translate/update this introductory manual at
flossmanuals (if possible at the English site, to make it easier for
contributors). It's a great way for getting people started with Inkscape.

As a second step, or in parallel, we could also have a more
glossary-like, more technical manual, that explains what each menu item
/LPE/... does. This technical manual could also be used by developers to
document their changes, and it could use the more technical style with
Sphinx/reST/readthedocs. It could even start out simple, with keywords /
lists, and be refined by people who don't like those ;-)

(btw. I have volunteered to set this up, seems you overlooked ;-) - for
customization, translation and version branches, I'd still have to learn
a bit, but it doesn't appear to be too hard).

The one issue I see with this split is that it would spread resources
(us) a bit wide, maybe. But from the time when I started using Inkscape,
I know that having a manual like the one Elisa wrote would have helped
me a lot - I barely understood a word in Tav's manual.

Now, as an advanced user, I (claim I) know everything that Elisa
explains, but Tav's more technical manual contains so much more info,
which I'm now able to understand (and often have the urge to update).

So that's why I think that having two different manuals wouldn't be such
a bad idea. The technical manual could be written by the more technical
users and, hopefully, devs (when they change something).

Well, just an idea. Let me know if you think it's crap ;-)

Kind Regards,
 Maren

Am 10.05.2017 um 07:47 schrieb brynn:
> Hi Everyone,
>I've tried to read up and study and understand the info which
> Maren presented.  Because my understanding is extremely limited, I
> hesitate to offer any comments at all.  But for whatever it might be
> worth, here they arealong with a couple of questions.
> 
>First, one of your last comments:
> 
>> All of them would be FLOSS, have support for internal linking, allow to
> insert images and allow editing via browser.
> 
>I think you're using "FLOSS" as a generic umbrella term, as
> opposed to the FLOSS Manuals, right?  Because a couple of the Cons are
> lack of wysiwyg, which I've had the understanding Floss Manuals has
> (although I haven't seen it yet).  So you don't mean that Floss Manuals
> can be used for the writing, for all of them, and then exported out or
> transfered elsewhere for publishing, right?
> 
> Gitlab Wiki + X
> It seems to me like the lack of a wysiwyg editor is the most limiting
> factor (at least for as much as I understand). I'm just thinking of
> people who might be interested in joining the manual or documentation
> team.  This is a good non-coding opportunity for non-programmers, to
> contribute to the project.  They might be less likely to participate if
> they had to learn, even a simple language like Markdown, or whatever you
> call the code that wikis use.
> 
> Gitlab Editor + Sphinx / readthedocs
> 
>> - learning curve for admin (theming, plugins,...)
> 
> You must mean that someone else besides Martin would be the admin for
> the manual project?  Or, as admin for the gitlab account, is there
> something about this option that he would need to learn still?
> 
> All the pros for this option make it sound so good (at least what I can
> understand).  But still no wysiwyg editor.  I still think that might
> scare away some