DragonFly kernel List (threaded) for 2004-02
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: time to kill
[posted and mailed]
"R. E. Ceiver" <lists@xxxxxxxxxxxxxxx> wrote in
news:40258068.3020701@xxxxxxxxxxxxxxx:
> should you need anybody for non-coding stuff at the moment; - i got a
> bit of time to kill. drop me a mail.
Things that could be done:
1: A indepth writeup of the installation process:
- From FreeBSD 4.x to DragonFly
- From the live CD (onto a system with IDE)
- From the live CD (onto a system with SCSI)
- Upgrading via cvsup, rsync
2: If you have layout experience, a "look" for the DragonFly website is
always fun. Come up with several, if for no other reason than to get
comments going.
3: How To: (for publishing on the site)
- Contribute code
- Contribute web site changes
- Provide a good bug report (what debug settings to have in the
kernel, what info to look up when there's a crash, etc.)
4: Provide port overrides
- Install various ports, and if they don't work, fiddle with them
until they do and submit a port override. Or at least point it out
so someone else can look at fixing it. - Write up how to create
a
port override.
5: Set up a third-party site. Something like FreshPorts, or, more
appropriate at this time, something like the "FreshSource" concept
( http://www.freshports.org/ http://www.freshsource.org/ )
6: The Easy Thing: keep an eye on these DragonFly discussion groups.
After a few months of reading them, you'll know the answers for other
folks that haven't been reading them as long. You'll also probably
learn a lot as people talk about their projects, or at least that's been
my experience.
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]