[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [security-services] Reminder: please review contributor listsand send updates
Being specially noted may be counterproductive if it ends up being confusing. Several people, including Marc Andressen and I were noted as major contributors to the HTTP spec. I have often had people refuse to believe that I contributed to the draft because they only read the list of people who sent emails to the mailing list. So if you do anything different (which may not be a good idea) make sure it is additional, not in place of. Phill > -----Original Message----- > From: Beach, Michael C [mailto:firstname.lastname@example.org] > Sent: Friday, August 13, 2004 9:43 AM > To: John Kemp; ext Anthony Nadalin > Cc: Eve L. Maler; email@example.com > Subject: RE: [security-services] Reminder: please review contributor > listsand send updates > > > I agree with John. Several folks contributed substantially more time > and effort above and beyond the general active membership. > They deserve > additional recognition. I believe this industry recognition is a > substantial motivation for assuming a leadership role in standards > development. Without leaders, no standards. > > Mike > > -----Original Message----- > From: John Kemp [mailto:firstname.lastname@example.org] > Sent: Thursday, August 12, 2004 7:20 AM > To: ext Anthony Nadalin > Cc: Eve L. Maler; 'email@example.com' > Subject: Re: [security-services] Reminder: please review contributor > listsand send updates > > Hi Tony, > > I believe that the entire TC is already acknowledged in a separate > "acknowledgements" page. I have to admit I don't know what other OASIS > TCs have done, or whether they even all do the same thing, > but it seems > to me that the following things are actually quite important (based on > my experience as an editor both here and elsewhere): > > 1) Active contributors of actual text should be acknowledged > separately > from general TC acknowledgements. I think the reasons for that are > two-fold - i) because contributing actual specification text and/or > substantial comments on specification text generally requires quite a > lot of thought over some sustained period of time - thus, I > think these > contributors should be noted for their additional work and ii) I think > it's also important to tell the public which companies were actively > involved in writing the specifications. > > 2) If a specification is largely based on a previous specification, I > think that the previous editors (if different than the > current editors) > should be listed as contributors, as they have basically > written most of > the text previously. > > I certainly agree that the contribution lists should be as > inclusive as > possible. I think also that it is not only possible, but only > proper to > distinguish between those who have submitted substantive or > substantial > pieces of text for the specifications from those who have contributed > during TC meetings. > > It would certainly be nice, however, if there was some stated (and > perhaps OASIS-wide) policy on what the editor and contributor lists > really meant. > > Cheers, > > - JohnK > > ext Anthony Nadalin wrote: > > > > > > > > >I think that the contributor list should apply to the > current version > >not past versions, so this should be cleaned up. Most other TCs list > >all current voting members as contributors since a what is a > >"contribution" is hard to judge. Lots of folks have > contributed in the > >meetings but not on list or via editing. > > > >Anthony Nadalin | work 512.838.0085 | cell 512.289.4122 > > > > > > > > > "Eve L. Maler" > > > <Eve.Maler@Sun.CO > > > M> > To > > > "'firstname.lastname@example.org > > 08/11/2004 04:53 n.org'" > > > PM > <email@example.com > > .org> > > > > > > cc > > > > > > Subject > > [security-services] Reminder: > > > please review > contributor lists > and > > send updates > > > > > > > > > > > > > > > > > > > > > > > > > > > > >When I prepare the Committee Draft versions, I will fill in the > >Acknowledgments sections of all the specs with the list of current > >members (and we will update it at the OASIS Standard stage). On the > >title pages of all the specs, we still have lists of > contributors; if > >you think your name should appear as a contributor because > you either > >sent in major comments or contributed some wads of text that were > >incorporated by an editor, just let me and Rob know. And if you > >literally edited one of the specs but didn't put your name on as an > >editor, let us know that too. Thanks! > > > >(Note to Maryann: I sent you a wrong description of the > purpose of the > >contributor list earlier; the one above is the correct one..) > > > > Eve > >-- > >Eve Maler +1 781 442 3190 > >Sun Microsystems cell +1 781 354 9441 > >Web Products, Technologies, and Standards eve.maler @ sun.com > > > >To unsubscribe from this mailing list (and be removed from > the roster > >of the OASIS TC), go to > >http://www.oasis-open.org/apps/org/workgroup/security-service s/members/ >leave_workgroup.php >. > > > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/security-services/members/l eave_workgroup.php. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/security-services/members/leave _workgroup.php.