I would like to first respond to Nathan's email,
"Not everyone who uses Fedora has easy, unlimited to access to the internet, so at some point we need to get the new Xfce guide available in some downloadable form. But the wiki is definitely a good place to develop the guide."
Great point, never thought about that, we should absolutely cater to those individuals. As far as the format, I'm not really a fan of PDF but I am sure individuals in the mailing lists have some ideas on how to make this portable for users.
Upon brainstorming, I thought that perhaps we use wiki as our testing grounds for what goes into the Official Documentation. We can all decide what makes it in, and while transferring it to Official Documentation we can also create portable formats for users. I think we should branch Wiki documentation into two areas, Stable and Rawhide, because I know some users already compile and use the newest releases and updates for Fedora and we can get a jump start on Rawhide Documentation by allowing those individuals to contribute in that wiki. Rawhide documentation could then transfer into stable after review and finally transfer to official docs prior to Rawhide's release.
On Fri, 21 Jan 2011 15:54:50 -0500 Brock Hudson escapingsummer@gmail.com wrote:
I would like to first respond to Nathan's email,
"Not everyone who uses Fedora has easy, unlimited to access to the internet, so at some point we need to get the new Xfce guide available in some downloadable form. But the wiki is definitely a good place to develop the guide."
Great point, never thought about that, we should absolutely cater to those individuals. As far as the format, I'm not really a fan of PDF but I am sure individuals in the mailing lists have some ideas on how to make this portable for users.
Upon brainstorming, I thought that perhaps we use wiki as our testing grounds for what goes into the Official Documentation. We can all decide what makes it in, and while transferring it to Official Documentation we can also create portable formats for users. I think we should branch Wiki documentation into two areas, Stable and Rawhide, because I know some users already compile and use the newest releases and updates for Fedora and we can get a jump start on Rawhide Documentation by allowing those individuals to contribute in that wiki. Rawhide documentation could then transfer into stable after review and finally transfer to official docs prior to Rawhide's release.
That sounds good to me.
Currently, f13/f14 have 4.6 and rawhide has 4.8, so there will be differences. It would be good to keep them seperate and work on them each.
I like the idea of writing up drafts and getting it put together before we import it into publican to allow widespead docs. :)
kevin
On Fri, 21 Jan 2011 14:05:18 -0700 Kevin Fenzi kevin@scrye.com wrote:
On Fri, 21 Jan 2011 15:54:50 -0500 Brock Hudson escapingsummer@gmail.com wrote:
I would like to first respond to Nathan's email,
"Not everyone who uses Fedora has easy, unlimited to access to the internet, so at some point we need to get the new Xfce guide available in some downloadable form. But the wiki is definitely a good place to develop the guide."
Great point, never thought about that, we should absolutely cater to those individuals. As far as the format, I'm not really a fan of PDF but I am sure individuals in the mailing lists have some ideas on how to make this portable for users.
Upon brainstorming, I thought that perhaps we use wiki as our testing grounds for what goes into the Official Documentation. We can all decide what makes it in, and while transferring it to Official Documentation we can also create portable formats for users. I think we should branch Wiki documentation into two areas, Stable and Rawhide, because I know some users already compile and use the newest releases and updates for Fedora and we can get a jump start on Rawhide Documentation by allowing those individuals to contribute in that wiki. Rawhide documentation could then transfer into stable after review and finally transfer to official docs prior to Rawhide's release.
That sounds good to me.
Currently, f13/f14 have 4.6 and rawhide has 4.8, so there will be differences. It would be good to keep them seperate and work on them each.
I like the idea of writing up drafts and getting it put together before we import it into publican to allow widespead docs. :)
kevin
Sounds good. I will start splitting wiki into stable and rawhide. If anyone else wants to help feel free to email me and we can figure out where each other left off. I will start write ups on rawhide and a user-guide asap as well.
Upon brainstorming, I thought that perhaps we use wiki as our testing grounds for what goes into the Official Documentation. We can all decide what makes it in, and while transferring it to Official Documentation we can also create portable formats for users. I think we should branch Wiki documentation into two areas, Stable and Rawhide, because I know some users already compile and use the newest releases and updates for Fedora and we can get a jump start on Rawhide Documentation by allowing those individuals to contribute in that wiki. Rawhide documentation could then transfer into stable after review and finally transfer to official docs prior to Rawhide's release.
That sounds good to me.
Currently, f13/f14 have 4.6 and rawhide has 4.8, so there will be differences. It would be good to keep them seperate and work on them each.
I like the idea of writing up drafts and getting it put together before we import it into publican to allow widespead docs. :)
kevin
Sounds good. I will start splitting wiki into stable and rawhide. If anyone else wants to help feel free to email me and we can figure out where each other left off. I will start write ups on rawhide and a user-guide asap as well.
Good stuff. Perhaps if we make a list on the wiki of all the topics we want to cover in the guide, a kind of outline of the document structure, then people can just fill in the sections as they go along?
Nathan
Nathan, I like that idea of the outline, perhaps since it involves moving things and creating new pages we should also have a goals and a deadline.
As far as what Kevin stated that there are both 4.6 and 4.8 releases out I certainly think we should focus on 4.8 for now because it will get us started in that cycle of Rawhide > Stable > Official Release notes. 4.6 we can always work on, however 4.8 will be what I am putting my attention on for now so we can get some awesome docs up.
On Sat, Jan 22, 2011 at 4:54 AM, Nathan Thomas <nathan.thomas@peacenik.co.uk
wrote:
Upon brainstorming, I thought that perhaps we use wiki as our testing grounds for what goes into the Official Documentation. We can all decide what makes it in, and while transferring it to Official Documentation we can also create portable formats for users. I think we should branch Wiki documentation into two areas, Stable and Rawhide, because I know some users already compile and use the newest releases and updates for Fedora and we can get a jump start on Rawhide Documentation by allowing those individuals to contribute in that wiki. Rawhide documentation could then transfer into stable after review and finally transfer to official docs prior to Rawhide's release.
That sounds good to me.
Currently, f13/f14 have 4.6 and rawhide has 4.8, so there will be differences. It would be good to keep them seperate and work on them each.
I like the idea of writing up drafts and getting it put together before we import it into publican to allow widespead docs. :)
kevin
Sounds good. I will start splitting wiki into stable and rawhide. If anyone else wants to help feel free to email me and we can figure out where each other left off. I will start write ups on rawhide and a user-guide asap as well.
Good stuff. Perhaps if we make a list on the wiki of all the topics we want to cover in the guide, a kind of outline of the document structure, then people can just fill in the sections as they go along?
Nathan
xfce mailing list xfce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xfce
On 22/01/11 17:25, Brock Hudson wrote:
Nathan, I like that idea of the outline, perhaps since it involves moving things and creating new pages we should also have a goals and a deadline.
As far as what Kevin stated that there are both 4.6 and 4.8 releases out I certainly think we should focus on 4.8 for now because it will get us started in that cycle of Rawhide > Stable > Official Release notes. 4.6 we can always work on, however 4.8 will be what I am putting my attention on for now so we can get some awesome docs up.
+1 to starting with 4.8.
I've begun an outline of the guide structure on my user namespace to get the ball rolling. If anyone can think of a more logical place to put it then do move it - the advantage of using the user namespace for drafts is that it isn't indexed by search engines, so shouldn't mislead anyone if incorrect! And feel free to dive in and start adding stuff - as the Docs Project mantra goes, "it's a wiki!"!
https://fedoraproject.org/wiki/User:Nathant/Xfce_Guide_draft
Nathan