docs May 2006

docs@lists.fedoraproject.org

33 participants
52 discussions

yum-software-management
by Rodrigo Menezes 17 May '06

17 May '06

Guys, I finished the translation of yum-software-management to pt_BR. I uploaded the files in CVS. My question, what's the URL for these files? How can I see this? Thanks in advance, -- Rodrigo de Oliveira Menezes Embaixador do Projeto Fedora http://www.projetofedora.org http://www.fedoraproject.org/wiki/RodrigoMenezes

3 5

Minutes of FDSCo Meeting 16th May 2006
by Stuart Ellis 16 May '06

16 May '06

Attending Members: ------------------ Karsten Wade (quaid) Tommy Reynolds (megacoder) Paul Frields (stickster) Stuart Ellis (elliss) Also Participating: ------------------- Bob Jensen (BobJensen) Hugo Cisneiros (Eitch) Schedule of Tasks: ------------------ http://www.fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule Highlights: ----------- * Bob Jensen and Hugo Cisneiros have been voted in as FDSCo members. * Paul: Has received the source for the Red Hat Installation Guide, and is looking at how to progress with it. * Karsten: To send a copy of the Google Summer of Code proposal for developing MoinMoin to the mailing list. Full IRC Log: ------------- https://www.redhat.com/archives/fedora-dsco-list/2006-May/msg00002.html

1 0

TOC for Command Prompt Survival Guide
by James McElhannon 16 May '06

16 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I wanted to propose the following TOC for the Command Prompt Survival Guide, one of the current Doc Ideas... I would plan on submitting this document to the LDP, too. Their equivalent doc is aging and is lite on details. Please let me know your feedback. - --- There are 5 chapters shown below, with the sections numbered. The Concepts chapter sets forth just enough theory to be able to use the commands below. The Scenario chapter would put forth some common scenarios that people would be faced with. The text would describe the usage of a set of commands to perform a task, cross referenced to the Commonly Used Commands section. The Commonly Used Commands would not be a reproduction of the man pages, but would instead focus on the common usage of the command. The Tools would section would be brief scripts to make some things easier. I would expect that the details of this section would arise during the writing of the rest of the text. Any redundant operations shown during the Scenarios would be candidates. Introduction 1. General introduction Concepts: 1. Shells 2. Executables and Processes 3. stdout, stderr, stdin 4. Scripts 5. Permissions 6. Redirection and Pipes 7. Bash prompt customization Scenarios 1. Handling zip/gz files 2. Handling tar files ... ... Commonly Used Commands: 1. basename 2. bash 3. bunzip 4. bzip 5. cd 6. chgrp 7. chmod 8. chown 9. clear 10. cp 11. cut 12. echo 13. expr 14. find 15. finger 16. grep 17. gunzip 18. gzip 19. head 20. hostname 21. info 22. kill 23. ln 24. ls 25. man 26. mkdir 27. more 28. mv 29. ping 30. popd 31. ps 32. pushd 33. rm 34. rmdir 35. rpm 36. set 37. stty 38. su 39. sudo 40. tail 41. tar 42. test [] 43. traceroute 44. uname 45. wait 46. wc 47. where 48. who am i 49. whoami Tools 1. echodo ... ... - --- - -- James McElhannon jlm(a)magnifisys.com MagnifiSys, LLC www.magnifisys.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEUoAa9KWEMihy1VsRAkRoAKCK6SrTfOj88bimwTbfZwhkd/iIvwCcCosD Yc1vIVhw7MEb2b0k7DEaYgI= =zrQY -----END PGP SIGNATURE-----

5 6

MoinMoin<=>DocBook XML Summer of Code Proposal
by Patrick W. Barnes 12 May '06

12 May '06

