project.xml updated in CVS HEAD & 2.0 Oleg
On Mon, 2004-05-03 at 19:39, Michael Becke wrote: > Oleg, > > I agree that we are still in need of a better way to track individual > contributions (committers and contributors). The "project team" page is > certainly not the long term answer, but I think we should stick with it > for now. This will ensure that people's contributions are not ignored > and that we don't upset anyone. > > My impression was that a "real solution" was under discussion by the > PMC, but I don't know if anything ever happened there. > > As you mention, I think just adding people to the "project team" page > will suffice for the time being. > > Mike > > Kalnichevski, Oleg wrote: > >> On a related note, Oleg, are you also working on updating the list > >> of > > > > > >> contributors? If not, I will take a look at it. > > > > > > Mike, > > > > I found this to be quite a touchy issue. I have been thinking whether > > there's an acceptable way to inject a little more structure into the > > standard Maven generated contributors page. In particular I'd like to > > be able to mark inactive contributors as, well, inactive ones and > > retired committers as retired ones to give a little more prominence > > to the active ones. I was unable so far to come up with any idea how > > this could be accomplished without taking a risk of upsetting some > > folks and provoking some tensions on the mailing list. I have been > > thinking about some sort 'HttpClient history' page which would > > contain chronological account of important events including credits > > for notable personal contributions, leaving the project team to > > reflect _current_ _active_ participation in the project. However, for > > the Lord's sake no way do I want to provoke no trouble between > > HttpClient contributors and committers thus causing more harm than > > good with my innovation. In my thoughts I was gradually gravitating > > towards not messing around the 'project team' page and simply > > appending new entries to the existing list when you caught me with > > your question ;-) > > > > If there are no better ideas how to deal with the issue, I'll add the > > new entrants to the existing list and get it over with > > > > Oleg > > > > > > -----Original Message----- From: Michael Becke > > [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 2:41 To: > > Commons HttpClient Project Subject: Re: Release notes update. Please > > review > > > > > > Wow, has it been a year already? It seems hard to believe. > > > > Oleg, nice work on compiling the list of changes. This is no small > > > > task. > > > > On a related note, Oleg, are you also working on updating the list of > > > > > > contributors? If not, I will take a look at it. > > > > Thanks, > > > > Mike > > > > On May 2, 2004, at 6:08 PM, Oleg Kalnichevski wrote: > > > > > >> Folks, I just updated the release notes doc to include personal > >> contributions made to HttpClient CVS HEAD since 2.0 was branched > >> out (approx a year from now) > >> > >> http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/ > > > > > >> release_notes.txt?rev=1.19&view=markup > >> > >> If you have contributed code or design ideas during that period, > >> please review the release notes to make sure your contribution is > >> mentioned. > >> > >> If certain contributions are not mentioned, it does not necessarily > >> > > > > > >> mean that they do not deserve mentioning. Going through several > >> hundreds of commit messages is tedious, not great fun, and very > >> prone to mistakes. > > > > > >> I may well have overlooked quite a few things > >> > >> It is important that we keep this document up to date, as one day > >> is > > > > > >> may become the only (easily accessible) vehicle of communicating > >> individual contributions. @author tags may have to be removed, if > >> so decides the Jakarta PMC > >> > >> So, no need to be shy. If there's anything omitted, please do let > >> me know > >> > >> Oleg > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: > > > > > >> [EMAIL PROTECTED] For > >> additional commands, e-mail: > > > > > >> [EMAIL PROTECTED] > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] For additional > > commands, e-mail: [EMAIL PROTECTED] > > > > > > *************************************************************************************************** > > The information in this email is confidential and may be legally > > privileged. Access to this email by anyone other than the intended > > addressee is unauthorized. If you are not the intended recipient of > > this message, any review, disclosure, copying, distribution, > > retention, or any action taken or omitted to be taken in reliance on > > it is prohibited and may be unlawful. If you are not the intended > > recipient, please reply to or forward a copy of this message to the > > sender and delete the message, any attachments, and any copies > > thereof from your system. > > *************************************************************************************************** > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] For additional > > commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
