do-windows team mailing list archive

["Krisztian Gyuris" <gyurisc@xxxxxxxxx>]

 Hi Brian,
I started to put together a solution and I have it almost ready for initial
checking. I am down to 34 compilation errors this morning :)
I will check in what I have this evening.

Krisztian

On Thu, Jul 3, 2008 at 12:00 PM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
wrote:

> Hi everyone
>
> It's a great thing that we now have a launchpad group, well two actually,
> but that's a whole different story :)
>
> I think we need to start structuring and coordinating our efforts a bit, we
> will be more efficient if we work together and have a common set of goals.
>
> I have tried to identify some of the tasks we need to perform, it is of
> course not a definite list and we need some sort of tool for organising
> them.
> Note that the numbers applied are not the ordering of the tasks, as the
> whole idea is that we should be able to work simultaneously.
>
> Some of the tasks are more milestones than actual tasks, but they help
> visualize the approach I am proposing.
>
>
> *01 - Find a task-/issue-/bug tracker*
> We need this in order to coordinate our efforts, maybe we can use the bug
> tracker in launchpad ?
>
> *02 - Initial Visual Studio setup*
> Create project, import source, resolve dependencies - no more than this.
> We need one person to do this, it doesn't have to be working, but it needs
> to be pushed to launchpad as soon as it is done in order to avoid the "lone
> ranger" approach
>
> *03 - Move to a compileable state*
> It still does not have to be working ...
>
> *04 - Move to a launchable state (FFF)*
> It still does not have to be working ...
> By FFF I mean that we should now Find, Formalize and Fix bugs
>
> *05 - Move to a base functional state (FFF)*
> Basic functionality working
>
> *06 - Do a 0.1 alpha release*
> Enable those who do not wan't to build it themselves, to install it for
> experimental use
>
> *07 - Get a single plugin to work*
> We need to verify that the plugin architecture is still working and get
> input for the upcomming reorganization/refactoring of modules
>
> *08 - Reorganize/refactor modules to ease maintainance*
> We need to isolate all which is platform specific, this will probably also
> involve the GNOME Do project
>
> *09 - Define platform requirements*
> Which versions of Windows and .NET will be supported , will it be required
> to install any prerequisites ?
>
> *10 - Define plugin strategy*
> Which plugins will we aim to port ourselves, will there be any changes
> needed to the plugin api, how can we make it easy for the end-user to know
> which plugins are compatible
>
> *11 - Port plugins*
> We may decide to port some plugins ourselves
>
> *12 - Define documentation strategy*
> Can we aim to have only an install guide, or do we need windows specific
> documentation ?
>
> *13 - Write documentation*
> We need a volunteer :)
>
> *14 - Define release plan*
> This will help others know what to expect, and help us focus on specific
> milestones
>
>
> I have not included any tasks regarding testing, as this is to a large
> extent dependant on the platforms we choose to support.
> I have also not included adhoc bug fixing, as this is something we can't
> really plan but which will be there.
>
> ... and i have of course left out all the important and unexpected ones :)
>
> I think no matter what, we need to decide on how to track tasks ASAP.
> It could be a simple spreadsheet or a real issue tracker, as long as we
> avoid email based task management.
>
> /Brian
>
> _______________________________________________
> Mailing list: https://launchpad.net/~do-windows
> Post to     : do-windows@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~do-windows
> More help   : https://help.launchpad.net/ListHelp
>
>