docs October 2007

docs@lists.fedoraproject.org

32 participants
60 discussions

permissions and access control
by Murray McAllister 09 Nov '07

09 Nov '07

Hi, I have been doing a bit on permissions and access control, will hopefully be finished soon. Is anyone else keen to do the "access control" part, because to be honest, I have no idea what is meant by this. Is this SELinux stuff? Thanks, Murray. PS sorry if this did not wrap :( --------------------------------------------------------------------------------------------------------------------------------------------------------------- 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]

3 5

The KDE-SIG needs (your) help
by Sebastian Vahl 07 Nov '07

07 Nov '07

This is a request for participation: The KDE-SIG [1] is atm lacking active contributors. And we really need some help in doing our job to provide a good KDE version in Fedora - especially with the upcoming KDE 4.0 and the inclusion in Fedora 9. If you don't know how you could help us here is a list (which is also in the wiki): * Packagers: There are so many interesting packages that are not yet packaged for Fedora. Package it to improve the user experience. * Reviewers: Only a few persons are doing the kde-related reviews. Help us reviewing so that more packages could be included. * Testers: If you love KDE use the development version or the updates-testing repository and report bugs, bugs, bugs, request enhancements or features. We need your feedback to improve KDE. * Bugs: Become a BugZapper and help us with kde-related bugs. * Documentation writers: The documentation (esp. the DesktopUserGuide) is GNOME-centered. Help us to provide an equivalent for KDE. * Release Notes: The few people that are working on the new KDE-Spin are quite busy with development issues. If you want to help us in writing the release notes for the next version of Fedora we would give you all the info you need. * Wiki: Maintain http://fedoraproject.org/wiki/KDE and keep it updated with end user information. * Artists: To provide a matching theme for nodoka-metacity-theme and provide an unified desktop experience. But this is not a complete list. If you're interested in making KDE in Fedora better, you're more than welcome. The list of participants in the wiki is atm not a list of active contributors. When setting up the wiki the only demand was an interest in KDE to be listed on this page. This list would be changed in the future to be culled down to the list of active (or reactivated) participants. This has become necessarely because there are only (less or more) 3 active contributors atm (plus Than Ngo). But the list indicates that there are enough people helping with KDE. If you are interested in joining the KDE-SIG please add your name to this list, answer to this mail, join us in #fedora-kde at freenode or attend the weekly KDE-SIG-Meetings (every tuesday 17:00 UTC). I will also add a topic to the agenda of the meeting next week to introduce new contributors. [2] The attendance at the SIG-Meetings is of course not required. But this way we would know of each other. And they are also the main place of discussing the next steps in the development (besides fedora-devel-list). If you have any further questions please answer to this mail or write me directly. And be sure: If your are willing to help you're welcome (regardless of your skills). :) Sebastian [1] http://fedoraproject.org/wiki/SIGs/KDE [2] http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2007-11-06

4 4

Yum Guide bugs
by Paul W. Frields 01 Nov '07

01 Nov '07

Rahul, You had taken up the flag for the "yum-software-management" module (Yum Guide). I would like to assign those bugs to you if you (and any teammates you've assembled) are still willing/able to do this work. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

4 5

F-8 Release Notes pt_BR.po
by Davidson Paulo 30 Oct '07

30 Oct '07

Follow pt_BR.po for Fedora 8 Release Notes. Status: 50 fuzzy, 0 wrong, 6 untranslated. Please somebody commit it. Thanks, -- Davidson Paulo Administrador de Sistemas Linux Certificado LPI Nível 1: LPI000132770 Embaixador Brasileiro do Fedora Líder Nacional do Grupo de Usuários BrOffice.org Editor da BrOffice.org Zine http://davidsonenatalia.blogspot.com/ http://unilivre.sourceforge.net/ http://medwiki.sourceforge.net/ http://natpack.sourceforge.net/

2 2

Re: Reviewing spec file descriptions
by Rahul Sundaram 30 Oct '07

30 Oct '07

Tom "spot" Callaway wrote: > On Wed, 2007-10-31 at 02:49 +0530, Rahul Sundaram wrote: >> 1) For new specs going forward, introduce a mandatory sign-off from >> the documentation team. It wouldn't take more than say 10 minutes for >> every review and anyone interested could do it even as a one off >> process. > > I'm really not crazy about this. I understand what you're trying to > accomplish, but our review process is already painfully slow. We will cause additional slowdown only if the review is otherwise complete but waiting on the docs team sign-off. Could we evaluate it as a option. Maybe mention it in the review guidelines, let us participate and then evaluate making in mandatory later on? > I'd rather let the documentation team go through after the fact and > check the description (and fix-up, if necessary). > > Ideally, the workflow would be: > > 1. New package passes review. Package goes into CVS. > 2. Translatable strings (Summary, Review, etc, etc) get emailed to the > doc team/put into some kind of queue. Ok. How can we make this happen? If anyone in the team wants to get involved and fix the spec themselves, will they get access? > 3. Translation team checks english for correctness, makes a correction > [using some sort of tool] > 4. Translation team translates strings into all languages handled by the > team. > 5. When all langs are ready, task is marked complete, committed to all > branches in CVS. > 6. Maintainer is notified that translations/corrections are done for > that package. Package picks up changes on next rebuild. Seems sane enough. Rahul

1 0

Reviewing spec file descriptions
by Rahul Sundaram 30 Oct '07

30 Oct '07

Hi, Each of the RPM packages in Fedora have descriptions in their spec files and while many of them are good, there are quite a few ones that are vague and not descriptive enough. I think the documentation team should look into this and maybe review guidelines can include a sign-off from someone in the documentation team to verify the quality of the descriptions. This is also very good for new contributors to participate (along with kbase.fedoraproject.org when it's launched) and help out without any long term commitment involved. Comments? Rahul

2 2

Administration-Guide
by Mike Dittmeier 30 Oct '07

30 Oct '07

Ok, I'll blame my lack of progress on being the new kid on the block. I am trying to checkout the existing Administration-guide project from cvs, and finding that there is only an empty shell of a project there as well as the administration-guide-devel project. Am I checking out the wrong project, or are we just starting this project? I have a chapter for Sendmail setup and configuration I would like to incorporate the chapters into the guide as well as other docs that I plan on updating for the following areas: users and groups network dns dhcpd iptables nis ldap dovecot squirrelmail mailman apache vncserver squid vsftpd cups snmpd mrtg webalizer syslog systat amanda Mike "Ditt" Dittmeier, RHCE mike(a)vegasitpros.com pub 1024D/3F08ECFB 2007-09-11 [expires: 2008-09-10] Key fingerprint = 8396 9850 E308 4EFF 1A22 6C5A 4FF5 DF6C 3F08 ECFB uid Mike Dittmeier (Just "Ditt" to my friends) <mike(a)vegasitpros.com> sub 2048g/1E6E4DBD 2007-09-11 [expires: 2008-09-10]

5 8

Re: Administration-guide/servers/sfind with the doc posted at:endmail posted
by Giorgi Shonia 30 Oct '07

30 Oct '07

good job Mike :up: in follow up to our emails today, I thought maybe ssl part can be separated too. and as you mentioned clamav, may be "Permissions and Access Control" better be upgraded to "Security", also covering firewall and seLinux. This is especially desirable if we could depart from self-signed certificates (which is the howtos all over the web) distinguish between authority and owner, and unifying all different services (sendmail, apache, dovecot) under one certificate. and speaking of ssl, I wonder how hard should it be to establish something like ".Fedora" or ca.gnu.org, FOSS kinda certificate authority, to have our brand in online security. member sponsorship and verification based certificate community, which would take us past self-signed "certificate" without giving big bucks to Verisign&Co Giorgi -- pub 1024D/10D99509 2007-10-15 Key fingerprint = F96D 6BB7 0B1D 8432 A7E1 5F3B C65A 510B 10D9 9509 uid Giorgi Shonia <gs(a)gesho.com> sub 1024g/851B4BEA 2007-10-15

2 1

What is more important at this time?
by Mike Dittmeier 30 Oct '07

30 Oct '07

What is more important at this time? Desktop User Guide Administration Guide I am prepared to work on either of the groups, but would like to focus my time on the project the group feels would be more beneficial. Mike "Ditt" Dittmeier, RHCE mike(a)vegasitpros.com pub 1024D/3F08ECFB 2007-09-11 [expires: 2008-09-10] Key fingerprint = 8396 9850 E308 4EFF 1A22 6C5A 4FF5 DF6C 3F08 ECFB uid Mike Dittmeier (Just "Ditt" to my friends) <mike(a)vegasitpros.com> sub 2048g/1E6E4DBD 2007-09-11 [expires: 2008-09-10]

4 4

IRC Log for FDSCo Meeting
by John Babich 30 Oct '07

30 Oct '07

If someone has the IRC log for last night's meeting, post it to the mailing list and I will do the formal process and create an HTML version. Thanks, John Babich Volunteer, FDP

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs October 2007