I'd like to suggest that we take the Docs/Beats/* pages, and strip out all existing data up through the original FC6 final release. Any remaining content is likely fresh enough for F7 release. That way, we don't risk contributors coming in to the "alpha" release thinking there's no work to do when there's really quite a bit.
I will volunteer to help if we can get enough +1's.
Paul W. Frields wrote:
I'd like to suggest that we take the Docs/Beats/* pages, and strip out all existing data up through the original FC6 final release. Any remaining content is likely fresh enough for F7 release. That way, we don't risk contributors coming in to the "alpha" release thinking there's no work to do when there's really quite a bit.
I will volunteer to help if we can get enough +1's.
Sure. We should do that as soon as we do a non-test Fedora release and write down that as the process we follow after Fedora 7.
Rahul
On Thu, 2007-03-01 at 04:53 +0530, Rahul Sundaram wrote:
Paul W. Frields wrote:
I'd like to suggest that we take the Docs/Beats/* pages, and strip out all existing data up through the original FC6 final release. Any remaining content is likely fresh enough for F7 release. That way, we don't risk contributors coming in to the "alpha" release thinking there's no work to do when there's really quite a bit.
I will volunteer to help if we can get enough +1's.
Sure. We should do that as soon as we do a non-test Fedora release and write down that as the process we follow after Fedora 7.
This page should have the high-level workflow for everything from here forward. It should point out to detailed process pages, where needed. I just added the following:
http://fedoraproject.org/wiki/DocsProject/WorkFlow#ReleaseNotes
I see there being only a few pages people need to know about to get work done in this project:
DocsProject/Join DocsProject/WorkFlow
Everything should be linked out from those pages. The first tells you how to get involved, the other directs you within each activity.
Just a first stab at a simplifying idea for our project docs.
- Karsten
This my friend..is plenty useful.
Will be very useful to have this one stop / process explained page especially to the n00bies.
I also think the ordering works well.
Excellent first stab!
On 2/28/07, Karsten Wade kwade@redhat.com wrote:
This page should have the high-level workflow for everything from here forward. It should point out to detailed process pages, where needed. I just added the following:
http://fedoraproject.org/wiki/DocsProject/WorkFlow#ReleaseNotes
I see there being only a few pages people need to know about to get work done in this project:
DocsProject/Join DocsProject/WorkFlow
Everything should be linked out from those pages. The first tells you how to get involved, the other directs you within each activity.
Just a first stab at a simplifying idea for our project docs.
- Karsten
-- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\
-- fedora-docs-list mailing list fedora-docs-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
On Wed, 2007-02-28 at 17:32 -0500, Paul W. Frields wrote:
I'd like to suggest that we take the Docs/Beats/* pages, and strip out all existing data up through the original FC6 final release. Any remaining content is likely fresh enough for F7 release.
I think I understand what you mean, but not for certain from the way this is worded. If you strip out everything, then there is nothing left to be fresh or stale for F7. But I believe you to mean that you are going to use the Get Info tool to generate a diff of the content added after the date of FC6 release from the content added before that date.
That way, we don't risk contributors coming in to the "alpha" release thinking there's no work to do when there's really quite a bit.
I will volunteer to help if we can get enough +1's.
+1 based on my understanding of the above situation/recommendation.
- Karsten