Re: [Inkscape-docs] News item...manual...first draft ready
Published :-) brynn -Original Message- From: Maren Hachmann Sent: Sunday, June 11, 2017 6:15 PM To: brynn ; inkscape-docs@lists.sourceforge.net Subject: Re: [Inkscape-docs] News item...manual...first draft ready Am 10.06.2017 um 08:54 schrieb brynn: First and most important. I take the first item in the list as calling for a few beginners to review it. But when I follow the link, the task appears to be calling for one person to locate some beginners and sort of coach them or guide them through reviewing it. So either the task itself needs to be changed. Or the first item in this article needs to change. Do you see what I mean? - Yes, I've thought about that myself. In the end, I had decided that people who want to join can still do it via adding a comment. I'll update the description a bit, now, to make that clearer. So do you know any way to force a line space between items in the list? If you know, I would suggest moving the links to the end of the period (well, maybe a couple spaces after the period) and making a line space before the next item. But if it can't be done easily, just forget it. It's not worth spending a lot of time to research. :-) - It's a bit difficult to do, if you want translators to mimick it and not lose it while translating. I think it can be published now :) Thanks again, Brynn! Kind Regards, Maren All best, brynn -Original Message- From: Maren Hachmann Sent: Thursday, June 08, 2017 4:04 PM To: inkscape-docs@lists.sourceforge.net Subject: Re: [Inkscape-docs] News item...manual...first draft ready Brynn, I've just updated the article draft. Can you have a short look? Kind Regards, Maren Am 07.06.2017 um 20:07 schrieb Maren Hachmann: I'll have a look again later today, first I'll need to get the README on gitlab ready, then I'll make the edits to include a link. I found a previous version of the news article yesterday and liked it a lot :) Thank you, Brynn, for working on this so quickly and phrasing it so nicely! Kind Regards, Maren Am 07.06.2017 um 14:14 schrieb brynn: I thought I posted that I had a first draft, but now I can't find it. So this is it: https://inkscape.org/en/news/unpublished/812/ Let me know if any changes are needed, or if it can be published as is. Or for those who have access, please feel free to make changes and/or publish it yourself :-) All best, brynn -Original Message- From: Maren Hachmann -- 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
Re: [Inkscape-docs] News item...manual...first draft ready
Am 10.06.2017 um 08:54 schrieb brynn: >First and most important. I take the first item in the list as > calling for a few beginners to review it. But when I follow the link, > the task appears to be calling for one person to locate some beginners > and sort of coach them or guide them through reviewing it. > >So either the task itself needs to be changed. Or the first item > in this article needs to change. Do you see what I mean? - Yes, I've thought about that myself. In the end, I had decided that people who want to join can still do it via adding a comment. I'll update the description a bit, now, to make that clearer. >So do you know any way to force a line space between items in the > list? If you know, I would suggest moving the links to the end of the > period (well, maybe a couple spaces after the period) and making a line > space before the next item. But if it can't be done easily, just forget > it. It's not worth spending a lot of time to research. :-) - It's a bit difficult to do, if you want translators to mimick it and not lose it while translating. I think it can be published now :) Thanks again, Brynn! Kind Regards, Maren > All best, > brynn > > -Original Message- From: Maren Hachmann > Sent: Thursday, June 08, 2017 4:04 PM > To: inkscape-docs@lists.sourceforge.net > Subject: Re: [Inkscape-docs] News item...manual...first draft ready > > Brynn, I've just updated the article draft. Can you have a short look? > > Kind Regards, > Maren > > Am 07.06.2017 um 20:07 schrieb Maren Hachmann: >> I'll have a look again later today, first I'll need to get the README on >> gitlab ready, then I'll make the edits to include a link. >> >> I found a previous version of the news article yesterday and liked it a >> lot :) >> Thank you, Brynn, for working on this so quickly and phrasing it so >> nicely! >> >> Kind Regards, >> Maren >> >> >> Am 07.06.2017 um 14:14 schrieb brynn: >>> I thought I posted that I had a first draft, but now I can't find it. >>> So this is it: https://inkscape.org/en/news/unpublished/812/ >>> >>> Let me know if any changes are needed, or if it can be published as is. >>> Or for those who have access, please feel free to make changes and/or >>> publish it yourself :-) >>> >>> All best, >>> brynn >>> >>> -Original Message- From: Maren Hachmann > > -- 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
Re: [Inkscape-docs] [Manual] Updates and news
Hi Brynn, we'll see how it goes on gitlab with the issues. There were no time constraints put on them (although that's possible on gitlab), I don't understand where that comes from. Go ahead creating your issues, let us know if you need help with it. Keep them concise, please, so it'll be quick to read and discuss. Kind Regards, Maren Am 10.06.2017 um 06:05 schrieb brynn: > Hi Everyone, >Regarding keeping up with tasks: I think it's a very good idea, > in general. But I have some reservations. In an open source community, > as far as I've learned, people tend to manage whatever projects they've > committed to on their own, and on their own schedule. > >Also, with a project such as this manual/guide, where it can be > edited at any time, by anyone who is interested Well, it's really > never quite completed - not any task is ever completely finished. > >So having a list of tasks, with the names of the people who are > working on it would be great. But using a list of tasks and putting > time constraints on it - I'm not sure how that could be effective or > helpful. > >Unless you're talking about the publishing side of it? I can see > where you'd actually want deadlines for certain things, for publishing > new versions. Sort of like when they freeze certain parts of development > right before a new release. > > >I'm very glad to know we'll be using gitlab to help manage the > project! I remember asking a couple of weeks ago about that. > >So now I can create an issue for the proposed different > organization of chapters that I mentioned. And also an Issue about the > graphics issues I mentioned. > >But first, I want to make sure that's how we're using it. Or are > we only using Issues for task management? > > Thanks, > brynn > > -Original Message- From: Maren Hachmann > Sent: Thursday, June 08, 2017 5:53 PM > To: Inkscape-Docs > Subject: [Inkscape-docs] [Manual] Updates and news > > Hi everyone, > > after sending out the message about having felt a bit lonely while > translating the manual, several people sent me some helpful tips on how > to do it better :) (Thanks!) > > This update message is the incarnation of one of those. > > Also, I was very pleased to see that there are so many people still > interested in helping, and to see some new people to join us on the > Beginners' Guide project. Welcome again, Jabier, Jelle and Marietta! > > > So, what happened this week? > - > > > - Brynn has worked on a friendly news item to get more contributors that > will soon be published (find it here, if you're a website editor: > https://inkscape.org/en/news/unpublished/812/) > > - CR posted a first draft (png) of a cover image, with a tasty Inkscape > ice cream (find it here: > https://www.dropbox.com/s/h4n88xpnc6declz/inkscape_cover_beginner_m) > > - Jabier has volunteered to work on the CSS a bit, and tested the pdf > export, where he found an issue, which, fortunately, we were able to > solve (see example pdf of draft from a couple of days ago: > http://objavi.booktype.pro/data/books/startwithinkscape-en-2017.06.07 > -01.46.42.pdf) > > - Jelle offered to help with proofreading, and possibly also with design > > - Marietta joined the team, and started out making a public task list > (here: https://gitlab.com/inkscape/inkscape-docs/manuals/issues/, more > on that further down) and committed to help keeping it updated. She also > proofread one chapter for language inaccuracies, and offered to help > with the glossary and testing of the manual's effectiveness. > > - Martin (doctormo) helped by giving me permissions to manage the manual > task list and members on gitlab > > - I have learnt a bit about managing a project this size (at least, I > hope I have... let me know when I'm stepping on your toes, please), did > some investigation on export formats, helped set up the gitlab issues > section, coordinated with members to get them set up, reviewed the news > article and translated and technically reviewed 17 chapters, also > feeding back to Elisa for the original French version. > There are 14 chapters left to be translated, I expect to be done with > that in a week, if nobody else joins me there. > > - Together we had some good discussions here on the list, that show that > work on the manual is very much alive :) > > Hope I haven't forgotten anyone, and didn't get the facts wrong - if I > have, please blame it on the lack of: > > The new task tracker > > > Marietta suggested that we have a task tracker to follow up on tasks and > to keep an overview about responsibilities. This is a good idea (while > currently, I'm still able to keep most of it in my head, that is not a > good place to keep records, and to allow people to self-assign and > update tasks, and to be responsible ;-) - it may also loose some info > here and there), and after a bit of searching, we s
Re: [Inkscape-docs] update "Getting Started with Development"
On Sun, Jun 11, 2017 at 12:02:44PM +0200, Maximilian Gaukler wrote: > Hi everyone, > > I would like to propose a change to this page: > https://inkscape.org/en/develop/getting-started/#install-build-dependencies > > Currently, the section "Install build dependencies" doesn't constructively > explain how to build the latest trunk without enabling some PPA. > > But, lucky enough, there is already a nice listing of apt-get commands in > this file: > https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml > As it is used in the CI (automatic build), it is automatically checked that > the commands there actually work for the current version. > > Therefore, I'd suggest the following change: > (pseudo-patch-file, - = remove, + = insert) > > - Note: If you are using the PPA for the latest builds on Debian, you > - can use this alternative command to get a more accurate set of build > - dependencies: > - > - sudo apt-get build-dep inkscape-trunk > Note that this will install the build dependencies of the Inkscape > package available in your repositories. If the package is old, you > might need to install some additional dependencies > - ; > + . > + > + A more accurate set of build dependencies > + can be found in this file in the lines containing 'apt-get': > + https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml > + > - the output of the configure script should give you hints on what > - else is required. > + In case of errors, the output of 'cmake' should give you hints on what > + else is required. Looks good to me, clever reuse of the CI scripts. They look comprehensible enough in current form. Note the CI was just set up, while the PPAs haven't been transitioned, so yes the former does give more accurate results right now, however we'll get them both working so either approach *should* work. The PPA / build-dep approach might be a bit more future proof since it will by definition work with a range of support ubuntu versions (and debian), but yes having to enable a PPA in order to build from source does seem awkward. > Also, the doc/HACKING.* files are really outdated (many technical details > are wrong), I would suggest simply replacing them with a link to the > develop/getting-started website. If it helps, I can hand in a merge request > for that, or a launchpad bug report, or whatever is the right thing during > the migration to GIT. Yeah you're right they've not been kept up to date. Technically HACKING should not be covering build directions anyway - that should be covered in other files. But the remainder are essentially our "development policy" and should remain; however what they're describing is development policy as it existed years ago. Obviously we still need to have our policies written down (and I don't think wiki is the right place - ref. my Jan 29th proposal on wiki restructuring). With the gitlab transition there's been a lot of questions about policy changes, so this'd be a good point to re-discuss and re-document all of that anyway. Bryce -- 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
[Inkscape-docs] update "Getting Started with Development"
Hi everyone, I would like to propose a change to this page: https://inkscape.org/en/develop/getting-started/#install-build-dependencies Currently, the section "Install build dependencies" doesn't constructively explain how to build the latest trunk without enabling some PPA. But, lucky enough, there is already a nice listing of apt-get commands in this file: https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml As it is used in the CI (automatic build), it is automatically checked that the commands there actually work for the current version. Therefore, I'd suggest the following change: (pseudo-patch-file, - = remove, + = insert) - Note: If you are using the PPA for the latest builds on Debian, you - can use this alternative command to get a more accurate set of build - dependencies: - - sudo apt-get build-dep inkscape-trunk Note that this will install the build dependencies of the Inkscape package available in your repositories. If the package is old, you might need to install some additional dependencies - ; + . + + A more accurate set of build dependencies + can be found in this file in the lines containing 'apt-get': + https://gitlab.com/inkscape/inkscape/blob/master/.gitlab-ci.yml + - the output of the configure script should give you hints on what - else is required. + In case of errors, the output of 'cmake' should give you hints on what + else is required. Also, the doc/HACKING.* files are really outdated (many technical details are wrong), I would suggest simply replacing them with a link to the develop/getting-started website. If it helps, I can hand in a merge request for that, or a launchpad bug report, or whatever is the right thing during the migration to GIT. Looking forward to your feedback, Max -- 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
