Hani, Let's stop with the "we're conservative folks" talk. "We" aren't anything. "You" are. Unless you are speaking for specific people (please list them), you are only speaking for yourself.
I know there are users like Rickard and Wayland that have opinions on this and I'm eager to hear from them. This is because you (admittedly) have a biased opinion of 2.x, which is unfortunate since you've taken over as the maintainer of the 1.x codebase. Because you are biased against 2.x and are the maintainer of 1.x, you are in serious danger of jeopardizing the user experience of both projects, as well as the projects themselves. Until I hear from other people, I'm going to translate whenever you say the word "we" on this issue as "I". As per the roadmap set forth by all the 1.x users a year ago, a roadmap and clear migration path has been provided for 2.0. The roadmap and implementation plan was agreed on by everyone (including you, I believe). The roadmap made it very clear that future development would be done in the 2.x codebase. If we can't come to some agreement, it might be necessary for you to step down from actively working on the 1.x version due to conflict of interest: your bias vs. the project goals. I, as do all WebWork users of bother versions, need a vote of confidence from you that 2.x is where future development will take place. Otherwise, as Wayland said, let's stop pretending and give the projects different names (I find that this should be an absolute last resort, as I provided extensive compatibility support). Patrick > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Hani Suleiman > Sent: Monday, February 09, 2004 8:05 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Intended roadmap for webwork project? > > On Feb 9, 2004, at 1:48 AM, Patrick Lightbody wrote: > > > I think the right thing to do, as Hani has said, is to _maintain_ 1.x. > > By maintain, I would assume this means continuing to provide support, > > documentation, bug fixes, and minor enhancements. It is important that > > any chance in 1.x is brought to the 2.0 developer's attention so that > > we > > can make the user experience of migrating from 1.x to 2.0 as painless > > as > > possible. > > > Well, we're not ruling out major new features (perhaps even borrowing > from 2.0 if there's enough demand for it). The goal is different from > 2.0 though, which is why both branches are alive and well. Think of 1.x > users as conservative old-fashioned people, who aren't huge fans of > change, and are much happier without having to spend a lot of time > sending emails to find out why feature X changed, etc etc. > > > However, I want to make it clear that, for the sake of users like > > Wayland that are seeing a bit of an identity crisis, WebWork 2.x is > > where all major enhancements and features will be built. It would be > > irresponsible to both the 1.x and 2.x users to let the branches > > continue > > to diverge any more than they already have. > > > Hopefully they won't diverge. 1.x definitely isn't on life support mode > either. I (on a personal level) will certainly not recommend people use > ww2, and will explain my (heavily biased) reasoning. > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
