Re: [RESULT][PMC VOTE] PMC Nominations
All I want to do is write code and manage HttpClient to a full release. Its all I have time for. Already this PMC chaos is taking more time than I want to spend on it. Cool - can you get rid of the logging dependence? I just started using HttpClient because I gave up on the JDK HttpConnection in disgust, and it's not quite drop-in if it requires logging Its open for discussion. Bring it up on the commons-httpclient-dev list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MS vs Open Source link
A good way to handle this is to take the Apache projects, name them something different, add a pretty UI and then sell them for lots of money to those same customers under a more restrictive and closed-source license. I'm in contact with one company that already does this with HttpClient, which is of course completely fine by the license. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMC Nomination
I am not excited by the idea of only PMC members voting on releases to the exclusion of active committers. I'm the release prime for Commons HttpClient where all committers vote on all issues all the time, including releases. HttpClient is somewhat unusual in commons as it is rather a large project with a dedicated mailing list and a rich family where many, such as myself, are primarily focused on just one project, HttpClient. The goal is to make all active committers PMC members. Then what, exactly, is the difference between a committer and a PMC member? I thought the goal was to have the release primes be the PMC members. It is the Project Management Committee after all. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMC Nomination
If the implication is that release management = project management, I don't agree. Typically there can only be one release manager, but it's takes lots of people to keep a project going. Certainly every release manager should forward themselves as PMC nominees, but the body of qualified candidates is much larger. Well said Morgan. Point taken. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMC Nomination
It is not to the exclusion of active committers. Http-client is part of jakarta-commons - and acording to the charter any jakarta-commons committer ( which is close to all jakarta ) can vote. As you probably know - only those who are really interested do that. I agree that we're not yet ready to have PMC votes on releases - we need to expand the PMC and include more people. Even when this will happen, I think the committer votes should be counted as well. That is reassuring Costin. To clarify HttpClient and voting, we absolutely *do* recognize all votes from all commons committers. Votes are held on the the same list where the httpclient discussions take place, the commons-httpclient-dev list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMC Nomination
Completely agree. We should see what the new PMC roles/responsibilites are before accepting PMC membership. robert burrell donkin wrote: On Tuesday, February 18, 2003, at 11:42 PM, Stephen Colebourne wrote: Yesterday I received the Jakarta Monthly Newsletter. Interesting as always, until I got to the section on PMC nominations. There, I suddenly found my name listed as elected to the Jakarta PMC. This came as a complete surprise and shock to me. When I followed the relevant link, I discovered that a discussion had taken place on this list, but I was not subscribed to general@jakarta (unless I' m mistaken, I'm not required to subscribe). At no point was a personal email sent to myself (or I guess the others nominated). I feel as though I have been pressganged. actively inviting new PMC members to join is something that i think should be done. in the same way that a developer receives a letter from apache (after a successful vote) inviting them to become a committer, i'd say that committers who have been voted onto the PMC should receive a letter explaining the role of a PMC member and asking them if they'd be willing to join. - robert - 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]
NOMINATE HttpClient committers
I would like to nominate the following committers from the Commons HttpClient project to the PMC. They are all very active and have been for many months. There are other committers that could be nominated, but the following are those whose primary association to Jakarta is through HttpClient: Jeff Dever [EMAIL PROTECTED] (me) Ortwin Glück [EMAIL PROTECTED] Oleg Kalnichevski [EMAIL PROTECTED] Jeff Dever HttpClient release prime - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DRAFT1] Jakarta Newsletter - January 2003
Commons HttpClient Release 2.0 Alpha 2! After many months and a great resurgence of developers, the new build of /HttpClient/ is finally here. The new group of developers has done extensive refactoring to move the project along the new vision. The code base has reached a significant level of maturity and we expect that another released build (possibly a beta) will be ready near the end of February Also check out the new /HttpClient/ logo on the website created by Jeff Dever with the Gimp! http://jakarta.apache.org/commons/httpclient/ Rob Oxspring wrote: Jakarta Newsletter == Issue: 7 Date: January 2003 Url: http://jakarta.apache.org/site/news/200301.html TODO Contents General Lucene General === Ideas, suggestions, and comments on the overall Jakarta project Editor: Rob Oxspring Robert Simmons kicked of a debate over the use of forum software to make it easier for users to get involved with jakarta subprojects [1,2]. The Jakarta developers seemed united in preferring mailing lists and pointed out archives [3] and services such as gmane [4] for more casual use of the lists. The Pluto subproject was proposed as a reference implementation of the Portlet API and was heavily discussed [5]. Relating to the portals theme, Charon was propsed ro implement the Web Services for Remote specification, although this recieved only a little discussion [6,7]. Dani Estermann asked for some advice on choosing a logging stratergy for future code. Some advocated using the JDK logging if Java 1.4 was guarenteed, others recommended using Log4j whatever the situation. It was also suggested that the use of a facade such as commons-logging should be limitted to situations where chioce is needed. Browse the archive for further detail [8]. Is it time for a new look Jakarta? Maybe a unified Apache site look and feel? Christoph Wilhelms suggested the use of his FakeForrest skin to give Jakarta a facelift [9]. This offers a Forrest[10] look a like and could act as a stepping stone towards the eventual use of forrest for the websites. [1] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=305266 [2] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=309508 [3] - http://archives.apache.org/eyebrowse/ [4] - http://www.gmane.org/ [5] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=308677 [6] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=308715 [7] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=308716 [8] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=314971 [9] - http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]by=threadfrom=315699 [10] - http://xml.apache.org/forrest/ Lucene == A high-performance, full-featured text search engine Editor: Otis Gospodnetic This month's notes come straight from Lucene's CHANGES.txt file. In addition to that I'll only mention that the Lucene team is preparing for packaging the first release candidate for the 1.3 release. a. Queries are no longer modified during a search. This makes it possible, e.g., to reuse the same query instance with multiple indexes from multiple threads. b. Term-expanding queries (e.g. PrefixQuery, WildcardQuery, etc.) now work correctly with MultiSearcher, fixing bugs 12619 and 12667. c. Boosting BooleanQuery's now works, and is supported by the query parser (problem reported by Lee Mallabone). Thus a query like (+foo +bar)^2 +baz is now supported and equivalent to (+foo^2 +bar^2) +baz. d. New method: Query.rewrite(IndexReader). This permits a query to re-write itself as an alternate, more primitive query. Most of the term-expanding query classes (PrefixQuery, WildcardQuery, etc.) are now implemented using this method. e. New method: Searchable.explain(Query q, int doc). This returns an Explanation instance that describes how a particular document is scored against a query. An explanation can be displayed as either plain text, with the toString() method, or as HTML, with the toHtml() method. Note that computing an explanation is as expensive as executing the query over the entire index. This is intended to be used in developing Similarity implementations, and, for good performance, should not be displayed with every hit. f. Scorer and Weight are public, not package protected. It now possible for someone to write a Scorer implementation that is not in the org.apache.lucene.search package. This is still fairly advanced programming, and I don't expect anyone to do this anytime soon, but at least now it is possible. g. Added public accessors to the primitive query classes (TermQuery, PhraseQuery and BooleanQuery), permitting access to their terms and clauses. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
No reply from root
I am the release prime for the commons-httpclient component. I have made several attempts to have a user added as a committer, but there is no response from multiple requests to [EMAIL PROTECTED] Can someone please: 1) determine if someone is actually reading the mail sent to root. 2) create a committer account for this very deserving contributor. New committer: Oleg Kalnichevski [EMAIL PROTECTED] Project: Jakarta Commons HttpClient Userid: oleg Voting results: +1 Jeff Dever [EMAIL PROTECTED] +1 Dion Gillard [EMAIL PROTECTED] +1 Ortwin Gluck [EMAIL PROTECTED] Thanks, -jsd -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Short Apache licence for source files
Interesting. All the HttpClient files have the full form. It would be nice to simply refrence the actual license file, if this is acceptable. Darrell DeBoer wrote: G'day, I know this has been discussed before, but has any progress been made on a short version of the Apache licence for source files? Most source files in James use the following: /* * Copyright (C) The Apache Software Foundation. All rights reserved. * * This software is published under the terms of the Apache Software License * version 1.1, a copy of which has been included with this distribution in * the LICENSE file. */ I don't know where it started, but if someone can someone tell me definitively that this is against ASF rules, I will move to rectify the situation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [TEST] Please ignore...
You are safe Pier ... live long and prosper. Pier Fumagalli wrote: Either this message goes in the newsgroup or I'm going to kill myself... Pier -- To unsubscribe, e-mail: mailto:general-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:general-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:general-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:general-help;jakarta.apache.org
