All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard <richardh@penguin.nl>
To: Eric Watkins <watkinse@attens.com>
Cc: Jay Carlson <nop@nop.com>, linux-mips@oss.sgi.com
Subject: Re: Status reports?
Date: Thu, 29 Jun 2000 18:29:18 +0200	[thread overview]
Message-ID: <395B795E.5CE23627@penguin.nl> (raw)
In-Reply-To: 001501bfe1e5$a86c6660$540ed7c0@hq.sd.cerf.net

>

Hi,

i've still got the linux-mips.org domain, but no time to build a website, if
someone builds the site, i'll be happy to put it up.

Richard

>
>
> I agree. I have a friend who lurks on this mailing list and he swears the
> port is dead.
>
> Having the only www page the port has have look 2 years old(the SGI one)
> looks really bad. People who obtain SGI boxes(like me) and want to do
> something linux, have to look really hard before they find anything new.
>
> This port needs some good docs and a good www page badly.
>
> IMHO of course. Nice to see I'm not the only one.
>
> > -----Original Message-----
> > From: owner-linux-mips@oss.sgi.com
> > [mailto:owner-linux-mips@oss.sgi.com]On Behalf Of Jay Carlson
> > Sent: Thursday, June 29, 2000 4:46 AM
> > To: Eric Watkins; linux-mips@oss.sgi.com
> > Subject: Re: Status reports?
> >
> >
> >  "Eric Watkins" <watkinse@attens.com> writes:
> >
> > [...]
> >
> > > I know lots of this information gets distributed via IRC but someone
> > should
> > > let everyone, who's not on IRC all the time, know what's going
> > on and what
> > > progress is being made.
> >
> > IMO this is a serious problem for many open source development projects
> > today.  Much of the interaction occurs in IRC or instant message
> > chats, and
> > not in email.  The people who are participating in the online chats have
> > much better coordination, but it ends up excluding a lot of people.  It's
> > not just people in the wrong timezone who lose out---projects
> > also lose the
> > potential effort of people who join the mailing list, see nothing
> > going on,
> > and don't get a chance to help.  I've found that even casual readers of a
> > mailing list can bring insight from other projects to bear on problems.
> >
> > Jay
> >
> >

  reply	other threads:[~2000-06-29 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-15 18:27 Status reports? Eric Watkins
2000-06-15 18:27 ` Eric Watkins
2000-06-29 11:46 ` Jay Carlson
2000-06-29 11:46   ` Jay Carlson
2000-06-29 16:18   ` Eric Watkins
2000-06-29 16:18     ` Eric Watkins
2000-06-29 16:29     ` Richard [this message]
2000-06-30  0:39       ` Ralf Baechle
2000-06-29 17:38   ` Ian Chilton
2000-06-29 17:38     ` Ian Chilton
2000-06-29 22:51     ` rob
2000-07-01 23:23     ` Jay Carlson
2000-07-01 23:23       ` Jay Carlson
2000-07-04 18:21       ` Robert Current

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=395B795E.5CE23627@penguin.nl \
    --to=richardh@penguin.nl \
    --cc=linux-mips@oss.sgi.com \
    --cc=nop@nop.com \
    --cc=watkinse@attens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.