/for those willing volunteers?
It would be a big help if the redhat types here could provide/add to over time, a list of documents that would be helpful, are needed etc?
I.e. a To Do list?
We can all do bits, If rh can say what bits (big.... small chunks) need doing, we can chip in to make it happen? regards DaveP
On Tue, 2004-02-24 at 12:13, Dave Pawson wrote:
/for those willing volunteers?
It would be a big help if the redhat types here could provide/add to over time, a list of documents that would be helpful, are needed etc?
I.e. a To Do list?
We can all do bits, If rh can say what bits (big.... small chunks) need doing, we can chip in to make it happen? regards DaveP
As people email me asking for tutorials to write, I have been suggesting topics. The problem is that I don't hear back from most people after we agree on a topic. I will go through my email tomorrow and send out an email with a list of topics and volunteers. It would help if the volunteers could give a status report of their tutorial. If people don't respond, then we can assume that they changed their mind, and someone else can volunteer for that topic.
Tammy
At 02:26 25/02/2004, Tammy Fox wrote:
As people email me asking for tutorials to write, I have been suggesting topics. The problem is that I don't hear back from most people after we agree on a topic. I will go through my email tomorrow and send out an email with a list of topics and volunteers. It would help if the volunteers could give a status report of their tutorial. If people don't respond, then we can assume that they changed their mind, and someone else can volunteer for that topic.
Unsure how it would be received, but if I saw, on the docs webpage somewhere,
topic X, Dave Pawson (started 1.1.04)
Then I'd be tempted to assume it was still down to me?
What do others think?
regards DaveP
Dave Pawson wrote:
At 02:26 25/02/2004, Tammy Fox wrote:
As people email me asking for tutorials to write, I have been suggesting topics. The problem is that I don't hear back from most people after we agree on a topic. I will go through my email tomorrow and send out an email with a list of topics and volunteers. It would help if the volunteers could give a status report of their tutorial. If people don't respond, then we can assume that they changed their mind, and someone else can volunteer for that topic.
Unsure how it would be received, but if I saw, on the docs webpage somewhere,
topic X, Dave Pawson (started 1.1.04)
Then I'd be tempted to assume it was still down to me?
What do others think?
regards DaveP
Good idea, I like the status report requirement too. Nothing stringent, just a "still working on it" if nothing else. If I was working on a topic and I got hit by a bus, somehow I doubt that my family's first thought would be "we need to alert the Fedora List" There are a million other reasons why someone might stop (or delay) work on their project, and this would allow someone else to pick up if need be. So, if there is no status update after <x amount of time (1 month?)> then that topic would be up for grabs. Some sort of communication attempt prior to reassigning it would be good manners.
On Thu, 2004-02-26 at 23:21, Darrin Auxier wrote:
Dave Pawson wrote:
At 02:26 25/02/2004, Tammy Fox wrote:
As people email me asking for tutorials to write, I have been suggesting topics. The problem is that I don't hear back from most people after we agree on a topic. I will go through my email tomorrow and send out an email with a list of topics and volunteers. It would help if the volunteers could give a status report of their tutorial. If people don't respond, then we can assume that they changed their mind, and someone else can volunteer for that topic.
Unsure how it would be received, but if I saw, on the docs webpage somewhere,
topic X, Dave Pawson (started 1.1.04)
Then I'd be tempted to assume it was still down to me?
What do others think?
regards DaveP
Good idea, I like the status report requirement too. Nothing stringent, just a "still working on it" if nothing else. If I was working on a topic and I got hit by a bus, somehow I doubt that my family's first thought would be "we need to alert the Fedora List" There are a million other reasons why someone might stop (or delay) work on their project, and this would allow someone else to pick up if need be. So, if there is no status update after <x amount of time (1 month?)> then that topic would be up for grabs. Some sort of communication attempt prior to reassigning it would be good manners.
Sure. I am working on a format for the list as well as the best format to put it in to make it easy to maintain.
Tammy
docs@lists.stg.fedoraproject.org
-
Darrin Auxier -
Dave Pawson -
Tammy Fox