Re: [Libreoffice-qa] ESC budget item review meeting minutes: 2023-06-22
Hi Eyal, [adding dev & qa list back - f'up to there, I'd say, project@ is more for general announcements] my personal take would be - we should indeed outline a bit better, what formal requirements the ESC has, to be able to evaluate such tender proposals. Hossein already mentioned some minimum verbosity, such that someone independent, but skilled in the art, can judge a submission. I would hesitate to prescribe any particular 'kind' of work. Whatever the project members deem important should go there - if, what & when to do it, is then up to the ESC to decide. What is useful to mention though, is that successful proposals almost always are from, or are supported by, someone with technical background. Finding an ESC member to refine & lobby for one's proposal also tends to be a good idea. Best, Thorsten Eyal Rozenberg wrote: > So, even though the ranking is not in yet, I want to use the opportunity > and ask the members and officers who attended this year's meeting, and > rankings in previous years, to consider trying to author some guidelines > regarding what constitutes a "good" tender proposal, e.g.: > > * Larger or smaller amount of work? > * Features or bug/misdesign fixes? > * Proposals which can be broken down easily into smaller pieces of work, > or rather work that is somewhat atomic and unlikely to be done > incrementally? > * Improvements to more commonly-used apps and parts of the code, or > rather improvements to the less popular ones which are unlikely to > result in sufficient pressure from the user base to make happen? > * Work that is only apriori relevant to some category of users (e.g. > people with disabilities, specific language groups etc.), or work that > is more universally relevant? > > Now, I realize that different people have different ideas regarding what > the tendering priorities should be, and of course this may also tie in > to the ongoing arguments regarding TDF-ecosystem-company relations, but > - it's all fine as long as you separate what you-personally believe is > better from what has, in recent years, gotten more support and ranked up. > > Eyal > > > > On 22/06/2023 19:43, Ilmari Lauhakangas wrote: > > * Present: > > + Affiliated with TDF: Ilmari Lauhakangas, Xisco Faulí, Heiko > > Tietze, Florian Effenberger, Italo Vignoli, Khaled Hosny, Sophie > > Gautier, Olivier Hallot, Christian Lohmaier, Stéphane Guillou, Hossein > > Nourikhah > > + Affiliated with Collabora: Tomaž Vajngerl, Justin Luth > > + Affiliated with allotropia: Thorsten Behrens > > + Affiliated with Omnis Cloud Sarl (or TDF Board?): Paolo Vecchi > > + Affiliated with Red Hat: Stephan Bergmann > > + Unaffiliated: V Stuart Foote, Regina Henschel, Simon Phipps, > > Gerald Pfeifer > > > > * current version of the proposal was sent to board at 15.06.23, 11:24 > > * starts with section "Preamble" and ends with "Database Rights On > > The Transparency Section" > > * 2.823 words, 16.737 characters > > * tdf_budget_2023-06-12_comments_CP-clean.odt > > * SHA256: > > 4890a4f9c5bec212ea56997c4056af0389d99e618ebeac66e1abf25c6f67e14e > > * shared with the ESC end of April (27/04/2023) was this: > > > > https://nextcloud.documentfoundation.org/s/YprpsFP45z7a7p3 > > > > * ESC version is ~4-5 weeks, w/o preamble and w/o board decision bits > > > > Registration of Affiliation > > > > "Means a person: > > • acting as a representative of; > > • OR is a legal representative of; > > • OR is an employee of; > > • OR is a current consultant to; > > • OR is a former employee of OR former consultant (unless a > > sufficient amount of time has elapsed since the relevant relationship > > has ended) to > > a relevant entity OR of an entity which is > > • controlled by; > > • OR controls; > > • OR is under a common control with; > > • OR shares substantial business interest, including by way of > > ◦ long term economic relationship; > > ◦ OR commercial partnership, distributorship or similar; > > ◦ OR business coordination agreements, including consortia; > > ◦ OR any kind of agreement that limit the competition against > > each other – especially in the same fields as where the TDF operates – > > with; > > • OR operates in a joint venture with > > a relevant entity. For the sake of clarification, being a member of a > > general business association (such as a guild) OR of a Free Software > > association (such as the FSFE, OSI and OSI Affiliates, Open Forum > > Europe, OpenUK, OW2, Eclipse Foundation, FFII, SFC, KDE, The Linux > > Foundation) would not create an Affiliation." > > > > "In order to avoid COI for those participating in ESC voting as per this > > Section, a voting member or a member applying to participate in the > > select committee as provided by the Ranking section MUST declare whether > > they are Affiliate to an entity which intends to place bids on the > > tend
[Libreoffice-qa] ESC budget item review meeting minutes: 2023-06-22
* Present: + Affiliated with TDF: Ilmari Lauhakangas, Xisco Faulí, Heiko Tietze, Florian Effenberger, Italo Vignoli, Khaled Hosny, Sophie Gautier, Olivier Hallot, Christian Lohmaier, Stéphane Guillou, Hossein Nourikhah + Affiliated with Collabora: Tomaž Vajngerl, Justin Luth + Affiliated with allotropia: Thorsten Behrens + Affiliated with Omnis Cloud Sarl (or TDF Board?): Paolo Vecchi + Affiliated with Red Hat: Stephan Bergmann + Unaffiliated: V Stuart Foote, Regina Henschel, Simon Phipps, Gerald Pfeifer * current version of the proposal was sent to board at 15.06.23, 11:24 * starts with section "Preamble" and ends with "Database Rights On The Transparency Section" * 2.823 words, 16.737 characters * tdf_budget_2023-06-12_comments_CP-clean.odt * SHA256: 4890a4f9c5bec212ea56997c4056af0389d99e618ebeac66e1abf25c6f67e14e * shared with the ESC end of April (27/04/2023) was this: https://nextcloud.documentfoundation.org/s/YprpsFP45z7a7p3 * ESC version is ~4-5 weeks, w/o preamble and w/o board decision bits Registration of Affiliation "Means a person: • acting as a representative of; • OR is a legal representative of; • OR is an employee of; • OR is a current consultant to; • OR is a former employee of OR former consultant (unless a sufficient amount of time has elapsed since the relevant relationship has ended) to a relevant entity OR of an entity which is • controlled by; • OR controls; • OR is under a common control with; • OR shares substantial business interest, including by way of ◦ long term economic relationship; ◦ OR commercial partnership, distributorship or similar; ◦ OR business coordination agreements, including consortia; ◦ OR any kind of agreement that limit the competition against each other – especially in the same fields as where the TDF operates – with; • OR operates in a joint venture with a relevant entity. For the sake of clarification, being a member of a general business association (such as a guild) OR of a Free Software association (such as the FSFE, OSI and OSI Affiliates, Open Forum Europe, OpenUK, OW2, Eclipse Foundation, FFII, SFC, KDE, The Linux Foundation) would not create an Affiliation." "In order to avoid COI for those participating in ESC voting as per this Section, a voting member or a member applying to participate in the select committee as provided by the Ranking section MUST declare whether they are Affiliate to an entity which intends to place bids on the tenders resulting from the Technical Budgeting OR, on their honour, whether they are aware of any such potential situation could reasonably materialize between the date of the vote and the date of tendering." "Voting on a matter OR making a determination while being in a COI situation on the subject matter, OR not declaring a potential COI as per the Declaration Of Potential Conflict Section is per se a COI and ground for exclusion from the tendering procedure, if at least one of the entities to which the member is Affiliate places a bid in a tender resulting form the Technical Budgeting." Preparations * blogpost with call for proposals was published with more than 15 days deadline * wiki page was available for everyone to edit * ESC minutes were shared publicly and sent to mailing lists * today's call was announced publicly * ranking spreadsheet was always public in an up to date version Pending items * transparency section of the website must be in place before tendering starts, Italo is working on it * blogpost with ranking spreadsheet must be published as soon as that one is finalized Proposals * No paid external expert was requested. * No urgency request was made. * Do all proposals on today's list have a sufficient description and cost estimate? Yes. * Have all cost estimates been re-evaluated by only non-conflicted members of the ESC? Yes. Ranking * ALL proposals must be ranked. * Proposal by a committee that has a majority of non-Conflicted members. * Decision then by CONSENSUS of only the non-Conflicted members. * Failing that, majority VOTE by only non-Conflicted members. * Spreadsheet with comments from TDF staff: https://nextcloud.documentfoundation.org/s/i9CSEs2gjFisc2y * Budget pages for reference: + https://wiki.documentfoundation.org/Development/Budget2021 + https://wiki.documentfoundation.org/Development/Budget2022 + https://wiki.documentfoundation.org/Development/Budget2023 * Thorsten noticed this item from 2022 was not estimated: https://wiki.documentfoundation.org/Development/Budget2022#Missing_ODF_Features:_Concentric_gradient_fill_of_custom-shapes there's likely more - e.g.Bridge the gap between drawinglayer and VCL, Bitmaps in vcl: Use a native format/depth etc.. * Procedure to rank: go through the items and arrive at a consensus, for 2023, use ranking from February 2023 (Ilmar
