establish more formal messaging processes for Inrupt
Closed this issue · 1 comments
I think we should move this issue here, it may be moved somewhere else but, I thought it prudent to start an issue as a place to begin the discussion off of the chat so as not to interfere with day to day conversations related to general questions and answers.
@ @d-a-v-i-- In the excitement of a fast-evolving ecosystem representing many voices, an engaged team sometimes can get ahead of itself. We apologize for any confusion or unintentional expectations about a statement to be made by Inrupt today. Monday was offered as time to bring people into the discussion, not a deadline for a specific announcement.
We take our responsibility around transparency very seriously, so we can all learn, improve and better serve the community. In response to your feedback, we are taking steps to improve our clarity (core to being transparent) by establishing more formal messaging processes. If you have questions about transparency anytime please do post them in appropriate channels.
Thank you to the solid community channels for your questions and concerns. Keep them coming, we continue to iterate to do better!
Mike Adams @mikeadams1 18:30
What would Inrupt Formal Messaging Process look like, how would it operate, how long would one have to wait for a response? Is this a security related matter? Is the head of security at Inrupt now taking over the duties as community manager? Should the solid community start a Solid-Security repo?