Hi, Eric, I totally agree with your point regarding “transparency first”, and I think so far ONAP community doing it relatively well:
1. We have bitergia to report all important activities and contributions with a public accessible hosted site of: https://onap.biterg.io 2. Jira tickets system allow everyone to report any issues and check issues there. 3. All projects’ / subcommittees’ weekly meeting open to everyone 4. Etc. Even with our integration testing sessions, we sent invitation to everyone who registered “onap-discussion” maillist. The testing results and videos, (we didn’t post every video since we have recorded 500+ hrs’ testing sessions, but they are available if anyone interested). (Since I am the PTL of Integration project, I talk more on integration point of view.) We have agreed that at Amsterdam release, especially the last few weeks, we will focus on those three “approved” use cases in the selected “gating” open lab, and bugs reported by those places have higher priority, (others are still in our jira site publically available). At the same time, we provided help on other labs when the resource and bandwidth were available. Regarding that SO bug found by you (thank you for your help on testing it, please continue doing so), it happens intermittently and depends on different java classloader’s behavior, and unfortunately (or luckily? ☺) we didn’t hit it at those four use cases testing process. And I am sure there’re more issues we didn’t catch at different infrastructure and use cases. Hopefully we could do better and better in future releases: testing on more clouds is in Integration’s Beijing release road map with the condition of available testing infrastructure. Regards, Helen Chen From: <[email protected]> on behalf of Eric Debeau <[email protected]> Date: Friday, November 17, 2017 at 7:17 PM To: onap-tsc <[email protected]> Subject: [onap-tsc] Transparency first Hello I would like to share some feedbacks from the yesterday TSC. We are working in an open source community with some guidelines from the ONAP TSC Charter “The Open Network Automation Platform (ONAP) will operate transparently, openly, collaboratively, and ethically”. As a result, we must work in a transparent way. We must not hide the problems, issues. At the end of the day, the code will remind us of the reality. There is no perfect software solution in our industry, and we must admit that we may have some issues and we must provide some documentation to avoid discovering them when using ONAP. Let’s go to Beijing ;-) Best regards Eric _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
