On Tue, Jan 04, 2011 at 11:47:22AM -0700, Stephen John Smoogen wrote: > Ok when testing a project it is important to update the /etc/motd file > with the following information: > > [fas username] - [date started] [date updated] > project title - project summary > directories/areas looked at. > > Example: > Project Owner: smooge - Started: 2010-12-31 Updated: 2010-01-30 > gnusong - a project to digitize the reading of all source code to a dance beat. > /usr/local/bin, /srv/web/songs > > 1) Systems that DO NOT have updated motd's will be wiped, reinstalled > to a fresh state and turned off until an RFR is needed for it. Systems > whose last update was over 90 days will also be subject to > wiping/reinstall/turn off. > > 2) publictest systems are NOT backed up. they are test/scratch systems > that are meant for eventual integration with some sort of > development/staging infrastructure. > 3) due to communal nature of systems, people need to work together on > them to make sure they are not overwriting and beating each other up. I updated the appropriate wiki page (I hope) with Insight info: https://fedoraproject.org/wiki/Infrastructure/Server/publictest04 -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
