Thank Ran Tao, my point exactly, Jira tickets are not meant to be used in this way in the scope of our project, although I get the motivation and I agree with it.
For the beginners contributions, there is consensus on using the "newbie" label (as per the discussion I linked above), since you went through many tickets already, it would be very nice if you could add this label where it's missing, in order to improve the labelling. For what is an important/interesting topic to work on, that's highly subjective and I am not sure we can easily agree on such a classification. Technically speaking, we could use the notion of "upvote" available in Jira as a proxy for importance (but at the moment it is not used). In general, there is consensus that "CVE > bugfix > improvement", other than that it's hard to say, even though the release manager tries to push some tickets over the finish line before a release when they seem close enough and important. I am starting from the assumption that this is meant to help contributors find relevant tickets to work on if they want, not as a way to (try to) push some tickets with higher priority, as that's a completely different discussion and scope that has to be checked under the ASF rules (just mentioning because you refer to "company-sponsored" projects and commitments on what goes into what release). Best regards, Alessandro On Fri, 26 Jan 2024 at 14:36, Ran Tao <chucheng...@gmail.com> wrote: > The starting point is good, but it seems a bit strange to > collect some unrelated issues and put them under one ticket (a jira case > collection). > > If it’s a personal blog, it’s okay to collect some interesting issues that > followers can check out. > > I guess Hongyu just wants to find a page to maintain some interesting > issues, > where both contributors and new beginners can see it intuitively, and next, > make some contributions. > > Can we categorize these issues and tag them? Users can use tags to filter. > > Best Regards, > Ran Tao > > > Hongyu Guo <guohongyu...@gmail.com> 于2024年1月26日周五 19:01写道： > > > Some active communities use the tags "good first issues" or "newbie" to > > help new members quickly integrate into the community. > > Additionally, these communities often create a "roadmap" to outline the > > future development plans. > > > > In the case of Calcite, there are not many Jira cases labeled as "newbie" > > and there is no roadmap. > > This is because Calcite lacks support from commercial companies, and the > > developers contribute to the community in their free time. > > Consequently, Calcite cannot guarantee the release of new features in > > specific versions. > > > > Back to CALCITE-6230, some of these issues are deemed valuable by the > > committers and PMCs; > > some of these have had PRs but have not been merged for various reasons. > > > > Based on the above reasons, I have collected some features that I think > are > > valuable, and it would be great if Calcite can implement them. > > > > It may be more appropriate to use umbrella tickets for these cases, > > but some of them are already sub-tasks of other tickets or are umbrella > > tickets themselves. > > I am unsure if this poses a problem. Additionally, I would prefer to > > display these tickets on a single page rather than multiple pages. > > > > Best, > > Hongyu > > > > On Fri, Jan 26, 2024 at 6:20 PM Alessandro Solimando < > > alessandro.solima...@gmail.com> wrote: > > > > > Hi Hongyu, > > > I replied to the ticket before seeing your email. > > > > > > For tickets for new contributors there has been a discussion in the ML, > > > with agreement on using a label (see > > > https://lists.apache.org/thread/jwc5g5msznlwcq73gh1vqg82dlmn1g1r). > > > > > > For interesting tickets that should be worked on, people generally ping > > on > > > the ML if they need a review, and I think this generally falls under > the > > > fact that we have more contributions than available reviewers, so even > > > interesting and needed contributions don't always get in, I doubt an > > extra > > > ticket will solve this issue. > > > > > > Best regards, > > > Alessandro > > > > > > On Fri, 26 Jan 2024 at 10:50, Hongyu Guo <guohongyu...@gmail.com> > wrote: > > > > > > > Hi devs, > > > > > > > > Calcite currently has over 1000 unresolved issues[1], and I have > > > gathered a > > > > few Jira cases that I find interesting[2]. These cases are helpful > for > > > > newcomers who want to contribute their first line of code to the > > Calcite > > > > community but are unsure where to begin. If you believe there are > other > > > > valuable issues, please feel free to add them. > > > > Please note that these issues are not "good first issues" and some of > > > them > > > > are quite difficult tasks. > > > > > > > > Best, > > > > Hongyu > > > > > > > > [1] > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/CALCITE-5912?jql=project%20%3D%20CALCITE%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20created%20DESC > > > > [2] https://issues.apache.org/jira/browse/CALCITE-6230 > > > > > > > > > >
