Get Connected!

As a national organization, the NCRA/ANREC relies on email listserves to help our members and other people interested in the sector stay in touch, swap stories and ask for advice. Here's the full list of lists:

Pic: Alan Wong wrangling data at CHSR-FM in Fredericton, back in the day (look at the size of that monitor!)

ncralist@ncra.ca: This mailing list is open to anyone who wishes to subscribe, including non-member stations, journalists, academics and the public in general. We maintain this list to promote NCRA and member activities and for the free exchange of information on subjects related to community radio and independent media in general. Low to medium traffic.

ncramembers@ncra.ca: This list connects members and is the main method of communication for advice and questions, announcements, swapping gear and official NCRA business. It is not for promotion of programming or non-station activities. Medium to high traffic.

ncramusic@ncra.ca: This is where Music Directors and other interested music people from stations across the country (regardless of whether or not they’re NCRA members) connect to share charts, discuss trends and challenge each other to messy office competitions. Medium traffic.

nativeprogrammers@ncra.ca: This list is for Aboriginal community radio programmers or people interested in programming about Native news, culture, languages and other issues. Low to medium traffic.

abilities@ncra.ca: This list was originally formed as a place for people to discuss the upcoming "Abilities Handbook" that will help stations become more accessible to people with physical and intellectual disabilities, as well as highlighting some of the amazing work around these issues already being done in our sector. But it's now also morphing into a place where people can discuss accessibility issues within c/c radio more generally. Low to medium traffic.

community@ncra.ca: This list is specifically for community-licensed stations and came out of the community station caucus, to help further discussions about their specific concerns. Low traffic.

ncrawomen@ncra.ca: This is a list for the women of our sector for the purposes of sharing information and ideas. Low traffic.

programming@ncra.ca (NEW!): A list for all things relating to c/c programming. Want to talk about special justice programming, or share PSAs, or share shows that your volunteers are looking to syndicate or ask advice about how to set up a Spoken Word deparment? THIS IS THE PLACE!  

ncragwire@ncra.ca: This list is focused specifically on production and fundraising for the NCRA’s collaborative community news program GroundWire. Medium to high traffic.

sales@ncra.ca (NEW!): This list is for anyone concerned with station advertising, sponsorships or fundraising. We're hoping to get a good mix of questions, concerns, ideas and high-minded debates on best practices. 

ncratech@ncra.ca: An oldie but a goodie. And pretty self-explanatory. 

ncrapacific@ncra.ca: This is a mailing list connecting a number of campus and community radio stations in the Canadian Pacific region. The NCRA can create other regional listservs too, if there are enough folks interested -- just let us know. Very low traffic.

If you want to subscribe to any of these lists email shelley (at) ncra (dot) ca or alan (at) ncra (dot) ca.

Please note that all of the NCRA's listserves are subject to the following rules of conduct, adopted by the NCRA Board of Directors in June 2010.

Rules of conduct:

The online services are meant to stimulate discussion – personal attacks on others will not be tolerated;

Do:

· Feel free to post questions regarding campus and community issues and programming;

Do Not:

· publish, post, distribute or disseminate defamatory, abusive, profane, obscene, threatening or other unlawful materials or information;

· post commercial messages

· engage in persistent off-topic comments, postings or statements;

· send “Spam” (unsolicited or junk email);

· quote personal emails without permission

If you violate these rules, you may be removed from the listserve in question.