Hello Danny, Jacques, Nitesh,
welcome in the doc team.
We are planning the docs and the release notes for Fedora 15.
Please, visit this page
and for any questions reach us in this mailing list or on IRC, where
there is always someone that can help you.
A (it) doc team-mate
I am Nitesh Narayan Lal.I am pursuing my bachelors degree in computer science from Manipal ,India ,right now I am about to complete my 2nd year .I am a Fedora lover and appreciator from a long time ,But now I wanted to be a part of the Fedora project .Recently I had made some cross platform applications in Qt(C++) and developed a website for a club using wordpress tool which is certainly quite an easy task (http://www.robomanipal.in).But its been a good learning thing for me .Now I am looking forward to participate in Fedora project .
I love to customize the looks of desktop .I have a knowledge of PHP,C++,JAVA,my SQL,wordpress tool.I could help in themes,wallpapers and stuffs like that if you want .
Besides this I would love to be the part of fedora's wiki page and Fedora Ambassador .
Hoping to listen from you guys soon .
Nitesh Narayan Lal
My name is Danny Stieben. I live near Dallas, Texas, USA, and I'm a
junior in high school. This is my first writing project, though I did
maintain my own blog for a short time. I've been using computer since I
was 5 or 6 years old, and used Linux full-time since the end of 2008.
Therefore, I learn a lot about the operating system I use and know what
to do when I want to do it. I can also type just under 50 wpm.
Currently I'm an Ambassador (for almost a year now), and am in the
process of joining a few more projects within Fedora. I enjoy talking to
people, making graphics, and explaining to people how to do things on
I feel that I am a good match for the Docs project because I always hate
when something is inadequately explained to me, no matter what it is.
Contributing to the Docs project would improve the overall image of
Fedora, which is something I work for. My writing should up to par with
quality, as I've received a couple awards for my writing in academic
Lastly, for the technical stuff...
pub 2048R/8D3706DC 2010-05-02
Key fingerprint = 9562 E497 1115 B0D0 6DF2 D619 76A0 83B9 8D37 06DC
uid Danny Stieben (Fedora Ambassador)
sub 2048R/5C1F8181 2010-05-02
I look forward to working with you guys!
My name is Jacques Boulet. I am currently earning an Associates
of Applied Science in Computer Information Systems here in the U.S. I
have approximately one more year before I earn my degree and I would
like to find something to help me solidify the skills I have already
learned. I would also like the opportunity to learn other skills that I
might not be able learn to in a school environment. Hopefully something
real world that I can use when I find a good career.
I would place my computer skill in the intermediate level. I
know enough to do minor code hacks, write very simple things in Java,
configure and operate servers, etc. Though I am no system admin capable
of running and trouble shooting networks for major corporations, or
leading a software development project. I have a good, solid
understanding of how computer work, and I am learning more everyday.
Furthermore, I am not new to Linux. I have been using it on and
off since 1997 or 1998. The first distribution I used was SuSE 5.2 and
it had KDE 1.0 beta on it. I started using Fedora around F11 and have
really fallen in love with it. I solely run Linux now and have for
about the past four years. Again, I am not capable of being a lead
Unix/Linux system admin for some big corporation, but I am an avid user
of Linux and I do posses a sound understanding of it.
I have also done work, briefly, on the Mephisto Backup Project.
I was in a beginning programming class and knew the founder of that
project. I only helped for about a month before I began to get
overwhelmed with school and work.
SourceForge project page for Mephisto:
Right off the top of my head the most beneficial skill that I
posses for the Documentation project is my use of OOo and MS Word over
the past year with school. I Think I have written enough reports to get
enough experience with those two office suites that I am confident I
can turn out some decent documents.
What I believe would make me a good match for this project is
that I really want to work on my writing skills. I know that English
and grammar are weak points for me and I can't think of a better way to
improve than to write documentation with the whole world as your
Anyway, I look forward to learning more, meeting you guys and
making some new friends.
pub 2048R/29DF0B89 2011-02-12
Key fingerprint = 8A4C 0C4E AFD9 B353 972D 73C5 F2CB 8C93 29DF 0B89
uid Jacques Boulet (Christ 4 Life) <jboulet(a)earthlink.net>
sub 2048R/DE55D6C9 2011-02-12
Wanted to start the conversation early to get people thinking...
Do we want to try to do a hackfest for Docs at SELF? Two years ago
we had a successful hackfest where we packaged software and talked
more about Publican. Last year we did a FAD that was more
generalized. I was thinking that we might spend a day working on
guides and working through QA. Just a thought...
I honestly don't remember when the last time I rebuilt this guide. I
can rebuild and see if this fixes the problem.
---------- Forwarded message ----------
From: Fedora Koji Build System <buildsys(a)fedoraproject.org>
Date: Tue, Feb 8, 2011 at 15:37
Subject: Package: fedora-accessibility-guide-en-US-12.0-2.fc15 Tag:
dist-f15-rebuild Status: failed Built by: ausil
To: ausil(a)fedoraproject.org, voronov(a)fedoraproject.org,
Built by: ausil
Started: Tue, 08 Feb 2011 20:27:53 UTC
Finished: Tue, 08 Feb 2011 20:37:29 UTC
fedora-accessibility-guide-en-US-12.0-2.fc15 (221613) failed on
ppc09.phx2.fedoraproject.org (noarch), x86-02.phx2.fedoraproject.org
BuildError: error building package (arch noarch), mock exited with
status 1; see build.log for more information
Task 2791605 on ppc09.phx2.fedoraproject.org
Task Type: build (dist-f15-rebuild,
Task 2792797 on x86-02.phx2.fedoraproject.org
Task Type: buildArch
Task 2792677 on x86-06.phx2.fedoraproject.org
Task Type: buildSRPMFromSCM
Task Info: http://koji.fedoraproject.org/koji/taskinfo?taskID=2791605
Build Info: http://koji.fedoraproject.org/koji/buildinfo?buildID=221613
On Sat, 2011-01-22 at 12:00 +0000, docs-request(a)lists.fedoraproject.org
> Date: Sat, 22 Jan 2011 06:45:16 +0000 (UTC)
> From: Jes?s Franco <tezcatl(a)fedoraproject.org>
> Subject: Re: Please tutor a crash course on Docs Project tools &
> To: docs(a)lists.fedoraproject.org
> Message-ID: <pan.2011.01.22.06.45.15(a)fedoraproject.org>
> Content-Type: text/plain; charset=UTF-8
> El Thu, 20 Jan 2011 17:56:23 -0500, Christopher Antila escribi?:
> Thank you Christopher for your encouraging words. It's really
> to me for continue this effort. But my proposal was not a document or
> guide covering the topics for beginner contributors. It is for a
> (or two) delivered on IRC as part of the Classroom initiative.
Sorry - I misunderstood what you meant. I do not know much about Fedora
Classroom, but this also sounds like a good idea.
> I'd be glad to write the whole guide (as complement to Publican User
> Guide), but maybe i'm the last person with the knowledge necessary to
> commit that, on this list. I've commited just a few minor tasks, (i'm
> a translator), and maybe my whole knowledge related to DocBook is the
> most basic of HTML and XML.
> However, you can count with when i get the knowledge needed, i'll
> the task for myself. I've even delivered a first class (in my mother
> language, castilian) for my fellow ambassadors on the basics of our
> ticketing system at latam (Redmine). I'm not shy to share even a
> amount of knowledge (should i be?). Just i like to get more knowledge
> do a more valuable contribution.
You can start the project, then learn how to finish it as you go. If you
make a good plan before you start, other contributors might want to help
you finish (I certainly will)! This is one of the benefits of
open-source development. If we had to wait for somebody who knows
*everything* about a project before it starts, we would be waiting for a
very long time.
> At the first very time the QA process was proposed for guides, one
> was something like "peer review" by another Doc contributor, able to
> the whole guide and making proposal for improvement, in the form of
> patches, apart from bugs filed against the guide.
> My feeling is than QA shouldn't be a bureaucratic blocking for writers
> commit the actual writing and maintenance of the guide for continuous
> improvement. It should be a way for let less experienced contributors
> help with the owners of the guides, but we need at least a minimum
> training to do so.
I agree that the QA process should not block writers from committing.
What would be nice is for a QA person to ensure that every Bugzilla bug
has been successfully solved. This can be done after the fix has already
been committed. Also, if a writer, whether new or experienced, wishes to
have their work approved by QA, they could make a bug request.
Hi doc team-mates,
I would like to write some things about accessibility or integrate some
things that already exist in the doc guide and that come in, with F15.
It's rested ... in a draft state
What do you think ?