Hi: 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?
It's one possible solution, but as I have mentioned, it mixes with bug/issue tracking in github issues. Github discussion is more like a forum for users, and as Piotr mentioned, we have observed positive engagement in other projects, such as apache datafusion <https://github.com/apache/datafusion/discussions> , apache opendal <https://github.com/apache/opendal/discussions> . The dev list is still the place for developer/contributors discussing designs and driving making decisions. I think most people prefer Slack or Github to mailing lists for this kind > of thing. +1 for this point. Slack or Github is more accessible for users asking questions, and Github is more search engine friendly I guess? 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. It's easy to filter unanswered questions in Github Discussion. It's not a complete solution, but it provides useful statistics for the status. 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. It's not about roadmap only, but all kinds of user questions around. On Wed, Jul 10, 2024 at 6:22 AM Ryan Blue <b...@databricks.com.invalid> wrote: > Thanks for sharing that context, Piotr! > > If we think that github discussions will be a place primarily for user > list discussions, then I think I'd support that over creating a separate > user mailing list. I think most people prefer Slack or Github to mailing > lists for this kind of thing. Personally, I'd much rather interact through > Github where I have an account than to need to join a separate mailing list > to ask a question. I've never done that and I suspect we'll get more people > interacting with discussions. > > Turning on discussions sounds good to me. Do we also have a way to steer > people to the right forum for development discussions? I assume that we > still want those primarily on the dev list. > > On Tue, Jul 9, 2024 at 2:36 PM Wing Yew Poon <wyp...@cloudera.com.invalid> > wrote: > >> I am not familiar with the GitHub discussion feature and do not have an >> opinion about using it. >> I do think though that it would be useful to have a user list as well as >> a dev list for Apache Iceberg. Many Apache projects have both. Discussions >> about project work should continue to happen on the dev list. A user list >> would be for users to ask questions about using Iceberg, to seek help, and >> also to report problems (potential bugs), which if confirmed, could be >> reported as GitHub issues. Oftentimes, in the absence of the user list, >> users resort to opening a GitHub issue to ask a question. Of course, there >> is Slack, but I think it wouldn't hurt to have a user list as another >> channel. >> >> - Wing Yew >> >> >> On Tue, Jul 9, 2024 at 2:07 PM Piotr Findeisen <piotr.findei...@gmail.com> >> wrote: >> >>> 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 >>>>> >>>> > > -- > Ryan Blue > Databricks >
