From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by oss.sgi.com id ; Sat, 1 Jul 2000 16:23:04 -0700 Received: from chmls05.mediaone.net ([24.147.1.143]:30145 "EHLO chmls05.mediaone.net") by oss.sgi.com with ESMTP id ; Sat, 1 Jul 2000 16:22:44 -0700 Received: from decoy (h00a0cc39f081.ne.mediaone.net [24.218.252.183]) by chmls05.mediaone.net (8.8.7/8.8.7) with SMTP id TAA23300; Sat, 1 Jul 2000 19:22:11 -0400 (EDT) Message-ID: <0c0801bfe3b3$62fde200$0a00000a@decoy> From: "Jay Carlson" To: "Ian Chilton" , "Linux-Mips Mailing List \(Old\)" , "Linux-MIPS Mailing List" , , , "Jay Carlson" , "Ralf" References: Subject: Re: Status reports? Date: Sat, 1 Jul 2000 19:23:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-mips-outgoing "Ian Chilton" writes: > * Not everything that happens on IRC is appropriate for the mailing list, > otherwise it would be a very high volume list. Yeah. > * The problem is, most of the people on the port and in #mipslinux are > developers, who are working on the ports, but have no time for > documentation. Which is best, a port that is dead with loads of > documentation, or an active / up-to-date / working port with little > documentation. There's a need for high quality documentation, but I think there's a greater need for just little status reports. Writing good documents is *hard*, but just little one-paragraph summaries, like a project diary, would be a wonderful service to the community. OTOH, although the current situation annoys me a little, it would annoy me a lot more if upstream work on mipslinux stopped. :-) So please don't take anything this list says about this as a demand. > I agree that the documentation is sparce, and see the above issues. That is > why, I am *thinking* of and suggesting to some of the guys that I, at least > for now, maintain a site with > * News from #mipslinux > * Links to current resources > * Possibly some documentation Doesn't have to be very heavyweight to be successful. > If you have any chance at all, I suggest you stop by #mipslinux at > times....all you need is an internet connection and one of the many IRC > clients... > > Details are: > /server irc.openprojects.net (port 6667) > /join #mipslinux I'll drop by soon. Jay From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <0c0801bfe3b3$62fde200$0a00000a@decoy> From: "Jay Carlson" References: Subject: Re: Status reports? Date: Sat, 1 Jul 2000 19:23:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-linux-mips@oss.sgi.com Return-Path: To: Ian Chilton , "Linux-Mips Mailing List (Old)" , Linux-MIPS Mailing List , richardh@penguin.nl, watkinse@attens.com, Jay Carlson , Ralf Message-ID: <20000701232318.RGwvMRKEigXfY-_WdUy3t5f1g6A9fBoEFD5ImiuWo3g@z> "Ian Chilton" writes: > * Not everything that happens on IRC is appropriate for the mailing list, > otherwise it would be a very high volume list. Yeah. > * The problem is, most of the people on the port and in #mipslinux are > developers, who are working on the ports, but have no time for > documentation. Which is best, a port that is dead with loads of > documentation, or an active / up-to-date / working port with little > documentation. There's a need for high quality documentation, but I think there's a greater need for just little status reports. Writing good documents is *hard*, but just little one-paragraph summaries, like a project diary, would be a wonderful service to the community. OTOH, although the current situation annoys me a little, it would annoy me a lot more if upstream work on mipslinux stopped. :-) So please don't take anything this list says about this as a demand. > I agree that the documentation is sparce, and see the above issues. That is > why, I am *thinking* of and suggesting to some of the guys that I, at least > for now, maintain a site with > * News from #mipslinux > * Links to current resources > * Possibly some documentation Doesn't have to be very heavyweight to be successful. > If you have any chance at all, I suggest you stop by #mipslinux at > times....all you need is an internet connection and one of the many IRC > clients... > > Details are: > /server irc.openprojects.net (port 6667) > /join #mipslinux I'll drop by soon. Jay