- Inkscape Devel - Inkscape Mailman

Launchpad team policy
by Ted Gould 28 Nov '07

28 Nov '07

Well, I got a lot more people wanting to be part of the various teams I set up on Launchpad than I expected. While, I don't think there is that much to hide in Launchpad I get the feeling that we should have some sort of policy on the two groups -- that way no one is making a decision arbitrarily. I'm going to throw out a couple ideas, you guys rip them up: Inkscape Bugs I'm willing to let anyone who's interested into this group. I think with many eyes all bugs are shallow. Now, that being said I'd like to at least know who the person is and that they're not just there to be a troll. So, I'm thinking a post to the -devel mailing list? Would that be too much traffic? Inkscape Admin I think that about the only thing that people in this group can do is change the description/links on the website and add people into the the bugs group. Oh, and define milestones. So again, I'm not as worried about giving away the keys to castle, but I think this should be more limited as these would be the folks implementing the policies in this discussion. I'm kinda thinking we grab the admins for SF: Mental, Bryce, Bulia and JonCruz and just leave it at that. If they need help they can ask for it. (Note: this would mean I'd remove myself from the group which I'm more than happy to do) --Ted

2 2

Re: [Inkscape-devel] Launchpad migration complete (was Re: Inkscape demo import)
by Bryce Harrington 28 Nov '07

28 Nov '07

On Tue, Nov 27, 2007 at 04:21:21PM +0900, James Henstridge wrote: > On 27/11/2007, James Henstridge <james@...1829...> wrote: > > For any developers with existing Launchpad accounts, it is likely that > > a duplicate person has been created for you. To fix this, go to the > > following URL and enter your $USER@...58... email > > address: > > > > https://edge.launchpad.net/people/+requestmerge > > This URL should have been: > > https://launchpad.net/people/+requestmerge > > The edge URL will work, but unless you're a member of the Launchpad > beta testers team you probably aren't logged in there. > > James. Thanks again for all your work on this, James. We're already poking and prodding with it, and looking forward to being able to pound our bugs into submission. :-) Bryce

1 0

Page of bug triaging projects
by Bryce Harrington 27 Nov '07

27 Nov '07

Hi all, Looking at the 1913 bugs in launchpad, it seems pretty overwhelming... But it can be attacked with smaller scoped projects. I've created a list here: http://wiki.inkscape.org/wiki/index.php/BugTriageProjects Each of these tasks should be manageable by one person over the course of a week or so, maybe less. None of them require any particular technical skill. They're all pretty important to do to get our bug tracker organized. By the way, Launchpad also has a handy email interface, and a lot of bulk work can be done by writing scripts that invoke changes through email. This is handy for bulk tagging bugs, updating status, or requesting re-testing bugs for example. Details here: https://help.launchpad.net/BugTrackerEmailInterface Bryce

1 0

Launchpad Tips & Tricks: Triaging
by Bryce Harrington 27 Nov '07

27 Nov '07

