Hi Basil et al,
Thanks for the follow-up. As we discussed in the DMs, with all due respect
to you and to your valuable contributions I do not appreciate the passive
aggressive tone you chose here or in the original DM conversation
yesterday. Scoffing about the adopted community process for budget
approvals does not help either. I do not such an approach helps you to get
this particular issue resolved faster, as well as it does not help in the
pull requests and other conversations I see here and there. Everyone in the
community tries to achieve the best for the project, and please use it as a
default assumption for communications. It would make the community a more
pleasant place for everyone. Thanks for understanding.
Back to the matter, indeed the budgeting process in JEP-15 follows the
general Jenkins community decision making process where decisions happen in
async channels, not during the live meetings. As for governance and
budgeting matters, this mailing list is used. Nothing has changed in these
regards since ages, so there is no reason to be surprised a 1,900 EUR
budget request, which is 20% of the total Jenkins funds available on LFX
Mentorship, would not be approved without a formal email thread in this
mailing list. Thanks for understanding again.
*The request itself*
Now I would like to share the request Basil, copying the meeting notes from
the October 03 meeting. So the feedback will be needed:
- *Given the lack of volunteer interest in JENKINS-68652 or alternatives
(e.g., writing a new parser without ANTLR), Basil Crow has reached out to
Federico Tomassetti at Strumenta, a consulting firm with experience
performing migrations from ANTLR2 to ANTLR4*
- *Strumenta is interested in the project and has scoped the work
required to migrate from ANTLR2 to ANTLR4*
- *Technical consensus has been reached on the developer mailing list
<https://groups.google.com/g/jenkinsci-dev/c/bGmc9bc0mp4/m/i1BhSIp-AAAJ>
(in
this thread)*
- *Proposal from Strumenta*
<https://app.pandadoc.com/document/55d611d49988df16a2c043c5669b679a282d04dc>
-
*Basil is requesting funding of 1,900 Euro, possibly with additional
Value-Added Tax (VAT), and approval from the governance board to engage
Strumenta to begin the project *
- *If approved, Basil plans to be the primary point of contact with
the Strumenta as they prepare the pull request to migrate from ANTLR2 to
ANTLR4*
- *The code is covered by automated testing, and Basil plans to
complete additional manual smoke testing beyond that*
- *Basil also plans to review and approve the pull request*
- *As thanks for their discount, we will publish a blog post with
technical content describing their work and our results of their work.
Basil will coordinate the blog post with Strumenta*
Some extra context:
- At the governing board meeting, the following contributors voted in
favor of the proposal: Mark Waite, Gavin, me, Basil himself, and Kevin.
Note that 3 of these voters are directly involved with the matter and work
for the same vendor that might have a commercial interest in the fix. It
does not make difference in the consensus building process, especially
since this change is definitely beneficial for the project.
- After the meeting an anonymous contributor has already shared their
feedback that the requested sum is too much for the scope of work in this
project.
Personally I am rather in favor of the request. We have money from Jenkins
supporters floating around, and we are not using them. Whether the use of
the budget is super efficient or not, as Basil said we are not moving
forward with the ticket. And it may impact vendors and end users requiring
clear security scans to have Jenkins adopted. So I keep my +1 vote for the
request.
Please share your feedback!
Best regards,
Oleg Nenashev
On Monday, October 17, 2022 at 8:18:18 PM UTC+2 [email protected] wrote:
> On Thu, Sep 22, 2022 at 11:54 AM Basil Crow <[email protected]> wrote:
> >
> > I am starting this thread to reach consensus on the technical side of
> > this proposal; namely, migrating from ANTLR2 to ANTLR4 to decrease
> > technical debt and facilitate compilation on Java 18 or newer.
>
> To summarize our progress in this area, we have reached technical
> consensus on the developer list and budgetary consensus with the
> governance board, which voted in favor of this engagement at its
> meeting on October 3, 2022. Oleg Nenashev has informed me that he is
> unwilling to move forward until the process documented in JEP-15 is
> followed; namely:
>
> > Budget requests should be submitted to the developer mailing list and
> discussed there[;] the Governance meeting will be doing a formal
> approval/rejection based on the community feedback.
>
> Whereas technical consensus has been reached on the developer list,
> and whereas budgetary consensus has been reached with the governance
> board; now, therefore, be it known that the preceding message
> constitutes a formal budget request, and that this formal budget
> request has been made to the developer mailing list pursuant to JEP-15
> (at revision 023ed9f0) ยง 3.3.2 ("Use of donations"), line 175.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/a58d069b-e7bd-4075-b5b7-a4ecca381eefn%40googlegroups.com.
