From: Royce Williams <royce@tycho.org>
To: Jody Bruchon <jody@jodybruchon.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Some questions on ELKS web sites
Date: Sun, 22 Mar 2015 07:38:36 -0800 [thread overview]
Message-ID: <CA+E3k91-xyLhoY9v=_YMEF14PWx0B1oO-p7vAsJJZ+WP6tZDyQ@mail.gmail.com> (raw)
In-Reply-To: <550EE05D.9020706@jodybruchon.com>
On Sun, Mar 22, 2015 at 7:31 AM, Jody Bruchon <jody@jodybruchon.com> wrote:
> On 3/22/2015 8:20 AM, MFLD wrote:
>>
>> Then, I would ask maybe a FAQ : what is the ELKS official web site today
>> ? I see mainly a SourceForge page (http://elks.sourceforge.net/) and a
>> GitHub page (https://github.com/jbruchon/elks). What is the right one ?
>
> The GitHub page is the current official site. I haven't touched SourceForge
> in aeons. The old site is mainly there for historical purposes; I've decided
> that until ELKS is a little further along in development, there's no point
> in trying to maintain an informational website for it. The info should be in
> the ELKS documentation/README first and on a website second.
Reasonable. I recommend quickly archiving most of the top-level
SourceForge page 'News' items on the top page into a /news/
subdirectory page, and replace it with a brief announcement of what
you've said above (with a link to GitHub) - and make this the
main/only content of that top-level page.
For just a few minutes' worth of work, all future searchers get a
clear idea of what's going on (and contributors can find their way to
us more quickly).
> I'd like to see some Ethernet card support in ELKS and that's where I
> personally draw the line; these days, everything is "connected" and SLIP is
> difficult to set up and requires a second computer. Everything in ELKS is
> designed solely to use SLIP and the ktcp program. Once we can connect to the
> Internet properly, we can port or write a text-mode web browser. I think
> that's when it will become more interesting to people in general and will
> justify having a new website.
That sounds awesome.
Royce
prev parent reply other threads:[~2015-03-22 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550EB2A1.5050706@gmail.com>
2015-03-22 12:20 ` Some questions on ELKS web sites MFLD
2015-03-22 15:31 ` Jody Bruchon
2015-03-22 15:38 ` Royce Williams [this message]
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='CA+E3k91-xyLhoY9v=_YMEF14PWx0B1oO-p7vAsJJZ+WP6tZDyQ@mail.gmail.com' \
--to=royce@tycho.org \
--cc=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).