From commits-return-11954-archive-asf-public=cust-asf.ponee.io@hc.apache.org Mon Jan 22 11:26:09 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 8D37A180609 for ; Mon, 22 Jan 2018 11:26:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7D431160C4B; Mon, 22 Jan 2018 10:26:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9D975160C4C for ; Mon, 22 Jan 2018 11:26:06 +0100 (CET) Received: (qmail 92238 invoked by uid 500); 22 Jan 2018 10:26:05 -0000 Mailing-List: contact commits-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list commits@hc.apache.org Received: (qmail 92228 invoked by uid 99); 22 Jan 2018 10:26:05 -0000 Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2018 10:26:05 +0000 Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 5E0823A0A0B for ; Mon, 22 Jan 2018 10:26:03 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1821833 [4/7] - in /httpcomponents/site: ./ css/ httpcomponents-client-4.5.x/ Date: Mon, 22 Jan 2018 10:26:00 -0000 To: commits@hc.apache.org From: olegk@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20180122102603.5E0823A0A0B@svn01-us-west.apache.org> Modified: httpcomponents/site/mail-lists.html URL: http://svn.apache.org/viewvc/httpcomponents/site/mail-lists.html?rev=1821833&r1=1821832&r2=1821833&view=diff ============================================================================== --- httpcomponents/site/mail-lists.html (original) +++ httpcomponents/site/mail-lists.html Mon Jan 22 10:26:00 2018 @@ -1,35 +1,47 @@ - -Apache HttpComponents – Project Mailing Lists + + + + + + + +

Personal Mail

+

Never send a question directly to one of the people you have seen active on the mailing lists, or whose email address you've found in the source code. You will be scorned and rebuffed, or at best ignored.
HttpComponents, as any other Apache project, is a community. Questions asked on a mailing list can be answered by any member of the community who knows the answer and has the time to write it down. Answers sent to a mailing list are available to everyone, through the public mailing list archives. This benefits the whole community.
By sending a question directly to somebody, you are implying that this person alone is responsible for helping you out, and only you. No, we're not. We participate in a community. Post your question to the community at large, and chances are that one of the members will answer it. If that requires information that is of little interest to the community, for example large log files, you will be asked to send such informa tion directly to the person that picked up your question.
It's OK to send a "Thank You" mail to a person that helped you. Just make sure that your next question goes to the mailing list again.

-

Shape Your Mail

-

Some of the people reading your mail will be processing dozens or hundreds of mails daily. To get their attention and a quick reply, it is important that you make your mail easy to read and that you provide the background information that is needed to answer your question. The biggest part of the article on asking smart questions mentioned above addresses this problem, so we'll only give you the highlights here.

-
  • Choose a descriptive Subject for your mail. Not:

    "Help! URGENT: Problem with HttpClient!!!"

    This subject does not give the least indication of what your mail is about. So you have a problem with HttpClient? And you need help? Duh, why else would you post to the mailing list. And it's urgent? For you maybe, but not for anyone else here.
  • Don't send HTML mail, or other stylized mails. Use plain text. Either format it with about 72 characters per line, or just type without linebreaks so automatic formatters can take care of it. Don't format your mails with 90 characters per line. Automatic formatters will split each line, making the result very hard to read.
  • Get to the point. Ideally, keep your mail short. Just describe the problem and give the necessary background information. If it's read in less than a minute, many people will read it and the answer can probably be given quickly as well. If it ta kes several minutes to read your mail, people will take care of other mails first, and may never bother to read yours. If you have to provide extensive background information, make sure to get to the point in the first paragraph. The one that can be read in less than a minute. Describe your problem there, so people can decide quickly whether it makes sense for them to read the rest.
  • Don't Reply to send a new question. If you have an answer or otherwise want to join an ongoing discussion, then use Reply-To on another mail. If you have a new question or want to start a new discussion, do not reply to a mail you've received from the list. Even if you change the subject, your mail client would still flag it as belonging to the existing thread. Many archives and email clients provide a threaded view, where only the initial mail of a thread is shown by default. Your mail will just get ignored by the people not interested in the original thread, even though they might be abl e to help you.
+

Shape Your Mail

+

Some of the people reading your mail will be processing dozens or hundreds of mails daily. To get their attention and a quick reply, it is important that you make your mail easy to read and that you provide the background information that is needed to answer your question. The biggest part of the article on asking smart questions mentioned above addresses this problem, so we'll only give you the highlights here.

