Re: [clc-devel] New CRUX/CLC website
--- Johannes Winkelmann <jw@tks6.net> wrote:
Hey,
Hi all,
some time ago I offered to help with the crux/clc website merge, I drop you some proposal/idea in case we're going to start to work on the project during the following weeks.
I've been evaluating some wiki package during the last days and my preference goes to wikka wiki:
http://wikka.jsnx.com/TestSkin I used wikka before, and it would certainly be a good wiki for our
On Thu, Mar 31, 2005 at 19:47:39 +0200, Simone Rota wrote: purpose. I also set up a MediaWiki (the thing befind Wikipedia) which was very simple, too (didn't look into ACLs and the like, though).
In my opinion with something like Wikka we could manage the entire CRUX/CLC website in a collaborative manner, and use cvstrac only as a bug tracker. Agreed. I'd also like to see subprojects appearing there, like amd64, or the mono ports if those guys manage to form a group :-)
Apart from the choice of software, we cannot really start something without some knowledge about the physical location of the site. Jay mentioned on IRC that he might help us here, since he has some connections to a local university (I hope I remember that correctly). Jay, can you elaborate on this?
Sure. I'm 90% confident that it would not be a problem at all for me to drop a box on UMass Dartmouth's T1. I can also probably convince my boss to donate some older hardware (something like a P3 700, 256MB) to the project. I live about 10 minutes from the university, and am still in contact with several of my professors. So handling hardware malfunctions in a timely manner wouldn't be terribly difficult. It would be completely free. The only problems we'd have to deal with would be power outages, etc..maybe twice a year. What I'd like to do, if we persue this, is get the machine up and running and drop it on the line. Then give root to those of you who require it (jw, jaeger, pli, sip..). You guys could then work your magic and get whatever else the box needs installed and running. I started thinking of this idea back at CruxCon, when we spoke of merging the CLC/Crux.nu websites. To me, it only makes sense that we'd be better off with our very own box..rather than dealing with someone else's hosting policies. Just an idea. Let me know if you wish for me to persue it further. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. http://www.advision.webevents.yahoo.com/emoticontest
Hi, On Tue, Apr 05, 2005 at 07:08:17 -0700, Jay Dolan wrote:
--- Johannes Winkelmann <jw@tks6.net> wrote:
[...]
Jay mentioned on IRC that he might help us here, since he has some connections to a local university (I hope I remember that correctly). Jay, can you elaborate on this?
Sure. I'm 90% confident that it would not be a problem at all for me to drop a box on UMass Dartmouth's T1. I can also probably convince my boss to donate some older hardware (something like a P3 700, 256MB) to the project. I live about 10 minutes from the university, and am still in contact with several of my professors. So handling hardware malfunctions in a timely manner wouldn't be terribly difficult. It would be completely free. The only problems we'd have to deal with would be power outages, etc..maybe twice a year. This sounds great; maybe we can collect some money for additional RAM and a RAID setup. WRT to power outages, we should work out a concept for mirroring, maybe even with ports(8) supporting a fallback-server; I don't mind when development stops for a few days, what matters more is that users can get the ports from somewhere.
Otherwise, I really like the plan. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
On Tue, 2005-04-05 at 16:39 +0200, Johannes Winkelmann wrote:
This sounds great; maybe we can collect some money for additional RAM and a RAID setup. WRT to power outages, we should work out a concept for mirroring, maybe even with ports(8) supporting a fallback-server; I don't mind when development stops for a few days, what matters more is that users can get the ports from somewhere.
I like this idea and will be happy to donate some money for hardware upgrades if needed; especially since morpheus.net may be moving soon, to a colocation facility in dallas, which is 4 hours south from me. That's not so much a problem since I do go down there every now and then and my co-admin lives there. What *might* be a problem is that we WILL have a bandwidth limit if we host the server there. I don't know the details on the colocation plan yet and it's not set in stone... but as I said when we moved clc to morpheus.net, it might not be a permanent solution. Not that I'm against hosting it, it just seems like Jay's solution is a better one in this case. </ramble> Matt (jaeger@freenode/#crux)
On 04/05/05 16:56 Matt Housh wrote:
This sounds great; maybe we can collect some money for additional RAM and a RAID setup.
I like this idea and will be happy to donate some money for hardware upgrades if needed; especially since morpheus.net may be moving soon, to a colocation facility in dallas, which is 4 hours south from me. That's not so much a problem since I do go down there every now and then and my co-admin lives there. What *might* be a problem is that we WILL have a bandwidth limit if we host the server there. I don't know the details on the colocation plan yet and it's not set in stone... but as I said when we moved clc to morpheus.net, it might not be a permanent solution. Not that I'm against hosting it, it just seems like Jay's solution is a better one in this case.
Well, I suggested using a 3rd party host for avoiding the hassle of the maintainance of another service, but I like the idea of a clc machine as well. Count me on for some financial contribution. Since we're on topic, I suggest also to dedicate a domain or subdomain for the machine in question (if possible), so next time we move the users won't be left alone in the cold :) Better again, using different subdomains (pointing to the same machine for now) such as ports.crux.nu, dev.crux.nu, etc would facilitate eventual future re-locations or addition of other machines. P.S. I don't remember what were Per's plan regarding the crux.nu domain and if we'd have to register a new one. Regards -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com
participants (4)
-
Jay Dolan -
Johannes Winkelmann -
Matt Housh -
Simone Rota