VOTE: Remaining funds in the Bugfix Accelerator Program 2023
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
* As per the SFC Conflict of Interest policy, Martin was not present during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan
I abstain.
(for the records)
On Thu, 29 Jun 2023 at 21:43, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
I vote a.
Am 29.06.2023 um 21:43 schrieb Jonathan Neuhauser jonathan.neuhauser@outlook.com:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
I vote a.
----- Original Message ----- | From: "René de Hesselle" dehesselle@icloud.com | To: "Inkscape Board" inkscape-board@lists.inkscape.org | Sent: Friday, June 30, 2023 10:15:51 AM | Subject: [Inkscape-board] Re: VOTE: Remaining funds in the Bugfix Accelerator Program 2023 | | I vote a. | | | > Am 29.06.2023 um 21:43 schrieb Jonathan Neuhauser | > jonathan.neuhauser@outlook.com: | > | > Dear PLC, | > | > In the meeting with Pono on June 14*, the present PLC members have | > discussed* the extension of the bugfix accelerator program, and | > based on this discussion, I've created the following ballot. | > | > *Background* | > | > The PLC has previously allocated a total of USD 20.000 for both | > contractors, but Rafael dropped out very early into his contract. | > On the other hand, Martin has made huge efforts to get the 1.3 | > release as smooth as possible, fixing - if my stats are correct - | > 52 issues within the contract, including 2 blockers and 10 | > crashes. (You can see the progress over time on this page: | > https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues) | > | > With this vote, I propose to repurpose the funds that have already | > been reserved for the Bugfix accelerator program for a contract | > extension for Martin so that he can fix issues at the project's | > discretion for the bugfix releases of the 1.3.x series. | > This is based on the understanding that the contract is not | > intended to pay for Inkscape development per se, but for the | > project's ability to decide which bugs the contractor work will | > work on. This includes issues outside of the contractors "comfort | > zone", as was the case with the already-fixed issues. | > | > Regarding a possible repetition of the bugfix accelerator next | > year: a poll will be conducted to find out how uses perceive our | > recent efforts to spend the project's resources, and where they | > would like to see our resources go. Much like the internal GTK | > contractor position, we would properly advertise the job posting | > on the mailing list, and have an open call for applications (from | > within the active developers). | > | > * As per the SFC Conflict of Interest policy, Martin was not | > present during this part of the meeting. He has stated that he | > would be available. | > | > *Ballot*: | > a. Extend Martin's contract under the terms of the Bugfix | > Accelerator Program 2023. The contract volume will not exceed the | > remaining budget allocated to the Bugfix Accelerator Program 2023. | > b. Do not extend the Bugfix Accelerator Program 2023, the remaining | > funds are deallocated. | > c. Other: _____ | > | > Best regards, | > | > Jonathan | > _______________________________________________ | > Inkscape Board of Directors mailing list -- | > inkscape-board@lists.inkscape.org | > To unsubscribe send an email to | > inkscape-board-leave@lists.inkscape.org | _______________________________________________ | Inkscape Board of Directors mailing list -- | inkscape-board@lists.inkscape.org | To unsubscribe send an email to | inkscape-board-leave@lists.inkscape.org |
Sound good to me, I'll vote (a)
I know Rafael dropped out pretty early, but, how much is remaining in the balance vs paid out to Rafael? I feel like that is relevant information.
Cheers, Josh
On Thu, Jun 29, 2023 at 12:43 PM Jonathan Neuhauser < jonathan.neuhauser@outlook.com> wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
On Tue, 2023-07-04 at 09:40 -0700, Josh Andler wrote:
I know Rafael dropped out pretty early, but, how much is remaining in the balance vs paid out to Rafael? I feel like that is relevant information.
I know this information because he and I was in close contact to write the blog posts.
Nothing was paid out.
He decided to gift us the time he has spent on issues for the first month and stop doing the program after that.
Martin,
Howdy,
Sorry for the delay, was on vacation and no I'm catching up on points everywhere all the things. I checked with Pono and we verified that the RT ticket for Rafal had no charges to it (not questioning anyone, just verifying as asked). It was originally allocated for $11,200. Ted On Jul 4 2023, at 11:40 am, Josh Andler scislac@gmail.com wrote:
I know Rafael dropped out pretty early, but, how much is remaining in the balance vs paid out to Rafael? I feel like that is relevant information.
Cheers, Josh
On Thu, Jun 29, 2023 at 12:43 PM Jonathan Neuhauser <jonathan.neuhauser@outlook.com (mailto:jonathan.neuhauser@outlook.com)> wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background* The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards, Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org (mailto:inkscape-board@lists.inkscape.org) To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org (mailto:inkscape-board-leave@lists.inkscape.org)
Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Hello Jonathan,
How do we expect this to work with regards to 1.3? I thought it was going to be release here soon, I'm worried it is "too late"? Or are we expecting this to be for a 1.3.1? Thanks, Ted
On Jun 29 2023, at 2:43 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background* The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards, Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
We expect this to work as stated in Jonathan’s proposal, I quote:
"With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series.“
How would you phrase „bugfix releases of 1.3.x series“ for more clarity?
Am 05.07.2023 um 21:31 schrieb Ted Gould ted@gould.cx:
Hello Jonathan,
How do we expect this to work with regards to 1.3? I thought it was going to be release here soon, I'm worried it is "too late"? Or are we expecting this to be for a 1.3.1?
Thanks, Ted
On Jun 29 2023, at 2:43 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote: Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org_______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Hi Ted, The release is currently scheduled for in two weeks, although there are still blocker issues and there was some discussion at the last dev meeting to postpone it so those can be fixed in time. But yes, I fully intended to stretch some hours into 1.3.1. From the vote email:
[…] so that he can fix issues at the project's discretion for the
bugfix releases of the 1.3.x series.
After all, this is a bugfix release, and some issues will only be found after a wide release! The contract should have the same terms as the original (it’s an extension after all), and the original one already allowed to bill hours within a year.
Jonathan
Am 05.07.2023 um 21:31 schrieb Ted Gould ted@gould.cx:
Hello Jonathan,
How do we expect this to work with regards to 1.3? I thought it was going to be release here soon, I'm worried it is "too late"? Or are we expecting this to be for a 1.3.1?
Thanks, Ted
On Jun 29 2023, at 2:43 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote: Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
* As per the SFC Conflict of Interest policy, Martin was not present during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Ah, sorry, I missed the 1.3.x part when I read through it. Thanks for pointing it out (Jonathan and Rene both). I think that makes sense. And, perhaps when we discuss this again might make more sense as a way to package a bug fix program longer term. We do get a complaint from professional users that they want more stable release maintenance, but frankly, volunteers don't get excited about that... could be a clear line.
Also I'm not sure if we'll be able to extend the current contract or have to make a new one. But that's paperwork, we can figure that out. Vote A. Ted On Jul 5 2023, at 3:29 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote:
Hi Ted, The release is currently scheduled for in two weeks, although there are still blocker issues and there was some discussion at the last dev meeting to postpone it so those can be fixed in time. But yes, I fully intended to stretch some hours into 1.3.1. From the vote email:
[…] so that he can fix issues at the project's discretion for the
bugfix releases of the 1.3.x series.
After all, this is a bugfix release, and some issues will only be found after a wide release! The contract should have the same terms as the original (it’s an extension after all), and the original one already allowed to bill hours within a year.
Jonathan
Am 05.07.2023 um 21:31 schrieb Ted Gould ted@gould.cx: Hello Jonathan,
How do we expect this to work with regards to 1.3? I thought it was going to be release here soon, I'm worried it is "too late"? Or are we expecting this to be for a 1.3.1? Thanks, Ted
On Jun 29 2023, at 2:43 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background* The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards, Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Good to know about the funding side, thanks for the info.
I vote A.
On Thu, Jun 29, 2023 at 12:43 PM Jonathan Neuhauser < jonathan.neuhauser@outlook.com> wrote:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Dear all,
thanks for voting! I also vote a.
With 6x a and 1x abstain, the motion passes.
Best regards, Jonathan
Am 29.06.2023 um 21:43 schrieb Jonathan Neuhauser:
Dear PLC,
In the meeting with Pono on June 14*, the present PLC members have discussed* the extension of the bugfix accelerator program, and based on this discussion, I've created the following ballot.
*Background*
The PLC has previously allocated a total of USD 20.000 for both contractors, but Rafael dropped out very early into his contract. On the other hand, Martin has made huge efforts to get the 1.3 release as smooth as possible, fixing - if my stats are correct - 52 issues within the contract, including 2 blockers and 10 crashes. (You can see the progress over time on this page: https://gitlab.com/groups/inkscape/-/milestones/11#tab-issues)
With this vote, I propose to repurpose the funds that have already been reserved for the Bugfix accelerator program for a contract extension for Martin so that he can fix issues at the project's discretion for the bugfix releases of the 1.3.x series. This is based on the understanding that the contract is not intended to pay for Inkscape development per se, but for the project's ability to decide which bugs the contractor work will work on. This includes issues outside of the contractors "comfort zone", as was the case with the already-fixed issues.
Regarding a possible repetition of the bugfix accelerator next year: a poll will be conducted to find out how uses perceive our recent efforts to spend the project's resources, and where they would like to see our resources go. Much like the internal GTK contractor position, we would properly advertise the job posting on the mailing list, and have an open call for applications (from within the active developers).
- As per the SFC Conflict of Interest policy, Martin was not present
during this part of the meeting. He has stated that he would be available.
*Ballot*: a. Extend Martin's contract under the terms of the Bugfix Accelerator Program 2023. The contract volume will not exceed the remaining budget allocated to the Bugfix Accelerator Program 2023. b. Do not extend the Bugfix Accelerator Program 2023, the remaining funds are deallocated. c. Other: _____
Best regards,
Jonathan _______________________________________________ Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
participants (8)
-
doctormo＠gmail.com -
Jonathan Neuhauser -
Josh Andler -
Marc Jeanmougin -
Martin Owens
-
René de Hesselle -
tavmjong＠free.fr -
Ted Gould