The Corona development
community is diverse. Its members are located in multiple continents as
well as timezones. Consequently, successfully communicating with the
community members can be a challenge because it lacks instant feedback commonly
associated with verbal communications.
The following are some suggestions to improving
communications within an OSS
development community.
- Use the newsgroup for communicating with the “user”
community.
- Use the development mailing
list for communicating with the “development” community.
- Post reference information to
the wiki
- Use Bugzilla to track issues.
- Update the issue’s
status to reflect its current state
- Post comments to maintain the issue’s
history
- Use email for discussion
threads for design/implementation/maintenance issues
- Be aware that emotions (mostly
negative) are often read into many messages
- Use Emoticon when appropriate :-)
(http://en.wikipedia.org/wiki/Emoticon)
- When making a request, please
specify a due date when you need the request completed.
- If a response is needed, try to
respond as soon as possible.
- If you are not able to take action
within a reasonable amount of time…
i.
Acknowledge you received the
ii.
Let the sender know when you will be
able to respond
- Participate in instant
messaging (IM) / chat
- Make yourself available as if
a team member has walked up to your cube and asked a quick question
- Any long dialog / conversation
that may be of interest to the community should be posted to the wiki or
dev mailing list.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