We have a Summer of Code proposal to work on MoinMoin DocBook XML conversion tools. This student identifies himself as the original author of the existing MoinMoin DocBook XML formatter. There isn't a mentor assigned yet, so if someone from the Docs team would like to step forward to mentor this person, they can sign up as a mentor through Google and we'll assign the proposal to them. Mentor Sign-Up: http://code.google.com/soc/mentor_step1.html Mentor Home: http://code.google.com/soc/mentor_home.html ---- Title/Summary: MoinMoin DocBook XML Conversion Tools Student: Mikko Virkkilä Student Email: mvirkkil(a)cc.hut.fi Student Major: Automation and systems technology Student Degree: masters Student Graduation: 2008 Student Home Page: http://users.tkk.fi/~mvirkkil Organization: The Fedora Project Assigned Mentor: No Mentor Assigned Name: Mikko Virkkilä Email: mvirkkil(a)cc.hut.fi IM: I am going to work during the summer, so I expect to be working on this project during evenings and weekends. As my gf is going to move to another town for the summer, so I'm going to have a lot of time to spare in the afternoons and evenings. In addition to working, I have no holidays, classes or anything else to work around. My school will start again at the end of August. = Experience = I've done development using Java, C/C++, Python and various web related techniques like XML, CSS, Javascript, XSTL, and I'm familiar with database programming. I'm also the administrator of the my Guild's (the Guild of Automation and Systems Technology) server, and know my way around shellscripts and linux. I'm the original author for the MoinMoin->Docbook formatter, so I'm intimately familiar with it, as well as that part of the MoinMoin infrastructure. I've worked on MoinMoin, and did a cleanup of the gnome-app-install program (which was never accepted upstream). I've also worked with TheOpenCD project. I've created the WebSANE sane-frontend (http://websane.berlios.de) = School = I'm studying at the Helsinki University of Techology where I have been studying for 3 years. The department is called Automation and Systemstechnology, but is also geard towards media and communication. = Details = I'm proposing to finish the MoinMoin->Docbook formatter, and fix any bugs that I find. This will in practice mean that some MoinMoin macros will need to be cleaned up. To make sure the formatter will remain working through the development cycles in the future, I will also write tests, with which it is easy to confirm that the generator is still working. All this will also be documented. Also some tools to support working with docbook inside moinmoin will be created. These include a mass exporter and a mass importer. Book importer, which will allow for exporting existing Docbook formatted books in to the wiki from the commandline. Each book will be split in to multiple chapters and pages. What worries me here is the possible loss of information. It is not possible to represent all information in a docbook using the wiki syntax. I'm hoping to find some way around this limitation, probably by embedding the extra information in to the page with one or several special macros. This script will use only readily available tools. It will also upload the necessary images. The Book exporter will format a moin moin page specially created for generating a docbook-book. The page will include links to the different chapters in the docbook. It will format these pages and create a complete docbook from them. For simple docbook books, the results of first importing a book to the wiki, and then exporting it should yield a book equivalent to the original. == Milestones == * 26.5 Start * 5.6. Work on cleanup and bugs in existing formatter done. * 15.6. Proof of concept for book importer * 30.6. Proof of concept for book exporter * 15.7. Storing _all_ information of a dookbook-book in the wiki possible (probably by adding calls to special docbook macros) but possibly not completely implemented. * 30.7 Importing and exporting a book works * 15.8 Tests done. All documentation done. Project done. == Deliverables == * Add any currently missing features incl better table support. * Book exporter in the form of a special moinmoin generator plugin * Tests (possibly unittests, depending no what the MoinMoin developers feel comfortable with) to ensure that the generator works. * Shellscripts to get a complete docbook book from the wiki (or individual pages) complete with images etc. All code will be documented. Usage instructions will be written. = Why me = As I'm the original author of the existing MoinMoin->Docbook code, so I'm very familiar with it. I'm also familiar with some MoinMoin developers, and many parts of the MoinMoin code. I am exited about this project, because many other projects use MoinMoin as their wiki, and I know for a fact that the Ubuntu documentation team have been very interested in using the Wiki as a means to create DocBook pages. For people not familiar to Docbook, who want to write documentation and usage instructions, a wiki will be a simple way to do so. Creating tools for people to collaborate, on writing documentation for open source projects, is to me a worthwile project. ---- -- Patrick "The N-Man" Barnes nman64(a)n-man.com http://www.n-man.com/ LinkedIn: http://www.linkedin.com/in/nman64 Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ --

2 4

Re: Converting XML files to PO
by Pawel Sadowski 11 May '06

11 May '06

Hi again, I am trying to convert XML files to *.po, but I get this error message: http://pastebin.com/706229 Likes as there was something missing... I am not sure what I should do. I will appreciate any help ;) Regards, Pawel Sadowski

2 5

Problems with CVS
by Rodrigo Menezes 11 May '06

11 May '06

