Hi, I totally hear Ryan's concerns about further dividing the discussion. I had the same feeling when we opened discussions in Trino. The reality was more positive though. Discussions predominantly serve as a way to ask questions rather than drive decision-making in the project. Thinking from user perspective -- is it obvious that they can send an email to the dev list? or should they join slack? Discussions look very accessible to those that have a github account already, but we should probably make sure we don't move there content that belongs on the dev list.
The other concern is whether the discussions will be getting attention from other project contributors. I.e. if someone is looking for help, are they getting it? We should at least informally monitor the situation here. Best Piotr On Tue, 9 Jul 2024 at 17:36, Jack Ye <yezhao...@gmail.com> wrote: > I am not familiar with the GitHub discussion feature, but could we start > with GitHub Issue tags + templates to distinguish between actual issues vs > this kind of questions? Why is that not sufficient? > > Also, if there are a lot of questions about the roadmap, I think we should > discuss and make good milestones for the project that are decoupled from > releases. > > I remember there was a similar question since we removed the roadmap page > in the website: https://github.com/apache/iceberg/issues/10390, maybe we > should reconsider adding at least a pointer in the website to the > milestones page. > > -Jack > > On Tue, Jul 9, 2024 at 8:32 AM Ryan Blue <b...@databricks.com.invalid> > wrote: > >> My only concern about using this tool is that we may be >> further separating where discussion happens and not everyone will see >> what's happening. Usually, the dev list is the canonical place for >> discussions. Is that not a good solution? What differentiates what we would >> use github discussions for vs the dev list? >> >> On Tue, Jul 9, 2024 at 6:52 AM Eduard Tudenhöfner < >> etudenhoef...@apache.org> wrote: >> >>> I think GH discussions would be great to have on the Iceberg repo(s), >>> so +1 from my side on this. >>> >>> Eduard >>> >>> On Tue, Jul 9, 2024 at 8:14 AM Renjie Liu <liurenjie2...@gmail.com> >>> wrote: >>> >>>> Hi: >>>> >>>> It's also possible to create a user mailing list if it helps. >>>> >>>> >>>> I'm neutral to this option. Seems we are actually missing the user mail >>>> list. >>>> >>>> On Tue, Jul 9, 2024 at 1:50 PM Xuanwo <xua...@apache.org> wrote: >>>> >>>>> Hi, >>>>> >>>>> > Regarding the discussion tab, it sounds good to me. It's pretty >>>>> straight forward to do by editing .asf.yaml. >>>>> >>>>> I tried this before. But the asf.yaml doesn't support controling >>>>> discussion yet. >>>>> We need the help from infra team. >>>>> >>>>> >>>>> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions >>>>> >>>>> >>>>> On Tue, Jul 9, 2024, at 13:44, Jean-Baptiste Onofré wrote: >>>>> > Hi >>>>> > >>>>> > It's also possible to create a user mailing list if it helps. >>>>> > >>>>> > Regarding the discussion tab, it sounds good to me. It's pretty >>>>> > straight forward to do by editing .asf.yaml. >>>>> > >>>>> > Regards >>>>> > JB >>>>> > >>>>> > On Tue, Jul 9, 2024 at 5:18 AM Renjie Liu <liurenjie2...@gmail.com> >>>>> wrote: >>>>> >> >>>>> >> Hi: >>>>> >> >>>>> >> Recently we have observed more and more user interested in >>>>> iceberg-rust, and they have many questions about it, for example the >>>>> status, relationship with others such pyiceberg. Slack is a great place to >>>>> discussion, but is not friendly for long discussion and not easy to >>>>> comment. We can also encourage user to use github issue, but it's easy to >>>>> mix with true issues, e.g. feature tracking, bug tracking, etc. >>>>> >> >>>>> >> So I propose to enable the discussion tab for repos of iceberg and >>>>> subprojects such as iceberg-rust, pyiceberg, iceberg-go. >>>>> >>>>> -- >>>>> Xuanwo >>>>> >>>>> https://xuanwo.io/ >>>>> >>>> >> >> -- >> Ryan Blue >> Databricks >> >
