From: WhyTea <whytea@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Transmission wiki
Date: Tue, 17 Jan 2012 17:53:48 +0100 [thread overview]
Message-ID: <4F15A79C.6040902@ipfire.org> (raw)
In-Reply-To: <1326817785.2165.30.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
Hi Michael,
if you think we don't need the disclaimer delete it. ;)
In my opinion it is easier to use/read if in every wiki the installation
part is included.
I don't like inkomplete wikis so I've to read several wikis if I want to
install one thing.
I will reduce the screenshots in size and colordeph so the loadtime will
get better.
Daniel
Am 17.01.2012 17:29, schrieb Michael Tremer:
> Hello,
>
> my advice for faster way of fixing mistakes:
> Choose a language to start with (this is preferably English) and
> then write the article. Create an outline, write chapters, add
> screenshots...
> Get as much feedback as you can get. Do the guide by the shown
> steps and check for errors. THEN translate.
>
> It's just easier if you don't need to fix minor issues in multiple
> versions.
>
> ----
>
> On the text itself. You guys need to fix the screenshot sizes. The page
> loads a while and the screenshots are that huge that you cannot tell
> where text is and where just crap is. Crop the stuff that does not
> matter (e.g. services screenshot) and use thumbnails.
>
> I would like to see the user pointed on how to create a samba share (bit
> more detailed though). You mentioned WinSCP which is specific to Windows
> and not very comfortable to use. Not sure if that is an option for
> anybody.
>
> I think we do not need the disclaimer. In our law, even ping, telnet and
> nmap are illegal tools and it's up to the user what he is going to do
> with transmission. Bittorrent by itself is not illegal.
>
> Furthermore, why do we have a huge "installation section" on every
> article? It is always the same. Why not create a very detailed guide and
> always refer to it and tell the names of the packages to install?
>
> Altogether the article is quite nice and to the point. One could collect
> some links to the official transmission documentation for further
> reading.
>
> -Michael
>
> On Tue, 2012-01-17 at 13:39 +0100, Florian Ortmann wrote:
>> Hi Erik,
>> currently I've a little problem. My Fire doesn't at the moment and
>> I've no time to fix it. So it would be nice if someone other could
>> make a picture.
>>
>>
>> Flo
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2012-01-17 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANSnPLJoBpxWJx_Tbsj6oFnL9sHfEDfFDZOdwkRAezk+iE5WRw@mail.gmail.com>
2012-01-17 16:29 ` Michael Tremer
2012-01-17 16:53 ` WhyTea [this message]
2012-01-17 18:30 ` Michael Tremer
2012-01-17 19:23 ` WhyTea
[not found] <CANSnPLJv=Hvy+_97hnjfdWvtyP4k-rsTzURnA7TVmA0UoprmxQ@mail.gmail.com>
2012-01-17 12:29 ` Erik K.
[not found] <CANSnPLKSyXPbyoU9UwqCNCJ+Am2e5p11pX0bqxq01F5woJp-vA@mail.gmail.com>
2012-01-17 9:09 ` Erik K.
[not found] <4F11F057.1060304@ipfire.org>
2012-01-14 21:16 ` [Documentation] Transmission Wiki Michael Tremer
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=4F15A79C.6040902@ipfire.org \
--to=whytea@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