> There's a huge amount you can contribute to this effort I'm sure. All it > needs is people like you on board!
Thank you for your nice compliments. I wouldn't speak so quickly, though. You haven't yet experienced how opinionated I really am. ;-) > How does that sit with you? I think you have many great ideas. My main worry is that my "vision" is just too different, and I would likely cause more friction and discordance than actually help the process. I suppose that I am one of those people best suited for new projects rather than joining in projects well under way. Also, although I have a technical background and recently have been doing almost 100% development, my main experience is more on the business side of things. To be blunt, the business approach is very different and so incompatible with the scientific/engineering mindset that it is very rare that tekkies can successfully cross over. For instance, thinking logically, which comes oh, so naturally for us programmers, can actually do more harm than good when dealing with people and customers. I now accept this as "fact" though I often have trouble acting accordingly. I say all this because I think that my way of doing things is just too different from what would be accepted by Cocoon members. Cocoon is an organisation made by tekkies, for tekkies. The reason I think that your suggested approach is faulty is because it's starting from what we already have. Well, what we already have has mostly been developer-centric. Rather, we need to be more user-centric. The process should be starting off with "who is the user and what does he/she/it want/need to know?" As a concrete example, I think that we can do away with (completely or almost completely) the "history" section. Is this useful for understanding Cocoon, evaluating if it's worth the risk for me (assuming we're dealing with a business, which I assume most users are) to invest my company's time? Does this help me to get up and running? Does this answer the concerns I have about how using Cocoon will affect my business? The answer is "no". So the action should be "delete". See now why I would just cause more debate than help move the project along? Anyway, if you still want to hear about what I think, perhaps I could make a separate wiki that gives a bit of an idea of my vision. The best that could happen is you'll see some things you like and we'll be able to find a good compromise. The worst that could happen is that you can decide that you don't like my approach and politely tell me to bugger off. ;-) WDYT? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
