Hi Chapel Community --
A few weeks ago, we kicked off a Chapel Facebook page as a means of
communicating about Chapel-related events in a lighter-weight, more
conversational way than the traditional SourceForge mailing lists. For
example, recent posts have included announcements of:
* the third and final part of the "Why Chapel?" series of blog articles
* a pointer to the hot-off-the-presses detailed release notes for v1.10
* a regressions week effort being undertaken by the Cray team (as we speak!)
* and of course, announcements that we'd also post to the mailing lists,
like the 1.10 release and upcoming SC14 activities.
The page also includes a historical timeline of significant events in the
project's history (which we'll try to continue to add to over time).
This page is available for viewing whether you have a Facebook account or
not:
https://www.facebook.com/ChapelLanguage
For those of you who do, we invite you to "Like" the page in order to get
a mix of Chapel activites posted regularly to your newsfeed and help
spread the word.
Chapel Mailing Lists
--------------------
While discussing Chapel communications, it's worth reviewing the major
Chapel mailing lists at SourceForge:
* chapel-announce: a "broadcast-only" list that we try to use sparingly
(less than a dozen times a year) to announce things like releases,
calls for participation in high-profile Chapel events like CHIUW and
SC, and the like. Mails to this list also forward to the following
three community discussion lists, so there's no need to subscribe to
it unless you don't want to belong to the following ones.
* chapel-users: a community list for users, developers, and fans of the
Chapel language to discuss the language and its implementation. Note
that bug reports or "Why is my build not working?" types of mail
should typically be directed to chapel-bugs rather than here.
* chapel-developers: a community list for developers and those who want
to pay attention to Chapel's implementation effort.
* chapel-education: a community list for educators interested in using
Chapel in their courses and interacting with similarly-minded folks.
* chapel-bugs: a place to wrestle through anything that isn't working
as expected or advertised.
There are also a few lists whose contents are auto-generated by code
commits (chapel-commmits) and nightly testing (chapel-test-results-*) for
those who are deeply involved in the development.
Any of these lists can be subscribed to or browsed at SourceForge:
http://sourceforge.net/p/chapel/mailman/
Chapel Webpage
--------------
For those who prefer a pull-based method of getting information, the
Chapel webpage is your best bet, where the front page will typically point
to the most interesting recent content and the "What's new?" section will
point to most any added content of significance:
http://chapel.cray.com/
http://chapel.cray.com/whatsnew.html
Chapel-developers chatroom
--------------------------
Finally, for Chapel developers, there is a chapel developers IRC channel for
real-time discussions with others who happen to be logged in at the time. See
the "Developer Resources" page at chapel.cray.com for details.
We hope that the community is able to hear about Chapel in the ways that suit
them best using these methods. If you have feedback on ways in which
additional modes of communication could be improved or enhanced, please
let us know.
Thanks,
-Brad
(on behalf of the Chapel community)
------------------------------------------------------------------------------
_______________________________________________
Chapel-announce mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-announce
------------------------------------------------------------------------------
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
