I'm not even done reading your email but I have to say this. I completely
agree with point 1! That's why I wanted to go to war on the errors
throughout the code, so we could actually work on a working version.
I know it's easier said than done. But many many errors are very simple and
easily corrected.
Sorry. I'll read the rest. (Where you probably declare the project dead..)
I am not a C++ programmer, nor a project manager, but I have enough
experience to see this project spiraling into the dust. As several
people have said, it looks to be just a collection of random thoughts
about what needs to be done. There appears to be no big picture and
therefore no plan to get there. Without the big picture, some of the
tasks could end up being irrelevant or a waste of effort. And without
a plan, the number of people likely to back the Kickstarter is going
to be low.
As I see it, the phases in this project will include at least the
following:
1.
Get the Windows version working reliably to provide a platform for
testing future work. Do not add any new features.
2.
STOP ALL DEVELOPMENT! Put together a project team. Get a project
manager. Make a plan for what is to be done and a rough timeline.
This is important as without this there are unlikely to be many
volunteers to help. This needs to be done right at the beginning to
avoid the project getting a bad reputation.
3.
Put together a team with the required skills to implement the plan.
4.
Start working according to the plan.
Now the plan needs to identify what the final goal is, perhaps something
like:
To create an open source e-mail client based on Eudora that will run
on at least Linux, Mac, Windows.
One might also add which operating systems are going to be targeted,
eg, Windows XP and later, Mac OS X Snow Leopard and later, flavours
of Linux. This is important because different development software
and software libraries may be required to work with all those
operating systems.
It then needs to list all the major tasks that need to be done, and
to give them a priority. Dependencies need to be considered in
determining priority, eg, it is no good working on something that
cannot be tested until something else is finished.
Tasks then need to be allocated to developers or teams of developers.
This could be by people volunteering to do particular tasks, provided
that meets the priorities.
Estimates of the time needed for each task should be identified to
allow for organised allocation of work. If a task is going to take
six months, it needs to start earlier than one which will take one
month.
Regular monitoring of progress is needed, so that if one area is a
bit slow, additional resources can be directed that way.
Milestones will show that progress is being made.
Some major decisions are going to have to be made, particularly in
terms of supporting other platforms. It would be silly to implement
something that does not translate easily to another platform.
I'm not even done reading your email but I have to say this. I completely
agree with point 1! That's why I wanted to go to war on the errors
throughout the code, so we could actually work on a working version.
I know it's easier said than done. But many many errors are very simple and
easily corrected.
Sorry. I'll read the rest. (Where you probably declare the project dead..)
Regards
On Monday, September 10, 2018, David Morrison davidmorr@users.sourceforge.net wrote:
--
Søren Bro Thygesen