Hello ONAP TSC Members:
We need to decide what tools we want to use to communicate with one another. Commonplace among these tools are email and a developer community wiki, or shared, collaborative, web space of some kind. Let?s start with the email lists. There are 3 set up right now: onap-discuss at lists.onap.org (aka discuss at lists.onap.org) - Distribution list for all general-purpose technical, procedural, and/or community oriented topics. If you want to be involved in the technical development community of ONAP, you should be on this list. The list is self-subscribed (you can do that at lists.onap.org), open to the public and archived (for historical viewing). onap-tsc at lists.onap.org (aka tsc at lists.onap.org) - This is the main/primary list for ONAP Technical Steering Committee (TSC) discussions and decisions. If you are on the TSC, this list is a must for you. If you are part of the technical community and want to stay up-to-date and involved in the leadership, direction, and operations of the project, then you should subscribe to this list. The list is self-subscribed (you can do that at lists.onap.org), open to the public and archived. onap-tsc-private at lists.onap.org (aka tsc-private at lists.onap.org) - This list is maintained by the Linux Foundation and only includes current members of the ONAP TSC and some Linux Foundation staff. This list is nearly *never* used. With very few exceptions (such as when an individual community member's privacy is at stake) this list is not to be used. Instead, all discussions, even those that ultimately only the TSC members can vote on, should be done on the open, public TSC list. We also need go-to place for everything from current events, to developer documentation. In some projects, this is done on a wiki (there are several wiki platforms to choose from), or shared documents (such as google docs ? not recommended here, but mentioned for completeness). The existing ECOMP code base documentation is in wiki form and is still under construction/conversion to proper ONAP nomenclature. In the meantime, I?ve set up a wiki page off of the the Open-O project that we can use temporarily until the ONAP wiki is ready to go. Once that happens, I will move all of the content over and archive the ONAP pages hanging-off-of the Open-O wiki instance. That page is located here, and it has lots of useful information: https://wiki.open-o.org/display/~agrimberg/Temporary+Open+Networking+Automation+Platform+%28ONAP%29+Project+Wiki+Page As you can see when you go there we will try to track ongoing conversations, TSC meeting minutes, TSC and other meeting logistics etc. If you feel something should be on this page and you don?t see it, and don?t have access to edit it, please just send the information to me or Annie Fisher and we?ll get it posted for you. We also need to decide on one or more instant message platforms to use such as Internet Relay Chat (IRC), Slack, WeChat, QQ, etc. for realtime chatting, taking of meeting minutes, etc. Please chime in on your experiences and preferences. Many projects use IRC, and some are starting to use Slack instead. In my opinion it is less important what is used and more important that everyone try to be on it whenever possible during waking hours. A lot of discussion, and collaboration happen through instant messaging in many open source projects. Please respond to this email with your thoughts, suggestions, and/or questions. I look forward to the discussion. Best, Phil. -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.onap.org/mailman/private/onap-tsc/attachments/20170319/cf4c6e6d/attachment.html>
