Date: Tue, 25 Jul 2000 15:00:45 -0700 From: "Albert Yang" <albert@achtung.com> To: freebsd-small@FreeBSD.ORG Subject: Design Specs Message-ID: <397DAB9D.25342.FF18EE@localhost> In-Reply-To: <Pine.BSF.4.20.0007252252500.44508-100000@mx.webgiro.com> References: <20000725162648.A18036@mithrandr.moria.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I always like to have an agenda of what is going to happen before a meeting, so people can be kept accountable for schedules during that meeting; same I think goes for builds. I don't want Pico to be a trashcan, I want some design specs, what flavors will have what, what specific functions etc... Also, the "captain" need not be the best programmer or engineer, just the person who is willing to take charge and be the person who oversees the big picture. If that's Jeffrey, then I'm all for it. We need some order. Also, I think Makefile based is great. That way, we can test different builds, and archive builds as needed. picobsd.org, and picobsd.com has been taken. I tried in the past to purchase picobsd.com, but I don't remember why but Network solutions bombed out, and so I didn't get it. Someone later on took it. The register's name for picobsd.org and .com is TUCOWS, so I guess tucows bought it... It's OK, I think sticking with the main group is good. ~~~~~~~~~~~~~~~~~ I think we should try for modularity. I kind of agree, instead of having flavors, we can have modules, and you pick and choose what items you want, like a BSD Buffet. If you guys what references, http://www.achtung.com/smallwall.html That's my personal homepage, I try (although not very successful) to keep links on projects that are like PicoBSD. Small firewalls etc... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?397DAB9D.25342.FF18EE>