hi, i have the fear that this topic is turning into a bikeshed discussion. a decision has already been made and been stalled by the difficulty of creating an appliance to implement it.
so maybe this decision needs to be revisited. but since the problem does not seem to be to decide which tool to use, but rather to actually implement it, i'd like to propose that anyone who favours a certain solution, back it up by implementing an appliance with that solution and start building a site with it. then contributors can vote with their feet and pick the site they feel most comfortable to work with. once we have a few sites running we can revisit and see which solution has the most potential. we will not get a new site until someone makes an effort to get one running. if only one person makes an effort that site wins by default like paul says. until someone else makes an effort to replace it with something even better. if multiple efforts start at the same time then we get to choose. until then the discussion is just academic. start your sites, and let us see some actual solutions. may the best one win. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix offering: programming, training and administration - anywhere in the world -- pike programmer working in china community.gotpike.org unix system- iaeste.(tuwien.ac|or).at open-steam.org administrator caudium.org is.schon.org Martin Bähr http://www.iaeste.or.at/~mbaehr/ _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
