Re: Prioritising which document?
by Rahul Sundaram
Hi
> There's surprisingly little visible change to
> anaconda. The internals
> have been changed to use glade and so the widgets
> etc. look different,
> but I haven't yet seen anything in Test 1 that
> requires changing the
> text as is.
So the current plan is to have a Installation guide
covering the basics and targetting FC4?. Will it be
ready before the final FC4 release is made?. If so we
might choose to explicitly point to the FC4 version in
the release notes
Regards
Rahul Sundaram
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
19 years
test2 release notes enshrined, CVS coming "sometime"
by Elliot Lee
Thank you to all of you, especially Karsten, for getting the release notes
together for FC4test2!
We are definitely getting closer to having CVS access for you all. I
created a blank repository for Fedora docs just a minute ago. The key
issue right now that affects not only you guys but everyone in Fedora is
getting the new account system in place so we can get new contributors
access faster.
One thing I'd like to know now is how you'd like to receive CVS commit
mails for the docs repo. These mails are an important part of the open
development process because they keep individuals accountable for their
changes. :) Is there a mailing list in existence that should receive these
future e-mails? Do we need to set up a new one, and if so, who should
manage it?
Best,
-- Elliot
19 years
RFC - sudo(8) mini-HOWTO [Bug 153750]
by Tommy Reynolds
Earlier on the list we mentioned using sudo(8) in preference to su(1), since sudo(8) doesn't compromise the superuser password. I've dashed off a small tutorial (attached) for your consideration.
Cheers!
19 years
Re: Prioritising which document?
by Rahul Sundaram
Hi
I don't think
> anyone's discussed integrating Xen installation into
> the general
> installation guide for the first cut.
I would like to clarify that this wasnt my intention
either but if xen changes some part of the
installation in a more visible way that the end users
typically has to deal with then its important to
document that changes in a guide targetting fc4
Regards
Rahul Sundaram
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
19 years
Re: Prioritising which document?
by Rahul Sundaram
--- Gavin Henry <ghenry(a)suretecsystems.com> wrote:
> Dear all,
>
> I would like to start the ball rolling on which
> document we should all
> work together to get completed in order for the Docs
> Project to be a
> winner.
>
> In my mind, this would be the Install Guide?
>
I agree with that however I dont think the current
Installation guide is covering FC4 development
(Targets FC3 I believe). I am not entirely sure how
anaconda has changed with respect to xen and other
things. It requires substantial investment in time and
effort if we are planning to release the installation
guide along with fc4
Regards
Rahul Sundaram
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
19 years
Re: Prioritising which document?
by Rahul Sundaram
Hi
> These are good points... I have been rewriting the
> partitioning section
> to point to TLDP HOWTO documents, for now, when it
> comes to topics that
> exceed the scope of a slimmer, simpler Installation
> Guide.
Can you provide a list of such howtos you are linking
to. Not all of the howtos are of the same quality.
Unfortunately some of them can be quite misleading.
Better to review this list and get it done right
Regards
Rahul Sundaram
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
19 years
Fedora Docs Steering Committee [IMPORTANT]
by Karsten Wade
As part of the evolution of the Fedora Project, we have formed a
steering committee to oversee documentation activity. This steering
committee format is now being used throughout the project, and derives
from the meritocracy method running a project.
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee
In essence, the overall Fedora Steering Committee empowers the Fedora
Documentation Steering Committee (FDSC) to run the documentation project
according the guidelines of the overall project. The chair of the
committee (that's me) is then accountable for the entirety of the
documentation process. The chair can delegate any of those tasks, from
writing and editing to managing CVS and Web publication. In fact, the
structure is such that the chair -must- delegate or drown in the
workload.
All committee work is done in the open. Read the charter and process
docs linked from the Wiki page above for more information.
It is a stated goal of Fedora steering committees to be balanced with
members of the Fedora community. This translates as, "People who don't
work for Red Hat." Yet. :)
For this reason, we have formed the first round of the committee with
four members of the community-at-large and three of us from Red Hat.
The FDSC is:
* Gavin Henry
* Karsten Wade (chair)
* Mark Johnson
* Paul Frields
* Stuart Ellis
* Tammy Fox
* Tommy Reynolds
If you want all the gory details of what the committee does and how it
works, read the charter and process docs. These people were picked for
the committee because of merit. In the future, when there is more room
on the committee and/or sub-committees are created, we will be looking
around for other project members who merit inclusion.
One note, regarding CVS access. My understanding is that we are at
least a few weeks away from having the externally available login to
CVS. In the meantime, the members of the FDSC are submitting their
paperwork for gaining CVS access, sponsored by myself. After we get
these four new people working in the FDP CVS tree, the committee will
discuss how and when to open up for requests for CVS access from the
writers and editors on the project.
My objective, in chairing the committee and running the project, is to
get relevant Fedora documentation written. My emphasis is on quality
over quantity. You will see the FDSC active on the list, working out
processes, and working within and without process to get stuff done.
There are advantages to having a minimal amount of order. Many here
would agree with this approach. It is easier to get stuff done. Even
grassroots organizing is organized.
There are also advantages of process. Without enough good process, the
project will not survive. A company can enforce process on their
management of a distro, but for a community to buy into the process, it
must arise from the community. There will be necessary process created
and followed for this project.
Thanks for your time, now and in the future,
- Karsten
--
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/
19 years
List of Table and List of Figures
by Gavin Henry
Dear Guys,
What would I need to change in the xslt files, so when using the book
format, the list of tables and list of figures/examples show on the
index.html page?
Thanks.
--
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 742001
E ghenry(a)suretecsystems.com
Open Source. Open Solutions(tm).
http://www.suretecsystems.com/
19 years
Re: How to submission
by Rahul Sundaram
--- Karsten Wade <kwade(a)redhat.com> wrote:
> On Mon, 2005-04-04 at 05:58 -0700, Rahul Sundaram
> wrote:
> > Hi
> >
> >
> > >
> > > What Rahul suggests is indeed how many people
> have
> > > solicited peer input,
> > > by using fedora-docs-list.
> >
> > which is how LDP peer reviews are done. I have
> > submitted a outline to this list before on that
> >
> >
>
http://www.tldp.org/LDP/LDP-Author-Guide/html/process.html
>
> One difference I see is that the peer review is done
> by an assigned
> person after sending the doc to submit(a)en.tldp.org.
> That peer reviewer
> sounds like our assigned editor.
>
> What we have been practicing with on-list
> discussions seems different
> from that process. It's a step _before_ having an
> editor assigned. For
> right now, this seems to make sense to help get a
> document in good shape
> for editing.
no. peer reviews arent assigned to anyone in LDP .
editors are assigned only after peer reviews are done
by volunteers in the discussion list.
Regards
Rahul Sundaram
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
19 years
