1:44 a.m.
I first used linux which was RH9 I think.
What I did was the web browser which was Navigator if I'm not wrong. I
then search through all the links to try and find out what I could and
couldn't do and how I was supposed to do things.
I suppose the 'best' example would have to be the http://ubuntuguide.org I
think thats the link. It basically explains everything including the
propietary stuff. The equivalent I've used at times has been fedorafaq
which was great but didn't imo go far enough.
I suppose a happy medium between the two as a link possibly. Or maybe the
standard home should have a help section then from there to a docs section
explaning.
I know a lot of people who still don't know about SElinux because they
don't know where to look. Granted fedoraforum for example has helped with
that however solving it in the first place by creating that link from the
front webpage.
Another great doc section I suppose could be the gentoo docs which
although its a 'hard' way of going for a newbie who has very little idea
of compiling it steps you through everything which really was helpful for
me for example when I first tried it. Stupid me forgot to enable the swap
space :(
Should we look at all examples of put all examples down and start creating
a 'template' of how to lay it out or has that already been done. If
so can someone point me in the right direction please.
Just putting suggestions forward and I suppose I'm trying to 'picture'
how it would look. Possibly start on a table of contents or has that been
progressed on.
On Fri, 2005-07-22 at 08:46 +0800, Marc Wiriadisastra wrote:
> Is this suggestions to be done straight away as in announcing it or
are
> we
> planning on making it big enough to hit people over the head with
in
> FC5?
- Ignored:
Both?
> The only thing I can suggest is adding it to the front page of
Firefox
> when you start it up after the install. It can say it there. Or
maybe
> when you find links to download the .iso's. Put a what
fedora does
and
> doesn't do section. What type of os it is regarding the fact
that
its
> imo
> semi-bleeding edge.
Then that would be a "Note" that appears at the top of the release
notes.
I agree with the concept of what you suggest, it certainly makes
it fairly obvious. However, I don't know about the idea of
making
the
first, biggest, and most regular information that readers see be a
message about MP3 patents.
We reorganized the release notes to be more friendly for a default
Firefox page.
Not all the changes are in FC4, but the basic idea
was to
add a "what's new" section and make the table of
contents more
visible
to show what information is in the release notes. The
"what's new"
contains links to useful information, and would be a
natural place to
put such a note.
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer *
http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E
0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
--
Regards
Marc Wiriadisastra
4:03 a.m.
New subject: [Fwd: [Bug 163675] mpeg situation not explained in ...
On Fri, 2005-07-22 at 14:44 +0800, Marc Wiriadisastra wrote:
I suppose the 'best' example would have to be the
http://ubuntuguide.org I
think thats the link. It basically explains everything including the
propietary stuff. The equivalent I've used at times has been fedorafaq
which was great but didn't imo go far enough.
ubuntuguide.org goes down the same road that fedorafaq.org and all
others do, a road we cannot walk. However, in the last few months, we
have received permission to link to sites that themselves may link to
any amount of unknown information.
However, we _cannot_ tell people how to circumnavigate, install, or
otherwise use this software. We cannot link to a site that tells how to
do that. If we link to a site, such as google.com, and it is possible
to find such information off that site _and_ it is a link away, then it
is out of our hands. AIUI.
I suppose a happy medium between the two as a link possibly. Or
maybe the
standard home should have a help section then from there to a docs section
explaning.
We can just add a section to the release notes that mirrors the
information on the Wiki.
Should we look at all examples of put all examples down and start
creating
a 'template' of how to lay it out or has that already been done. If
so can someone point me in the right direction please.
Sorry, I don't understand what 'it' is that we would lay out.
Just putting suggestions forward and I suppose I'm trying to
'picture'
how it would look. Possibly start on a table of contents or has that been
progressed on.
Sorry, a ToC for what exactly?
thx - Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
11:04 a.m.
New subject: [Fwd: [Bug 163675] mpeg situation not explained in ...
One thing that would be handy in these situations would be a "review"
that accomanied the release notes. You highlight the product, the way
you wish a journalist would, and send it out. If you answer the
recurring mistakes (e.g. they evaluate it as a production distro, they
assume mulimedia issues are shallower than they are, etc).
You write the spotlights from with the position you want Fedora to
maintain (i.e. from and for the point of view of the appopriate user.)
We can tell people why DVD and MP3 support is gone, point out
alternative technologies, or anit-patent petitions, and even link to
sites that have workaround instructions. Even safer, we can advise
they "Google it".
It's not fair to say all journalists are lazy, but enough of them are
lazy and/or sloppy (or have editors/fact checkers less familiar with
the material than they are) to make this worthwhile, since they will
cut paste and paraphrase this into a "story" the way they do with
press releases on slow news days. For those that don't, it's very easy
for us to post a link to this "release review" and the tertiary,
release notes and FAQs in the comments of any article that takes the
wrong approach.
--jeremy
11:45 a.m.
New subject: [Fwd: [Bug 163675] mpeg situation not explained in ...
On Fri, 2005-07-22 at 12:04 -0400, Jeremy Hogan wrote:
One thing that would be handy in these situations would be a
"review"
that accomanied the release notes. You highlight the product, the way
you wish a journalist would, and send it out. If you answer the
recurring mistakes (e.g. they evaluate it as a production distro, they
assume mulimedia issues are shallower than they are, etc).
Thanks to Rahul, that is largely what we have this release notes.
Although it wasn't created as a canned review, it is certainly a
starting point, and appears at the top of the release notes. In the
latest version of the relnotes, the legalnotice has been moved from the
top to a new section, so the ToC is available and shows:
1. Welcome to Fedora Core 4
1.1. New in Fedora Core 4
1.2. MP3 Codecs and Other Patented or Closed Source Software
2. Legalnotice
3. Introduction and Technical Release Notes
4. Hardware Requirements
...
http://fedora.redhat.com/docs/release-notes/fc4/errata/index.html
I think this What's New section needs a little more of what you suggest,
and then, yeah, we need to distribute it in advance of the release.
We came really, really close to having this right for this release. The
relnotes were such a throw-together that we are proud to have just done
them, so the next time is going to ROCK!
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
9:31 p.m.
New subject: [Fwd: [Bug 163675] mpeg situation not explained in ...
We can just add a section to the release notes that mirrors the
information on the Wiki.
> Should we look at all examples of put all examples down and start
> creating
> a 'template' of how to lay it out or has that already been done. If
> so can someone point me in the right direction please.
Sorry, I don't understand what 'it' is that we would lay out.
I meant like a template in a constant way of the marketing group or doc's
group to release information. I think however in recent months it has
improved a hell of a lot however I think getting the message out is
important.
> Just putting suggestions forward and I suppose I'm trying to
> 'picture'
> how it would look. Possibly start on a table of contents or has that
> been
> progressed on.
Sorry, a ToC for what exactly?
Sorry for not being concise enough. As you bootup firefox after fedora
has been installed it brings up the front page of I believe of
fedora.redhat.com is that right?
I suppose adding links to that for help and or what to do. Where to get
information and things like that. The ToC related to I suppose what other
information should we link up to it.
10:55 a.m.
New subject: [Fwd: [Bug 163675] mpeg situation not explained in ...
On Sun, 2005-07-24 at 10:31 +0800, Marc Wiriadisastra wrote:
> Sorry, a ToC for what exactly?
Sorry for not being concise enough. As you bootup firefox after fedora
has been installed it brings up the front page of I believe of
fedora.redhat.com is that right?
Actually, it's a local copy of the release notes. It is in a visual
template that is the same as fedora.redhat.com, and the side links take
you to live URLs. It is a local copy because we can't be sure someone
has network access and don't want the browser to not have a page to
show.
This was why we updated the release notes to address the kinds of things
you are talking about. We (tried) to move the legalese so that it was
not at the top of the page, made the ToC more prominent, and have
introduced a What's New in Fedora Core section, and now there is a 1.2.
MP3 Codecs and Other Patented or Closed Source Software. If you look at
this page:
http://fedora.redhat.com/docs/release-notes/fc4/errata/
That is similar to what it *should* look like for FC5. Unfortunately,
the changes to make the legalnotice lower didn't make it into the
release version of fedora-release. There is an errata of this package
in QA that has the legalnotice moved. We might release another errata
in a while, after we get more kinks ironed out of the relnotes.
We didn't have time or a proper marketing group to talk about this with,
so Rahul and I just made the changes. It's good to see that we were
anticipating a need.
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
6881
days inactive
6883
days old
marketing@lists.fedoraproject.org
5 comments
3 participants
participants (3)
-
Jeremy Hogan -
Karsten Wade -
Marc Wiriadisastra