+
    +
  • Choose a descriptive Subject for your mail. Not:
    "Help! URGENT: Problem with HttpClient!!!"
    This subject does not give the least indication of what your mail is about. So you have a problem with HttpClient? And you need help? Duh, why else would you post to the mailing list. And it's urgent? For you maybe, but not for anyone else here.
    • +
  • Don't send HTML mail, or other stylized mails. Use plain text. Either format it with about 72 characters per line, or just type without linebreaks so automatic formatters can take care of it. Don't format your mails with 90 characters per line. Automatic formatters will split each line, making the result very hard to read.
    • +
  • Get to the point. Ideally, keep your mail short. Just describe the problem and give the necessary background information. If it's read in less than a minute, many people will read it and the answer can probably be given quickly as well. If it takes several minutes to read your mail, people will take care of other mails first, and may never bother to read yours. If you have to provide extensive background information, make sure to get to the point in the first paragraph. The one that can be read in less than a minute. Describe your problem there, so people can decide quickly whether it makes sense for them to read the rest.
    • +
  • Don't Reply to send a new question. If you have an answer or otherwise want to join an ongoing discussion, then use Reply-To on another mail. If you have a new question or want to start a new discussion, do not reply to a mail you've received from the list. Even if you change the subject, your mail client would still flag it as belonging to the existing thread. Many archives and email clients provide a threaded view, where only the initial mail of a thread is shown by default. Your mail will just get ignored by the people not interested in the original thread, even though they might be able to help you.
-

The Lists

+

The Lists

The HttpComponents project currently uses the following lists. Clicking on a list name will take you to a page with subscribe, unsubscribe, and archive information. See below for information on digests.

-
  • httpclient-users - The list for users of HttpClient, either version 3 or 4. Users of HttpCore can also post their questions here, although most subscribers will probably not be able to answer them.
  • dev - The list for developers of HttpComponents and HttpClient 3. We don't mind getting HttpCore user questions here. Our issues tracker JIRA also posts here.
  • commits - The list for messages from our source code repository. Whenever the source code is modified, a mail with the changes is sent. This list is read-only. HttpComponents committers are expected to subscribe to the commits list, so they can review the changes.
  • private - The list for private communication of the HttpComponents PMC. Only PMC members and ASF members can subscribe. There is no public archive.
-
-

Subscribe And Unsubscribe

-

To subscribe to the list "xxx", send a mail to "xxx-subscribe@hc.apache.org". While you are subscribed, you will receive all mails sent to the list. You can send mails to the list yourself using the address "xxx@hc.apache.org". This does not apply for the commits list, where only the source code repository is allowed to send mails.

-

To unsubscribe from the list "xxx", send a mail to "xxx-unsubscribe@hc.apache.org". Unsubscribe information is also appended to every mail sent via the list.

+
    +
  • httpclient-users - The list for users of HttpClient, either version 3 or 4. Users of HttpCore can also post their questions here, although most subscribers will probably not be able to answer them.
    • +
  • dev - The list for developers of HttpComponents and HttpClient 3. We don't mind getting HttpCore user questions here. Our issues tracker JIRA also posts here.
    • +
  • commits - The list for messages from our source code repository. Whenever the source code is modified, a mail with the changes is sent. This list is read-only. HttpComponents committers are expected to subscribe to the commits list, so they can review the changes.
    • +
  • private - The list for private communication of the HttpComponents PMC. Only PMC members and ASF members can subscribe. There is no public archive.
+
+

Subscribe And Unsubscribe

+

To subscribe to the list "xxx", send a mail to "xxx-subscribe@hc.apache.org". While you are subscribed, you will receive all mails sent to the list. You can send mails to the list yourself using the address "xxx@hc.apache.org". This does not apply for the commits list, where only the source code repository is allowed to send mails.

+

To unsubscribe from the list "xxx", send a mail to "xxx-unsubscribe@hc.apache.org". Unsubscribe information is also appended to every mail sent via the list.

The digest of a list collects all mails of that list, sending you occasional updates. Each update contains the subjects of the recent mails, and the mails themselves as attachments. This significantly reduces the number of individual mails you receive from the list, while still giving you access to all the information.

-

To subscribe to the digest of list "xxx", send a mail to "xxx-digest-subscribe@hc.apache.org". While you are subscribed to the digest, you can send mails to the list itself using the address "xxx@hc.apache.org". This does not apply for the commits list, where only the source code repository is allowed to send mails.

-

To unsubscribe from the digest of list "xxx", send a mail to "xxx-digest-unsubscribe@hc.apache.org". Unsubscribe information is also appended to every mail sent by the digest.

+

To subscribe to the digest of list "xxx", send a mail to "xxx-digest-subscribe@hc.apache.org". While you are subscribed to the digest, you can send mails to the list itself using the address "xxx@hc.apache.org". This does not apply for the commits list, where only the source code repository is allowed to send mails.

+

To unsubscribe from the digest of list "xxx", send a mail to "xxx-digest-unsubscribe@hc.apache.org". Unsubscribe information is also appended to every mail sent by the digest.

-
+
- + +