THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
- For installation and usage problems, send to cloudstack-users@incubator.apache.org. There are developers who can help you there. Do not send to cloudstack-dev@incubator.apache.org.
- For development discussions, send to cloudstack-dev@incubator.apache.org.
- For requirements on features, send to both cloudstack-users@incubator.apache.org and cloudstack-dev@incubator.apache.org.
- On replying, if you've determined a certain list is not necessary, strip it from the TO/CC line.
- Always use "Reply to All", to keep everyone and mailing list in the thread. Don't be afraid to make a correction if you used "Reply" to single people involved by mistake.
Email Formatting
The CloudStack mailing list works like other mailing lists on the internet. It prefers the following format:
...
Tag | Meaning | ||
|---|---|---|---|
DISCUSS | Discuss a certain topic. Use this tag if you're proposing a feature and is collecting requirements. | ||
VOTE | Voting on a a topic. Use this sparingly and it should be after a discussion has taken place. Before using VOTE, please read the bylaws on what it means. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="816fd60238bff162-4e04e003-43db408b-9d2b8341-12b3cc05adf8acab4e36ee27"><ac:plain-text-body><![CDATA[ | ACS[Release #] | Message regarding a certain release in progress. | ]]></ac:plain-text-body></ac:structured-macro> |
AWSAPI | Email is regarding the AWS API component of CloudStack | ||
DOCS | Email is regarding CloudStack documentation | ||
EVENT | Email is announcing a CloudStack event | ||
MERGE | Use to discuss merging a branch into another branch | ||
PROPOSAL | Use this tag if you are proposing a functional spec, test plan for a feature, and other related documentation. | ||
QA | Email is regarding CloudStack QA effort. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b5a0747bd4579210-6793c249-48854003-8843a32a-9b8bccffb8550eeb8cf33b7a"><ac:plain-text-body><![CDATA[ | RESULT | This tag is used with the VOTE tag to indicate the voting has concluded and the tallying is indicated in this email. The subject line should look like [VOTE][RESULT]. | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d27009c07da27e9f-f6326dca-4de64659-8ea2b080-673a502be93477dc83acc508"><ac:plain-text-body><![CDATA[ | RESOLVED | This tag is used with other tags to indicate that the original poster believes the discussion has been resolved. The subject line should look like [VOTE][RESOLVED]. | ]]></ac:plain-text-body></ac:structured-macro> |
OFFLINE | An email message to indicate a contributor is offline from the mailing list for a certain period of days and replies should not be expected. | ||
WIKI | Emails to discuss Wiki content | ||
CI | Anything related to the continuous integration systems - build, jenkins, automated tests |
Dealing with the List
- Always use "Reply to All", to keep everyone and mailing list in the thread. Don't be afraid to make a correction if you used "Reply" to single people involved by mistake.
- Rude behavior is not appreciated on the mailing list. Always remember that words in email can sound harsher than the intent when you're reading or writing emails.
- Setup filters on tags will help the traffic flow.
- You may not get a reply. Don't be afraid to resend your email after a few days.
- If you're expecting someone to see your email, include them in the CC/TO line after you sent out the initial email and didn't get a reply.
- Communicate often.
...
Overview
Content Tools
Apps