Athar - In an ideal (read "paid") setting, your ideas may make sense.
However - Open Source is based on respect for your fellows; in this case, Stefano and his group (of which there have been many) have not only created an outstanding and extensible email server, they also provide some of the best support I have ever seen in an open-source project. If you want support for your own initiatives, you need to: #1 Understand the project already, at least a good amount of it #2 Show respect for the efforts already spent #3 Respectfully suggest some improvements #4 Display some expertise/leadership/knowledge that might rally support So far you've done the opposite on every point. This is basic open-source conduct - before you get involved in your first OS project, you should familiarize yourself with how they operate. It's not another day job. Google "open source conduct" to get an idea. Here's a nice example: http://krow.livejournal.com/594596.html Kent Butler -----Original Message----- From: Athar Shiraz Siddiqui [mailto:[EMAIL PROTECTED] Sent: Monday, May 05, 2008 3:01 PM To: James Users List Subject: Project Path : to do list > > I would like to start with documentation and arch. diagrams etc. > > That > > is critical to newcomers and fresh ideas and even updates, I feel. > > > > If you dont know the roadmap how will you get to where you want to go? > > We need some guy with project management background ; I can help with > > that if no one volunteers. > > > > No, we need people doing the work. You can't even imagine how many managers > we have here. But 100 managers do not dig a single hole in the ground. We need architecture related docs pronto; its the difference between reliable coding and hacks. If we have enough managers we ought to have such documentation by now and a methodology in place. Whoever these people are who cannot dig a hole in the ground are not really managers now are they? You could call them parasites but lets not even go there. I have my own prejudices and politics I would like your help in keeping that to the minimum and keeping my goals and productivity to the maximum so we can make using this software enjoyable for everyone. > We don't have a roadmap, currently. Lets begin with a simple to do list (pdf screen shot http://tech.groups.yahoo.com/group/apachejames/files/ it is the one titled pdf screen shot) from projectpath / basecamp? the full url to this is http://tech.groups.yahoo.com/group/apachejames/files/ We however definitely need docs and arch. for our own understanding. http://f1.grp.yahoofs.com/v1/IEsfSKfWuD6f0zvZPv2ax8pJDAZBlxkmS9al3FFaKSG g0Co7c4bn8CQEdQEYOYBNvK2KXi_sRo1Xym0eAhMRDw/Screenshot%201.pdf Thanks Ersoy for the link to the modeling tool. I have access to some of them in IBM Rational App Developer and recall using some of their primitive features. Though some intelligent software that auto documents would be cool. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
