nvidia cuda tutorial
by William Blackburn
If I wrote a guide on setting up the Nvidia SDK for CUDA with OpenCL implementation, would it go in the fedora docs? Or.......is there a wiki place for something like this. I would like to do it for my own reference as well as for others. Thnks. All replies are welcome.
William(tertl3)
> From: docs-request(a)lists.fedoraproject.org
> Subject: docs Digest, Vol 79, Issue 15
> To: docs(a)lists.fedoraproject.org
> Date: Sat, 18 Sep 2010 12:00:08 +0000
>
> Send docs mailing list submissions to
> docs(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://admin.fedoraproject.org/mailman/listinfo/docs
> or, via email, send a message with subject or body 'help' to
> docs-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> docs-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of docs digest..."
>
>
> Today's Topics:
>
> 1. Re: Docs site (Justin Clift)
> 2. Re: Docs site (daniel cabrera)
> 3. Re: Docs site (Mike McGrath)
> 4. Re: Fwd: SE Linux docs (Karsten Wade)
> 5. Re: Fwd: SE Linux docs (John J. McDonough)
> 6. Re: Fwd: SE Linux docs (Paul W. Frields)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 17 Sep 2010 22:04:49 +1000
> From: Justin Clift <justin(a)salasaga.org>
> Subject: Re: Docs site
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Cc: Piotr Dr?g <piotrdrag(a)gmail.com>
> Message-ID: <4C935961.3060805(a)salasaga.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 09/17/2010 04:24 PM, Piotr Dr?g wrote:
> <snip>
> > Anyway, reverting a bad commit is easy, basically it's "git revert
> > commit_hash". Commit hash can be obtained from some git command I
> > don't know or from my favorite gitweb. :)
>
> (in case it's useful, or anyone's curious)
>
> The command "git log" could be what you want. It shows the history
> of what has been committed, with the most recent first, then the commit
> before it, then the one before that, and so on:
>
> $ git log
> commit 10c592801c32247d1d82520df17ae409d2e55fc7
> Author: Eric Blake <eblake(a)redhat.com>
> Date: Thu Sep 9 20:32:50 2010 -0600
>
> tests: clean up qemuargv2xmltest
>
> Since commit 107a7bd06bc, the extraFlags argument was unused.
>
> * tests/qemuargv2xmltest.c (DO_TEST): Drop extraFlags argument.
> Adjust all callers.
>
> commit df1718cc7366296be4ab71c830cc2b93e505ceec
> Author: Justin Clift <jclift(a)redhat.com>
> Date: Thu Sep 16 22:14:18 2010 +1000
>
> docs: reworked the policykit patch submitted by Patrick Dignan
>
> Tweaked the PolicyKit documentation improvement patch submitted
> by Patrick Dignan.
>
> Additionally, removed the reference to PolicyKit.conf, which is
> no longer used by PolicyKit, plus added a link to the expanded
> PolicyKit example page on the wiki.
>
> commit 5bc4307597d382ab8a951feee0daf13439926238
> <snip>
>
> There's also a "--oneline" version:
>
> $ git log --oneline
> 10c5928 tests: clean up qemuargv2xmltest
> df1718c docs: reworked the policykit patch submitted by Patrick Dignan
> 5bc4307 docs: fix the xml validity errors regarding name and id
> 8ae354f build: avoid non-portable IPv6 struct member, for MacOS X
> 58ba49a virsh: change wexitstatus order to allow compilation on mac osx
> 63d1b07 libvirtd: improve the error message displayed on tls client
> auth failure
> 8a93daf maint: silence warning from libtool
> 38ba6e1 Rebuild network filter for UML guests on updates
>
> I'm not a git expert, it's just something I'm learning from necessity. :)
>
> Regards and best wishes,
>
> Justin Clift
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 17 Sep 2010 10:27:12 -0300
> From: daniel cabrera <logan(a)fedoraproject.org>
> Subject: Re: Docs site
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Message-ID: <1284730032.27493.17.camel@ulysses>
> Content-Type: text/plain; charset="utf-8"
>
> On Fri, 2010-09-17 at 08:24 +0200, Piotr Dr?g wrote:
> > 2010/9/17 daniel cabrera <logan(a)fedoraproject.org>:
> > > On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:
> > >> can you revert it?
> > >>
> > > I think so, but I'd like some guidance... I don't want to make things
> > > worse.
> > > I'm on the IRC.
> > >
> >
> > I'm very sorry, it appears I've noticed the problem and reverted this
> > commit before I've read your e-mails. I hope I didn't get in your way
> > or something.
> >
> > Anyway, reverting a bad commit is easy, basically it's "git revert
> > commit_hash". Commit hash can be obtained from some git command I
> > don't know or from my favorite gitweb. :)
> >
> > --
> > Piotr Dr?g
>
> Well, I guess everything is back to normal.
> Nick and Piotr, thank you very much for helping me to clean up my mess.
> Now I know what was my mistake and it won't happen again.
> See you around, logan.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 490 bytes
> Desc: This is a digitally signed message part
> Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20100917/8e5f2a...
>
> ------------------------------
>
> Message: 3
> Date: Fri, 17 Sep 2010 13:13:45 -0500 (CDT)
> From: Mike McGrath <mmcgrath(a)redhat.com>
> Subject: Re: Docs site
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Message-ID: <alpine.LFD.2.00.1009171313220.2351(a)laptop1.mmcgrath.net>
> Content-Type: text/plain; charset="utf-8"
>
> On Fri, 17 Sep 2010, daniel cabrera wrote:
>
> > On Fri, 2010-09-17 at 08:24 +0200, Piotr Dr?g wrote:
> > > 2010/9/17 daniel cabrera <logan(a)fedoraproject.org>:
> > > > On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:
> > > >> can you revert it?
> > > >>
> > > > I think so, but I'd like some guidance... I don't want to make things
> > > > worse.
> > > > I'm on the IRC.
> > > >
> > >
> > > I'm very sorry, it appears I've noticed the problem and reverted this
> > > commit before I've read your e-mails. I hope I didn't get in your way
> > > or something.
> > >
> > > Anyway, reverting a bad commit is easy, basically it's "git revert
> > > commit_hash". Commit hash can be obtained from some git command I
> > > don't know or from my favorite gitweb. :)
> > >
> > > --
> > > Piotr Dr?g
> >
> > Well, I guess everything is back to normal.
> > Nick and Piotr, thank you very much for helping me to clean up my mess.
> > Now I know what was my mistake and it won't happen again.
> > See you around, logan.
> >
>
> I just realized I never sent a note to the list, yes everything is back to
> normal. Thanks to everyone for the quick response.
>
> -Mike
>
> ------------------------------
>
> Message: 4
> Date: Fri, 17 Sep 2010 13:32:46 -0700
> From: Karsten Wade <kwade(a)redhat.com>
> Subject: Re: Fwd: SE Linux docs
> To: docs(a)lists.fedoraproject.org
> Message-ID: <20100917203246.GA31949(a)calliope.phig.org>
> Content-Type: text/plain; charset="us-ascii"
>
> On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:
> > Hello Docs team and Publican knowledge-meisters,
> >
> > I received this email from a contributor and tested his results. This
> > appears to be a valid bug. How can we properly link to the interior of
> > a document on the docs.fedoraproject.org site? All targets seem to
> > take one to the top of a document, which is not only unhelpful, but
> > breaks the simple principle of least surprise.
>
> We might also want to have SELinux Troubleshooter point to a wiki
> page, and we can update that wiki page with links to the latest guide
> or FAQ.
>
> It's a bit unclear to me where the bug lies. I see:
>
> 1. SELinux Troubleshooter is deep linking when maybe it should go to a
> wiki page.
>
> 2. The SELinux FAQ has a section without an ID tag.
>
> 3. The SELinux FAQ has a broken link to itself.
>
> - Karsten
>
> > Paul
> >
> >
> > ---------- Forwarded message ----------
> > From: Dan Haskell <geekus.org(a)gmail.com>
> > Date: Mon, Sep 13, 2010 at 2:00 PM
> > Subject: SE Linux docs
> >
> >
> > Clicked on the link in the SELinux Security Alerts screen that says
> > "You can generate a local policy module to allow this access - see
> > FAQ" and it takes me to:
> >
> > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/#id2961385
> >
> > Which is the top of the whole document. :(
> >
> > So, I find the link there that says "To see how to write a simple
> > policy module, check out Local Policy Customizations. " and it takes
> > me to:
> >
> > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html...
> >
> > Which, again, is the top of the whole document. Sigh.
> >
> > Please don't respond with a link to the correct document. Someone
> > needs to fix this. People hate SELinux enough already...
> >
> > Dan
> > --
> > docs mailing list
> > docs(a)lists.fedoraproject.org
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/docs
>
> --
> name: Karsten 'quaid' Wade, Sr. Community Gardener
> team: Red Hat Community Architecture
> uri: http://TheOpenSourceWay.org/wiki
> gpg: AD0E0C41
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: not available
> Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20100917/9459ca...
>
> ------------------------------
>
> Message: 5
> Date: Fri, 17 Sep 2010 17:21:03 -0400
> From: "John J. McDonough" <wb8rcr(a)arrl.net>
> Subject: Re: Fwd: SE Linux docs
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Message-ID: <1284758463.7672.9.camel@Aidan>
> Content-Type: text/plain; charset="UTF-8"
>
> On Fri, 2010-09-17 at 13:32 -0700, Karsten Wade wrote:
> > On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:
> > > Hello Docs team and Publican knowledge-meisters,
> > >
> > > I received this email from a contributor and tested his results. This
> > > appears to be a valid bug. How can we properly link to the interior of
> > > a document on the docs.fedoraproject.org site? All targets seem to
> > > take one to the top of a document, which is not only unhelpful, but
> > > breaks the simple principle of least surprise.
> >
> > We might also want to have SELinux Troubleshooter point to a wiki
> > page, and we can update that wiki page with links to the latest guide
> > or FAQ.
> >
> > It's a bit unclear to me where the bug lies. I see:
> >
> > 1. SELinux Troubleshooter is deep linking when maybe it should go to a
> > wiki page.
> >
> > 2. The SELinux FAQ has a section without an ID tag.
> >
> > 3. The SELinux FAQ has a broken link to itself.
> >
> > - Karsten
> >
> > > Paul
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Dan Haskell <geekus.org(a)gmail.com>
> > > Date: Mon, Sep 13, 2010 at 2:00 PM
> > > Subject: SE Linux docs
> > >
> > >
> > > Clicked on the link in the SELinux Security Alerts screen that says
> > > "You can generate a local policy module to allow this access - see
> > > FAQ" and it takes me to:
> > >
> > > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/#id2961385
> > >
> > > Which is the top of the whole document. :(
> > >
> > > So, I find the link there that says "To see how to write a simple
> > > policy module, check out Local Policy Customizations. " and it takes
> > > me to:
> > >
> > > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html...
> > >
> > > Which, again, is the top of the whole document. Sigh.
> > >
> > > Please don't respond with a link to the correct document. Someone
> > > needs to fix this. People hate SELinux enough already...
> > >
> > > Dan
> > > --
>
> This is a tad confusing because there are multiple things going on. We
> (relatively) recently reorganized docs.fp.o to support Publican
> publishing and managing the site with git. As a result, a lot of links
> in old documents were broken. Sometimes new documents simply replaced
> f12 with f13, which means even some new documents don't point to the
> right place. I believe the site essentially redirects 404's to the top
> of the site.
>
> However, this specific document has some rather peculiar behavior, which
> makes me wonder just how it was produced. Even the table of contents
> doesn't work reliably, something that is not evident on other documents.
>
> In addition, some things on docs.fp.o seem not quite right. We had an
> event last night where over 150,000 pages were committed and I'm not
> sure we have totally recovered from that event.
>
> But, I do think there is something peculiar about this particular
> document, and it might be helpful to rebuild and republish it.
>
> Since you are the author, did you test it before publishing? Does this
> behavior exist on a local copy? Is the copy on docs.fp.o actually the
> same as the one you committed?
>
> --McD
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 17 Sep 2010 17:39:50 -0400
> From: "Paul W. Frields" <stickster(a)gmail.com>
> Subject: Re: Fwd: SE Linux docs
> To: docs(a)lists.fedoraproject.org
> Message-ID: <20100917213950.GQ3855(a)victoria.internal.frields.org>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Sep 17, 2010 at 01:32:46PM -0700, Karsten Wade wrote:
> > On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:
> > > Hello Docs team and Publican knowledge-meisters,
> > >
> > > I received this email from a contributor and tested his results. This
> > > appears to be a valid bug. How can we properly link to the interior of
> > > a document on the docs.fedoraproject.org site? All targets seem to
> > > take one to the top of a document, which is not only unhelpful, but
> > > breaks the simple principle of least surprise.
> >
> > We might also want to have SELinux Troubleshooter point to a wiki
> > page, and we can update that wiki page with links to the latest guide
> > or FAQ.
> >
> > It's a bit unclear to me where the bug lies. I see:
> >
> > 1. SELinux Troubleshooter is deep linking when maybe it should go to a
> > wiki page.
> >
> > 2. The SELinux FAQ has a section without an ID tag.
> >
> > 3. The SELinux FAQ has a broken link to itself.
>
> Possibly:
>
> 4. The subject matter is now explored so widely that the SELinux Guide
> is where we should collect all the material, and then link to the
> appropriate section which has an relatively unchanging URL.
>
> --
> 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/
> Where open source multiplies: http://opensource.com
>
>
> ------------------------------
>
> --
> docs mailing list
> docs(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/docs
>
> End of docs Digest, Vol 79, Issue 15
> ************************************
13 years, 6 months
Fwd: SE Linux docs
by Paul Frields
Hello Docs team and Publican knowledge-meisters,
I received this email from a contributor and tested his results. This
appears to be a valid bug. How can we properly link to the interior of
a document on the docs.fedoraproject.org site? All targets seem to
take one to the top of a document, which is not only unhelpful, but
breaks the simple principle of least surprise.
Paul
---------- Forwarded message ----------
From: Dan Haskell <geekus.org(a)gmail.com>
Date: Mon, Sep 13, 2010 at 2:00 PM
Subject: SE Linux docs
Clicked on the link in the SELinux Security Alerts screen that says
"You can generate a local policy module to allow this access - see
FAQ" and it takes me to:
http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/#id2961385
Which is the top of the whole document. :(
So, I find the link there that says "To see how to write a simple
policy module, check out Local Policy Customizations. " and it takes
me to:
http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html...
Which, again, is the top of the whole document. Sigh.
Please don't respond with a link to the correct document. Someone
needs to fix this. People hate SELinux enough already...
Dan
13 years, 6 months
Docs site
by Mike McGrath
hey guys, something went wrong with the docs site tonight. Not quite sure
what yet but it has increased in size at least double, possibly more. You
can see from the storage watch:
http://tinyurl.com/299s5nz
we went from 7G used to about 12G used. We think that was mostly docs.
here's the dir structure at the moment:
364K fedoradocs.db
8.0K homepage.tmp
4.5G public_html
4.5G web
any ideas? looks like two copies of the same data?
-Mike
13 years, 6 months
Docs Project meeting summary for 15 September 2010
by John J. McDonough
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2010-09-15/fedora-meeting...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2010-09-15/fedora-meeting...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2010-09-15/fedora-meeting...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by jjmcd at 23:00:09 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2010-09-15/fedora-meeting...
.
Meeting summary
---------------
* Roll call (jjmcd, 23:00:16)
* follow up on last week's action items (jjmcd, 23:02:51)
* LINK:
http://meetbot.fedoraproject.org/fedora-meeting/2010-09-08/fedora_docs.20...
(jjmcd, 23:02:55)
* ACTION: Sparks to talk with rbergeron and mo about who will handle
the Release Announcements (jjmcd, 23:10:47)
* ACTION: jjmcd to document the process of translating non-English
source guides (jjmcd, 23:11:00)
* ACTION: Sparks to set default ticket holder to Docs list to allow
everyone ability to see new tickets (jjmcd, 23:11:14)
* ACTION: Meeting Sep 22, Sparks and rudi to chime in with feelings
about making docs group invite only (jjmcd, 23:13:08)
* Release Notes (jjmcd, 23:13:40)
* LINK: https://fedoraproject.org/wiki/Giving_a_document_karma
(jjmcd, 23:16:34)
* Guide Status (jjmcd, 23:18:58)
* ACTION: jjmcd to post the link to sending draft translations to
fedorapeople (jjmcd, 23:23:14)
* ACTION: nb will look into providing a way for infra to create the
l10n drafts (jjmcd, 23:26:46)
* Outstanding BZ tickets (jjmcd, 23:32:53)
* Open Discussion (jjmcd, 23:34:22)
* bethlynn did an outstanding job on OLF (jjmcd, 23:34:38)
* LINK: https://fedoraproject.org/wiki/Etherpad_FAD in Needham,MA
(bethlynn, 23:37:10)
Meeting ended at 23:52:59 UTC.
Action Items
------------
* Sparks to talk with rbergeron and mo about who will handle the Release
Announcements
* jjmcd to document the process of translating non-English source guides
* Sparks to set default ticket holder to Docs list to allow everyone
ability to see new tickets
* Meeting Sep 22, Sparks and rudi to chime in with feelings about making
docs group invite only
* jjmcd to post the link to sending draft translations to fedorapeople
* nb will look into providing a way for infra to create the l10n drafts
Action Items, by person
-----------------------
* jjmcd
* jjmcd to document the process of translating non-English source
guides
* jjmcd to post the link to sending draft translations to fedorapeople
* nb
* nb will look into providing a way for infra to create the l10n
drafts
* **UNASSIGNED**
* Sparks to talk with rbergeron and mo about who will handle the
Release Announcements
* Sparks to set default ticket holder to Docs list to allow everyone
ability to see new tickets
* Meeting Sep 22, Sparks and rudi to chime in with feelings about
making docs group invite only
People Present (lines said)
---------------------------
* jjmcd (115)
* nb (30)
* nathant (20)
* bethlynn (19)
* bcotton (6)
* zodbot (2)
* rrix (2)
* frostbite (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
13 years, 6 months
Giving a document karma
by John J. McDonough
I realized that some of the newer contributors might want to help test
the release notes, but may be a bit put off by all the Koji/Bodhi
mumbo-jumbo.
So, I put together a step-by-step wiki page on testing a document. It
is kind of a long page, not so much because the process is hard, but
because there is a screenshot for almost every mouse click.
You may find my rambling at
https://fedoraproject.org/wiki/Giving_a_document_karma
Thanks for your help
--McD
13 years, 6 months
Please Give Karma
by John J. McDonough
fedora-release-notes-13.95.0-4.fc14 has been pushed to Bodhi and needs
your love. Please download and install this package, check it out, and
give it some karma. This is intended for the Fedora 14 beta.
If you can check it out on KDE, LXDE or XFCE better yet.
Besides U.S. English, the package includes Dutch, Spanish and Ukranian.
You can do a yum localinstall, and then when you are done you can get
back the old RNs with a yum downgrade. Or, if you have a USB stick or
VM of the nightly compose, this is the best way. You can find the
nightly composes at
http://alt.fedoraproject.org/pub/alt/nightly-composes/
Thanks for your help
--McD
13 years, 6 months
UG status at Docs Meeting
by Susan Lauber
Hi All,
I am going to TRY (really really really try) to make the Docs meeting this
week.
I'm a bit behind schedule with the F14 User Guide updates - like I should
have started getting helpers working a few weeks ago :)
But I plan to hammer out as much as I can over the next 10 days -
specifically M-F of next week.
Why post here?
1. give me more incentive to make sure I keep my word and show up :)
2. Help Wanted: Great entry level positions available!
Seriously, this is a great opportunity for new contributors to get
involved. It is real simple:
Install the latest F14 versions (alpha should be fine, Beta candidates are
even better).
Read the current F13 User Guide and note what needs to change for F14.
Some examples of what to look for when reviewing the guide:
Maybe the default GNOME irc client has changed names or been replaced. Is
the old one still available just not default? Tell me something similar (or
even better) different about the new one.
So the default music player is the same but the description is outdated -
what is wrong and needs to be removed? what new features need to be
included.
Are all the URL links still valid?
This guide is intended for "new to Fedora" (and "new to linux") users. We
want to show that we have the apps to do most anything but we also do not
want to bore anyone with lists of features. We also do not want to duplicate
demos and screenshots that are available in upstream documentation and wiki
sites - links are better.
Many chapters can be done in a virtual machine.
I'll take what ever format is offered -
want to checkout the git repo, make changes to a unit, and commit/push it
yourself? wonderfull!
want to checkout the git repo, make changes locally, and send in a patch? no
problem
want to just send me a descriptive email that I can use as checklist to make
the changes? I'll take it (you can send it here, or even better - open a
bug for each section that needs to be changed)
Last release I had a wiki page with the units and their status and a place
for anyone to make a note that they would do a specific unit. I need to
find that page and clear it and update it for F14 then we will be off to the
races. I may not get that done by this week's meeting, but I will have it
done by the end of this week.
Thanks,
-Susan
--
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974
13 years, 6 months
Education with Fedora
by Tezcatl Franco
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Fedoreans!
My name is Jesús Franco and i'm a teacher in a k12 school in a suburb of
Mexico City. My interest in Fedora as the best distro for education
begun a year ago when i met for first time Sugar on a Stick. I'm user of
free software since 4 years ago, and i have collaborated mainly in
translations for riseup.net
Now, in my work for developing course materials for the Sixth Meeting of
Free Education, Culture and Software EDUSOL 2010, i have started to
contributing to the Fedora community with translations of Release Notes,
and several pages in the wiki.
My purpose in this email to you, is starting a discussion about how
could we use (and develop documentation) Fedora for introduction to
literacy informatics, not for children only, but adults too. The ICT's
are transforming all the education panorama, since they are letting
think in new ways, and sharing with enhanced flexibility the knowledge.
We don't need just OLPC, we need too Tutors for adults ;)
We have two Fedora spins aimed "specifically" to education, Fedora-Edu
and Sugar Live. I'm very interested on using Sugar for adults'
education, and i started a page reflecting my own experience.
http://proyectofedora.org/wiki/AlfabetizacionTicAdultos . But i wanted
to share this with these Fedora communities, with the hope of reaching
other educators concerned in those population groups.
I'd like to having too the support of some translators in translating
some Sugar documentation yet done in flossmanuals.net to spanish, and as
contribution of the project "Instalar no es suficiente" to Fedora,
translating to english some materials for a LXDE-spin guide. You see,
i'm not perfect writing in english, even when i translate from english
to spanish. I've seen some mails in docs/trans lists about contributing
documentation non written originally in English, but translating to
English for letting others translators communities reaching the contribs
from LATAM/Spanish fedora people.
Excuse me for cross-posting this time to several lists, i think is
worthy do like this for starting the discussion, but i'll just continue
writing inside the lists that answer to this challenge.
In solidarity,
Jesus (tezcatl) Franco
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAgAGBQJMjxx9AAoJEOhbL7d9uDpZE4MP/i8lTD20V+RkgKwvx1mz+ewR
GVyDXfvNztBDh1uS75qXUSWAfsvydklXZ6vuujgUlnGHDx9RwWORdgkl/Hc9uDTE
aW+HuO1YaMd1dHVDUKcToyKpADKG1c6AlQtULeEaSFc7IydcIZx5WoAN2+B2HqQJ
3RjK6phq4xoyK3mcyv8med6oW8ZLkl+yamSpWl5v8W8qnyuC3ZcYt4gDt2MwaLsK
Gb3sSp2C1UQ+DEiAKnTlGJ/AYIhmw6eDnkU4/Py6kG0jq5dt0+/igS7RSMnLrc2m
bBCXzQ8RUGlM/T2dMh5mfq7TIZTqnJZhUWlwVNnQnK2hjgF/NJCv7Jbaen1YexEg
3Su4/ybR4ocurCzRUmzHR1baFQ9F70ATgeZ9XLXcL3qw4msGkN9u+//g92Zk5C99
XgZzLzqrs5pMarwSXRQdiIvUmp0bBw/Iy14LNU1wgZrBgS7xQEYEE5bfX+gso6/V
/eZlF9TkV07E+p4HFLw+lELNWrHdlWEa8KRI2WXDlhtTz/J7hD2jS4UjppHLD85N
mtNsvP+dXj1H4Evj9dMIITWnLIgpQvkXtKh4s3jHxWcEze6N5AfpWMwL15cFYczK
SHKBsvmTSuMMZJ++OwJZIIFSiFfRSqyR23xSrGSD9JGnT31ywPjC8qx93I5ltPXj
/HXpulnnUtjgQgCn1IcV
=UAkL
-----END PGP SIGNATURE-----
13 years, 6 months
Upcoming Fedora 14 Tasks
by John Poelstra
Start End Name
Thu 02-Sep Tue 21-Sep Generate nightly POT files all fed-rel-notes.rpm
content
Mon 06-Sep Mon 13-Sep Ongoing build translation review htmls
Mon 13-Sep Mon 13-Sep Translation Deadline: Beta Release Notes (PO
Files complete)
Mon 13-Sep Wed 15-Sep Build f-r-n.rpm and Push to updates-candidate
Tue 14-Sep Tue 14-Sep Reminder to Trans that Final Guides POT files
are coming
Tue 14-Sep Tue 14-Sep Beta Change Deadline
Tue 14-Sep Tue 14-Sep Features 100% Complete Deadline
Wed 22-Sep Wed 22-Sep Remind new guide owners SRPM package review
Wed 22-Sep Mon 27-Sep Final Build All Guides: All Languages
Thu 23-Sep Thu 23-Sep Reminder: Send Project Wide-Final Release Notes
Deadlines
Thu 23-Sep Thu 23-Sep Fedora 14 Beta Release Readiness Meeting
Thu 23-Sep Mon 27-Sep Create Beta Announcement (Docs & Marketing)
Mon 27-Sep Mon 27-Sep Build and Post Fedora Technical Notes to
docs.fedoraproject.org
Mon 27-Sep Mon 27-Sep Reminder to Development: Wiki Freeze in 7 days
Mon 27-Sep Mon 27-Sep Build and Post Beta release-notes to
docs.fedoraproject.org
Tue 28-Sep Tue 28-Sep Beta Release Public Availability
Tue 28-Sep Tue 28-Sep Prepare GA Release Notes
Tue 28-Sep Mon 04-Oct Test guides against Beta and correct
13 years, 6 months