Thanks for reviewing, Stamatis! To clarify, the mentors have been very helpful and consistently responsive on Slack, so I’m definitely not questioning or challenging their support. What I was trying to highlight is the confusion around the interpretation of licensing requirements, particularly regarding what content should go into the LICENSE/NOTICE file and how it should be represented.
I’ve reviewed multiple ASF projects that bundle jars, and I’ve seen varying approaches to how LICENSE and NOTICE files are written. This inconsistency has left me uncertain about what’s considered the “best” or compliant way to draft these files. It also gives me a fair amount of anxiety with every release vote on the dev/general incubator list because the evaluation of the LICENSE/NOTICE files often feels like going through a non-deterministic process, where the outcome (approval or rejection) can hinge on differing interpretations or preferences, even when we believe we’ve followed the requirements carefully. To begin with, it would be really helpful if all project mentors could align on this PR and the expected content and representation of the LICENSE/NOTICE files. That would give the release manager much more confidence that we can secure the required +3 votes when the release moves to the general incubator vote. https://github.com/apache/incubator-xtable/pull/707 Thanks Vinish On Tue, May 6, 2025 at 11:37 PM Stamatis Zampetakis <zabe...@gmail.com> wrote: > Thanks for preparing the report, Vinish! > > What I find slightly unclear is the comment about if the mentors are > helpful or not. > > "However for the licensing of new bundled jars, there's conflicting > interpretations of the ASF documentation between the dev vote, the > general incubator vote." > > I don't understand the phrase above, especially since there hasn't > been an incubator vote. As far as I know the two votes don't have > different requirements so I don't understand the problem here. > > "We would benefit from additional guidance and support specifically on > resolving these licensing issues for bundled jars and "what content" > to write in LICENSE/NOTICE files." > > I am not against having additional people or additional mentors review > the licensing issues but for this to happen you should send an email > to the incubator list and ask for help. When it comes to specific > questions or disagreements the best path is to raise a LEGAL ticket > and get an official answer from the respective team. > > Best, > Stamatis > > > On Wed, May 7, 2025 at 1:44 AM Vinish Reddy <vin...@apache.org> wrote: > > > > I have submitted the report. > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2025#xtable > > > > Thanks > > Vinish > > > > On Wed, Apr 30, 2025 at 4:54 PM <jmcl...@apache.org> wrote: > > > > > Dear podling, > > > > > > This email was sent by an automated system on behalf of the Apache > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > prepare your quarterly board report. > > > > > > The board meeting is scheduled for Wed, 21 May 2025. > > > The report for your podling will form a part of the Incubator PMC > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > before the board meeting, to allow sufficient time for review and > > > submission (Wed, May 07). > > > > > > Please submit your report with sufficient time to allow the Incubator > > > PMC, and subsequently board members to review and digest. Again, the > > > very latest you should submit your report is 2 weeks prior to the board > > > meeting. > > > > > > Candidate names should not be made public before people are actually > > > elected, so please do not include the names of potential committers or > > > PPMC members in your report. > > > > > > Thanks, > > > > > > The Apache Incubator PMC > > > > > > Submitting your Report > > > > > > ---------------------- > > > > > > Your report should contain the following: > > > > > > * Your project name > > > * A brief description of your project, which assumes no knowledge of > > > the project or necessarily of its field > > > * A list of the three most important issues to address in the move > > > towards graduation. > > > * Any issues that the Incubator PMC or ASF Board might wish/need to > be > > > aware of > > > * How has the community developed since the last report > > > * How has the project developed since the last report. > > > * How does the podling rate their own maturity. > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2025 > > > > > > Note: This is manually populated. You may need to wait a little before > > > this page is created from a template. > > > > > > Note: The format of the report has changed to use markdown. > > > > > > Mentors > > > ------- > > > > > > Mentors should review reports for their project(s) and sign them off on > > > the Incubator wiki page. Signing off reports shows that you are > > > following the project - projects that are not signed may raise alarms > > > for the Incubator PMC. > > > > > > Incubator PMC > > > >
