Hi Tim, well, yes and no. there are simple things that can be decided by one man. and the template engine is one of those, plus other small things. but when it comes to deciding the namespaces or the overall db desing or the architecture, well this is - at least as i think it - collegial decision.
gj. Tim Schofield wrote: > Hi Gjergj, > > I wasn't thinking of a one man development team, but one man leading it. > My experience in open source projects is that when you have a community > discussion you get a wide variety of ideas. Often complete opposites. > Try starting a discussion on what templating engine should be used. You > will get several ideas from different people each with their loyalty to > a particular one. And some who will advocate not using one. > > This isn't a bad thing, but if you wait for a consensus to evolve you > will wait a long time. At some point somebody has to take these ideas, > listen to them but then take a decision. > > Tim > > > Gjergj Sheldija wrote: > >> Hi Tim, Mark, >> >> you have grasped exactly my ideas. >> i'd like to point something here. although the one-man-dictatorship >> concept my produce more uniform code, it's only - in my opinion - >> suitable for small things - cms and such. >> when you start to think on all the requirements a functional >> his system has - as Mark points out - then the one-man idea start >> to loose it's attraction. not because of the lack of desire to create >> something practical and functional, but for the nature of healthcare in >> general. as a simple example the way acl's work in a healthcare environment >> is no more 2 dimensional ( role - resource ) it becomes 3 dimensional >> ( role - resource - hierarchy position ). >> >> so my proposal is simple, we have to change the way c2x is developed, >> and i think everyone agrees here. >> we have to broaden the developers access, we need a stable group that drives >> the developing process composed by programmers, doctors, and healthcare >> experts. >> and we should start thinking of it now. >> >> gj. >> >> ------------------------------------------------------------------------------ >> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) >> software. With Adobe AIR, Ajax developers can use existing skills and code to >> build responsive, highly engaging applications that combine the power of >> local >> resources and data with the reach of the web. Download the Adobe AIR SDK and >> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com >> _______________________________________________ >> Care2002-developers mailing list >> Care2002-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/care2002-developers >> > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Care2002-developers mailing list > Care2002-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/care2002-developers > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
