I've taken a butcher's knife to the roadmap and moved a ton of tasks forward, so that for 0.38 we can focus explicitly on bug fixing.
Of course, if anyone feels like working on tasks for future releases, please go ahead, it's just that they're not required to be done for this release.
So, the trimmed todo list is as follows:
* Incorporate (or reject) all patches posted to patch tracker * Knock bug list count down to 10 or fewer, or to a ratio of 10% open/total [all] * Change the SEGV and SIGABRT handlers to reliably autosave and put up a crash dialog * Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
There are 3 patches in the patch tracker. I think that should be an easy task to reach closure on.
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
The SEGV and SIGABRT task may be a bit of a challenge but I think it's extremely important for our users. There's little more frustrating for a user than losing the last N hours worth of work. Who would like to take the lead on this task?
Bryce
On Sat, 2004-02-21 at 03:21, Bryce Harrington wrote:
- Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
[snip]
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
Please consider liasing with Jody Goldbery who is doing a lot of work on libgoffice. Part of libgoffice is a plugin/extension framework.
On Sat, 21 Feb 2004, Charles Goodwin wrote:
On Sat, 2004-02-21 at 03:21, Bryce Harrington wrote:
- Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
[snip]
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
Please consider liasing with Jody Goldbery who is doing a lot of work on libgoffice. Part of libgoffice is a plugin/extension framework.
Yup, we're aware of libgoffice. I'm hoping someone will submit a solid proposal for it, that will explain how using it would be better from other options we're considering.
Note that we won't be adopting any solution blindly. I think we are best served to lay out all the possible options and weigh all the pros and cons, and select the approach that is the all-around best.
I've asked a couple Inkscape developers to look into libgoffice, but initial feedback suggests the choice is not totally clearcut, so we're going to need to go through a process to examine options. I would love to see a sales pitch made by someone more familiar with libgoffice's capabilities, particularly as it relates to Inkscape's needs.
I'd love to see libgoffice give us a perfect solution, as it'd save us a ton of time. We'd be able to focus on making extensions (or making inkscape itself pluggable into other things), but it's critical that the extension system we select will meet our requirements, as we plan to make heavy use of it. A good extension system will help us scale our developer base beyond what can be achieved otherwise.
Bryce
Btw, the requirements we've identified so far (but probably incomplete) for our Extension system is itemized here:
http://www.inkscape.org/cgi-bin/wiki.pl?PlugIns
Bryce
On Fri, 20 Feb 2004, Bryce Harrington wrote:
On Sat, 21 Feb 2004, Charles Goodwin wrote:
On Sat, 2004-02-21 at 03:21, Bryce Harrington wrote:
- Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
[snip]
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
Please consider liasing with Jody Goldbery who is doing a lot of work on libgoffice. Part of libgoffice is a plugin/extension framework.
Yup, we're aware of libgoffice. I'm hoping someone will submit a solid proposal for it, that will explain how using it would be better from other options we're considering.
Note that we won't be adopting any solution blindly. I think we are best served to lay out all the possible options and weigh all the pros and cons, and select the approach that is the all-around best.
I've asked a couple Inkscape developers to look into libgoffice, but initial feedback suggests the choice is not totally clearcut, so we're going to need to go through a process to examine options. I would love to see a sales pitch made by someone more familiar with libgoffice's capabilities, particularly as it relates to Inkscape's needs.
I'd love to see libgoffice give us a perfect solution, as it'd save us a ton of time. We'd be able to focus on making extensions (or making inkscape itself pluggable into other things), but it's critical that the extension system we select will meet our requirements, as we plan to make heavy use of it. A good extension system will help us scale our developer base beyond what can be achieved otherwise.
Bryce
On Sat, 2004-02-21 at 03:45, Bryce Harrington wrote:
Btw, the requirements we've identified so far (but probably incomplete) for our Extension system is itemized here:
http://www.inkscape.org/cgi-bin/wiki.pl?PlugInsBryce
On Fri, 20 Feb 2004, Bryce Harrington wrote:
Yup, we're aware of libgoffice. I'm hoping someone will submit a solid proposal for it, that will explain how using it would be better from other options we're considering.
Note that we won't be adopting any solution blindly.
Of course, nobody would expect you to blindly go with anything. ;)
Things to remember about the libgoffice framework:
o Already exists
It's already partially implemented, partially in-use and being actively developed. Think of it as a headstart. ;)
o A problem shared is a problem halved
I can almost guarrantee that Jody will be receptive to help and input. Given his hopes for libgoffice, he'll probably be eager to see it meet pretty much all of your requirements.
Whoever is investigating it should definitely get directly in touch with Jody in order to establish the scope for working together on libgoffice to make it meet Inkscape's requirements where it doesn't already do so.
On Fri, 2004-02-20 at 21:11, Charles Goodwin wrote:
Whoever is investigating it should definitely get directly in touch with Jody in order to establish the scope for working together on libgoffice to make it meet Inkscape's requirements where it doesn't already do so.
I'll take this one up. I'm writing the e-mail right now. I'll write a more in depth summary.
--Ted
That sounds good Bryce. It would be good to have a quicker milestone where we can smooth out the bumps and not focus on a ton of things. I posted our release announcmenets to many places thus far.
Jon
On Fri, 2004-02-20 at 19:21, Bryce Harrington wrote:
I've taken a butcher's knife to the roadmap and moved a ton of tasks forward, so that for 0.38 we can focus explicitly on bug fixing.
Of course, if anyone feels like working on tasks for future releases, please go ahead, it's just that they're not required to be done for this release.
So, the trimmed todo list is as follows:
- Incorporate (or reject) all patches posted to patch tracker
- Knock bug list count down to 10 or fewer, or to a ratio of 10% open/total [all]
- Change the SEGV and SIGABRT handlers to reliably autosave and put up a crash dialog
- Write an extensions/plugin enhancement proposal(s) and post to mailing list for review
There are 3 patches in the patch tracker. I think that should be an easy task to reach closure on.
The extensions proposal is necessary for this release because implementing a solution will be the focus for next release. Multiple proposals is fine, but we need at least one, and we'll need concensus on which to use by the time we finish cutting this release.
The SEGV and SIGABRT task may be a bit of a challenge but I think it's extremely important for our users. There's little more frustrating for a user than losing the last N hours worth of work. Who would like to take the lead on this task?
Bryce
SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (4)
-
Bryce Harrington -
Charles Goodwin -
Jonathan Phillips -
Ted Gould