From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Hardware wiki
Date: Fri, 03 Feb 2012 17:20:43 +0100 [thread overview]
Message-ID: <1328286043.3694.44.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4F2BB6B5.1050604@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
Hey Daniel,
On Fri, 2012-02-03 at 11:28 +0100, Daniel Weismüller wrote:
> Hello
>
> I'm thinking about to rework our hardware wiki.
Just because I am curious: What is wrong with the way it is now?
> In that case i want to write a few reviews about hardware such as
> motherboards, cases, all-in-one-systems (like the fit-pc2 or Dreamplug) etc.
>
> The general informations an the entrance-site are quite good but not
> actual enough I think so I'll spent some time on it, too.
Fair enough, so reorganizing the start page would be where to begin?
I am missing fireinfo at this place. Can we add this too?
>
> On the top of the entrance-site we find already two reviews. Instead of
> them I'll create a subitem and will move them into it.
> Future review will be part of the subitem.
>
> Of course there won't be a review of every peace of hardware on the market.
> I'll only want to discribe some usual hardware and their possibilities
> for what it may used.
I think there are two ways how to design this section. You could either
start explaining to the user what kind of NICs there are (active and
passive ones) and add the vendors to those groups. This is a very user
friendly solution and I could think of some information about wireless
hardware, too. But for developers or a simple table in the way there is
at the moment would be sufficient.
You want to take the user-friendly version, right?
>
> Some examples systems I want to reviews about are:
> an ALIX;
> a single core Atom,
> a dual core Atom,
> a Via C7,
> a Transmeta TM5800 (800 Mhz)
> an ARM
An important thing to add would be the year of the review. Opinions
change and as the market is evolving that fast, there might be a much
superior and cheaper solution. The Little Falls II review I have written
is pretty old and the new generation of Atom-based boards consumes much
less power.
Maybe a monthly updated matrix could help deciding what one would need?
Like making 3 to 4 examples for a to b users and compare them? I guess
you already have such a thing in mind.
>
> Supplements and opinions are highly appreciated...
That were my ideas.
Who should work on this?
- Michael
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2012-02-03 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 10:28 Daniel Weismüller
2012-02-03 16:20 ` Michael Tremer [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=1328286043.3694.44.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.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