Hi Suresh, Sounds great! This would make it much easier to access and manage discussions efficiently.
Thanks, Lahiru On Mon, Sep 2, 2024 at 10:24 AM Pamidighantam, Sudhakar V < spami...@illinois.edu> wrote: > +1 fully agree that one place make it convenient and efficient. > > > > Thanks, > > Sudhakar. > > > > *From: *DImuthu Upeksha <dimuthu...@apache.org> > *Date: *Monday, September 2, 2024 at 9:29 AM > *To: *dev@airavata.apache.org <dev@airavata.apache.org> > *Subject: *Re: Use of GitHub Discussion > > Hi Suresh, > > > > +1 for this. It is great for developers to stay on one platform for both > code and discussion contributions. > > > > Thanks > > Dimuthu > > > > On Sun, Sep 1, 2024 at 11:00 PM Ganning Xu <gannin...@gmail.com> wrote: > > Hi Suresh, > > > > I agree, this sounds like a great idea. This also allows us to link pull > requests to specific discussions, and members to be assigned to specific > issues/discussions. > > > > Thanks! > > Ganning Xu > > > > On Sun, Sep 1, 2024 at 10:57 PM Piyush Nalawade <nalawadepiy...@gmail.com> > wrote: > > Hey Suresh, > > Sounds like a great visibility initiative. This will benefit developers > who want to contribute but are not added on the mailing list. They can also > have visibility regarding repository-specific discussions. > > > > On Sun, Sep 1, 2024 at 3:42 PM Suresh Marru <sma...@apache.org> wrote: > > Hi All, > > We have stalled our mailing list usage, discussions are spread across > GitHub Issues, and some are buried in PRs and Slack. How about we have > repository-specific discussions on GitHub? For instance, we can use the > Custos repository as an example trial to see of how it goes. > > We can see other projects, and I am referencing Airflow as an example - > https://airflow.apache.org/community/ > <https://urldefense.com/v3/__https:/airflow.apache.org/community/__;!!DZ3fjg!-iDMWxvub26AETif4uUbAaN8jFN0hsBqbd_srSP5Ipj5O5FwweJw1EGteRUAzCYaGETLOrYEEY4jPRPWbJJDm4g$> > > Thoughts? > > Suresh > >
