Seeking Review: Inkscape Development for Users
Hi Everyone,
Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development.
http://grtuts.com/inkscape-development-builds/
He's asked me for advice on the details and I figure I'd throw it open to everyone.
You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too.
Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write)
Thoughts?
Best Regards, Martin Owens
On Mon, Jan 30, 2017 at 09:52:31PM -0500, Martin Owens wrote:
Hi Everyone,
Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development.
http://grtuts.com/inkscape-development-builds/
He's asked me for advice on the details and I figure I'd throw it open to everyone.
You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too.
Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write)
Thoughts?
Some copyedit suggestions:
1. "Developmental Builds are pre-released Inkscape binaries packed with new features that will be released into the "trunk" of the next stable release."
Probably better to not use the word 'trunk' since it has a particular meaning internally. So maybe clearer to just say:
"Developmental Builds are Inkscape binaries packed with fixes and new features being tested out for possible inclusion in future stable releases."
2. It's great to invite people to join the inkscape-devel@ mailing list, but in practice it's probably unnecessary for most bug reporting. We don't at all expect people to join the list before reporting bugs.
3. I'm not sure if it's important to recommend checking for existing bug reports. Launchpad already does a scan automatically when bug reports are filed. Beyond that, it can be tricky for users to know if their issue matches a given report; I've often seen mistakes made here. Launchpad actually makes it pretty easy for bug triagers to dupe up bug reports, so having multiple duplicate reports can actually be helpful in some ways.
4. The bug submission checklist is great. Thumbs up for including that. A few copyedits: "to get persons to" -> "to get people to" "save the developer" -> "saves the developer" "screen-short" -> "screenshot" "(video link)so" -> "(video link) so" "for the developed" -> "for the developer" "Inkscape version Operating" -> "Inkscape version, Operating"
Also, I'd highly suggest making "include the SVG file" a top level checklist item. Rendering bugs in particular will benefit from having an example file that demonstrates the issue.
5. System error logs - I'm not sure what this is referring to particularly, but it might help to name some specific system files to look for. I'm guessing this intends to mean the Inkscape stderr output, as opposed to dmesg?
6. Crash bugs - debugger backtraces are the most important type of info for debugging Inkscape crashes. Collecting backtraces is an advanced technique that may be too technical for ordinary users, but it's an extremely valuable skill for bug reporters to have, particularly if they're using development builds.
Finally, the info graphic looks great, it's very readable, inspiring, and easy on the eyes. :-)
Bryce
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
Am 31.01.2017 um 04:30 schrieb Bryce Harrington:
- The bug submission checklist is great. Thumbs up for including that. A few copyedits: "to get persons to" -> "to get people to" "save the developer" -> "saves the developer" "screen-short" -> "screenshot" "(video link)so" -> "(video link) so" "for the developed" -> "for the developer" "Inkscape version Operating" -> "Inkscape version, Operating"
- Some more: "Developement/Nightly Builds" -> "Development/Nightly Builds" "e.g. Fill..." -> "E.g. Fill..." "Title: Bug Appropriately" -> "Title Bug Appropriately" "Remember an title" -> "Remember a title" "Save Screen Shot/ Or Cast" -> "Save Screen Shot Or Cast" "OS, Language, date" -> "OS, Language, Date" ""Seeing is believing" save the developer..." -> "Seeing is believing: Save the developer..." "and select development" -> "and select "Development versions"" and consistent punctuation (period at end of paragraph or not).
Does everyone out there know what 'binaries' are? Maybe 'program packages', 'installation files', or similar?
Finally, the info graphic looks great, it's very readable, inspiring, and easy on the eyes. :-)
- Agreed :) Thank you!
Off topic
- I'm not sure if it's important to recommend checking for existing
bug reports. Launchpad already does a scan automatically when bug reports are filed. Beyond that, it can be tricky for users to know if their issue matches a given report; I've often seen mistakes made here. Launchpad actually makes it pretty easy for bug triagers to dupe up bug reports, so having multiple duplicate reports can actually be helpful in some ways.
I've actually been scolded for not searching first. Or maybe "admonished" is a better word. That's why when I post a new report, I always state that I searched.
Yes, it is very tricky, and I usually consider it a waste of time. But I do sometimes find my issue already reported.
All best, brynn
-----Original Message----- From: Bryce Harrington Sent: Monday, January 30, 2017 8:30 PM To: Martin Owens Cc: inkscape-devel Subject: Re: [Inkscape-devel] Seeking Review: Inkscape Development for Users
On Mon, Jan 30, 2017 at 09:52:31PM -0500, Martin Owens wrote:
Hi Everyone,
Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development.
http://grtuts.com/inkscape-development-builds/
He's asked me for advice on the details and I figure I'd throw it open to everyone.
You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too.
Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write)
Thoughts?
Some copyedit suggestions:
1. "Developmental Builds are pre-released Inkscape binaries packed with new features that will be released into the "trunk" of the next stable release."
Probably better to not use the word 'trunk' since it has a particular meaning internally. So maybe clearer to just say:
"Developmental Builds are Inkscape binaries packed with fixes and new features being tested out for possible inclusion in future stable releases."
2. It's great to invite people to join the inkscape-devel@ mailing list, but in practice it's probably unnecessary for most bug reporting. We don't at all expect people to join the list before reporting bugs.
3. I'm not sure if it's important to recommend checking for existing bug reports. Launchpad already does a scan automatically when bug reports are filed. Beyond that, it can be tricky for users to know if their issue matches a given report; I've often seen mistakes made here. Launchpad actually makes it pretty easy for bug triagers to dupe up bug reports, so having multiple duplicate reports can actually be helpful in some ways.
4. The bug submission checklist is great. Thumbs up for including that. A few copyedits: "to get persons to" -> "to get people to" "save the developer" -> "saves the developer" "screen-short" -> "screenshot" "(video link)so" -> "(video link) so" "for the developed" -> "for the developer" "Inkscape version Operating" -> "Inkscape version, Operating"
Also, I'd highly suggest making "include the SVG file" a top level checklist item. Rendering bugs in particular will benefit from having an example file that demonstrates the issue.
5. System error logs - I'm not sure what this is referring to particularly, but it might help to name some specific system files to look for. I'm guessing this intends to mean the Inkscape stderr output, as opposed to dmesg?
6. Crash bugs - debugger backtraces are the most important type of info for debugging Inkscape crashes. Collecting backtraces is an advanced technique that may be too technical for ordinary users, but it's an extremely valuable skill for bug reporters to have, particularly if they're using development builds.
Finally, the info graphic looks great, it's very readable, inspiring, and easy on the eyes. :-)
Bryce
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
Love-LOVE IT!
Just 3 minor suggestions, in no particular order
1 - Near the bottom "Avoid emotive language...." "emotive" might not be clear for some people. Maybe add a couple of examples in parentheses? Or instead of "emotive" maybe 'avoid exaggerating'?? Not sure if "exaggerating" is inclusive of "emotive" though??
Possible short but sweet idea....although probably only the old folks will "get it". "Just the facts ma'am."
2 - "Title: Bug Appropriately" That punctuation indicates that the title is "Bug Appropriately", which of course is meaningless. I think you mean "Title the Bug Appropriately."? Or just removing the colon would work too.
And the line just below that "Remember an title is the best...." Should be "Remember a title is the best....". Even better would be a comma after "Remember".
3 - At the very top, instead of "register a bug report", maybe "file a bug report", or "submit" a bug report? "Register" isn't entirely wrong, but just a thought.
I'd love to see it on the website. I'm thinking on its own page. And there would be a link to it on the Report Bugs page. Not sure if that's what GR wants though.
I'll definitely link to it from my forum, if it's going to remain in GR's blog.
Planet is for tutorials, right? Or any kind of bloggish content? Lazur might be interested. He's not subscribed to the list, but I can ask. I keep urging him to get more involved, but so far, isn't ready. Off topic, but he's done some amazing work on filters!!!! (https://forum.inkscapecommunity.com/index.php?topic=329.0)
All best, brynn
-----Original Message----- From: Martin Owens Sent: Monday, January 30, 2017 7:52 PM To: inkscape-devel Subject: [Inkscape-devel] Seeking Review: Inkscape Development for Users
Hi Everyone,
Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development.
http://grtuts.com/inkscape-development-builds/
He's asked me for advice on the details and I figure I'd throw it open to everyone.
You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too.
Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write)
Thoughts?
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
This is beautiful. Amazingly beautiful.
We should encourage more docs like this. It empowers users and it showcase our app at the same time.
--Victor Westmann
2017-01-31 4:45 GMT-08:00 brynn <brynn@...3133...>:
Love-LOVE IT!
Just 3 minor suggestions, in no particular order
1 - Near the bottom "Avoid emotive language...." "emotive" might not be clear for some people. Maybe add a couple of examples in parentheses? Or instead of "emotive" maybe 'avoid exaggerating'?? Not sure if "exaggerating" is inclusive of "emotive" though??
Possible short but sweet idea....although probably only the old folks will "get it". "Just the facts ma'am."
2 - "Title: Bug Appropriately" That punctuation indicates that the title is "Bug Appropriately", which of course is meaningless. I think you mean "Title the Bug Appropriately."? Or just removing the colon would work too.
And the line just below that "Remember an title is the best...." Should be "Remember a title is the best....". Even better would be a comma after "Remember".
3 - At the very top, instead of "register a bug report", maybe "file a bug report", or "submit" a bug report? "Register" isn't entirely wrong, but just a thought.
I'd love to see it on the website. I'm thinking on its own page. And there would be a link to it on the Report Bugs page. Not sure if that's what GR wants though.
I'll definitely link to it from my forum, if it's going to remain in GR's blog.
Planet is for tutorials, right? Or any kind of bloggish content? Lazur might be interested. He's not subscribed to the list, but I can ask. I keep urging him to get more involved, but so far, isn't ready. Off topic, but he's done some amazing work on filters!!!! (https://forum.inkscapecommunity.com/index.php?topic=329.0)
All best, brynn
-----Original Message----- From: Martin Owens Sent: Monday, January 30, 2017 7:52 PM To: inkscape-devel Subject: [Inkscape-devel] Seeking Review: Inkscape Development for Users
Hi Everyone,
Golden Ribbon (GR) has made this slick info graphic to explain and prompt more users to help with Inkscape development.
http://grtuts.com/inkscape-development-builds/
He's asked me for advice on the details and I figure I'd throw it open to everyone.
You can comment directly in the blog post if you like. Or here, since I know GR is subscribed here too.
Also I think we might like to think about brining the planet back to life with some new blood. I wouldn't mind having non-coders on the planet, professionals perhaps. Or more than one if a planet is put into the website for example (they're fairly easy to write)
Thoughts?
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 (5)
-
Bryce Harrington -
brynn -
Maren Hachmann -
Martin Owens -
Victor Westmann