Hi Guys, I'm trying to take a look in the CVS and I'm having some problems. I have an approved CLA, I'm in the cvsdocs group but here is the problem: $ export CVSROOT=:ext:rMenezes@cvs.fedoraproject.org:/cvs/docs $ cvs co -c For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs Permission denied (publickey,keyboard-interactive). cvs [checkout aborted]: end of file from server (consult above messages if any) Can someone help me? Thanks in advance, -- Rodrigo de Oliveira Menezes Embaixador do Projeto Fedora http://www.projetofedora.org http://www.fedoraproject.org/wiki/RodrigoMenezes

2 3

Re: desktop-up2date/po - New directory
by Paul W. Frields 10 May '06

10 May '06

On Mon, 2006-05-08 at 02:26 -0700, José Nuno Coelho Sanarra Pires wrote: > Author: zepires > > Update of /cvs/docs/desktop-up2date/po > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14178/po > > Log Message: > Directory /cvs/docs/desktop-up2date/po added to the repository Isn't this a dead document? Or is just a little grey-whiskered? -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Documentation Project: http://fedora.redhat.com/projects/docs/

4 3

Minutes of FDSCo Meeting 9th May 2006
by Stuart Ellis 09 May '06

09 May '06

Attending Members: ------------------ Karsten Wade (quaid) Tommy Reynolds (megacoder) Paul Frields (stickster) Gavin Henry (ghenry) Stuart Ellis (elliss) Also Participating: ------------------- Bob Jensen (EvilBob, and BobJensen) Scott Glaser (Sonar_Guy) RahulSundaram (mether) Schedule of Tasks: ------------------ http://www.fedoraproject.org/wiki/DocsProject/FedoraDocsSchedule Highlights: ----------- - The meeting was taken up with a wide-ranging discussion on the future shape of the Documentation Project. It has become apparent that project the Project needs to evolve, in order to attract and maintain a significant level of contributors. Karsten summarises the plan that emerged: "1. Consolidate Beats into functional groups to work on topic areas 2. Relnotes are only one of the Beats outputs 3. Enable Beat groups to contribute little bits by using a queue within the CMS 3.1 This means each Beat needs a strong leader/editor type 4. Beat groups work on outputting one guide or several tutorials based around their area 5. Incoming docs e.g. RHEL docs, usable LDP or other OPL content, etc. are parsed into the Beats in chunks (chunk == all of the content about a topic area) 6. We ask all writers to choose one or more Beats to join, now and when new; then we can populate their queue with relevant bits to work on. 7. Every content area gets double+ coverage to give relief/back-up" - The Installation Guide and Yum tutorial now need new maintainers, as the current maintainer will not be able to support them for a period of time. Full IRC Log: ------------- https://www.redhat.com/archives/fedora-dsco-list/2006-May/msg00001.html

1 0

testing my pgp/introducing myself
by "Guillermo Gómez S." 09 May '06

09 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First i would like to introduce myself My name is Guillermo Gómez. I live in Caracas/Venezuela and would like to contribute with Spanish translations at all levels for Fedora project. First, i would like to know if im doing it right about PGP, never use it before. I'm using Thunderbird with extensions to manage OpenPGP. I'm signing this email and attaching my public key. Thanks for the help to help ;) kg Guillermo Gómez S. "De la tierra de Bolívar para el mundo." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEVsUqsDkDUAWcF3URAi3AAKCIuWxxZS5Pl4lzydPhXO110sxHdACbBDN6 E7O5FyRwmKm22GRCDayiCrE= =dZGW -----END PGP SIGNATURE-----

4 7

Introduction
by Rodrigo Menezes 09 May '06

09 May '06

Hi guys, My name is Rodrigo, I'm and Fedora Ambassador in Brazil and we are working to distribute and show Fedora Core for a lot of people. One of our interest is to create a extension of Fedora Docs Project but with portuguese documentation, so the people in Brazil can use this files. Today we have the www.fedoraproject.org/wiki/pt, a translation of the original page, I want to create a http://fedoraproject.org/wiki/pt/DocsProject. What do you think? This way we can translate english documentation to portuguese and create portuguese documentation and translate to English. Thanks in advance, -- Rodrigo de Oliveira Menezes Embaixador do Projeto Fedora http://www.projetofedora.org http://www.fedoraproject.org/wiki/RodrigoMenezes

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs May 2006