Hi Pifta, Thank you for chiming in.
I have actually not considered how to revive the mailing list for technical and design discussions. I am not sure why mailing lists are no longer as popular, in general I see a decline of using emails for discussions other than formal one way communication. I agree that the mailing list has more control over the data shared vs. hosting it on Github. Github Discussions do have lower friction than switching to email to discuss. For design my personal preference is markdown and PRs Example: https://github.com/apache/ozone/pull/6121 This is something I insisted we do for the container reconciliation design. One other aspect I wanted to bring up, there are many new contributors from China and China has its own eco system of messaging and chat apps where the community interacts. I would like to hear from them as well for a suitable approach to keep discussions out in the open and not behind closed walls of apps such as Slack or Weibo. In the note we leave in Slack and other documentation we can encourage both mailing lists as well as Github Discussions. Regards, Ritesh > On Jan 31, 2024, at 9:31 AM, István Fajth <fapi...@gmail.com> wrote: > > Hi Ritesh, > > thank you for the proposal, and taking action during the last community > sync. > I support the idea of using GitHub Discussions, but I would like to bring > up one thing with GH Discussions. I am not a fan of Slack either and I > agree Slack is far from optimal and is hard to search. > > It did not happen with Ozone, but as I remember there were projects that > have been migrated to github and before that they were running in a > different system, this makes me skeptical, as it might happen in the future > also. > So I would like to add one more thing to the table, mailing lists will > remain with us (as they are within the control of the foundation), and are > also indexed by search engines. > > In my opinion to move the operational problems and questions to github > discussions is definitely ok, as I see the value of having a dedicated > place where user centric questions are collected and discussed. > In the meantime I think we should promote the dev@ list for technical > discussions that are about design, code, or for any other topic that > really is affecting mainly the developer community. > > Looking at our @dev mailing list, it is pretty silent recently even though > we are working on stabilization, performance, and features. (I myself am > also guilty and silent, I realized and would like to change that, instead > of just doing things within JIRA and PRs.) > > So I am absolutely +1 for using github discussions in favor of Slack for > user/operational problems, I think it is more engaging than the user@ list > for operational questions and can be our place to help out those members of > the community who use Ozone, but I would still use the dev@ mailing list > for technical/design discussions and any other developer related > discussions/decisions as that remains within Apache, and for us it can > become a place where we can look for specific information. > This is my preference of course, but I felt it important to emphasise, as > from your mail it is not clear for me if/what is our plan with the mailing > list usage, as discussions and slack are probably both a contributing > factor to the relative silence of the mailing lists. > > Regards, > Pifta > > Kernel Time <kernelt...@gmail.com> ezt írta (időpont: 2024. jan. 30., K, > 23:01): > >> We started using https://github.com/apache/ozone/discussions from May 2023 >> and this has been a good place for developers to reach out to the community >> as well as for the community to post ongoing progress. >> >> Pros for GitHub Discussions: >> 1. GitHub Discussions have less friction than Slack and are cheaper for >> Apache Org. Users only need a GitHub account. >> 2. GitHub Discussions are indexed by Google. Ref: >> >> https://www.google.com/search?q=apache+Cleaning+up+missing+containers+on+Ozone >> 3. GitHub Discussions can be organized, labelled >> 4. Github Discussion threads tend to be kept alive for a longer duration >> than what Slack messages tend to be (anecdotally). >> >> Pros for Slack: >> 1. Slack is more real time than GitHub >> 2. Slack notifications are better than GitHub on mobile devices. >> >> I would like to propose that we deprecate Slack for technical discussions >> and move them to GitHub Discussions. >> >> What does this mean? >> 1. We will not shut down slack channel >> 1.1 Use the Slack channel for urgent non technical needs or casual >> conversations. >> 2. Any technical discussion initiated will be encouraged to be moved to >> Github Discussions. >> 3. We will remove documentation encouraging users to engage on Slack and >> instead make sure GitHub Discussions are encouraged. >> 4. We will add to the Slack channel a note encouraging developers to use >> GitHub Discussions. >> >> Please let me know what you think. >> I plan to make the change in around 15-30 days if the majority of >> developers feel this is a cleaner approach to engage with the community. >> >> Regards, >> Ritesh >> > > > -- > Pifta
