Since the genie is out of the bottle now and I have been involved in this discussion all the way, I think the question ought to be "Apache Spark DEV community asks Databricks to differentiate its Spark version string". That makes more sense as Spark DEV community is a superset of PMC if I am not wrong". Whether Spark DEV community can make such request is another matter,
That aside, I believe both Dongioon and Sean passionately believe in their respective views so this is going to be a hard nut to crack. A good number of Spark DEV community members work for Databricks as well so there is a potential conflict of interest here. Notwithstanding there are multiple other companies that use Spark version in one form or shape, so how about them! Even if we collect 100 votes, what Apache Spark is going to do if Databricks or for that matter others ignore the request and the request backfires. Franfly, I don't think it is worth the effort, regardless of how passionately we believe in it. I vote to let it rest. HTH Mich Talebzadeh, Lead Solutions Architect/Engineering Lead Palantir Technologies Limited London United Kingdom view my Linkedin profile <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> https://en.everybodywiki.com/Mich_Talebzadeh *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On Fri, 16 Jun 2023 at 21:23, Sean Owen <sro...@gmail.com> wrote: > As we noted in the last thread, this discussion should have been on > private@ to begin with, but, the ship has sailed. > > You are suggesting that non-PMC members vote on whether the PMC has to do > something? No, that's not how anything works here. > It's certainly the PMC that decides what to put in the board report, or > take action on behalf of the project. > > This doesn't make sense here. Frankly, repeating this publicly without > relevant context, and avoiding the response you already got, is > inappropriate. > > You may call a PMC vote on whether there's even an issue here, sure. If > you pursue it, you should explain specifically what the issue is w.r.t. > policy, and argue against the response you've already received. > We put valid issues in the board report, for sure. We do not include > invalid issues in the board report. That part needs no decision from anyone. > > > On Fri, Jun 16, 2023 at 3:08 PM Dongjoon Hyun <dongjoon.h...@gmail.com> > wrote: > >> No, this is a vote on dev@ intentionally as a part of our previous >> thread, "ASF policy violation and Scala version issues" ( >> https://lists.apache.org/thread/k7gr65wt0fwtldc7hp7bd0vkg1k93rrb) >> >> > did you mean this for the PMC list? >> >> I clearly started the thread with the following. >> > - Apache Spark PMC should include this incident report and the result >> in the next Apache Spark Quarterly Report (August). >> >> However, there is a perspective that this is none of Apache Spark PMC's >> role here. >> >> That's the rationale of this vote. >> >> This vote is whether this is Apache Spark PMC's role or not. >> >> Dongjoon. >> >
