At FUDcon, Florian Festi approached me about Docs updating the RPM Guide and the book, Maximum RPM, both of which have gotten a little stale. The RPM Guide was already on our radar, and Ben Cotton has taken point on getting that ready to be worked on.
Maximum RPM is currently hosted at rpm.org, and does not appear to have been built with the old doc tools. There seem to be some specific dependencies on Fedora 8, so there will be a little work converting it to something more up to date.
The other issue, though, is licensing. This probably won't be difficult to deal with but it is something that needs to be addressed. The current copyright holder is Red Hat.
We will probably discuss this at an upcoming Docs Team meeting, but I did want to give everyone a heads-up that this is going on. We may also want to carry on some discussion on an rpm.org mailing list so that community is also aware of the effort.
At this point not much has actually happened. Ben has moved the RPM Guide to git, but I don't think anything else has happened there, I have looked at the Maximum RPM sources and verified Florian's assessment that this isn't a straightforward build, and quaid is aware of the licensing issues.
The RPM Guide is at: git.fedoraproject.org/rpmguide.git
Maximum RPM is at rpm.org/git/max-rpm.git
--McD
McD,
You're right, apart from getting the RPM Guide into git last night, nothing has been done on it yet. When I tried to make it last night, I got some errors barfed at me that were apparently bad enough to prevent the creation of a PDF. I got an intro to DocBook/Publican from jsmith yesterday, so I feel reasonably well-equipped to get it figured out.
BC
On 7/10/09, John J. McDonough wb8rcr@arrl.net wrote:
At FUDcon, Florian Festi approached me about Docs updating the RPM Guide and the book, Maximum RPM, both of which have gotten a little stale. The RPM Guide was already on our radar, and Ben Cotton has taken point on getting that ready to be worked on.
Maximum RPM is currently hosted at rpm.org, and does not appear to have been built with the old doc tools. There seem to be some specific dependencies on Fedora 8, so there will be a little work converting it to something more up to date.
The other issue, though, is licensing. This probably won't be difficult to deal with but it is something that needs to be addressed. The current copyright holder is Red Hat.
We will probably discuss this at an upcoming Docs Team meeting, but I did want to give everyone a heads-up that this is going on. We may also want to carry on some discussion on an rpm.org mailing list so that community is also aware of the effort.
At this point not much has actually happened. Ben has moved the RPM Guide to git, but I don't think anything else has happened there, I have looked at the Maximum RPM sources and verified Florian's assessment that this isn't a straightforward build, and quaid is aware of the licensing issues.
The RPM Guide is at: git.fedoraproject.org/rpmguide.git
Maximum RPM is at rpm.org/git/max-rpm.git
--McD
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
----- Original Message ----- From: "Ben Cotton" bcotton+fedora@gmail.com To: "For participants of the Documentation Project" fedora-docs-list@redhat.com; "Florian Festi" ffesti@redhat.com Sent: Friday, July 10, 2009 8:31 AM Subject: Re: RPM Guide and RPM Max
McD,
You're right, apart from getting the RPM Guide into git last night, nothing has been done on it yet. When I tried to make it last night, I got some errors barfed at me that were apparently bad enough to prevent the creation of a PDF.
I think there is an issue with creating pdf's with the current version of Publican. You might try make-html-en-US
--McD
On Fri, Jul 10, 2009 at 08:05:08AM -0400, John J. McDonough wrote:
At FUDcon, Florian Festi approached me about Docs updating the RPM Guide and the book, Maximum RPM, both of which have gotten a little stale. The RPM Guide was already on our radar, and Ben Cotton has taken point on getting that ready to be worked on.
Maximum RPM is currently hosted at rpm.org, and does not appear to have been built with the old doc tools. There seem to be some specific dependencies on Fedora 8, so there will be a little work converting it to something more up to date.
The other issue, though, is licensing. This probably won't be difficult to deal with but it is something that needs to be addressed. The current copyright holder is Red Hat.
Do we need to update both, or is it sufficient to get all coverage into the new RPM Guide, and make that our focus?
As for licensing:
* Maximum RPM is under OPL + exception (no paper publication without express permission). It has one author, Ed Bailey, and the copyright is owned by Red Hat, probably making re-licensing easy. (We ask, and Legal approves, maybe following a discussion, likely brief and simple, with Red Hat Content Services.)
* RPM Guide is under OPL with no exceptions. It has a single author, Eric Foster-Johnson, whom we'd need to ask to relicense the material.
We will probably discuss this at an upcoming Docs Team meeting, but I did want to give everyone a heads-up that this is going on. We may also want to carry on some discussion on an rpm.org mailing list so that community is also aware of the effort.
At this point not much has actually happened. Ben has moved the RPM Guide to git, but I don't think anything else has happened there, I have looked at the Maximum RPM sources and verified Florian's assessment that this isn't a straightforward build, and quaid is aware of the licensing issues.
The RPM Guide is at: git.fedoraproject.org/rpmguide.git
Did you make this into a git repo using the instructions provided on the wiki? There's a one line log, which looks wrong to me. Since we're just starting out, I would recommend you blow away this git repo and replace it with a fresh one, done by following these instructions:
https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git
Maximum RPM is at rpm.org/git/max-rpm.git
On Fri, Jul 10, 2009 at 9:12 AM, Paul W. Frieldsstickster@gmail.com wrote:
Did you make this into a git repo using the instructions provided on the wiki? There's a one line log, which looks wrong to me. Since we're just starting out, I would recommend you blow away this git repo and replace it with a fresh one, done by following these instructions:
https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git
With help from Paul and Ricky, the RPM Guide has been re-uploaded to git, correctly this time.
On Fri, Jul 10, 2009 at 11:27:32AM -0400, Ben Cotton wrote:
On Fri, Jul 10, 2009 at 9:12 AM, Paul W. Frieldsstickster@gmail.com wrote:
Did you make this into a git repo using the instructions provided on the wiki? There's a one line log, which looks wrong to me. Since we're just starting out, I would recommend you blow away this git repo and replace it with a fresh one, done by following these instructions:
https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git
With help from Paul and Ricky, the RPM Guide has been re-uploaded to git, correctly this time.
We didn't have to help much -- awesome job Ben!
On Fri, Jul 10, 2009 at 09:12:35AM -0400, Paul W. Frields wrote:
Do we need to update both, or is it sufficient to get all coverage into the new RPM Guide, and make that our focus?
+1
A single, canonical RPM guide should be the goal. As Rahul said, updating content from the wiki is important, much has changed. Concepts need vetting, too. Old locations should be deprecated, including the wiki content, once it has been moved. Too much is inaccurate and scattered. One of the best services we can do for rpm.org is to give them a single, canonical upstream to steer.
As for licensing:
- Maximum RPM is under OPL + exception (no paper publication without
express permission). It has one author, Ed Bailey, and the copyright is owned by Red Hat, probably making re-licensing easy. (We ask, and Legal approves, maybe following a discussion, likely brief and simple, with Red Hat Content Services.)
I joined and emailed rpm-maint about this; I haven't seen my join yet (held for approval?), nor the email I sent.
I'm compiling a single list on the wiki of all the content in Fedora and in Red Hat, and now rpm.org, that we want to relicense.
https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA#Specific_content_...
I'm seeing the OPL all over the place - Infrastructure's CSI work, the system-config-* content, etc. I don't think we can do the update in a single swooping move, we'll still find stragglers for some time.
But I don't think I need to take each and every guide individually to Red Hat Legal or Content Services, a list should be sufficient. I'll confirm that with Richard Fontana and Michael Hideo-Smith (after I compile it a bit), but I heard a clear mandate from Legal to move entirely from the OPL to CC BY SA 3.0 Unported in all cases. Content Services also wanted to move all and not selectively. They don't want any stragglers, either.
- RPM Guide is under OPL with no exceptions. It has a single author,
Eric Foster-Johnson, whom we'd need to ask to relicense the material.
Ah, good point. He did that at our request, and it is covered by the CLA, but even simple courtesy says, let's ask. I take care of that.
- Karsten
On Thu, Jul 16, 2009 at 4:56 PM, Karsten Wade kwade@redhat.com wrote:
Ah, good point. He did that at our request, and it is covered by the CLA, but even simple courtesy says, let's ask. I take care of that.
So I made a promise last night that I'd actually get something done on the RPM Guide in the near future. It seems everyone is in agreement that we should absorb Maximum RPM into the RPM Guide and get the Guide up-to-date and maintained.
Quaid, is Eric Foster-Johnson amenable to the re-licensing that we're forcing on the Guide?
Everyone, since this is my first attempt at such work, I'm going to need a lot of help knowing what needs to be changed and how it should look. If you're aware of changes that need to be made, please bombard me with Bugzilla entries or gentle, loving advice via e-mail, etc. I'll hang out in IRC a lot more, too.
I know it's been a while since I volunteered to oversee the RPM Guide, and I feel bad that it has continued to be dormant. I do want to start moving it forward, so any help I can get from the seasoned vets would be great. It's about time I started earning my salary here. :-)
Thanks, BC