Re: [argouml-dev] Thinking about the big picture.

[Tony | "Zearin"]

Hello! Linus Tolke wrote: You are right Tony, of course this is the way it is and the problems we are facing and over the past years several people has expressed similar concerns. The main question for me is, how do we fix it? What shall I do? What shall we do? I have not yet a solution to this. We need suggestions of concrete things to do. Things suggested before I have either not understood or thought too vague to be implementable. Yep—it's definitely a tall order. But ignoring an illness even as the symptoms worsen and spread does not help cure it in any way. :( Let me highlight this bit: I have not yet a solution to this. We need suggestions of concrete things to do. Things suggested before I have either not understood or thought too vague to be implementable. Agreed. But rather than jumping directly to this, I think a very important step is to ask the right questions. Asking, “What shall I do? What shall we do?” are big questions that are hard to answer. By breaking this big question into smaller questions—or asking the same big questions from a specific angle—it's easier for more people to participate, because it's easier to answer specific bits like that. To that end, let me start off with these: What are the most painful parts of the development process? What tools are you currently using that are frustrating/painful/tedious? Are there any “bad habits” or recurring problems in the dev process? (This could be problems with the system or “bad habits” of people themselves. I'm talking about the stuff that's been around so long you put up with it because it feels like it's always been that way. But truly, it doesn't have to be!) What are the weak spots in our developer community? (I.E., do we have a very small number of people familiar with component X, even though X really needs work?) What are open source communities (like Inkscape) doing that we are not? From John Daigle's e-mail (some paraphrased): Is it time to start over with new requirements and architecture? If people CAN create a feature without having it implement undo, is that an indication that the object model is flawed? Could it be that solving that problem in a way that insures new features implement Undo means changing how new features are added? What are the missing/incomplete features of ArgoUML that could be obtained from other Open Source projects? And last, but not least: What makes development fun? —Tony --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]