From: Geoff S. <ge...@ho...> - 2002-12-28 19:28:48
|
I disagree with part of your analysis. For the module to become part of the distro, the in-house developer needs take over the module. If the original developer wants to help, that is great. But, if the outside developer disappears or gets hit by a truck, the maintenance would revert to the in-house developer. Also, if the module becomes part of the distribution, then the in-house developer is de facto responsible for it even if the original developer is still involved. The in-house developer takes on responsibility to insure that the module: 1. Continues to reflect architecture and coding standards. 2. Maintains consistent user interface. 3. Enhancements meet the approval of the in-house team. Seems to me there ought to be three levels of module: 1. Those developed in-house or "taken over" as part of the distro. 2. Those that meet a certification standard and are considered "official" modules developed by a third-party. 3. Those that work with phpWebsite but which have not been reviewed and approved. Geoff www.hostricity.com At 01:46 PM 12/28/2002 -0500, Matthew McNaney wrote: >This is not in direct response to Eloi's new module (good job btw) but >just a question that needs consideration for the future. > >Suppose someone creates a better content module than one produced >in-house. I know that many of the developers here have several things >going on at one time (I can think of two huge ones off the top of my >head). Perhaps, if an outside developer is willing, we could ask if they >would like their module to become part of our distro. > >Here is the rub though. >- We would all need to agree it should be done. >- The in house developer would need to agree >- The outside developer would have to guarantee support. > >Again, this may not come up, but I know that there are some modules we are >working on that might have a more dedicated developer outside the >unversity. > >Please discuss with pros and cons for both sides. > >Matt >-- >Matthew McNaney >Internet Systems Architect >Electronic Student Services >Appalachian State University >Phone: 828-262-6493 >phpwebsite.appstate.edu >ess.appstate.edu > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Phpwebsite-developers mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |