Assistance Needed: Crypto Guide
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been working on updating the Crypto Guide (or Encryption and Privacy Guide) [1] but I've run into a few snags. Karsten "Quaid" and I have been talking about the different information that should be included but we've come to a point where we need input from the group.
Originally the Crypto Guide was written to show how to implement LUKS disk encryption within Fedora. This has been done and tested. Being that this is the "Encryption and Privacy Guide" proposed topics to include in the guide are:
- - LUKS Disk Encryption Solution
- - eCryptfs Disk Encryption Solution
- - GnuPG (GPG) File Encryption Solution
- - GnuPG (GPG) Email Encryption Solution
- - SSH
- - VPNs
- - Other related references.
I guess the biggest problem is where do you draw the line between Fedora-specific implementations and good security practices that have information available somewhere else?
So I'm asking you what should be included in the Guide and what shouldn't. I'm going to try to go put as much information into the topics that are listed above but this has to be out the door for F9 so I don't want to put too much information into it. If anyone would like to assist writing on any of the above topics please let me know.
Eric
[1] http://fedoraproject.org/wiki/Docs/Drafts/CryptoGuide
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFH4lyDL5V8yddJCO0RAolhAJ4vMDQW9Bjmn/MT3FPidtmPxnI/MwCfVsPh
nosx5HWtD06EiZCa3Yu/Fow=
=K+dq
-----END PGP SIGNATURE-----
16 years
[DRAFT] F9 Beta release announcement
by Paul W. Frields
Jesse, look this over and correct as needed.
= = = = =
Ah, spring... when a young penguin's fancy lightly turns to thoughts
of... Beta testing! Yes, spring has sprung, and so has the Beta release
of Fedora 9!
The Beta release is the point at which we really want and need the wider
community's help with testing. Beta is a point of much greater
stability in Fedora's development branch, but some fixes continue to
occur to improve usability, performance, and stability. This release is
great for early adopters and Linux enthusiasts! The Fedora 9 Beta boots
on the majority of systems, and gives you an idea of how the final
Fedora 9 will look and feel. Most importantly, we absolutely need
community assistance to check features and provide feedback and bug
reports, to help ensure that Fedora 9 is our best release ever.
Some highlights of Fedora 9 Beta:
* GNOME 2.22, with new features like a helpful world time clock, better
file system performance, security improvements, power management at the
login screen, the ability to dynamically configure displays, better
Bluetooth integration, DVD and on-air and satellite digital TV support,
YouTube searching, improved podcast support, and many other enhancements
* KDE 4.0.2, which includes a brand new desktop and panel with many new
concepts, integrated desktop search, a brand new visual style called
Oxygen, a new multimedia API called Phonon, and a new hardware
integration framework called Solid -- all integrated by Fedora's KDE SIG
* Firefox 3 Beta 5, featuring a native look and feel, desktop
integration, the new Places that replaces bookmarks, and a reworked
address bar
* Support for resizing ext2, ext3 and NTFS partitions during install
* Support for creating and installing to encrypted filesystems
* PackageKit, a cross-distribution package management solution with a
complete yum backend, designed to unify different distributions'
software management with the latest technologies
* Kernel 2.6.25-rc5
And numerous other improvements and enhancements.
The full release notes are available at:
http://fedoraproject.org/f9-beta-relnotes
Getting it:
==========
The Beta release is available both through our mirroring system and
via bittorrent.
For direct http access to a local mirror:
http://download.fedoraproject.org/pub/fedora/linux/releases/test/9-Beta/
For a list of mirrors carrying the content and the various protocols
they support:
http://mirrors.fedoraproject.org/publiclist/Fedora/9-Beta/
For bittorrent:
http://torrent.fedoraproject.org/
More Information:
============
For more information regarding the Beta release, please visit the
release notes page:
http://fedoraproject.org/f9-beta-relnotes
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
16 years
FDSCo Meeting 2008-03-26 Summary
by Bart Couvreur
Summary of Fedora Documentation Steering Committee (FDSCo) meeting
held on Wednesday, 26 March 2008 at 20:00 hrs UTC
Attendees:
-----------
Karsten Wade (quaid)
Paul Frields (stickster)
Jared Smith (jsmith)
John Babich (jmbuser)
Bart Couvreur (couf)
Summary:
---------
* Release notes colophon:
- Decision: create the colophon per release
- Requirement: checking both Beats logs and cvs logs for contributors
(needs a volunteer)
- Community: add yourself to the colophon if you aren't on it yet
* Single Source Summary (SSS):
- Use the content in the Beats to add information to the SSS, mark the
appropriate sections with ## comments in the wiki
- Action items:
° wrap ## comments around OverView in the Beats, then pull that back
in to the SSS
° Look at what is common amongst the other content for merging
° mark ## comments around that content for inclusion in other pages
° scope all pages needing content, what do they need, etc.
° pull in the content
- create a new type of relnotes based on SSS summaries (human
language) to be used on the main landing site, sort of like the GNOME
release notes. These would link to the complete notes which still live
at docs.fp.o (Karsten, Paul)
- Website freeze: April 15th
* Other work: to be addressed on-list
16 years
FDSCo Meeting 2008-03-26 IRC log
by Bart Couvreur
20:17 < quaid> <meeting>
20:17 < couf> disco
20:17 -!- quaid changed the topic of #fedora-meeting to: FDSCO meeting, gathering the souls
20:19 -!- jmtaylor [n=jason@fedora/jmtaylor] has joined #fedora-meeting
20:19 < stickster> Documentation, wooo!
20:19 < quaid> docmentation lad
20:19 -!- stickster changed the topic of #fedora-meeting to: Fedora Documentation Project -- it's all about the Docs, baby!
20:19 < quaid> lesson one of the wiki, if you have a page loaded, don't edit that, edit in a new tab, because there is no guarantee you'll get it up in time for the meeting to start
20:20 -!- quaid changed the topic of #fedora-meeting to: FDocumentation!SCo mtg ::: Colophon policy for release notes
20:20 < quaid> by golly, a new thing to discuss
20:21 < couf> fiesta
20:21 -!- smooge [n=smooge(a)canopus.unm.edu] has left #fedora-meeting ["-ENOTIME"]
20:21 * stickster takes credit for new topic
20:21 < quaid> ok, so who knows anything about this?
20:21 < quaid> you may speak
20:22 < stickster> Re: http://www.redhat.com/archives/fedora-docs-list/2008-March/msg00152.html
20:22 < stickster> The responses so far are unanimous that #2 is the solution, wipe the Colophon each release and gather it again based on CVS commits and other activity.
20:22 < stickster> Makes for easier tracking (i.e. only have to do it for the release we're in)
20:23 < couf> +1 to #2
20:23 < stickster> And if you want your name in, you better get hoppin'! :-)
20:23 -!- schlobinux_ [n=xavierb(a)AGrenoble-257-1-112-6.w90-27.abo.wanadoo.fr] has left #fedora-meeting []
20:23 < stickster> I'm +1 to #2 as well.
20:23 < couf> yeah and the old names are still available in other versions of the relnotes
20:23 < stickster> Exactly.
20:23 -!- gospo [n=gospo@nat/redhat/x-999a994c8af35a5e] has left #fedora-meeting []
20:24 * quaid looks, one second
20:24 < couf> Q: where do we start? as in everyone who committed to devel since the F-<previous version> branch or after the pot-drop?
20:25 < quaid> also there is the wiki commits
20:25 < stickster> couf: I'd say start with beat writers for the current release
20:25 < quaid> so I'd say, anything after the last wiki snapshot for the previous release
20:25 < stickster> quaid *jinx
20:25 < couf> aye
20:25 < stickster> So it would be those people, plus any translators from the first POT drop
20:25 < stickster> onward
20:25 < quaid> yeah, man, give credit to the soul who comes and cleans up the last mess
20:25 < quaid> onward
20:25 < stickster> No kidding
20:25 < couf> right-o
20:26 < stickster> Votes? Votes?
20:26 < stickster> We have (2) +1's thus far
20:26 < couf> and about 10 communitized +1's too
20:26 < quaid> looks like list agrees
20:26 -!- knurd is now known as knurd_afk
20:27 < quaid> +1 to "slick that sucker each release" method
20:27 < quaid> all right!
20:27 < quaid> we have a real consensus
20:27 < quaid> now we just need a volunteer to do the work
20:28 < couf> right, that was my second question :-)
20:29 < couf> looking at the page it seems that a lot have actually added themselves, so that'll probably be an easy one
20:30 < quaid> ok, I emailed the question to the thread
20:30 < quaid> and asking translators to add themselves to the wiki page is a great method, too
20:30 < quaid> that is, add yourself if you want guarantee, and we'll look in the logs anyway
20:31 < couf> indeed
20:31 -!- ldimagg__ [n=ldimaggi@nat/redhat/x-ca74e5403d1c08be] has quit [Read error: 113 (No route to host)]
20:31 < quaid> ok
20:32 < quaid> I think we have what we need squeezed from that topic, eh?
20:32 * quaid momentarily distracted by short, adorable people
20:32 < quaid> any mo' on this topic?
20:32 -!- kital [n=Joerg_Si@fedora/kital] has joined #fedora-meeting
20:33 -!- quaid changed the topic of #fedora-meeting to: FDocumentation!SCo mtg ::: Single source summary ...
20:33 < quaid> onward then
20:33 * quaid heard the sound of the bell there, he was sure of it
20:33 < quaid> http://fedoraproject.org/wiki/DocsProject/SingleSourceSummary
20:33 < quaid> now, as I expected, I haven't touched it since I poured it all into the pot, gave it a stir, and added some salt and pepper
20:34 -!- ldimagg__ [n=ldimaggi@nat/redhat/x-f047abd9f59e823b] has joined #fedora-meeting
20:34 < stickster> quaid: You took my bell joke!
20:35 * stickster meant to devote some time to SSS and ran out of cycles.
20:35 < quaid> stickster: "redistributed"
20:36 < quaid> I'm going to hang a CC BY SA sign around my neck
20:36 < stickster> ha
20:36 < quaid> "You may take whatever I say, think about it, and say what you will from it."
20:36 * couf needs to say photographic evidence first
20:36 < stickster> So about the SSS...
20:37 < couf> s/say/see
20:37 < quaid> http://fedoraproject.org/wiki/Releases/9/SingleSourceSummary actually
20:38 < quaid> what we manage ther
20:38 < quaid> e
20:38 < quaid> is the technical content
20:39 < quaid> so, ideally, we can give some raw ideas into the overview type pages and let other writers (who may be some of us) add their polish; share this with Mktg
20:39 -!- jsmith [n=user(a)72.21.36.138] has joined #fedora-meeting
20:39 * jsmith stumbles in late
20:39 < stickster> quaid: I don't think enough people know what tasks they're supposed to complete on this page.
20:39 -!- GeroldKa [n=GeroldKa@fedora/geroldka] has joined #fedora-meeting
20:39 < quaid> moin jsmith :D
20:39 < jsmith> moin moin
20:39 < stickster> ~lart jsmith
20:39 < quaid> stickster: I haven't really put thunks into it
20:45 -!- rdieter [n=rdieter(a)sting.unl.edu] has quit [Read error: 104 (Connection reset by peer)]
20:46 < quaid> and there we are
20:46 * quaid had in house distractions, sorry
20:46 < quaid> not sure how to tackle the SSS
20:48 < stickster> quaid: Should we be marking tags around the beginning and end of each section?
20:48 < stickster> Adding content?
20:48 < quaid> well, I see that some content actually needs to be sucked in _from_ the Beats pages, not vice versa, right?
20:48 * stickster tempted to ask about next actions since he's reading that part of GTD
20:48 < quaid> that is, let people continue editing the Beats pages as-is
20:49 < stickster> Yeah, we don't want to screw the Beats process at this point in F9
20:49 < quaid> ok, if I had the time to do this, i would do these actions:
20:50 < quaid> * wrap ## comments around OverView in the Beats, then pull that back in to the SSS
20:50 < quaid> * Look at what is common amongst the other content for merging
20:50 < quaid> * mark ## comments around that content for inclusion in other pages
20:51 < quaid> * scope all pages needing content, what do they need, etc.
20:51 < quaid> ** begin pulling pieces
20:51 * stickster suggests for anywhere we use [[Include(x,y,z)]] outside the SSS page, we should leave a starting note to let people know not to bother it
20:51 < stickster> ## This content is drawn from another page. Don't remove this macro without talking to the Docs Project first.
20:52 < stickster> ## Or unless you really, REALLY know what you're doing.
20:52 < quaid> +1
20:52 < couf> yeah, good idea
20:52 < quaid> ok, there are my actions
20:53 < quaid> let's at least get them minutes-ized
20:53 < stickster> We haven't jmbabich today, who's minutizing?
20:53 * quaid just noticed that
20:54 < couf> I'll do it
20:54 < quaid> thanks!
20:54 < stickster> Thank you couf!
20:54 * quaid was about to say something sarcastic
20:54 < couf> which would be? :-)
20:54 < quaid> in a good way, of course :)
20:55 < quaid> "don't hurt your arm sockets waving your volunteering hands"
20:55 < quaid> something stupid like that :)
20:55 < quaid> seriously ...
20:55 -!- alleycat [n=lonewolf@fedora/wolfy] has left #fedora-meeting ["If you look like your passport picture, you probably need the trip!"]
20:55 < couf> heh :)
20:56 -!- abadger1999 [n=abadger1(a)136.245.7.181] has quit [Read error: 113 (No route to host)]
20:56 < quaid> ok, while the wiki is whacked ...
20:56 < quaid> last few minutes we can talk about ///
20:56 -!- quaid changed the topic of #fedora-meeting to: FDSCo mtg ::: active content work
20:57 < quaid> relnotes are doing OK ...
20:57 < quaid> some changes rolled in to wiki, etc.
20:58 < quaid> beta notes went fine
20:58 < stickster> Yeah, this one came together pretty well
20:58 < stickster> I did a little frenzied stuff with f13 the night before, but it was less than par for the course, actually
20:58 < quaid> mizmo, mlanglie came in to help with making a mucho cooler relnotes landing page for F9 final
20:58 < couf> thumbs up to all who did the work
20:58 < stickster> One thing we should definitely try to keep in mind is to standardize our linking to the downloads
20:58 -!- jmbuser [n=jmbuser(a)c-98-204-160-140.hsd1.md.comcast.net] has joined #fedora-meeting
20:59 < jmbuser> meeting?
20:59 < quaid> the current discussion is to reorganize the content around reader interests, and we'll try to do that with the existing XML pulled in a different XInclude structure
20:59 < quaid> jmbuser: still going
20:59 < couf> moin jmbuser
20:59 < stickster> We tried to consistently use http://fp.o/get-prerelease and http://fp.o/<static_relnotes> this time around
20:59 < couf> which worries me a little cause the final relnotes are supposed to go to docs.fp.o
21:00 < stickster> couf: That's an interesting point, and intersects with quaid's last statement
21:00 < stickster> You see...
21:00 < stickster> I think that the notes on the static site, where we send people at first, either from fp.o front page or start.fp.o, need more reworking than just content shuffling.
21:01 < stickster> I think they ought to be trimmed and edited to be more like gnome.org's
21:02 < stickster> On every page/section, those trimmed "splashy" notes can link to our big release notes document for indepth info
21:02 < couf> agreed
21:02 * couf always liked gnome's way of doing it
21:02 < stickster> This *could* mean more work and strings, but since we have to do this repeatedly anyway for release announcements and other overview, it's actually a way to save some work
21:02 < stickster> Especially if we use summaries on SSS to write in human language.
21:03 < quaid> hrm
21:03 < quaid> this is a bit of an effort, for sure
21:03 < stickster> "How does this help the <user/developer/admin> kick ass?"
21:03 < quaid> can we do this in the time remaining? do we have the resources?
21:03 < stickster> We have the power
21:03 * quaid puts on his curmudgeon hat
21:03 < stickster> We have some webmonkey help
21:03 < couf> l10n won't like this ;-)
21:03 < stickster> couf: Well, it's putting some new strings on the web site, to be sure.
21:03 < quaid> well
21:04 < quaid> yes, website side
21:04 < quaid> so
21:04 < quaid> if we do the work *now*ish
21:04 < couf> ricky: ping
21:04 < quaid> then it can be translated in the weeks up to GA where the main package trans is mostly done
21:04 < stickster> Right
21:04 < stickster> And we know the feature set already.
21:04 < couf> true enough
21:05 < quaid> can we suck in the strings from OverView PO files into the website PO files?
21:05 < stickster> Probably
21:05 < quaid> so that's the idea on the table
21:05 < stickster> But much of the OverView beat as it is right now needs to be rewritten for this usage.
21:05 < quaid> turn our resources to doing this
21:05 * stickster for it.
21:05 < stickster> We've got EvilBob+team on IG already
21:05 < quaid> while we still have DUG, AG, SMG, and Enc/CryptoG
21:06 < quaid> we really need a new source of editors
21:06 < stickster> quaid: I think the relnotes are a good place for you and me to put our experience, since it's a new venture.
21:06 < stickster> We can spread that particular love/pain in F10
21:06 < stickster> We're already doing pretty well at spreading out the other guides
21:06 < couf> you've got mdious too on relnotes
21:07 < stickster> True
21:07 < stickster> So I say let's go for it
21:07 < quaid> heh
21:07 < quaid> but I'm a curmudgeon!
21:07 < quaid> ah, well, rising tide and all that
21:07 * quaid sends begging for editors email
21:07 * stickster needs to bail for a bit... call
21:07 < stickster> back in 10 on #f-docs
21:07 < quaid> k
21:08 < quaid> there isn't anything new on the other content, fwiw
21:08 < quaid> so we can call for other business or quit
21:08 -!- quaid changed the topic of #fedora-meeting to: FDSCo mtg ::: Other bidness
21:08 < couf> the only thing would be: DUG target version
21:08 < quaid> oh, right!
21:08 < quaid> well, do we need to decide that? or is that an on-list discussion/decision?
21:09 < couf> on-list is fine
21:09 < couf> writers are following that topic
21:10 < ricky> couf: Ah, sorry, I pretty much have to leave in a minute.
21:10 < quaid> yep, agreed
21:10 < couf> ricky: no problem, was just wondering what date the website would freeze for F9
21:10 * quaid sees it has wandered
21:10 < quaid> all right then, we'll get ready to pull the plug on this mtg
21:11 < couf> go for it
21:11 < ricky> couf: How long do you think translators need?
21:11 < ricky> (Before final release)
21:12 < couf> ricky: if you can give them 2 weeks that would be awesome
21:12 < ricky> OK, in that case, around mid-april (15th or before fine?)
21:13 < couf> 15th is fine
21:13 < ricky> All right, thanks for the reminder.
21:13 < quaid> ok
21:13 < couf> quaid: that means we need to finish the web transition on the 15 too
21:13 < quaid> right
21:13 < quaid> got that stickster !!!
21:13 < couf> heh
21:13 < quaid> ok, closing in 5
21:13 < quaid> 5
21:13 < quaid> 4
21:13 < quaid> 3
21:14 < quaid> 2
21:14 < quaid> </meeting>
16 years
A Few Questions...
by Zachary Hamed
Hi again guys,
First of all, thank you Mr. McAllister for your help with the GPG
key...clearly it's all fixed below.
Next, can anyone give me an idea of what you usually do with this
project? About how many people contribute to the Fedora Docs project?
How does the editing process occur (i.e. how do the editors circulate
the documents they edit)? Most importantly, though, how do you get
editing jobs? I'm all ready for some editing, so how am I informed of
the documents I should edit?
Thanks again,
Zach
--
pub 1024D/FEC6E7F6 2008-03-25 [expires 2009-01-20]
key fingerprint = CA07 844A 0730 4C1B C11A 381E A2A5 4FE2 FEC6 E7F6
Zachary Hamed (Fedora Docs Contributor) <zachfedora(a)gmail.com>
sub 2048g/3F7CCFAB 2008-03-25 [expires 2009-01-20]
16 years
static Beta notes
by Karsten Wade
Jon, Rahul, et al, thanks much for a great set of Beta release notes.
We followed through with a proper static page this time, which was only
a minor challenge:
http://fedoraproject.org/en/f9-beta-relnotes.html
FYI, I did:
* Wiki => DocBook
* Add DOCTYPE header (Moin bug), xmlto to make HTML
* Edit HTML into the fp.org template
- Skipped the markup that allows it to be translated (not a goal for
Beta notes)
- Removed lots of <div/> blocks in troubleshooting that probably
didn't matter in the end; that is, could have left them to minimize
conversion hassles
Anyway, hoping we have a regular CMS in place for fp.o and don't have to
do this sort of thing again. :)
- Karsten
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
16 years
Intro, Revised and Reformulated
by Zachary Hamed
EDIT: Sorry, I just read the Fedora requirements for this introduction
email, so I'm resending my previous one with corrections. Please
disregard my previous email, and sorry for the inconvenience.
-------------------------------------------------------------------------
Hi everyone,
My name is Zachary Hamed, Zach for short, and I live in the New York
City area, USA. I'm a sophomore (grade 10) high school student at
Collegiate School, and I got interested in Linux in general about a
year ago. I tried OpenSUSE and found the installation to be a huge
pain, so I switched to Fedora and have been using it ever since
(dual-booting with Vista (1) because of school work and (2) because I
can't get my Broadcom WiFi card to work with Fedora 8...grr...). I
also just finished reading two books about Linux and the Open Source
movement (Rebel Code: Inside Linux and the Open Source Revolution, by
Glyn Moody, and Just for Fun: The Story of an Accidental
Revolutionary, by Linus Tovalds and David Diamond, both of which I
highly recommend).
I have a bit of programming experience. I can program pretty well in
BASIC, and my dad is a computer programmer for a living. I'm also in
the process of learning Ruby (and Rails for that matter). I've written
a book on computers (www.joiningthedigitalworld.com) that I edited
completely by myself, and of which I've sold about 200-250 copies
(available on Amazon, BarnesAndNoble.com, and other retailers online).
I'm now working on a project called Ease of Tech (www.easeoftech.com),
which is kind of an Adobe AIR type overlay system to an OS...can't
really get into it in detail here.
In terms of what I would like to do for the Fedora Project, I can't
really contribute much to the coding side, but I would love to help
out in any way I can (I know it'll look good on the college
applications; hoping to go to MIT!). Additionally, I am a very good
English student (not my favorite subject, but I do well), so I would
like to edit as many documents as I can, and I can even write some
docs on newbie things (as I am one anyway). One thing I think is
lacking for the documentation project is some kind of complete guide
for complete newcomers to Linux. Ubuntu has been attracting a lot more
users because of this, and I think Fedora could be a real alternative
to Mac and Windows for older people if they had a comprehensive guide
to just about everything up until the post-install period—it's also
something I wouldn't mind working on.
I think I'm a good match for the project because I'm a hard worker, am
good in English (and getting better with programming), and really want
to contribute to the community.
I looked over the Style Guide and the associated rules, most to all of
which I am familiar with (my school has a grammar proficiency test
every year which I always pass, thought it's pass/fail so I can't
share any grades with you). Again, it would be great for me to be
another step in the editing process, or to even make a guide of my
own.
Can anyone tell me where I go from here? What you guys are doing so
far? I should get the gist of it once I get daily mailing list
digests, but just in case...
Thanks,
Zach
P.S. This email is in no way representative of my "formal writing"
writing style; I had to rant and use parentheses a bit more than I
usually do.
P.P.S. I'm still new to the idea of signing emails with this key. I
submitted the key (or what I think was a key) to pgp.mit.edu, but is
the stuff below in the correct format? I saw what format it *should*
be in on the Fedora intro-email page, but I don't want to screw up and
send out my private key, because apparently that would be really bad.
All I did below was paste the text copied when I right-clicked on my
key and selected "Copy Public Key" (this is in "Passwords and
Encrypted Keys").
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.7 (GNU/Linux)
mQGiBEfoiZ4RBADF/B8jv2irteaWjEB1+C7SXHCJmWIAI9+duvrKpIdj+UiV6aZi
OijfMtMm/PEosHbhA47F8vNQAOYhcSBeasc2omvntrguHicBnP3WWKpFgU7jvJ8D
Qch6nCDrjV/gpoyhdEUSp+3P7+DS31qHKb8ti44UQNzsGeb6Yi5Ucw2p/wCggu4H
Ro27QPG+BxVJM3r7N5BFcisEAJPIsTJBxz5GmH5cgWJDmELJtgx78Ozq755SgdJt
NqdL1vXUkOnwkvXytQ3TUehuq0Yi2aiM6YwN1D/kceWNdL7uyB0DhhAuU4UTf9i5
GPqSNpYCtajSVZueEp0x9Zo2eYS3qRocsg/Nxp8u1bXG1r7QKowbHth6bd97inKR
6QYSA/48glKFr41nEju2Y9QqYyy6BNmyPn1rkpfYmovRCKS6u1RgkfUNmdStflIa
nmA5j49i/eknDt7g0HRQuOue9xJlgmf66W2AEP/+93UFp81Hc9o16Sz/wtODx8Kf
Ld62RzC/fAFKv8lE9l3NOGQAWhK0Wvi0vBW0ndX0sWNBScsPfLRWWmFjaGFyeSBI
YW1lZCAoSGlnaCBTY2hvb2wgU3R1ZGVudCBhbmQgRmVkb3JhIERvY3MgQ29udHJp
YnV0b3IpIDx6YWNoZmVkb3JhQGdtYWlsLmNvbT6IYAQTEQIAIAUCR+iJngIbIwYL
CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEKKlT+L+xuf25d8An31S/k3oepwYT7if
LlHQrYxTusSEAJ9tuJreyAhOYIDhUD5zmnddXnBj7bkCDQRH6ImeEAgAjMtcFkaT
TUVx6aGzelAGqHwlApFlQ70mJE+fUqyOLT/abEdX2aw+UWXOLMFkMKY0kBnlQtE9
n5IJwHGfUge0Al2fhJA4dy/fV6v78rqV9GBbA08MZ4n+HI6F89P0VLeYrB/20IgB
IgcWimDwC2A22MIQzOoKJcylQIagSxfTxliTjKgG2IxY/9yn3NHSHh3jI3nUfW3F
hOxzV0/l9P9en+4/bect2qheRLMpJB/jo0/ZDnJJ4VP3pZ+HeTZ2zsvAaED2M6aX
1tuqb/PYQLRoW7rXpGbBW1JC1x8sKZUgu/wVBYmTDekeO/y+kqE03lfLpWb4/Y/b
orXKCe9D0xasFwADBQgAgeKd3f+HPwpIXZ8i0/IErLt7xGO342zAWzKMI0vCWE/2
5mG9EwmJqH2yDI4hSd6rfyzxV1QXTBBnrXqZagrdbWXXmhQiZwu6kSgUUwcEW9C0
ZWcByeiVzjkuUDTz7Krr6aJgdk/IqDa1QsvMFC1CQpI/U7DAksg9L+MTwR8300wl
uCC7gQo3P9m7IOKSHLO3uRwkz/koYNHzfdF0Gnsn/ccAS1VNW77wWGa7lDzEBchY
LBEVjeA8P2WE3Re6cjJDNy1RAnpkS/kAa5d+NYMqfwPvWFQ+VX8Utt4cMaZdsAh2
VdKW9OQt0zmF77EzxUvenp4ARjpacyKu7M3Ufgu51IhJBBgRAgAJBQJH6ImeAhsM
AAoJEKKlT+L+xuf2IJwAn1WvpJrPTU1W8eEBdvYe1ciwxx8VAJ9TjiM5+6Y0YG7M
dzWBVeCzF8cvDA==
=QFDP
-----END PGP PUBLIC KEY BLOCK-----
16 years
Short Intro...
by Zachary Hamed
Hi everyone,
My name is Zachary Hamed, Zach for short, and I live in the New York
City area. I'm a sophomore high school student and got interested in
Linux in general about a year ago. I tried Suse and found the
installation to be a huge pain, so I switched to Fedora and have been
using it ever since (dual-booting with Vista (1) because of school
work and (2) because I can't get my Broadcom WiFi card to work with
Fedora 8...grr...). I also just finished reading two books about Linux
and the Open Source movement (Rebel Code: Inside Linux and the Open
Source Revolution, by Glyn Moody, and Just for Fun: The Story of an
Accidental Revolutionary, by Linus Tovalds and David Diamond). At my
current programming level (already know BASIC pretty well and trying
to learn Ruby, but I also have to balance it with my schoolwork), I
can't really contribute to the coding side of the Fedora Project, but
I would love to help out in any way I can (I know it'll look good on
the college applications; hoping to go to MIT!). Additionally, I am a
very good English student (not my favorite subject, but I do well), so
I would like to edit as many documents as I can, and I can even write
some docs on newbie things (as I am one anyway).
I looked over the Style Guide and all that, most to all of which I am
familiar with (my school has a grammar proficiency test every year
which I always pass, thought it's pass/fail so I can't share any
grades with you). Again, it would be great to be another step in the
editing process.
Can anyone tell me where I go from here? What you guys are doing so
far? I should get the gist of it once I get daily mailing list
digests, but just in case...
Thanks,
Zach
P.S. This email is in no way representative of my "formal writing"
writing style; I had to rant and use parentheses a bit more than I
usually do.
16 years
fedora-release-notes package
by Murray McAllister
Hi,
According to http://fedoraproject.org/wiki/DocsProject/Schedule, on
the 1st of April, a "fedora-release-notes" package is sent to Fedora
release engineering. What exactly is this package? Is it something for
people to install?
Thanks,
Murray.
---------------------------------------------------------------------
pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18]
Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB
Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com>
sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
16 years
Release Notes reminder!
by Paul W. Frields
FOR ALL TRANSLATORS:
Please make sure that before you translate Release Notes, you translate
the "Docs:: Common entities" module. If your language does not exist in
that module, we cannot build or include your translations in the package
of Release Notes.
http://translate.fedoraproject.org/module/docs-common-entities
If you are a command-line user/translator, you can do a "make
validate-xml-<LANG>" to check your work as you go, and before you
commit.
There are 5 other modules which also pertain to Release Notes:
Docs:: about-fedora
homepage
readme
readme-burning-isos
readme-live-image
Remember that for these last 5 modules, as well as the release-notes
themselves, you want the "devel" branch for the module PO.
We look forward to having even more languages for this release of
Fedora, and growing our international community even larger than for
Fedora 8. Thank you to everyone for participating!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
16 years