Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
KDE GUI

KOffice Team: A Handful of Coders, a Lot of Code 224

Posted by timothy from the kword-rocks dept.
nickbrown writes: "In this interview with the KOffice development team it is revealed that only about 4-6 people are working on the suite of applications. It would appear they lack the resources to keep up with the likes of openoffice. Worth a read as it highlights the troubles they are having trying to produce a truly productive office suite for KDE."
This discussion has been archived. No new comments can be posted.

KOffice Team: A Handful of Coders, a Lot of Code More

KOffice Team: A Handful of Coders, a Lot of Code

Comments Filter:
  • StarOffice isn't mentioned. Has it fallen into obscureness, or are we just not supporting it because it's not free anymore? IMO - any solution that isn't Micro$oft Office is a good solution.

    • Re:StarOffice? (Score:3, Informative)

      by fiziko ( 97143 )
      The free version of StarOffice is OpenOffice, which was mentioned.
      • Yes OpenOffice is mentioned - but is based on older versions of StarOffice. The fine people at Sun - whose free version deserves commendation - at the same time keep improving their StarOffice suite past that of the OpenOffice one, and is now far more robust than it's previous workings. At a fraction of M$'s suite - it's still a good solution.
    • Hardly something to get excited about. Plus StarOffice is going to be payware will OpenOffice will remain free (LGPL).

      Just use OpenOffice and forget about StarOffice unless you work for a big corporation. In which case, a payware like StarOffice might be a good choice.

  • hmm (Score:2)

    by perdida ( 251676 )
    I am not sure whether the author here is trying to start an office-suite software choice argument or is trying to get people to code for this project.

    Exposing the core business weakness of this software development is not going to help it get more work done. It's like putting out a flea-ridden sad puppy and saying, "look how sick he is, don't you want to adopt him?"
    • 4-6 people isn't that few. You would like to have people to participate in UI design, icons, etc. But the 'engine' of these applications could be done by a handful of people. Perhaps they want to much and they should concentrate on the word processor. Just an idea.
    • Problem solved

      Its easier to be a part of a duopoly than fight a monopoly.

    • yeah but... (Score:2, Interesting)

      by jefe289 ( 34351 )
      Koffice is pretty damn good as is... but unfortunately, there are some major insufficiencies: notably, filter support. I think most people who have actually tried using staroffice/openoffice would agree that there is a lot of unnecessary bloat. Another problem, for KDE-zealots like myself, is that other office suites don't integrate well into the slick, advanced, well supported, and popular KDE.

      It just seems that with all the different projects out there that are supported by thousands of developers... there are only a few people for each that actually use the program. However, I see K-Office getting a lot more usage. It just seems that you get a LOT more *useful* code by improving k-office than by improving xyz-random project on Freshmeat. (my 2 cents)
  • Does anyone out there want to mirror that in a readable font?
  • The project is so big, to compete with MSO, that perhaps all the different groups (OpenOffice, KDEOffice, Gnome office, Gnumeric, Abiword, etc) should all collaborate somehow and make a killer product. Then maybe we'd have a MSO killer.

    All the elements are there, and it's all open source anyway, so how about 'together we stand' and not 'divided we fall'?

    • The project is so big, to compete with MSO, that perhaps all the different groups (OpenOffice, KDEOffice, Gnome office, Gnumeric, Abiword, etc) should all collaborate somehow and make a killer product. Then maybe we'd have a MSO killer.

      Sure! Because combining 4-5 totally different codebases that do the same thing always results in a product that's 4-5 times better!
      • Sure! Because combining 4-5 totally different codebases that do the same thing always results in a product that's 4-5 times better!

        Wasn't that the way Emacs was made?

      • Not quite sure how this apparently deliberate misunderstanding has achieved a score of 5 - to my mind the parent statement is clear: collaboration means collaboration, not necessarily convergence by merging code.
        • Point taken. :)

          I was poking fun at the original post because in my mind, for the disparate groups of developers to band together and make The One Office Suite to Challenge Microsoft Office, they'd either have to start (largely) from scratch, or basically take one of the existing open office suites and all work on that from now on.

          It's not that the original post was wrong... as a matter of fact, it was probably right, but it was such an oversimplification as to invite a little fun-poking. Saying "all office suite developers should collaborate to produce a true competitor to MS Office" is like saying "We should all be able grow wings and fly and beer should be free". It's right, but how should it be done?
          • Yes, it is a bit idealistic, fair comment.

            Part of the problem, IMHO, is that C/C++ require or at least encourage the development of frameworks (GUI, RPC, storage, threading etc.) before you can get started on real functionality. This almost guarantees that development will fragment even if you start from the same place. A Java or maybe Smalltalk project would be less prone to this, though still no picnic from the convergence PoV.
    • The problem is that the OpenOffice people and many others are copying and not thinking of doing things differently.

      For example when I developed my DeNotes I wanted to solve some problems. So I stepped back and said, Ok if I could how would I really do this?

      Maybe if they thought like that it would change how we protray office applications. Sure it would be a hard learning curve for the user. BUT it is that or not being able to keep up.

    • Re:How about collaboration? (Score:1, Interesting)

      by Anonymous Coward
      The project is so big, to compete with MSO, that perhaps all the different groups (OpenOffice, KDEOffice, Gnome office, Gnumeric, Abiword, etc) should all collaborate somehow and make a killer product. Then maybe we'd have a MSO killer.

      This IMHO is the only way Linux will eventually 'win' within our lifetimes.
      Their are so many projects which essentially do exactly the same thing, with no real difference or benefit (other than perhaps the choice of window enviroment they use). I personally think thats alot of wasted effort. Some unification would easily stomp MicroSoft but atm that doesnt seem to be the nature of Linux.

      Also as for 'Linux conquering the desktop', it 'ain't never gonna happen'! The nearest thing youll get is 'GNOME conquering the desktop' or 'KDE'. It will be irrelevent what kernel its on as that probably wont effect its use.

      Im not saying merge BSD/Linux/Herd thats madness :) But I feel some unification on the desktop side of things would only be beneficial to Linux

      I know everyone likes choices, but if you encorperate the options into the Office suite/Desktop environment then you still retain your choice

  • 4 to 6 employees (Score:4, Insightful)

    by yintercept ( 517362 ) on Saturday March 16, 2002 @03:12PM (#3174179) Homepage Journal
    While I wait for the poor slashdotted server to retreive the article, I should mention that the right 4 to 6 people can outperform the wrong 400 person programming department.

    Small teams often can focus on the issues at hand and make a more tightly tuned product than the big teams, and if they fail...not as much is lost. This is especially true when you have a good well established foundation onwhich to build.

    • Re:4 to 6 employees (Score:1, Flamebait)

      by krogoth ( 134320 )
      This is especially true when you have a good well established foundation onwhich to build.

      Such as a proper grasp of the English language...
    • I don't think you understand the magnitude of this project. It is huge, and very complicated. It takes a very long time just to reverse engineer other file formats and build filters.

      There is no way that 4-6 people working in their spare time can complete a project like this. Read the source code and you'll begin to get a real feel for the magnitude of things.

      • Re:4 to 6 employees (Score:3, Interesting)

        by yintercept ( 517362 )
        There is no way that 4-6 people working in their spare time can complete a project like this.

        The article says:

        David: People usually assume that writing an office suite is very difficult That's not true. _Some_ part of it are difficult (can I say WYSIWYG ? ;), but there are many many missing features that are easy to add.


        Thomas: It is not too hard to get in. It is written in a Object Oriented language after all. Most stuff is cleanly isolated from the core and well documented. The hard part is getting to know the structures of the applications, but here, we can help. After that, its just programming, which is fun ;)
        When you get down to it, an office product is really just a collection of different objects that have defined rules for interacting with eachother. You don't have to read all 350,000 lines of code to find a starting point for a new module.

        It takes a very long time just to reverse engineer other file formats and build filters.

        The article confirms your point on the filters. They mention the filters as the one area where they need the most help. It would be nice to live in the ideal world where the producers of file formats create cleaner documentation, or provide industry standard filters for their formats that you can integrate in a product. Unfortunately, the temptation is to use poorly documented, proprietary formats to create a monopoly position in the market.

        I didn't say small groups can handle all projects, just that they can do some things very well. I would agree with the article that filters are a rough edge.

    • ... I should mention that the right 4 to 6 people can outperform the wrong 400 person programming department.

      Well, yes and no, depending on how focused the task is. David Faure and some volunteers on the Konqueror team kicked Eazel ($12 million in VC money, 100+ employees) around the block, and the Konqueror + khtml guys did the same to Mozilla. (Yes, I know Mozilla has gotten a lot better, but they still did. Yes, I know Mozilla isn't a browser but a portable development platform -- that's why the Konqueror guys kicked them around the block by making a browser.)

      But building an office suite involves a lot of modularized tasks, and there's just no way for a handful of even the best devs to do them all the way a large team can.

      • Err...speaking about the web browser part of Konqueror, it has not kicked Mozilla's arse in any way, shape or form. Here's why:

        1) Stability. You can not honestly say Konqueror is any more stable than Mozilla
        2) Cross-platform support. Konqueror is not available on Windows or Mac OS
        3) Standards support. Mozilla has better support for more standards than Konqueror
        4) Scope. Konqueror is just a web browser/file manager. Mozilla has a mail client and an HTML composer. Some people may not want them, but others do. I think the mail part of Mozilla kicks KMail all the way to next Tuesday.
        5) Tabs :)
        • 4) Scope. Konqueror is just a web browser/file manager. Mozilla has a mail client and an HTML composer. Some people may not want them, but others do. I think the mail part of Mozilla kicks KMail all the way to next Tuesday.

          Funny, I think that Netscape 4.7 is still a better newsreader/emailer than Mozilla.

          Why you ask?

          Simple: Because it doesn't force you to use the very, very moronic layout where you have to have the message occupying the lower half of the window. This is moronic because messages are usually truncated at 80 chars (which is moronic too, but that's another thread) so you have lots of empty space in the message area, yet it is not tall enough.

          Netscape4 allowed you to open messages in another window so you could put this window beside the main window to be as tall as the screen.

          Yes I know Mozilla can also open it in another window, but that's 100% useless because it doesn't reuse your perfectly arranged window and takes too long to open the new window.

          KNode is the only newsreader I know that let's you choose a sane layout. This makes it IMO the best newsreader available. Unfortunately KMail can't do it (yet?)

          Ironically Mozilla lets you choose between two perfectly useless layouts but misses the obvious. (which is folders on top-right, message overview bottom-right and message left - you get the idea, I would not mind if the message is on the right side as long as I can have it as tall as the screen)

        • And another thing...

          The main reason why I prefer Konqueror is because it has far superior bookmark-handling (creating bookmark-directories is much much less painful), and more importantly, it respawns all windows when I relogin.

          So when I read slashdot or other forums, I just leave the windows open and they will be loaded just like they were the next day. - No more need for temporary bookmarks.

    • The original GEOS development team was probably a dozen people (I'd have to look at some old files to get the exact count). Geoworks Ensemble not only included the GEOS operating system (pre-emptive multi-tasking, object-oriented UI, single image model, etc.), but a word processor, vector drawing program, PIMs, file manager, and other goodies. At the time, it was well beyond the Microsoft offering of Windows 3.0 + MS Works.

      GEOS didn't get a spreadsheet and flatfile database until V2.0, and Internet apps until later. I recall one of the 3.5 engineers on the spreadsheet project (1 = FP math, 1 = data storage and calculation, 1 = app framework and UI (me), 0.5 = charting) finding an article about the Lotus 1-2-3 development team, and their engineering team was larger than all of Geoworks at the time.

      Sadly, the same miracle of small numbers wasn't pulled off by Geoworks' sales department. Not entirely their fault, as the 'chicken and egg' problem of lack of available apps, and a Unix-based SDK kept most developers (other than AOL née Quantum Computer Services) away, which didn't add many available apps.

      The target that KOffice, et al, are facing now is a lot further along (especially Excel; Word still sucks), but the general idea is still true: adding bodies doesn't always make the results come any faster. In the words of Wernher von Braun:

      Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month.
      Which isn't to say more programmers wouldn't help, just that they need to be the right programmers.

  • Scratch an itch? (Score:4, Insightful)

    by Anonymous Coward on Saturday March 16, 2002 @03:16PM (#3174196)
    Where's the "scratch an itch" factor in coding an office suite? People that are smart enough to contribute to these projects tend to prefer logical markup such as LaTeX. So you'd expect very few OSS programmers choosing to work on this as their hobby.
  • probably isn't worth it to most people. Face it, when MS has 90% of the office market and businesses are willing to pay, it just doesn't seem worth it. Could there come a point when you could get a sizable number of defectors to switch? Yes, but MS isn't going to price their cash cow in such a manner as to kill it. A bit off-topic but one interesting facet to this argument is the one about purchasing from MS as they provide "support". When was the last time that your average business user called MS for support?

  • a better article would be an investigation of ... (Score:3, Interesting)

    by Anonymous Coward on Saturday March 16, 2002 @03:17PM (#3174206)

    ...open source tactics.

    I mean, like, really.

    Why don't open source coders collaborate more? Why in the hell do we need a half dozen different office suites?? Give me one good implementation, and that's all I'll ever use. Is it just that getting geeks to cooperate is like trying to get a group of 3 yr olds (or cats) to all go in the same direction -- near to impossible??

    • Re:a better article would be an investigation of . (Score:5, Insightful)

      by Fnkmaster ( 89084 ) on Saturday March 16, 2002 @04:10PM (#3174410)
      Software developers rarely agree on things. I've seen fights (usually relatively calm and technical ones, but sometimes escalating to heated yelling and nearly to blows) in engineering team meetings. The only thing that forces people to work together at a company and come to agreement on some idea (often a shitty one, but decided for them nonetheless) is MONEY. Quite simply, your employer is paying you. Sometimes you just have to give up and accept that the motivations of the source of the money need to be accepted if you want them to keep giving you all this nice cash, rather than your own concepts of what is nice, aesthetic or well-engineered.


      Open Source projects are motivated by ego in some cases ("I want to bulid the next great window manager") or some sense of technical correctness in others ("I hate the way OpenOffice looks/I hate Gtk widgets/etc."). So there's no real incentive to work together on a bigger project - why would you want to say "yeah, I built some tiny component that's part of this megalithic Open Source project, UltraOffice" when you can say "I am the lead programmer on KWord".


      So knock closed source software all you will, money can be an effective way to motivate people to cooperate on bigger software tasks and put differences aside to achieve an overall better result. And though some Open Source business models make this possible, for lots of products (like office suites), nobody yet has figured out how to do this and it very well may be impossible.

      • I pretty much agree with you, but I'd add a twist.
        It's funny, a few months ago, I was saying that open source would never have the polish of commerical OSes like OS X or Windows, because nobody's paid to do the dirty work of making sure that things work consistently across menus, then dialogs, then apps, then the entire package.
        My rationale was like yours, people who are in it for free want to do the interesting part, not sweating it out with a hex editor as the article mentions.
        Lately, though, I've been muddling on the kde-usability list, and am really quite surprised how much work people are willing to put in to polish up the desktop. Who knows how far the efforts will get, or if people will tire quickly, but at least for now, there seems to be a scratch for every itch. Maybe those open source avatars were right after all.
    • I don't want an office suite for KDE. I want an office suite for Linux.

      If there's any advantages exposed in having an application written by a particular toolkit running under a particular environment, then that is the problem. We already have standards for drag and drop, and window manager hints. How about putting 4-5 developers on to the task of making Linux apps act like Linux apps, with the same look, feel, drag and drop, shortcut keys, mime types, etc. Keep the choice, just allow standardized configuration by default.
      • How about putting 4-5 developers on to the task of making Linux apps act like Linux apps , with the same look, feel, drag and drop, shortcut keys, mime types, etc. Keep the choice, just allow standardized configuration by default.

        I believe there is such a project. It's called KDE. And there's another one called GNOME. Oops. Back to the drawing board.

        Frankly, get the keyboard accellerators standard and most of cut/paste interoperating, and you'll be fine. It's not like people expect to be able to drop an excel spreadsheet range into a wordperfect doc after all. People will take an 80% solution if they don't really need the missing 20% (hell, look how well linux has done without acl's standard). Themes don't need to be perfectly consistent so long as the metaphors are consistent. Even microsoft isn't obeying that consistency principle itself (WMP 7 looks like nothing else on win9x)

        It's not the consistency (people don't expect it these days), it's not the documentation (people don't read it), it's that the average user isn't being offered a value proposition any better than what they're using now. So you have an office suite and a web browser and chat programs ... which is precisely what you get with windows as well. Not one end user gives a tinker's damn about the source code. If they did, they wouldn't be end users.

        It's things like the outrageous pricing of Office XP that might really give the free alternatives a boost. Too early to tell...

  • Concentrate on useful apps for 90% of people (Score:1, Interesting)

    by Anonymous Coward
    Most people do not need a full Office suite.

    So concentrate on the applications that your average person needs, and accept that OpenOffice is going to be the heavyweight Office suite.

    Make a flat file database program for people to store various bits of data. Make a word processor that can be used to write good looking letters and documents, but not have the more business features of Word. Make a spreadsheet that can be used to help calculate taxes or the monthly bills.

    • Here we go again. I am once again going to mention something that NO ONE seems to understand is IMPORTANT in a wordprocessor. CITATIONS and REFERENCE HANDLING.


      There is NOTHING that really separates one of these wordprocessors (abiword, kword, openoffice/staroffice) from one another. They ALL do the same sorts of things in the same ways...but not a one of them has something a real professional writer REQUIRES. None of them has what ALL college students (and many highschool kids) REQUIRES: an ability to handle citations and build reference pages.


      Word and Wordperfect have this on Macs and Windoze via third party apps like EndNote, because the processors were designed so apps like EndNote could seamlessly become part of the wordprocessor (for all practical purposes). Endnote adds its own menubar entry so you can insert citations into your text as you go and then it AUTOMATICALLY generates correctly formatted reference page(s) based on user selection.


      There is one and ONLY one "wordprocessor" app in linux/unix that can handle this well and that is Lyx. Lyx is IT. The ONLY show in town for any student or professional writer who needs to cite references in their writings. This is ALL scientists and ALL college students and anyone else who wants/needs to write serious research papers. You MUST cite references or your paper is unfounded heresay, yet NO wordprocessor project is even TRYING to add this capability to their app.


      Obviously, none of the projects is interested in any professional writers. Their targets would appear to be letter writers and writers of any work that needs no support (fiction). This is fine, such as it is, but no one gets through this life without having to write SOME papers that require citations and reference pages damnit! If you actually have managed to avoid this then your degree must be astrology or basket weaving.


      Someone on ANY of these projects: OpenOffice, Abiword, Koffice...provide either a pipe (like Lyx uses to communicate with the most excellent Pybliographic) so third party apps can work seamlessly with your wordprocessors and insert citation markers and handle reference page generation OR add this capability directly into your wordprocessors! Hell, OpenOffice/StarOffice is PARTWAY there but they dropped the ball BIGTIME. OpenOffice/StarOffice actually has what it calls a bibliography database but it is totally useless. All it will do is store whatever you enter into it MANUALLY. Then, it wont use this database to allow you to insert references/citations into a document, no, it just holds the information uselessly. Go that ONE extra step and make the bibliography database USEFUL: it should be able to import and export all the major citation formats (bibtex, refer, pubmed) and there should a menu item in the wordprocessor that talks directly to this database and will allow the writer to insert citations. At the end, you should be able to hit a "create reference page(s)" button and have staroffice/openoffice add a formatted set of reference pages to the ass-end of the finished document just like Endnote plus Word or Wordperfect will!


      I mean, c'mon! Quit focusing on toy writing and add something that hardcore researchers and all college students require. If Lyx can do it, so can the more user-friendly wordprocessors like Kword, Abiword, OpenOffice, etc.


      Because of this fatal failing in ALL available linux WYSIWYG wordprocessors, I have to keep Lyx around so I can do my real writing, leaving the rare note or letter to Kword or OpenOffice. What a waste. A nice, BIG app that is kept around just for simplistic writing. Lyx is OK but damnit, I want and need to write, not learn a programming language (latex). My job is to do biological research, not learn programming or hundreds of obscure latex commands just to publish. Lyx and I get by but there needs to be more options for the research paper writer/college student/scientist.

      • Here's a great example of the benefit of kword. Launch kword and then run "dcop". You will see kword-xxxxx processes listed. You can then see all the documents in each of those processes.

        There are many functions available for communicating with a kword document that is open. Something missing? File a wishlist or contact the mailing list. I'm sure it's easy to add.

        Graphically, you can do this with the "kdcop" tool too.
      • Don't worry praedor, you are still on my TODO list :)

        Maybe you missed the fact that KWord does have plugins like you seem to require. The latest version has a thesaurus plugin for example.

        Anyway, exactly _this_ is why more authors are needed. The basis is there; just the work needs to be done.

        • Don't worry praedor, you are still on my TODO list :)


          Thank GAWD! If I were a coder, or even had the time to teach myself (I am working on a thesis in molec. biology, not computer programming) I WOULD offer myself to handle it. Unfortunately, I am a plain ole enduser that needs certain functionality to do my basic day-to-day writing. The ONLY writing I do that doesn't include references these days is in emails.


          Lyx IS powerful but damn, it is NOT all that user friendly. I just do not have the time right now to learn the ins and outs of latex (or all the oddball quirks of Lyx). I just want to write and move on to the next experiment.

  • Open Source Leeches (Score:2, Interesting)

    by Anonymous Coward
    This is the real way open source works. Everyone cries and screams about open source, but when the rubber hits the road only a couple of people do a decent job and do the actual work, while the rest of the people just rave on about how l33t an open source coder they are. Most programmers expound open source... then try and figure out ways to sneak the code into their own stuff to make money.

  • Article (Score:3, Informative)

    by smak ( 193931 ) on Saturday March 16, 2002 @03:22PM (#3174226)
    This interview was originally planned to take place during the FOSDEM, but we didn't have the time to do it, so it was held on IRC on Tuesday, February 19th 2002. Of course, the log had to be edited and reshaped. The result is this informal interview.

    The participants were:

    Philippe: Philippe Fremy, (freehackers team), interviewer.

    Thomas Capricelli: support, hosting, photos and help (freehackers team).

    Ben: Ben Adler, logging and help

    Werner: Werner Trobin, KOffice developer

    David: David Faure, KOffice developer

    Laurent: Laurent Montel, KOffice developer

    Thomas: Thomas Zander, KOffice developer

    The KDE room at fosdem Philippe: How was KOffice started ?
    David: Torben Weis originally started KOffice. He wrote the libs and Reggie (Reginald Stadlbauer) wrote KWord and KPresenter. Torben also wrote KSpread.
    Werner: Torben is a programming-ueber-god. He is a programming-task-force in himself. :-) Kalle (Matthias Kalle Dallheimer) added KChart, which was developed for his company (Klaralvdalens Datakonsult)

    Philippe: Where are they now ?
    David: Reggie is working for Trolltech. He is behind QtDesigner. This is why it had a "Tools" menu for inserting things, instead of "Insert". Tools is what KWord and KPresenter had.
    Werner: Torben is working at the Technical University of Berlin IIRC. Last time I talked to him he was developing a CASE tool or so. Nothing KOffice related.

    Philippe: How and when did you get involved in KOffice ?
    Thomas: Ohh, I don't recall exactly when. Something like 2 or 3 years ago. I picked up where Reggie left off since he ran out of time. KWord was unmaintained at the time.
    David: One year ago. KWord was really needing some help, so I jumped on the boat. I proved that it was actually possible to use the richtext stuff in KWord, which Reggie and Thomas had started to doubt, I think. Backporting QRichtext to Qt2 was easy. The real challenge was redesigning KWord around it. Reggie and Thomas had great plans, but no time for them, so I just did it.

    David: In general I realized that I never *ever* started anything new in KDE ;) I always joined in the effort started by someone else. I'm the "manpower that makes things possible", maybe, but I never take the initiative to break things myself. I joined Waldo for ksycoca, Coolo for kio-make-it-cool, etc.
    Thomas: I like working with David. I have ideas and a general design (plans sounds good) in my head but no time to do it. David is just someone very good at the implementation and the details and stuff; works great together IMO :)
    David: I agree :)

    Philippe: Could you give us a short report of who is doing what on which application in KOffice right now ?
    Werner: I am mainly hacking the core libraries and filter related stuff.
    David: I am implementing WYSIWYG in libkotext (common to KWord and KPresenter), and some other KWord fixes. I really thank Mandrake for letting me work fulltime on KDE.
    David: Nobody is hacking KSpread right now except some random contributors
    Laurent: I improve KPresenter (zoom + page), add the DCOP interface to KWord/KPresenter. I also fix some bugs in KChart.
    Thomas: I am hacking the tables in KWord. For 2 versions they have been rewritten twice, lets do it another time. This time I actually think I know what I am doing. So I am implementing it the way I think it should be done. Plus fixing the bugs that bug me in other parts of KWord. Plus I am always bugging David about stuff he is doing in KWord.
    Laurent: Nobody is working on kugar and kivio.
    David: Kontour is being redesigned by 2 or 3 people, but although they had the time to break everything, it doesn't look like they have time for fixing things now. :) Krayon had nobody for quite some time. Recently someone committed a few fixes, though.
    All in all, it's almost one main developer per application only, and random contributors... surely not enough.

    Philippe: What about KFormula and KChart ?
    David: KFormula has a single developer, Ulrich Küttler with little time. KChart has two parts. The core engine, developed by Klaralvdalens Datakonsult (Kalle's company), and the KOffice part, on which Laurent works sometimes.

    Philippe: What about the remaining ones, in the KOffice cvs: KPlato, graphite, kosoap ?
    David: those 3 are unreleased alpha stuff.
    Werner: graphite is my little pet project, nothing worth writing about in the current shape.
    David: koshell is an old hack of mine, I'm trying to pass its maintainance to Sven Lueppken, but it's really Werner who's hacking it for now ;)
    Werner: I'm really lacking time for hacking
    Thomas: KPlato is a planning application, its been through the design phase. The design is implemented and it is basically waiting for people to finalize the design, I.e. fill the classes allready there. KPlato is 'designed' by 5 people talking on a mailing list without a line of code. I have implemented that design completely. The design I am talking about is just the data classes, nothing more. Naturally the next thing that has to be build after that is a GUI. But that is simply not done.

    Philippe: a good project planning application is really something missing.
    Thomas: I know, that is why I jumped in, hoping to kickstart the project. But after almost no code was written by others I found that this was not worth my time for now.

    Thomas Zander and Laurent Montel
    Philippe: So basically, you are 2 full time, paid developers, plus some filter developers, plus 3 or 4 part time contributors.
    David: hmm, more than 3 or 4 I think, if you allow "part time" to be very small.
    Werner: Yes, the filter developers are Nicolas Goutte, Shaheed Haque (lacking time), Ariya Hidayat, Clarence Dang,...
    David: lots of filter developers, if you count them. Usually one per filter.

    Philippe: It looks like some help would be welcome.
    David: Yes, definitely. On the applications (e.g. Krayon, KPlato, Kontour etc.) we definitely need help. Those apps have almost nobody working on them. The other apps do need contributors, too.

    Philippe: What is the programming experience required to contribute ?
    David: People usually assume that writing an office suite is very difficult That's not true. _Some_ part of it are difficult (can I say WYSIWYG ? ;), but there are many many missing features that are easy to add.
    Thomas: It is not too hard to get in. It is written in a Object Oriented language after all. Most stuff is cleanly isolated from the core and well documented. The hard part is getting to know the structures of the applications, but here, we can help. After that, its just programming, which is fun ;)
    Laurent: Any help is welcome, whatever the experience. Some people can create templates or write documentation, tutorials, etc... It's not necessary to know C++. Of course, you must know C++ if you want to hack on KWord.
    Werner: There's also a need for GUI guys and artists. We don't have a KoShell icon, for example, and the user interfaces are a bit crowded.

    Philippe: Do you have places where you would like to see someone contributing right now ?
    David: Definitely. Right now, KPresenter could have a UI redesign (hiding the least used toolbar buttons etc.). KWord needs dialogs for creating envelopes. etc. etc. Many small jobs. A new KWord developer actually started by fixing a simple error message, and is now porting all of KOffice-1.1.1 to KDE3....

    Philippe: What are the planned improvements for KOffice ?
    David: Right now we are busy fixing the things that we broke. In KWord, due to the WYSIWYG text layouting. In KPresenter, due to zooming support. This sounds small, but actually, it led to a big design change.
    Laurent: I am fixing KChart and adding some features. Footnotes for KWord is also planned.
    Werner: My short term goal is to implement the rest of the new filter system. The long term goals are e.g. a better clipboard, better support for embedding, a general clean up of the core libraries, ... I also plan to work on graphite a bit more if the free time allows it.

    Philippe: Do you have a list of features that will make it into the upcoming release ?
    David: Now about the long term plans... Those really depend on how much man power we can get. We have a list for what's already done (see the KOffice release plan, more stuff will be added to that while being done) However, I can't say what will be in the release that is not already done. That's where time / number of developers is the problem.
    Thomas: My long term plans for KWord (which is all I am restricting myself to at the moment) is adding more stuff that makes it easier to use the application. Like markup macros. And character styles, frame styles and page styles..
    David: My next step for KWord is frame z-order, and then looking at the buglist to see what people requested (for instance, double underline...)

    Philippe: You planned 3 Beta and 1 Release Candidate, isn't that too much ? KDE3 had originally 1 beta and 1 rc (which turn into a second beta), no ?
    David: It's exactly what we had for KOffice-1.1 . The release plan for 1.2 is _exactly_ the same as the one for 1.1, just one year later. Code reuse, release plan reuse ;) I think KOffice-1.1.1 is only as stable as it is due to the multiple betas
    Werner: KOffice gets very few testers. Some people download it and work with it for five minutes. This simply doesn't highlight nasty bugs, but just real showstoppers. There are only few people actually e.g. writing a longer letter or creating a whole presentation.

    Philippe: So you need more users too ?
    Laurent: yes !
    Werner: Definitely. Most of the testing is done by us developers
    David: Actually, betas are a really great thing for developers. We can release code for people to test, without having to worry about it being considered a final version, and hence a must-be-completely-stable one. More developers is much more needed than more users. Not handled bug reports are the proof of that. But it's true that more (advanced) users helps finding the source of some problems. Sometimes.
    Thomas: We have a number of end-term students (last year project in the company) basically they all say that KOffice is not usable at the moment, most bugs are being fixed, when that is done the not-enough-users problem will go away.

    Laurent Montel and David Faure hacking
    KPresenter during a boring presentation
    Philippe: The must-ask question: what is the state of the import/export filter for MsOffice ?
    Werner: We have some import filters, at least. The WinWord import filter imports tables and text/basic formatting (pictures are disabled). The Excel import filter works quite nicely.
    David: There is currently no export filter for MsWord. This is an area that definitely needs help.
    Werner: As I worked on that myself I can assure you that exporting to WinWord is *not* funny.

    Thomas Capricelli: Could we have some more information about picture embedding in KWord ? What's the problem ?
    David: Actually, the problem is for the Windows Meta Files, which map to a Kontour part. Since KIllustrator (now called Kontour) crashed for some time, importing wmfs was disabled. And since Kontour is currently very broken (redesigned), enabling it now wouldn't do much good :}
    Thomas: Picture embedding has gone a long way since the horrible support in 1.0. Pictures are correctly scaled, correctly and intuitively placed and can be embedded or placed external of the main document. Lots of stuff has to be done, but it is getting there quite rapidly.
    David: I think it's only WMF embedding that is disabled. Importing MSWord an document with bitmaps should work ok even in 1.1.1

    Philippe: I remember the guy of wvWare starting a project for creating a generic Word import/export. Did that work ?
    Werner: This "guy of wvWare" was me :) ...and as noone except Shaheed joined, it somehow didn't really work out. Some code is there, but I just don't find the time
    Philippe: And on the side of abiword ? Weren't they supposed to help out ?
    Werner: The abiword guys said they're going to help, but noone really did. They were also lacking time. I've written 99% of all code in wv2 ;)

    Philippe: Can you reuse the stuff from OpenOffice ?
    Werner: It's really hard. They use libc and nothing more. They have their own toolkit and stuff. You can't just take parts of it and reuse it. And the design is, well, hard to follow.

    Philippe: But they somehow managed to understand how MsWord works, so I imagine you can at least get hints from there ?
    Werner: yes, it helps, but it's very time consuming.
    Philippe: What is the difficulty with writing it ? Is MsWord's format so messy ?
    David: Afaik one very messy part is the incremental saving, i.e. appending the changes at the end of the doc instead of modifying the real data.
    Werner: They don't save the full file all the time, but append "diffs". For example, I spent 3 days hunting a bug in my filter. The bug was in the specification.
    David: I also suppose that writing an export filter for a closed commercial app is awful - if it crashes or says "can't open", you have no way of debugging that The format is just partially documented and somehow broken, not fully secret & broken.
    Werner: There are situations where WinWord just crashes without further notice if one bit(!) is set incorrectly ... incorrectly as in "according to the SPEC" ;) It's really not funny to develop that, I can assure you. So when you don't get paid for it you lose the motivation and move on to something more interesting.
    Philippe: We sure all can understand that.
    David: Sometimes I wonder if I shouldn't spend some time continuing the wv2 stuff.

    Philippe: I did not pick it up: you are working on the filter directly in KOffice or working on wv2 which will be used by KOffice ?
    Werner: Both, but I am lacking of time. Just to give you some numbers, StarDivision had 2 full-time developers for the im/export filter for more than a year! Now guess why KWord can't export .doc :(
    David: AFAIK Shaheed started to work on wv2, then seeing that no abiword developer could help making this advance, went back to his KWord msword filter....

    Werner: The problem isn't (at least for the import case) that the file format is ultra secret/broken. It's just lack of time. It's so frustrating to read a .doc file in the hexeditor for hours
    Philippe: Yes, not very funky stuff to work on !
    Philippe: Some distro should give a kick to that ! I can't think of any Redhat support, but we could contact Suse.
    David: Mandrake already sponsors two fulltime KOffice developers. Maybe it's time for the other distros to give a hand ?
    Werner: Caldera sponsored my development last summer. I had six weeks to work on wv2. All the code which is there was written in that six weeks :)

    Philippe: Everyone seem to be thinking OpenOffice is the Office Suite of choice for Linux. But I am not sure it integrates as nicely as KOffice applications do.
    David: OpenOffice is not the Suite of choice, it is rather the only one that's currently doing the job. If KOffice improves, everyone (almost) will prefer KOffice (lighter, more integrated with the rest of KDE, nicer toolkit to use IMHO, etc.)
    Thomas: After hearing 2 students swear for 3 days, I'm pretty sure Openoffice will not be the solution for companies for some time to come. (They switched to LaTeX now)
    Philippe: KOffice has much more potential: it was developed by very tiny manpower in comparison with other suits or applications.
    David: Yes, the power of KOffice is that it fully reuses the power of Qt and KDE. KOffice can embed documents thanks to kparts, it has configurable toolbars thanks to the XML-GUI, etc. This means KOffice development can concentrate on the actual office functionality. The rest is provided by Qt & Kdelibs.
    Werner: Some people compare the pure line counts. OpenOffice has approx 8million lines, KOffice about 350.000 or so. We can use a lot of nice stuff from Qt and KDE. OpenOffice has to invent *everything* above libc. For a good example please see David Faure's 8-lines text editor, or the KPart article
    David: I wrote a 5 lines "generic viewer". It can show any kind of file for which there's a KParts part. See docu in componentfactory.h ;)

    Thomas Capricelli: Did you read about latest RMS statement about KDE/Gnome cooperation ? What do you think about it ?
    David: this doesn't apply to KOffice, since there's not really a gnome office suite. :)) But I find this very good that RMS states this. I think this 1) finally gives some credibility to KDE for the "GNU only" people. 2) it might actually foster some cooperation.

    Philippe: Is the Euro symbol supported ?
    Laurent: The Euro works in KOffice no problem !
    David: Yes. see this link on the KOffice website.

    Philippe: And i18n support ? Are various exotic languages correctly supported ?
    Thomas: Yes, see this example.
    Laurent: Yes, now KWord supports bidirectional languages => arabic language etc ...
    Werner: Qt (thus KOffice) supports UTF-16 and we use QString for everything the user sees. The translations are done by the KDE translation team (http://i18n.kde.org)

    Philippe: I wonder if Abiword does that too. Do they use Pango and Gtk 2.0 ?
    Werner: Yes, Abiword does that too. At least Dom Lachowicz, the guy I talked with about wv2, was implementing that. But they do their own Right-to-left support, from what Dom told me. I have no idea if that is in the latest stable release, though.
    Laurent: Abiword is not integrated in Gnome. It uses some gnome libraries but not much.

    Ben: Doesn't Microsoft want to use xml file formats in future office formats? If yes, wouldn't that make import/export a lot easier ?
    David: Good question. It mostly depends on how they do it. The main advantage of XML is that it's readable. At least that will help. As for conforming to any spec of theirs, we know how bad they are at that. They will surely "extend" XML to do things their own way.

    Ben: What about Aethera in KOffice? As a user, I'd LOVE to see Aethera in KOffice. How much do you trust theKompany to actually deliver Aethera, would you put it into KOffice CVS if it was an open license ?
    David: Aethera is a mailer, right ? Then it has nothing to do with KOffice. It's important to understand what KOffice is about. It's about editing *documents*, and being able to embed documents from other KOffice components. There are plans for more KDE PIM stuff, integrating kmail with contact / calendar stuff. The kdepim module in CVS. This needs help too! KOffice doesn't mean "stuff you do at the office" in general. KMail is in KDE, but not in KOffice.
    Laurent: Nobody works on Aethera ! At least publicly.
    Ben: The latest aethera beta is 4/2001!
    Werner: They also have Kivio there, but it doesn't seem to be maintained either.

    Philippe: Where would you like to see more cooperation with other projects ?
    Laurent: Filters, I think.
    David: Yes, filters definitely.

    Philippe: Do you think it would be possible to define a common free format for Office files, like it was done for .desktop files ?
    Werner: The first step is the common packaging format. This is discussed on the office_standards list, on their website. But I don't know the current KWord DTD good enough to participate in such a discussion.
    David: We are currently discussing with the OpenOffice hackers about the ZIP packaging. So the thing we can say in the interview is that one of the plans for KOffice is to maybe switch to ZIP instead of .tar.gz for two reasons:

    for efficiency reasons (ZIP allows "load on demand", "partial saving")
    for compatibility with openoffice.
    The other plan would be to use openoffice's zip code, and this is what we're discussing with them currently. This solutions makes loading/saving in KOffice much more efficient than using an external ioslave.

    Philippe: Are you actively participating ?
    David: Maybe we should get more involved in discussing this. You can say this interview will have been useful, I'll discuss the common file format with openoffice in the near future ;)
    Thomas (Capricelli): We are glad for that :)

    Ben: can KOffice be compiled for embedded devices? Do you think making KOffice available for embedded devices would noticeably increase KOffice's user base ?
    David: I think this is technically possible. I don't think any of us will take the time to do that, but anyone with interest in this can surely try.
    Werner: It's probably no big deal to get it to compile, but it's hard to strip down the UI that it's usable.

    Philippe: Thank you all for participating!
    • Right now, KPresenter could have a UI redesign (hiding the least used toolbar buttons etc.).

      Might not be a bad idea to add a "logger" so that all features used are logged, their frequency, etc. This could be used by the developers to fine-tune the displayed features, and hide the lesser-used ones.

      Of course, this should be disabled by default like the Mozilla auto-loader, but it could be a prominent option in the installation (again, like the Mozilla auto-loader).

  • But why? (Score:1, Redundant)

    by chill ( 34294 )
    Yet Another Office Suite...

    It is kind of hard to get motivated for KOffice when OpenOffice, Star Office, Applix (still around?) and other acceptable components such as Abiword, Gnumeric, etc. exist.

    There is nothing wrong with KOffice, though personally I have a hard time with frame-based word processors. It just seems that there is a lot of redundancy in these office projects and that sort of saps the strength of those with the necessary skills. You can only do so much.

    • Re:But why? (Score:2, Informative)

      by PoiBoy ( 525770 )
      Applix (still around?)

      Applix is still available, but my impression (based on past /. reports) is that the parent company isn't marketing it very heavily or planning on making major new releases. I think the real problem is that they got clobbered by StarOffice and all the other free packages available.

      It's a shame, really, since I have always liked it better than all of the other office suites available. Fortunately, the current version is very mature, so the lack of future development isn't a problem -- I'll be using it for years to come just the way it is now.

    • Basically it comes down to this: let the best man win.

      None of those products that you mentioned are fully accepted as MS-Office replacements, so that opportunity is still there. When a winner exists, everyone will know.
  • Do they have any testers? I guess that mean WE are the testers.

  • Unrealistic Goals (Score:5, Insightful)

    by lkaos ( 187507 ) <{sw.yeknomedoc} {ta} {ynohtna}> on Saturday March 16, 2002 @03:27PM (#3174250) Homepage Journal
    The Free Software community is more than capable of delivering an office suite. 4-6 individuals in not a bad team, but they should be focusing on a specific component instead of trying to do it all at once.

    Abiword is an excellent word processor and Gnumeric is a great spreadsheet program. Gnome's figured it out. No one wants to work on a large, bloated project for free. Break it up into littl projects and you'll get a couple 4-6 individual teams.

    Of course, the article is /.'d already so I am only guessing...
    • KOffice is a set of components, not a monolith. KDE uses a component based development model. Thus each of these "applications", kword, kspread, kpresenter, etc, are kparts. You can work on one and never even see the source for the rest. They are just released together as a bundle by the KDE project.
      • KOffice is a set of components, not a monolith. KDE uses a component based development model. Thus each of these "applications", kword, kspread, kpresenter, etc, are kparts. You can work on one and never even see the source for the rest. They are just released together as a bundle by the KDE project.

        That's exactly the problem. Break each application out as a tarball instead of requiring people to deal with the whole bundle and the project will take off.

        Mind you it's impressive what's been accomplished with a tiny team, however koffice is in no way usable, I know, I've tried. It's pretty but it doesn't do the job.
        • i agree with your point on the usability of koffice. i'm fairly happy with using staroffice 5.2 for any office type work i need to do.
          but.. i can't agree with your comment on breaking the source out. i assume you've installed kde itself from source? i have 13 tar files for my kde install which includes kdevelop and koffice. i know there are still a few bandwidth challenged individuals out there (i feel your pain), but i would really prefer a kdecore and kdeother tar that is all encompassing.
    • Actually, from my experience, programming in a BFS (breadth-first) manner is more productive and motivating than programming in a DFS (depth-first) manner.

      You get to see more results and get more satisfaction sooner by showing fewer capabilities in many fields, compared to showing many capabilities in fewer fields.
  • are they using supper tools.

    Remember that these are the same guys who had a hard time with Corba and had to invent DCOP and KPARTS.

    I would say that KOffice being anywhere withing sight of the other Office suites is a prety strong testiment to the quality of the KDE Libraries and foundation.

    • Re:Are they supper coders or (Score:1, Funny)

      by Anonymous Coward
      are they using supper tools.

      Actually, these aren't requirements even for great programmers. Linus, for example, still takes time to eat with his family, and codes with just his hands.

  • Anyone who has read Brooks' "The Mythical Man-Month" will tell you that more coders != more productivity. Not always, anyway. And I think that this especially applies to open source projects where coders are often doing their work in different countries, if not different continents. I'm sure the openoffice team spends a hell of a lot of time just getting together and planning stuff, integrating everyone's code, etc. During this time the core KOffice developers can be banging away at the keyboard writing more code.

    So it's not hopeless, even the smallest coder can change the course of the future :)

  • what's wrong with NOT reinventing the wheel, and throwing your support behind open office? why not start submitting patches there, merging their technology? They could still fork it later if things didn't go well for them, right?

    • Openoffice is huge, slow, and doesn't fit into the KDE model.

      KOffice is also quite an old project. It definitely predates the OpenOffice project (though not StarOffice).

  • What I'd like to see (Score:2, Interesting)

    by haeger ( 85819 )
    Someone suggested not too long ago that since most of these projects use XML for aving files and such, a common standard should be set so that each and every Office-app can read any document created on any app on any platform. And they should render those documents to look the same way too, unfortunatly Staroffice/Openoffice isnt quite there yet but I guess that their job is a bit harder since MS probably won't share their specs for their fileformats.

    I personally I would love to be able to use KOffice on my linux-box at home, mail it to my job and complete it on Star/OpenOffice on IRIX and then mail it to my PHB to watch on his new spiffy OfficeXP, because I really think that if the whole open community unified around a few common fileformats for Office-apps then MS wouldn't have a choice but to support it.

    Perhaps we could call it "Portable Document Format"?

    .haeger

    Play soccer manager on the web: Hattrick [hattrick.org]

    Cure cancer:Team 249 [stanford.edu]

    • Re:What I'd like to see (Score:4, Interesting)

      by __past__ ( 542467 ) on Saturday March 16, 2002 @06:31PM (#3174961)
      Well, there is actually work done for KOffice to use XSLT (XML Transformations for the buzzword-impaired) to import/export XML-based file formats - a nice idea, scince KOffice, OpenOffice and AbiWord all use XML (however, AFAIK none of them "plain" XML documents, e.g. a KOffice doc is a tarball containing severaly XML docs, included files etc.)

      However, I doubt that XML makes finding a common file format any easier. The problem is that there is a reason that there are different formats, most of all that the programs have different features. No file format will make KSpread deal with VBA makros.

      XML may make things easier - I guess writing an export filter will be more fun if you have a DTD or Schema, and reverse engineering a file format that uses <heading> instead of @(;$- may cause less headaches - but it is certainly not the one solution to all interoperability problems. And, after all, just look at the HTML output any MS Word version generates, and you'll notice that XML isn't neccessarily more readable than binary...

    • What touching faith people have in the value of putting information into a tree. No need for other data structures, or a 'language' in a meaningful sense of the word - no verbs or variables or control structures of any kind in fact - just so long as it's got that cool tree shape.

      As will be obvious to TeX users, writing a document is really writing a program. One might reasonably guess that a computationally complete language would be a good starting point for a document format. Bu, hey, if you want to hide a new and kludgy language in buckets of XML gibberish, I'm sure you could get the disk drive makers to sponsor you.

  • Let's hear it for the "many eyes"! (Score:3, Insightful)

    by reemul ( 1554 ) on Saturday March 16, 2002 @04:16PM (#3174439)
    Whatever happened to those many eyes that were supposed to magically appear to review and help out with open source software? One would expect a lot of interest in an application suite that was supposed to directly attack Microsoft's most profitable offering, but instead they can only rustle up 4-6 regular coders? Yikes. I've had more _testers_ reporting to me on just a maintenance release of a commercial product. The team for the new releases was rather larger, and the product really wasn't that complex. I don't care how godlike the code-fu of the participants is, they can't possibly handle the immense task of building an entire office suite with so few people. Just dealing with proper handling of MS file formats (particularly given that the formats aren't published) would take up most of the time of such a small group, without leaving much in the way of resources to actually do anything with the files once they're read. And that is about the number one requirement to compete in the space, like it or not. Formal testing and documentation are clearly out of the question, along with lower priority functions like installers and forward planning.

    Why aren't more of the rabid open source zealots - such as the ones who will immediately mod me down for trolling/flaming/having mismatched socks - helping out instead of just talking (loudly) about helping. A few more folks spending less time on advocacy and more time on utility could make a real difference, so that apps like KOffice can become attractive not just because they aren't from MS, but because they were actually useful and well-written.

    disclaimer: I don't work for MS. I have not in the past worked for MS, and I do not anticipate working for MS in the future. I would be perfectly happy never using an MS product again if the open source alternatives would actually work and were easy to install.

    • Re:Let's hear it for the "many eyes"! (Score:5, Interesting)

      by Guillaume Laurent ( 155210 ) on Saturday March 16, 2002 @05:48PM (#3174826) Homepage
      Whatever happened to those many eyes that were supposed to magically appear to review and help out with open source software?

      They don't exist. That's one of the Great Myths of Open Source.

      I'm one of the developers of Rosegarden [sf.net], a MIDI sequencer and editor. Since our 0.1 release in october, we've been receiving about 2 or 3 requests from people saying they want to help. Only ONE so far has produced real code.

      I've talked about this with David Faure at the Linux Expo in Paris, and he's having the exact same problem. Many good wills which fade away almost immediately. And we both were guilty of this too in the past, offering our help to a project but never delivering anything.

      I've also talked with a friend who is the author of GWM [koala.ilog.fr], a window manager with a lisp intepreter, like sawfish, except it predates it by 10 years or so. Even then it was the same thing : he practically never had any contributions on the core C code. However he had lots of people writing lisp modules.

      The reason is simple : programming is hard, and it takes time. It's already hard to "enter" into someone else's code, it's even harder when you're doing it on your spare time, after a whole day's work, or only during week-ends.

      Community development works for modular projects, like the Linux kernel, Gnome, KDE, where each one can realistically take care of their own small part and be autonomous with it. But the best way to develop software is still to round up competent people in the same physical place, where they can actually talk to each other. irc and email do not replace that. Unfortunately, such a configuration costs money, and so far it seems very few Open Source joints can make that happen.

      • Interesting... you're the author of a fairly obscure project (2300 downloads doesn't break any records), and since you haven't "many eyes", you decide they don't exist.

        You then go on to accuse other people of doing what you do. You can't possibly expect everyone who expresses interest to become a developers on your project, just like you can't expect everyone who visits your site to download it.
        • For the record, rosegarden is older than KDE or Gnome, and is listed on most sites which talk about Linux and MIDI, it's not that obscure :-). The 0.1 release is a rewrite (check the homepage for the whole story).

          Also, in case the testimonies of Colas (GWM author) and David don't persuade you, I've also been a co-maintainer of Gtk-- for a bit more than 2 years, and it was the same there. Lots of people offerring help, very few delivering.

          I'm not accusing people of anything, just making a plain statement derived from almost 7 years working in the Open Source community (started in 95), collaborating on Rosegarden, Gnome, Gtk--, and KDE. And well, when someone sends an email basically saying "Can I help you developing your project ?", I believe most people would expect them to actually do so. Only I've long ago learned not to.

      • Re:Let's hear it for the "many eyes"! (Score:4, Insightful)

        by bnf ( 16861 ) on Saturday March 16, 2002 @06:54PM (#3175047) Homepage
        > The reason is simple : programming is hard, and it takes time. It's already hard to "enter" into someone else's code, it's even harder when you're doing it on your spare time, after a whole day's work, or only during week-ends.

        I agree that programming is hard, but harder still is leadership and community building, especially under the circumstances that open source projects operate. If you look at the early posts of Linus Torvalds anouncing linux you can see a flair for the dramatic. Mind you, it was a sexy problem set and he has technical ability, but his human skills had at least as much to do with the kernel's early success. He was interesting enough to provide support to, and was good about communicating his progress back to his audience.

        In a similar fasion, the KDE project as a whole has done an excellent job of community buiding by using kde.org to communicate with the wider community. I believe it's a better desktop overall, which certainly doesn't hurt, but there's a buzz about KDE which shows up in the website and other outlets and I feel like I hear about its progress frequently. This buzz is driven by the developer community which works on KDE.

        Getting developers to work in a community fassion is more difficult than setting up a mailing list and a cvs tree and hacking away. There's a certain amount of PR stuff and one-on-one engagement that needs to occur in order to draw new talent into a project.

        bnf
      • The reason is simple : programming is hard

        But according to your evidence, programming was hard in C, but not in LISP (or presumably an equivalently high level language), so this is not the right conclusion to draw.

        Interesting to speculate whether a significant fraction of the Open Source community will realize that they need abstract, portable, high-level languages before Dotnet takes the mind-share.

        Good luck with RoseGarden - I have heard of it, and even played with it! If it was written in Python/LISP/Java I might have got deeper.

  • Too hard to get started (Score:5, Insightful)

    by SurfsUp ( 11523 ) on Saturday March 16, 2002 @06:19PM (#3174924)
    "In this interview with the KOffice development team it is revealed that only about 4-6 people are working on the suite of applications.

    Yes, well I know exactly why that is. A few years ago I decided to hack kmail a little, until I found I had to build pretty much all of kde from source to do it. As opposed to installing the -devel headers as you would for more developer-friendly applications, then just untarring, ./configure, make. This stopped me, I see no reason why it wouldn't stop lots of folks.

    Casual hacking is the way to get started on a project, it's wrong to require a whole huge cvs import and hours of mucking around with scripts trying to get the thing to build. Once you start with the casual hacking and submit a few patches, it's much easier to justify the effort to get in all the way and sync up to cvs.

    If the koffice team wants more helpers, then they should put the effort into making it easier to get started. That means writing some scripts to pull tarballs out of cvs and hacking together some autoconf stuff. This effort will for sure pay off. People will start sending patches, and after a while some of them will get involved in a more hardcore way.

    Look, why are the 1,000's of people hacking the Linux kernel tree? Because you can just grab the tarball and build it, no fuss no muss. Only super-hardcore developers or paid employees are going to get into a project by syncing to the cvs from the word go.

    David, bless him, didn't get this 3 years ago, I hope he'll think about it now.
  • The article incorrectly stated that Aethera was not being worked on, and that the last beta was in april of 2001; in fact, there have been at least two betas that I know of, just in 2002. And Kivio is not only being worked on but is supported under windows as well, in the commercial version.
  • 4-6 developers for such a large project is a very small team. However, when tasks are defined well and goals are set with care, you can do a lot with 4 to 6 people. However, after reading the interview, I got the feeling that KOffice is currently being worked over by some demosceners without any big plan nor well defined tasklist. How can they expect people to jump in when the team itself doesn't sound very solid? (For contrast: in the teams I've worked in in the last 10 years, things were planned, done for a reason, people worked on stuff that they knew was filling in the blanks of the total project. This is IMHO not the case with KOffice. Very sad because I don't think that all this effort these programmers are putting in is paying off in the end.)

Slashdot Top Deals

Outside of a dog, a book is man's best friend. Inside of a dog, it is too dark to read.

Close