Our release notes "Colophon," which lists all the people who have contributed to the Release Notes, always accumulates names. In the past, we've never stripped out any old names.
However, there is an important question we should resolve: How do we go forward from here? Options include:
1. Leave all the names on the list. a. ...because figuring out when someone's individual contributions are gone is REALLY hard, and people should be credited for that work as long as we think it might still be in the Release Notes or a translation somewhere. b. ...because people drift in and out of Fedora Project work, and shuffling names might not be a good use of time.
2. Erase the whole list and start over each cycle. a. ...because this is reflective of who's working hard on writing, editing, translating, and packaging this edition. b. ...because it's easier to track and makes for a more sane length and meaningful content for the Colophon.
There are probably other options but they all involve some give and take, and more work overall. These options are equally easy to maintain, I think; we just need to discuss them publicly and then pick. The FDSCo should probably decide on a policy in Wednesday's meeting, but it would be good to hear what the L10N and Docs communities think.
Paul W. Frields wrote:
Our release notes "Colophon," which lists all the people who have contributed to the Release Notes, always accumulates names. In the past, we've never stripped out any old names.
However, there is an important question we should resolve: How do we go forward from here? Options include:
- Leave all the names on the list.
a. ...because figuring out when someone's individual contributions are gone is REALLY hard, and people should be credited for that work as long as we think it might still be in the Release Notes or a translation somewhere. b. ...because people drift in and out of Fedora Project work, and shuffling names might not be a good use of time.
- Erase the whole list and start over each cycle.
a. ...because this is reflective of who's working hard on writing, editing, translating, and packaging this edition. b. ...because it's easier to track and makes for a more sane length and meaningful content for the Colophon.
+1 We still can see the contributors' names who worked previous version(s) in those version's colophon, can't we?
noriko
There are probably other options but they all involve some give and take, and more work overall. These options are equally easy to maintain, I think; we just need to discuss them publicly and then pick. The FDSCo should probably decide on a policy in Wednesday's meeting, but it would be good to hear what the L10N and Docs communities think.
Rahul Sundaram ha scritto:
Noriko Mizumoto wrote:
- Erase the whole list and start over each cycle.
Release notes stuff is release specific usually. I would go with this.
Rahul
+1
On Tue, 2008-03-25 at 10:01 +0100, Emmanuel Seyman wrote:
- Paul W. Frields [24/03/2008 17:57] :
- Erase the whole list and start over each cycle.
This seems the best approach but it would be nice if we kept the complete list somewhere on the website for historical purposes.
The info history has this, as do the prior release notes, preserved for prosperity. If we do take option #2, I don't see a need to create yet another list of the same information.
2008/3/24, Paul W. Frields stickster@gmail.com:
Leave all the names on the list.
Erase the whole list and start over each cycle.
+1 for option 2 It would encourage to contribute once more. And it will reflect who is working hard.
regards
Domingo Becker (es)
2008/3/24, Paul W. Frields stickster@gmail.com:
- Erase the whole list and start over each cycle.
+1
- Erase the whole list and start over each cycle.
+1
Old release notes will give credit where it is due, and I think it will encourage more continued participation.
On Mon, 2008-03-24 at 09:53 -0400, Paul W. Frields wrote:
- Erase the whole list and start over each cycle.
This has the consensus, great. Seems from the meeting happening right now we have 100% agreement.
Any volunteer(s) to help with the colophon? This first time is going to be a bit harder because we have to write the how-to documentation as we learn it.
- Karsten
Paul W. Frields ha scritto:
Our release notes "Colophon," which lists all the people who have contributed to the Release Notes, always accumulates names. In the past, we've never stripped out any old names.
...
The FDSCo should probably decide on a policy in Wednesday's meeting, but it would be good to hear what the L10N and Docs communities think.
Why not add a colophon to Install guide and other documents too?
On Tue, 2008-04-08 at 20:16 +0200, Francesco Tombolini wrote:
Paul W. Frields ha scritto:
Our release notes "Colophon," which lists all the people who have contributed to the Release Notes, always accumulates names. In the past, we've never stripped out any old names.
...
The FDSCo should probably decide on a policy in Wednesday's meeting, but it would be good to hear what the L10N and Docs communities think.
Why not add a colophon to Install guide and other documents too?
It's a lot easier to add this stuff than to maintain it. Witness the fact that no one's swept the Colophon beat for the release notes. So while I agree in principle, it needs to be backed up by elbow grease. :-)
-
Cody DeHaan -
Diego Búrigo Zacarão -
Domingo Becker -
Emmanuel Seyman -
Francesco Tombolini -
Karsten Wade -
Noriko Mizumoto -
Paul W. Frields -
Rahul Sundaram