Hi Martin, In all honesty the idea of moving HttpClient out of Jakarta Commons to become a full-fledged Jakarta project has been discussed a while ago on HttpClient developer's list. However, at that time we were not sure if HttpClient merited such a promotion.
The decision to offload HttpClient related mail traffic predates most (if not all) current contributors and committers. I personally am not aware of the rationale behind it and I do not know if HttpClient was initially meant to be a Jakarta level project, but simply was not mature enough. Anyways, a request for promotion to Jakarta level may be a very political move. Certainly, we would feel honoured to be considered, but to some HttpClient may be just a utility component and as such appropriately placed in Jakarta commons. On the other hand, based on the mail traffic, Bugzilla content HttpClient has been generating, the size of the community HttpCleint has got, I believe we have long outgrown Jakarta Commons. Martin, how would you advise up to go about this issue? Who shall we approach? Michael, since this is no longer just a Bugzilla issue, I think you, being our project lead, should take over from here Cheers, Oleg On Sat, 2004-01-31 at 22:07, Martin Cooper wrote: > To be honest, I think you need to seriously consider moving HttpClient out > of Jakarta Commons, either to a full Jakarta project or to a TLP. Already, > HttpClient has its own mailing list, and as a result, it has become its > own world, with little relation to the rest of Jakarta Commons except in > name. > > If HttpClient has its own mailing list, its own Bugzilla category, and its > own separate community, there doesn't seem to be much reason to stay > within Jakarta Commons, whereas I see good reasons for it to move out. > > -- > Martin Cooper > > > On Sat, 31 Jan 2004, Oleg Kalnichevski wrote: > > > Good day, > > > > I am approaching you on behalf of the Jakarta Commons HttpClient project > > > > We are wondering if it would be possible to promote Jakarta Commons > > HttpClient to a top level project in Bugzilla. We would like to be able > > to set release versions and milestones specific to HttpClient, which is > > not possible as long as HttpClient remains a sub-component of > > jakarta-commmons. > > > > Please let us know if that's feasible > > > > Cheers, > > > > Oleg Kalnichevski > > > > > > > > On Thu, 2004-01-22 at 21:28, Oleg Kalnichevski wrote: > > > Good day, > > > > > > Following the proposal to migrate Jakarta Commons projects from Bugzilla > > > to JIRA posted to the Jakarta commons-dev list, we would like to have a > > > few points clarified, before the final decision can be made whether > > > Jakarta Commons HttpClient project stays with Bugzilla or migrates > > > (kindly requests to be migrated) to JIRA. > > > > > > * Do you actually encourage migration from Bugzilla to JIRA? Will it > > > make the task of to administering and supporting projects' > > > infrastructure (issue tracking in the first place) easier for you? > > > > > > * Can existing bug reports (including closed ones) be migrated to JIRA > > > in their entirety, if at all? What kind of data would not be migrated > > > automatically? Would existing user accounts be preserved? > > > > > > * We (HttpClient committers & contributors) have been in fact quite > > > satisfied with Bugzilla so far. It has served us well. The only thing we > > > have found constraining is the release management (versions, milestones, > > > etc). As an alternative to migration to JIRA would it be possible to > > > promote HttpClient from a component of Jakarta-commons project to a full > > > fledged top level project with its own set of versions and milestones? > > > HttpClient has already got its own mailing list. HttpClient related > > > content constitutes 20-30% Bugzilla entries for the Jakarta-commons > > > project. I believe this might be the best option, as least as far as we > > > are concerned. I am just not sure it is technically feasible. > > > > > > Cheers, > > > > > > 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]
