From: Jane Vinet <jvinet@linuxcare.com>
To: R P Herrold <herrold@owlriver.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: Administrivia and a question was: [parisc-linux] Question for theFaq
Date: Sat, 20 Jan 2001 10:46:11 -0500 [thread overview]
Message-ID: <3A69B2C3.86F207FC@linuxcare.com> (raw)
In-Reply-To: Pine.LNX.4.30.0101200918470.28153-100000@swampfox.owlriver.com
Thanks Russ for your comments, I will try to have these issues addressed
this week.
Jane
R P Herrold wrote:
>
> On Sat, 20 Jan 2001, Phillip D. Beal wrote:
>
> > I thought I'd post this to be added to the faq, as I was stumped on this
> > problem for a while, and I think some people might hit the same problem.
>
> <snip good 'hint and kink type' contribution>
>
> 1. The submission got me thinking. I just examined
> http://parisc-linux.org/faq.html --- and there is no listing
> of a formal role-address for an 'editor' of FAQ content. So
> it will probably be lost in the essectially unsearchable
> archive at:
> http://puffin.external.hp.com/mailing-lists/parisc-linux/
>
> 2, I was going to address the question of who is responsible
> for making sure these gems to not get lost to the
> administratative contact on the mailing list, so I checked
> http://parisc-linux.org/lists.html -- no mention of the
> role-address for parisc-linux-owner@thepuffingroup.com or
> owner-parisc-linux@thepuffingroup.com.
>
> Of course the first entry on that page, for the announce
> archive is a dead link ...
> http://parisc.thepuffingroup.com/mailing-lists/parisc-linux-announce
>
> 3. So I checked the mailer headers -- nope- the list
> namagement headers are not there, of this sort from another
> list:
>
> List-Help: <http://www.suncoastlug.org/lists.html>
> List-Unsubscribe:
> <mailto:majordomo@owlriver.com?body=unsubscribe%20slug>
> List-Subscribe:
> <mailto:majordomo@owlriver.com?body=subscribe%20slug%20YourName>
> List-Owner: <mailto:owner-slug@owlriver.com> (Human contact
> for the list)
> List-Post: <mailto:slug@owlriver.com>
> Sender: owner-slug@owlriver.com
>
> Nope, no help there.
>
> 4. In getting to the project webpages, I pasted
> parisc-linux-owner@thepuffingroup.com, and editted that down
> to www.thepuffingroup.com -- which went through two redirects
> to get to: http://parisc-linux.org/
>
> A one line trailer might be useful:
>
> See the website: http://parisc-linux.org/
>
> -------------------------------
>
> I don't see problems so much as too much work for too few
> hands, resulting in the technical side getting done first (as
> it must be a priority, lest the project be Yet Anither Dead
> Open Source Project [tm]). Pollyanna would say they were
> 'opportunities'.
>
> I can file a good bug report describing what I see -- I can
> follow documentation with the best of them -- I stand in awe
> of Alex, Grant and the rest of the coding team on the depth of
> their knowledge in getting the port up and running.
>
> So my question is: How may one contribute at an editorial and
> project infrastructure level? I wish to do so, and bet others
> on the list do too.
>
> -- Russ Herrold
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
--
Jane Vinet, Director Professional Services/Canadian Operations
Linuxcare, Inc. 613.562.9260 (tel), 613.562.9700 fax
jvinet@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Support for the Revolution
next prev parent reply other threads:[~2001-01-20 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 13:26 [parisc-linux] Question for the Faq Phillip D. Beal
2001-01-20 14:39 ` Administrivia and a question was: " R P Herrold
2001-01-20 15:46 ` Jane Vinet [this message]
2001-01-20 19:52 ` Administrivia and a question Grant Grundler
2001-01-20 20:46 ` Administrivia and a question was: [parisc-linux] Question for the Faq Matt Taggart
2001-01-20 21:03 ` Matt Taggart
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=3A69B2C3.86F207FC@linuxcare.com \
--to=jvinet@linuxcare.com \
--cc=herrold@owlriver.com \
--cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox