minutes/log 26-Apr-2005 meeting

[Gavin Henry]

As the Americans say on chat shows, "First of all", I would like to say
sorry for last night. I had my son on my lap, so I could only watch and
not type (it was his Mum night off ;-) ), but here are my comments:

<quote who="Karsten Wade">
> Here are the meta-minutes from the meeting:
>
> CVS Access
>
> * New page is ready for use:
>
> http://www.fedoraproject.org/wiki/DocsProject_2fCvsUsage

Looks great. Well done Paul and everyone!

>
> * Access control for CVS will be social. This means, people are told
>   to be good and are trusted to do so.

I think this has to be the way to go.

>
> * Karsten and Paul will administate CVS for now.  We'll be leaning on
>   Elliot and Tammy for help.  We need to capture a process that
>   describes how to add new users.

With CV access, can a use update anything in the docs module or only what
they have been allocated, I can't remember what was said before?

> * The CVSAccess loosely describes what can get you in trouble or
>   kicked out of docscvs:
>
>   * System cracking of any kind (very bad)
>   * Putting illegal files in CVS (very bad)
>   * Intentionally messing with other people's docs (moderately bad)
>   * Not asking first and making lots of mistakes (minor)

I think this answer my question above, messing with peoples files.

> * CVS ACLs will be used to control high-risk areas under our
>   influence:
>   * Fedora website
>   * CVSROOT
>   * Doc Guide

Fair enough.

> * Karsten will send out group email about CVS that includes our
>   general philosophy, a link to the usage guidelines, and how to apply
>   for CVS.

OK.

> * Karsten will edit the style chapter for the Doc Guide, which will
>   help other editors and writers, and hopefully Karsten can pass on
>   some of his editing tasks at that point.

I'm waiting for some task ;-)

> * Stuart will build a Wiki page about docs in progress, tied to
>   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129807.  We
>   then need to see if anyone needs nudging, help, etc.

Anyway way to have some sort of include that pulls that page into the wiki
and vice versa in order not to duplicate work?

> * Karsten will update the V2 Doc Guide outline to include any process
>   changes/consolidation.
>
> * We're looking into forming a website editing group.  We first want
>   to know the future of fedora.redhat.com.  Then we can write up some
>   more style guidelines that are helpful to page maintainers, and
>   follow-up with editing support for the entire site.

Yes, what do people want on the site?

> * Karsten is working on updates to the FDP pages, with Stuart
>   submitting patches.  The bug to track this is
>   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155642

Checking...

> * Paul and Tammy will work on updating the various CVS sections on
>   f.r.c and in the Doc Guide.  Tammy will update the PHP to create a
>   new function that has CVS in the new location on
>   cvs.fedora.redhat.com.

Gavin will....

Who needs some help?

Thanks.


>
> ## 30 ##
>
> --
> Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
> gpg fingerprint:  2680 DBFD D968 3141 0115    5F1B D992 0E06 AD0E 0C41
>                        Red Hat SELinux Guide
> http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
> --
> fedora-dsco-list mailing list
> fedora-dsco-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-dsco-list
>