faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Need more concentration on wysiwyg and...
by anon on Monday 01/Dec/2003, @23:58
|
I didn't mention the developer list as I didn't want to overload the post and did want him to get in contact with you easily instead of having to do the legwork himself (and risk the posibility that another project may distract him along the way ;o)
I was sure that you would put him on the developer list if the interest was there on your part.
Awaiting wysiwyg with bated breath.
The BE release sounds like you're taking on too much/spreading development thin. You don't have enough people testing (or developers) prior to BE coming out (as posted on the list), yet it looks like you want to release faster than kde releases...so now there are two versions? Or are there two versions? It is more than stable and cvs, right?
That's just my observation, which from the outside is quite possibly wrong.
But you are severely underestimating wysiwyg. While the candidates who are more likely to use wysiwyg won't bring you more developers, it will bring more observers, fans, and buzz. And press. And this will very likely bring more developers.
Just another observation. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Need more concentration on wysiwyg and...
by Eric Laffoon on Tuesday 02/Dec/2003, @11:34
|
> The BE release sounds like you're taking on too much/spreading development thin. You don't have enough people testing (or developers) prior to BE coming out (as posted on the list),
Okay, by this rational we've always been too thin and are thicker now than ever. ;-) We have more people developing on more things, more people per feature and substantially more people testing. Many people on our user list are running CVS and helping us a great deal by finding bugs, for which I am very thankful. The point I make where you might get the idea we are thin is how much we do with so few people. We should have more developers in a perfect world, but it isn't perfect. Because we've always had to deal with this we decided on a tactical approach that would make Quanta user extensible, but so many people are used to a "consumer" mentality that the community aspect has not taken hold yet on over 99% of users WRT Quanta and testing, developing or donating.
Our approach is that any substantial area of Quanta becomes a sub-project and gets it's own leader. Chris does XML and shares Docs with Fab, Nicolas does VPL, Marc does Kommander, Luciano does CSS and other people are doing various tasks that could move about. Andras does the parser and main project as well as fill in on whatever else needs done and so far, just directing and interfacing along with everything else, I do a very limited amount of coding. I plan to take a couple weeks "coding vacation" later this month to get more proficient prior to taking on some larger design projects.
> yet it looks like you want to release faster than kde releases...so now there are two versions? Or are there two versions? It is more than stable and cvs, right?
BE is a development version. This means a BE release will be a branch off of HEAD prior to KDE 3.2 final and from HEAD after. In all cases it will be a snapshot where we have taken several weeks of testing and withheld destabilizing commits so that it should be pretty stable and usable. It will have more functionality than prior releases but some features may be incomplete. It will be close to release stability but with some obvious bugs that should not interfere with most people's use.
As I said in our story, the decision to begin an external release schedule had to do with the rate which various tasks were reaching maturity. Our release schedule for some features is a year, but they don't start always with KDE's schedule. Other features are 1-3 months. Quanta has become a large complex application and note that Kdevelop and Koffice have not been able to make KDE release schedules. We're proud to be a part of the official release package, but a lot of what we wanted to get into 3.2 will be ready first quarter of 2004. No matter what anyone says statistical probabilities place 3.3 a year out. Going to a dual release schedule seems imperative. We are also seeing a good number of new developer interest emails and people learning Qt/KDE programming wanting to be part of our project. We hope they all become active developers and will do all we can to help them. So it's all good.
> But you are severely underestimating wysiwyg. While the candidates who are more likely to use wysiwyg won't bring you more developers, it will bring more observers, fans, and buzz. And press. And this will very likely bring more developers.
Well I don't know who you are, but it appears you're operating at a disadvantage of not having discussed my thoughts on the matter with me. ;-) Once we have reached a level that I believe we are a serious contender for professional development you can be sure that I will be promoting Quanta on KDE to the mainstream press, if they don't get to me first. BTW visual design is actually only one of three critical components that will cause this buzz. ;-)
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