Triaging is the initial bug review process, that anyone with a bit of patience can help with. A good technique for triaging is to use the advanced search page (https://bugs.launchpad.net/inkscape/+bugs?advanced=1). Search for 'New'+'Undecided' bugs, and/or some search term you care about (say, "layers dialog"). Looking at a specific bug, look over to the far right for a downward pointed arrow. Clicking this expands the bug settings panel. The Status and Importance fields are the main ones to deal with. The goal of triaging is to get the bug out of 'New'. Review the bug and see if it has enough information to troubleshoot; if not, move it to state 'Incomplete'. If it does have enough, set it to 'Confirmed'. If the bug is really a feature request, set Status to Confirmed, and Importance to Wishlist. If the bug is out of date or otherwise invalid, mark it Invalid. Bryce

2 1

Launchpad Tips & Tricks: Tags
by Bryce Harrington 27 Nov '07

27 Nov '07

On the left side of https://bugs.launchpad.net/inkscape/ you'll see an unobtrusive grey bar labeled 'Tags'. Click on it and you'll see a list of Inkscape-specific tags. Click on a tab and it brings up the corresponding list of bugs. Tags are a flexible mechanism for organizing bugs, sort of like with SF where we could put a bug in a category, except in LP a bug can be assigned any number of tags. Also, in SF only admins could add new categories; with LP, bug triagers can define new tags too. Click on one of the tagged bugs. You'll see the tags listed right after the Bug description. On the top left, click on 'Edit description/tags'. Under the fields for updating the summary and description is the Tags box. This is a simple space-delimited list of tags. Defining a new tag is as trivial as writing a new term into this box. It's a good idea to try to use existing tags where possible; too many tags may become unmanageable. Here's some different ideas that tags could be used for: * Identifying the platforms the bug occurs on (e.g. 'osx', 'windows-vista', 'ubuntu-linux') * Hook into more elaborate workflows (e.g. 'needs-testing', 'needs-performance-measurement', 'add-to-release-notes') * Marking bugs that are all dependent on a particular feature (e.g. 'needs-animation', 'needs-multipage') * Marking bugs that need processing by automated scripts (e.g. 'needs-all-retrace', 'render-svg-attachments') Bryce

1 0

Launchpad Groups
by Ted Gould 27 Nov '07

27 Nov '07

Hello, With the bugs now I Launchpad I made two "teams" -- groups really. They are: inkscape.admin http://launchpad.net/~inkscape.admin inkscape.bugs http://launchpad.net/~inkscape.bugs Basically the first one can edit the Inkscape project and the second is set up for the bug tracker. I don't believe that you need to be in inkscape.bugs to work with bugs, but I do believe it'll give you more ability to work with bugs. Anyway, if you think you should be in those groups apply to them and I'll add you. --Ted PS - If you're in inkscape.admin that automatically puts you in inkscape.bugs

2 2

Status report
by Maximilian Albert 27 Nov '07

27 Nov '07

Hi all, just to keep you informed, and because some people are probably waiting for status updates from me (I hope this is not the reason why Bryce hasn't announced Chill yet) - I'm now almost finished with the transition of the 3D box tool from the old to the new internal representation. I'm planning to merge the changes into trunk sometime this week and continue working there. I'm also going to write up a description of what these changes comprise (and why they were necessary/what they will be useful for), what's still missing and what is on my TODO list for further work on the tool. Well, going to sleep now so as to be fresh for work tomorrow (although it's probably already too late for that). :) Max

2 1

Re: [Inkscape-devel] Launchpad migration complete (was Re: Inkscape demo import)
by Bryce Harrington 27 Nov '07

27 Nov '07

On Tue, Nov 27, 2007 at 02:57:34PM +0900, James Henstridge wrote: > The import was performed with a fresh screen scrape of the SF.net > tracker, so it should be fairly complete. It would be good to hide > the SF.net tracker now to prevent people from filing new bugs in the > wrong place. This has been done. We're in the middle of transitioning the website to a new VM, but we'll get the links and such updated after that. Bryce

1 0

DOM for scripting?
by Terry Hancock 26 Nov '07

26 Nov '07

Hi all, About a year ago, I posted regarding a Python graphical scripting tool I was working on. I got sort of hung in the middle, because I started with Skencil, then started looking at Inkscape. Inkscape was simpler in one respect because the SVG representation is easier to manipulate, but it's harder to integrate the plugin because I couldn't (easily) *use* Inkscape from the script. For example, it would be nice to be able to select and skew an object using Inkscape's selection and transformation tool rather than having to compute and apply the transformation at the point level within my program, but that would require a way to call that tool from the Python script. In Skencil, by contrast, this is relatively simple to do, because the Skencil API is completely accessible to scripts and plugins. The downside is that Skencil uses an internal Python object model for the drawing which is not easily serializable. Thus, for example, it is very awkward to keep a library of drawing components available for my program to manipulate. When I brought this up on inkscape-user, I was told that a DOM API would (at sometime) be made available which would solve this problem (although now that I think about it, "document" doesn't really fit, though "object model" does -- this may've been a miscommunication?) I have recently seen "DOM" mentioned in the inkscape-devel archives, but that seems to be a different concept -- the idea of a DOM to describe the SVG file being manipulated, not the Inkscape application doing the manipulation. I didn't have a pressing enough need for the tool I was writing to plow through this obstacle, so I wound up setting it aside, thinking that it might prove easier later anyway. So I'd just like to ask if functionality like this already exists in Inkscape, is on an existing roadmap, or if this is something I ought to place as a feature request? Cheers, Terry -- Terry Hancock (hancock@...1838...) Anansi Spaceworks http://www.AnansiSpaceworks.com

3 2

Inkscape Contract Programming
by Michael Yinger 26 Nov '07

26 Nov '07

First, I apologize in advance if this is the wrong forum for this kind of question. I've been getting up to speed on Inkscape and Scribus. I'd like to get up to speed much faster and would be happy to pay someone to help me do that. If you are interested please email me at myinger@...1835... -- Mike Yinger

2 3