Forgive my top post but this client is problematic. Gave up on working with upstream to fix it.
In the past when changes like this happened they were discussed and an attempt to contact the people effected was made. This is the problem and the most annoying point of this whole action item. I don't care about the change in status, in fact I agree with it I have not been able to be active in quite some time. I have been trying to read the meeting minutes or summaries so that I can speak up if needed or chip in for a very small task. Hopefully in this calendar year things can get back to having more time to contribute.
You know where to find me.
Robert 'Bob' Jensen
----- Original Message -----
From: "Paul W. Frields" <stickster(a)gmail.com>
Sent: Wednesday, April 1, 2009 10:25:42 AM GMT -06:00 US/Canada Central
Subject: Re: Fwd: Your Fedora 'docs' membership has been downgraded
In general, I think any team ought to reach out to people if access
levels need to change for some reason. An example might be packager
group changes, which are typically relayed to fedora-devel-announce.
I think that Eric was discussing the need to put active people in
sponsorship roles on IRC earlier. I talked to him briefly and we
agreed that these sorts of things should go to the list first, to give
plenty of notice. Let's also try and cut Eric a bit of slack while
he's getting the hang of holding the reins of the team -- there's a
lot going on, and I'm sure no slight was intended.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
fedora-docs-list mailing list
----- Forwarded Message -----
Sent: Wednesday, April 1, 2009 9:06:08 AM GMT -06:00 US/Canada Central
Subject: Your Fedora 'docs' membership has been downgraded
sparks <eric(a)christensenplace.us> has downgraded you to user status in the
'docs' group of the Fedora Accounts System This change is
effective immediately for new operations, and should propagate
into the e-mail aliases within an hour.
Firing people via email... bad form. Might as well go all the way and remove my docs membership while you are at it.
Former Fedora Docs Contributor,
Robert 'Bob' Jensen
| Robert 'Bob' Jensen || Fedora Unity Founder |
| bob(a)fedoraunity.org || http://fedoraunity.org/ |
| http://bjensen.fedorapeople.org/ |
| http://blogs.fedoraunity.org/bobjensen |
| http://www.facebook.com/people/Robert-Bob-Jensen/1332998420 |
Earlier today the Fedora Packaging Committee (FPC) looked at two
"obstacles" to Publican-generated documentation. The first was the
naming convention and the second was how Publican handles
the .desktop in the SPEC file. Both passed the FPC.
The FPC did say that we (the Docs Project) need to create a review
process to ask "is this documentation really version specific? is there
value in having multiple releases in the same dist at once?". This is
an important test that we need to develop and handle in-house. This is
NOT a solution to allow all Publican documents but it is a solution for
allowing release-specific documents in Fedora.
Also discussed was the multiple SRPMs that are generated by having
multiple languages for each document. To simplify the process of
reviewing these it was suggested that we use subpackaging. Each SRPM
for each language would be wrapped into a single package.
I'm adding these three items to the agenda for this week's Docs
Tomorrow's string freeze sort of snuck up on us, and we could use all hands
on deck between now and tomorrow night.
There are a few items that need someone to research and develop some content
for, and there are also a few places where we could get some help converting
the wiki content to xml. Fortunately, most of the work is done, but there
are some holes, a few critical, so if you can spare some time, please raise
Even if you are not an expert on something, you can check the beta repo
version against the current and then track down the upstream's release notes
to develop some content. Although it might not be as good as having an
expert do it, it certainly is better than leaving the user hanging.
Places we need content:
- Architecture specific notes
- Networking (Ryan Lerch?)
- Games and Entertainment
- Live spins
- Boot time
- Servers - Mail, Web, Database, File (Andrew Ross?)
- System Daemons
- Server tools
- File systems (David Nally?)
- I have the feeling we are missing some stuff in Scientific and Technical
but I haven't had an opportunity to research it fully
Larger conversion pieces:
(lots of little pieces, tho)
xml conversion requires git access.
The current state of the xml is at
(of course this will change frequently during the day. The real authority
is git, and I will endeavor to keep the latest content pushed.)
So we don't trip over each other, why don't I coordinate the noon to
midnight zulu time period, and hopefully Ryan Lerch can organize the
midnight to noon shift. I assume that Ryan and myself will be doing
anything that someone else doesn't cover.
Hi Docs team,
I didn't know if the IG guru was on fedora-test-list. This seemed
like a worthwhile suggestion; maybe the author could be persuaded to
file a bug!
----- Forwarded message from Gireesh Sreekantan <sgireeshmail(a)gmail.com> -----
From: Gireesh Sreekantan <sgireeshmail(a)gmail.com>
To: For testers of Fedora Core development releases
Date: Wed, 01 Apr 2009 02:29:51 +0530
Subject: Re: Testing the Fedora 11 Installation Guide
> As you can see, essentially what we'd like you to do is to take a look
> at the Fedora 11 Installation Guide as it currently stands - it's at
> http://docs.fedoraproject.org/install-guide/ - and try installing either
> Fedora 11 Beta or current Rawhide according to the instructions found in
> the Installation Guide.
Should section 7.2 of the install guide have more detail about this
As the developer himself recommends, should users be recommended to try
xdriver=vesa before resorting to text mode?
----- End forwarded message -----