Define Communication Channels for the Project

[ssteinbuss]

To ensure effective and organized communication within our community, it is essential to establish clear and dedicated communication channels. This will help streamline our discussions, support, and collaborations, making it easier for all contributors to engage and stay informed.

I propose that we utilize the following communication channels for our project:

• Mailing List: For formal announcements, important updates, and discussions that require more in-depth conversation.
• GitHub Discussions: For casual conversations, questions, feature requests, and other project-related interactions that can benefit from the visibility and structure provided by GitHub.

Proposed Solution

• Utilize the existing Mailing list of the project.
• Utilize GitHub discussions.
• Document the communication channels: Update the README and CONTRIBUTING documents to include information about our communication channels, how to access them, and what types of discussions are best suited for each channel.

Action Items

• [ ] Create categories and guidelines for GitHub Discussions.
• [ ] Update the README and CONTRIBUTING documents to include information about the mailing list and GitHub Discussions.

[ssteinbuss]

Announced the mailing list here, too.

https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol/discussions/24

Need to add this to the Contributing file and the Readme