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