Hi Eiji, > 1. There is no BlueOnyx server placed in out of Europe, > at least in this maillinglist.
Hmm? http://www.blueonyx.it/pub/BlueOnyx/ <- USA http://devel.blueonyx.it/pub/BlueOnyx/ <- USA http://mirror.blueonyx.de/pub/BlueOnyx/ <- Germany http://mirror.blueonyx.it/pub/BlueOnyx/ <- Germany http://blueonyx.precisionweb.net/BlueOnyx/ <- USA http://bb-one.blueonyx.it/pub/BlueOnyx/ <- Germany http://www.blueonyx.nl/pub/BlueOnyx/ <- Netherlands So the main project site and main YUM repository are in the USA. Germany is a good choice for European mirrors, as it's smack in the middle of Europe and well connected. Sure, there is no mirror in Asia, but the project runs on sponsored servers. Or sponsor donated mirrors in half the cases. How to set up a mirror (and how to get it listed!) is explained here: http://devel.blueonyx.it/trac/ We'd love to have a mirror in Asia, too, but so far nobody came forward and offered one. > 2. The developers of BlueOnyx are not eager for fixing bug > in other than Europe. Not true. It's an open source project and all input is welcome. Including your suggested improvement ([BlueOnyx:03007]) which was posted not even five days ago. Hey, I wouldn't even rate it as a bug, as it's a non critical item that has no functional impact whatsoever and can easily be addressed from the command line by editing proftpd.conf and restarting Xinetd. You even quoted the link to the suggested fix. To incorporate that change in the distribution we'd need to recompile the Proftpd SRPM so that the default Proftpd has the suggested lines in it and we need to entirely rebuild the virtual host containers from scratch with a script to make sure that all the relevant sites don't loose their FTP functionality. We already did ProFTPd config changes in the past in a similar fashion and it is a bit intrusive and risky. Hence this change is laid off until the next scheduled ProFTPd update, when we upgrade ProFTPd to the very latest version. Which makes a lot more sense than re-releasing just a rebuilt ProFTPd of the same version that we're currently have in usage. Not even BlueQuartz has that "fix" yet. It was just discussed on the mailing list in March 2009 but nothing ever came off it. If it were something critical we would have been addressed ASAP, but please don't expect us to drop the ball and jump the gun just to make sure that a trivial configurational change is pushed out hell over heels. Right now there is a list of about 8-10 other tickets which are a trifle more critical and that probably will get fixed first. I don't say your input is of lesser value or less welcome - to the contrary! It's just that there are a handfull of more pressing items. But in due course your suggestion will also find it's way into BlueOnyx, too. > 3. The Team of BlueOnyx is a good friend in relatives, > but is not good for persons whom an opinion is different. > So, it is not OPEN, it might be CLOSED community. Sorry, but that is not true. Maybe your expectations are slightly off here. Commercial grade support and "open source project" are simply two different pairs of shoes. -- With best regards Michael Stauber _______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
