[Inkscape-devel] Inkscape roadmap for 0.46 and beyond

Hi all,
I think I've mostly finished with the reworking of the roadmap. Thank
you to everyone who has provided ideas or critique:
http://wiki.inkscape.org:8080/wiki/index.php/Roadmap
This shouldn't be taken as gospel, of course. It's likely that tasks
will need to be resorted as we move forward, but I think this gives us a
starting point to plan around.
Two factors I've tried to account for in the prioritization are first,
that we have a goal to achieve SVG Mobile (aka SVG Tiny) support by
version 0.50, and second that developers are going to want to work on
separate aspects of Inkscape in parallel, rather than everyone focusing
on one area for one release. Thus I've added categories in each section
to roughly define what these different areas are, and have attempted to
avoid putting too many tasks in any one area.
Please feel free to re-prioritize or elaborate on any of the items
here. It would especially be nice if we could more distinctly call out
lower level tasks for some of the higher level task descriptions, so
that new developers can more easily find things defined well enough for
them to work on. Also, linking to mail archives or wiki pages with more
info about the tasks would be quite helpful!
If you adjust priorities, it would probably be better to move things
*later* than earlier. There's no problem with planning to do things far
in the future but actually getting them done early! But if we put too
many things into 0.46, it could get a bit overwhelming.
One of the things that's gotten really clear is that if we really do
want to get SVG Mobile support by 0.50, then we're going to need to
start thinking about cutting ground on Animation. Fortunately the spec
only requires "Basic Animation support", with a subset of the features,
so it sounds pretty doable if we give ourselves plenty of time and do
some really good brain storming on it. For 0.46, we could focus on
conceptual definition - what we want, how it should work, and so forth.
I know a lot of people have good ideas on this, so it's probably going
to be mostly a matter of getting those ideas recorded and organized, so
future prototypers have something to inspire and guide their work.
Bryce

Thread view

Hi all,
I think I've mostly finished with the reworking of the roadmap. Thank
you to everyone who has provided ideas or critique:
http://wiki.inkscape.org:8080/wiki/index.php/Roadmap
This shouldn't be taken as gospel, of course. It's likely that tasks
will need to be resorted as we move forward, but I think this gives us a
starting point to plan around.
Two factors I've tried to account for in the prioritization are first,
that we have a goal to achieve SVG Mobile (aka SVG Tiny) support by
version 0.50, and second that developers are going to want to work on
separate aspects of Inkscape in parallel, rather than everyone focusing
on one area for one release. Thus I've added categories in each section
to roughly define what these different areas are, and have attempted to
avoid putting too many tasks in any one area.
Please feel free to re-prioritize or elaborate on any of the items
here. It would especially be nice if we could more distinctly call out
lower level tasks for some of the higher level task descriptions, so
that new developers can more easily find things defined well enough for
them to work on. Also, linking to mail archives or wiki pages with more
info about the tasks would be quite helpful!
If you adjust priorities, it would probably be better to move things
*later* than earlier. There's no problem with planning to do things far
in the future but actually getting them done early! But if we put too
many things into 0.46, it could get a bit overwhelming.
One of the things that's gotten really clear is that if we really do
want to get SVG Mobile support by 0.50, then we're going to need to
start thinking about cutting ground on Animation. Fortunately the spec
only requires "Basic Animation support", with a subset of the features,
so it sounds pretty doable if we give ourselves plenty of time and do
some really good brain storming on it. For 0.46, we could focus on
conceptual definition - what we want, how it should work, and so forth.
I know a lot of people have good ideas on this, so it's probably going
to be mostly a matter of getting those ideas recorded and organized, so
future prototypers have something to inspire and guide their work.
Bryce

On Wed, 2007-01-31 at 13:30 -0800, Bryce Harrington wrote:
> Hi all,
>
> I think I've mostly finished with the reworking of the roadmap. Thank
> you to everyone who has provided ideas or critique:
>
> http://wiki.inkscape.org:8080/wiki/index.php/Roadmap
>
> This shouldn't be taken as gospel, of course. It's likely that tasks
> will need to be resorted as we move forward, but I think this gives us a
> starting point to plan around.
>
> Two factors I've tried to account for in the prioritization are first,
> that we have a goal to achieve SVG Mobile (aka SVG Tiny) support by
> version 0.50, and second that developers are going to want to work on
> separate aspects of Inkscape in parallel, rather than everyone focusing
> on one area for one release. Thus I've added categories in each section
> to roughly define what these different areas are, and have attempted to
> avoid putting too many tasks in any one area.
>
> Please feel free to re-prioritize or elaborate on any of the items
> here. It would especially be nice if we could more distinctly call out
> lower level tasks for some of the higher level task descriptions, so
> that new developers can more easily find things defined well enough for
> them to work on. Also, linking to mail archives or wiki pages with more
> info about the tasks would be quite helpful!
>
> If you adjust priorities, it would probably be better to move things
> *later* than earlier. There's no problem with planning to do things far
> in the future but actually getting them done early! But if we put too
> many things into 0.46, it could get a bit overwhelming.
>
> One of the things that's gotten really clear is that if we really do
> want to get SVG Mobile support by 0.50, then we're going to need to
> start thinking about cutting ground on Animation. Fortunately the spec
> only requires "Basic Animation support", with a subset of the features,
> so it sounds pretty doable if we give ourselves plenty of time and do
> some really good brain storming on it. For 0.46, we could focus on
> conceptual definition - what we want, how it should work, and so forth.
> I know a lot of people have good ideas on this, so it's probably going
> to be mostly a matter of getting those ideas recorded and organized, so
> future prototypers have something to inspire and guide their work.
>
> Bryce
>
I weakly added the strategy for Inkcore as 0.53 basically to start
moving towards refactoring towards Inkscape as a set of libraries others
can use.
Also, what would be great is for people to go and pencil in on the wiki
as we usually do, who is interested in what. Obviously anyone can take
any task, but this is always good so that people know who is interested
and possibly more knowledgeable about different parts of the codebase.
Example:
* Task name (YOUR NAME)
Jon
--
Jon Phillips
San Francisco, CA
USA PH 510.499.0894
jon@...
http://www.rejon.org
MSN, AIM, Yahoo Chat: kidproto
Jabber Chat: rejon@...
IRC: rejon@...