![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ![]() | ![]() | ![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ![]()
|
Castor Mailing ListsMailing Lists announce user dev user vs. dev Interaction and acronyms Acronyms [XML] or [JDO] Guidelines A note about HTML formatted e-mail Mailing ListsNote: Presently we are hosting three mailing lists. Traffic is not too high, so if you are interested in keeping up to date with new releases, or have problems, questions or feedback please subscribe to the appropriate list. announceannounce Low volume (possibly more than 1 message per week) mailing list for special announcements about Castor, such as new releases.
useruser Moderate volume expected (possibly more than 15 messages a day) mailing list dedicated to the users of Castor. This list will be used by users and committers equally to discuss the following items (amongst many others):
Note: Please familiarize yourself with the guidelines before posting to the list. Archives:
devModerate volume (possibly more than 15 messages a day) mailing list dedicated to the developers of Castor. This list will be used by the main committers to discuss the following items:
We invite everybody (interested) to subscribe to this mailing list, as we believe that feedback from the user community on many of these issues is essential for the progress of the project.
Note: Please familiarize yourself with the guidelines before posting to the list. Archives:
user vs. devPlease use above mailing lists for what they are intended for. Please use the descriptions above to target your message to the correct mailing list. By all means, please avoid cross-posting messages to both lists, as it will decrease the quality of service we would like to offer. Note: Having said that, there might be a valid case for cross-posting a message (e.g. us confirming that a problem is a result of a bug, and hence referring you to 'dev' for further discussions), but in general the use of this should be restricted as much as possible. Interaction and acronymsAs we believe that an effective interaction with the user community is essential for Castor to progress as a project, we have decided to establish a slightly more structured approach in dealing with many of the issues we and you encounter. AcronymsEspecially on (but not necessarily restricted to) 'dev', we will be much more interactive about many of the issues mentioned above. As such, we have decided to structure our messages more thoroughly, and have come up with the following set of acronyms to show our intention:
[XML] or [JDO]Please prefix your messages to all mailing list with either [XML] or [JDO]. This will help us to improve the time it takes us to react to your needs. Having said that, all committers will monitor both areas. GuidelinesThe following are some general "common-sense" guidelines for using the mailing lists: Most people are already following these guidelines. To those people, we thank you. For those of you who are not ... please read carefully. Please be kind and respectful to your fellow castor users. Please refrain from using words and phrases like URGENT, IMPORTANT, MY WIFE WILL LEAVE ME IF YOU DO NOT RESPOND, etc, in the subject line of your postings. Or even in the body of the message for that matter. You may think that things which are URGENT, or IMPORTANT to you, are just as urgent and important to everyone else reading this list. You'd be surprised at just how wrong an assumption like that can be. Please use meaningful subject lines. "Newbie Question", is not meaningful what-so-ever. Please provide necessary information, where applicable. Statements like, "I receive a NullPointerException when using Castor, what's up with that?", are not very helpful, add unnecessary traffic on the list, and will probably never get an answer. As a follow on to #3, when submitting examples, please try to submit the smallest possible example which demonstrates the problem. Short examples are easier to follow and will get quicker responses from developers or other users than long examples with lots of extraneous code/data. Please read the documentation before posting. It doesn't take long and it will save us valuable time from having to answer questions that are already covered in the docs. Please check the mail archives before posting. Many questions on this list have already been answered before. Please refrain from posting confidential information. Once an e-mail is sent to the list, it goes out to all subscribers, including archive engines. We cannot remove or delete messages sent to the list. Once sent they are available for the public to see. If you are unsure about what is confidential or not, check with your manager, supervisor, or the person in charge at your company. If you are going on vacation. Please enjoy yourself. We really want you to have fun and get some much needed rest and relaxation. With that being said and to be perfectly honest none of us really want to receive your automated vacation responses. So please either add a filter to your vacation response so it doesn't get sent to the list or users posting to the list, or simply remove yourself from the list before you go, and add yourself back when you return. Please refrain from sending emails to this mailing list formatted as text/html. Please start a new thread per topic/question. As a result of this, please avoid 'hijacking' existing threads. A note about HTML formatted e-mailAs stated in the guildelines above (see #10), please refrain from sending email to these mailing lists formatted as 'text/html' under all circumstances. Amongst other things, it complicates life for users not working on Windows and decreases usability of the mailing list archives, as it prevents text searches from returning useful results. Additional information why we consider HTML emails to be avoided can be found here. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() ![]() | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() | ![]() | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |