From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by oss.sgi.com id ; Tue, 4 Jul 2000 11:22:55 -0700 Received: from mx1.hcvlny.cv.net ([167.206.112.76]:45777 "EHLO mx1.hcvlny.cv.net") by oss.sgi.com with ESMTP id ; Tue, 4 Jul 2000 11:22:30 -0700 Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.9.3/8.9.3) with ESMTP id OAA09010; Tue, 4 Jul 2000 14:22:00 -0400 (EDT) Received: from hel-inc.com (d150-198.hmtmnj.optonline.net [24.189.150.198]) by s1.optonline.net (8.9.1/8.9.3) with ESMTP id OAA27633; Tue, 4 Jul 2000 14:21:38 -0400 (EDT) Message-ID: <39622B31.23124622@hel-inc.com> Date: Tue, 04 Jul 2000 14:21:37 -0400 From: Robert Current X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.16-9mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Jay Carlson CC: Ian Chilton , "Linux-Mips Mailing List (Old)" , Linux-MIPS Mailing List , richardh@penguin.nl, watkinse@attens.com, Jay Carlson , Ralf Subject: Re: Status reports? References: <0c0801bfe3b3$62fde200$0a00000a@decoy> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-mips@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-mips-outgoing http://www.acheron-design.com/windowmaker.org-new/ <--that's the kind of thing I was thinking largo could do for ya, just set it up, and let you guys update it via web/php admin... So you have a good idea what he can do... http://www.acheron-design.com/leninmaker/ <--joke windowmaker one. http://wm.current.nu/ his site. If you want him to do a layout for the linux-mips page, just let me or him (largo@current.nu) know, and we can get it set up (layout and graphics), and all you will have to do is provide some content and update the news and such through web interface. Jay Carlson wrote: > > "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