From: Jody <jbruchon@nc.rr.com>
To: alriddoch@users.sourceforge.net
Cc: Linux-8086 <linux-8086@vger.kernel.org>,
harkal@users.sourceforge.net, miguelb@users.sourceforge.net,
pnasrat@users.sourceforge.net
Subject: ELKS Website Maintenance Volunteer
Date: Mon, 01 May 2006 21:58:31 -0400 [thread overview]
Message-ID: <4456BCC7.4010004@nc.rr.com> (raw)
Greetings to all who do not know of me yet. My name is Jody Bruchon,
and I would like to take on the task of maintaining the ELKS project
website and related documentation. While I can't bring C programming
skills to the table, I can certainly manage a website and assist with
documentation. Since there is no one beating the door down to do this
work (for the past three years or so, in fact) I would like to take the
first step.
I have CC'ed this message to the SF mail addresses of the admins because
I am not certain as to whether they read the Linux-8086 list any longer.
If an admin is needed that has more spare time to maintain the entire
project, I am willing to do that as well. Despite the fact that I was
not knowledgeable enough in C to render Lynx even buildable on ELKS, I
have many other areas in which I am more skilled and can be a contributor.
My user name on SourceForge is "megamanidx" (I made it up eleven years
ago, don't ask). If I can take on any of the previously mentioned
duties, please let me know. Due to the unfortunate demise of Riley
Williams, who appeared to be the last active contributor to the project,
we have a flag lying on the ground, and I'd like to see that picked back up.
Sincerely,
Jody Bruchon
next reply other threads:[~2006-05-02 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 1:58 Jody [this message]
2006-05-02 7:57 ` ELKS Website Maintenance Volunteer Hans
2006-05-02 17:56 ` pfengland
2006-05-02 19:54 ` Segin
[not found] ` <4b05edd10605021701k7babdf45x87d1797875c0f1ba@mail.gmail.com>
2006-05-03 1:49 ` Segin
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=4456BCC7.4010004@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=alriddoch@users.sourceforge.net \
--cc=harkal@users.sourceforge.net \
--cc=linux-8086@vger.kernel.org \
--cc=miguelb@users.sourceforge.net \
--cc=pnasrat@users.sourceforge.net \
/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.