@Moini
send a reply
6 years, 5 months ago
@john.morgan I'm online now. If you want to have your account on flossmanuals deleted, you need to contact Mick, the admin. But what would be the drawback of just leaving it as is? It doesn't mean you need to do anything.
@john.morgan
send a reply
6 years, 5 months ago
@Moini @john.morgan LOL, Moini, do you have a minute?
@john.morgan
send a reply
6 years, 5 months ago
@Moini @john.morgan LOL, Moini, do you have a minute?
@john.morgan
send a reply
6 years, 5 months ago
@Moini
Snippet:
[
Context]
Hi Jon,
those tasks were meant as a list to choose from (or think of your own) - I think you've made a good choice that will help bring the manual forward in an important way.
I very much value contributors who are realistic about how much they can and would like to do - it makes it a lot easier to plan and to understand what one can ask from someone, without making them uncomfortable. So - thanks :) And no worries!
So, what I'd like you to do is to open an issue at gitlab for your selected task, which we can use to more conveniently (and more publicly) communicate.
These snippets here are not exactly fun to use ... ;-)
Then the next step would be to check out the recently added Mac installation chapter, and to see if you can make something similar (or even better) for Windows.
Do you have any questions before you get started?
Thanks for your help,
Maren
@Moini
send a reply
6 years, 9 months ago
@Sergio Hi there :) What's up? This seems to be the markers file that comes with Inkscape, right?
@Moini
send a reply
6 years, 9 months ago
@jon.peyer
Snippet:
[
Context]
Hi Jon,
those tasks were meant as a list to choose from (or think of your own) - I think you've made a good choice that will help bring the manual forward in an important way.
I very much value contributors who are realistic about how much they can and would like to do - it makes it a lot easier to plan and to understand what one can ask from someone, without making them uncomfortable. So - thanks :) And no worries!
So, what I'd like you to do is to open an issue at gitlab for your selected task, which we can use to more conveniently (and more publicly) communicate.
These snippets here are not exactly fun to use ... ;-)
Then the next step would be to check out the recently added Mac installation chapter, and to see if you can make something similar (or even better) for Windows.
Do you have any questions before you get started?
Thanks for your help,
Maren
@Moini
send a reply
6 years, 9 months ago
@jon.peyer
Snippet:
[
Context]
Hi Jon,
Cool, I didn't know anything like that would be part of university education, I love that :)
How long will your course last?
It's not a problem that you don't have any previous Inkscape experience - this is a beginners' guide, so having beginners working on it and clarifying things is good, as the hurdles that people like you encounter are then still fresh on their mind, and are likely the same ones the readers stumble over.
Also, you being a native speaker is great, because I am not (I'm German), and I've translated this thing from French.
I don't know if you've already found it, but the discussions about the book mostly take place at gitlab:
https://gitlab.com/inkscape/inkscape-docs/manuals/
Please read the README, and take a peek into the issues section there.
If you are on Windows, then your first contribution could be writing the chapter for installation on Windows. It should be mostly version agnostic, and may have ample screenshots. The recently finished Mac chapter could be a good model. Requirements for good screenshots are listed here: https://gitlab.com/inkscape/inkscape-docs/manuals/issues/16
We also need someone to retake all (or some of) the remaining French-containing screenshots, in a good resolution.
Or we could use help styling and formatting the pages. This may need some inter-project communication and web (CSS + Javascript) skills, depending on whether we want to do it all manually, or whether we want to adapt the editing website to make editing easier first.
Proofreading and copyediting would be another way to contribute. The book has already been read by 3 non-native speakers who have given their feedback, and one native speaker has worked on some chapters. We need checking for consistency, and some work on making chapters follow a similar pattern.
Or there's the task of designing a layout, and adapting the pages' contents to it. I already have some stuff in mind and would be happy to discuss with someone.
You need to know that this manual is not a part of the Inkscape project that many people regularly work on, so it's maybe not the full open source project experience that you'd get here. I would make sure to be available for mentoring, but I cannot promise that many other people will come along and help us (although, we could also find a community-outreach job for you, to try and pull in others, and there's also some announcement work, and even some Inkscape program work to be done, when this is ready ;-))
Let me know if any of these tasks sound interesting to you.
As for the 'proof of contribution' (or whatever you'd call it), it was more or less that I would like to know what I'll be required to do for it (if anything). Not being a native speaker makes me a bit afraid of writing something like a recommendation or whatever could be needed ;-)
I hope to hear from you soon, and I'd very much love having your help here.
Maren
@Moini
send a reply
6 years, 9 months ago
@jon.peyer Hi Jon, that's great, your help would be very welcome. To help you find the best task for you, can you tell us a bit about your level of experience with Inkscape, with layout/design, and web technology, or manual writing in general? What's your study subject? Do you need any kind of confirmation of your contributions? Maren
@Moini
send a reply
6 years, 9 months ago
@aplusburger Thank you, Allison, that would be awesome. We already have a couple of dedicated 'issues' on gitlab for proofreading (the list might not be complete, but you can create issues if needed) Here it is: https://gitlab.com/inkscape/inkscape-docs/manuals/issues. You can use them to put your feedback in, if it's something that seems to need discussion (maybe because you don't know the functionality well), or you can edit directly in the book and let us know on the issue when a chapter is done. Also, when you have made any edits, don't forget to add yourself to the authors list ;-)
@Moini
send a reply
6 years, 9 months ago
@aplusburger Hi there, yes, we need some help in very different areas. Can you tell us a bit about your background - e.g. do you know how to edit html, or are you a native speaker of English, or are you an expert user or a new user of Inkscape etc.? Our editing guidelines and organizational things are described in this document at gitlab: https://gitlab.com/inkscape/inkscape-docs/manuals/blob/master/README.md . Please introduce yourself on the Inkscape docs mailing list, if you want to help with editing the book. If you want to provide feedback only, it's sufficient to contact us via 'issues' on gitlab. Thanks! See you there! Maren
@Moini
send a reply
6 years, 10 months ago
@rosalind.lord As far as I know, a simple account on gitlab should be sufficient (and a mailing list subscription). I've made you a 'reporter', because, unless you know what to do with git, there's no need for developer permissions. Please let me know if you require more.
@Moini
send a reply
6 years, 10 months ago
@john.morgan Hi! Great, seems you've already got an account! Can you join the group: http://write.flossmanuals.net/groups/beginners-manual-for-inkscape/ ?
@Moini
send a reply
6 years, 10 months ago
@rosalind.lord Hey, welcome! Can you please join us on gitlab or introduce yourself on the inkscape-docs mailing list? https://gitlab.com/inkscape/inkscape-docs/manuals