Clean. Clean. Clean. If Do has a future, it really needs to be tidied up. We get an A+ for encouraging contributions over the last few years, but we get a low D for keeping the codebase sane. Do is already great, and I'm sure there are interesting directions we could take it further in, but before anything new is added we should optimize. RAOF had some good ideas about this... Maybe he can repeat them here.
We've also tarnished Do's reputation with a few buggy releases (luckily, this can be fixed). We need to follow a release schedule, including strict code freezes. We can regain the userbase that we've lost due to buggy releases by first addressing stability issues, then delivering incremental exciting new changes at regular release dates. We should release bug fixes and stability improvements monthly or bimonthly, and new features releases should sync with Ubuntu. "What are we doing for Ubuntu 10.10?" should be the question we use to structure the conversation. Also, we desperately need to *sanitize the version number*. This 0.8.0.3.1.2r291 is killing me! David On Mon, Mar 8, 2010 at 5:49 PM, Chris Szikszoy <[email protected]> wrote: > Hi, > > On Sun, Mar 7, 2010 at 5:14 PM, Alex Launi <[email protected]> wrote: > >> The main goal of this meeting will be to draft a 1.0 roadmap, and get Do >> back to being killer. >> We need to address current bugs, what new features to add, status of >> windows >> port, and probably some more. Let me know if you can be at the meeting! >> >> -- >> -- Alex Launi >> > > I'd like to propose that each of us identify one or two specific goal or > area where improvement is necessary and vaguely what would be required to > accomplish that goal. I think it's important that we set clear goals and > have a vision of where we want to take Do in the future. If everyone can > come on Tuesday having already thought about and prioritized project goals > as they see them we should be able to have a very productive meeting. > > My goals for the project: > Platform and GUI toolkit independent Do core. > - The core of Do (relevancy engine, Item classes, Abstract service classes, > etc. should be completely platform AND GUI toolkit independent. I think > we've already done a good job of making everything platform independent, but > we really need to cut out the toolkit related stuff and move it to the > appropriate assemblies (Do.Interface.Gtk). It's legitimate to still use GTK > libs as long as they are only interface libs. > - Difficulty: 3 (out of 3). Mostly this involves just cleaning up the > Do.Interface.* assemblies, making sure all abstract / common stuff lives in > Do.Interface, and we move all GTK stuff to Do.Interface.Gtk. The hardest > part will probably be coming up with a way to abstract the configuration > window and moving that out of the Do assembly. The config window has to > interact with our PluginManager class, which currently lives in the core Do > assembly. > - Priority: 3 (out of 3). I'd really like this to be done before I pick up > the windows port again. > > Contextual Relevance. > - We need to develop a smarter and more contextual definition of > "relevance". Currently items or actions are simply ranked by amount of > use. We should develop some sort of relevance that ranks how items interact > with actions and vice versa. > - Difficulty: 1 (out of 3). As far as impact to the code, this should be > minimal. We shouldn't have to change any API or how items interact with > actions. The hardest part will be developing and implementing some sort of > associative item - action algorithm. > - Priority: 2 (out of 3). I think this would result in a great improvement > for our users. As I see it, this is a nice piece of low hanging fruit. > While not the top priority as I see it, we should discuss just how hard it > would be to come up with and implement a proper algorithm. If we agree that > it isn't too hard I think it would make a great goal for the 0.9 release. > > Thanks, > - Chris S. > > -- > You received this message because you are subscribed to the Google Groups > "GNOME Do" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/gnome-do?hl=en. > -- You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en.
