==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
Jonathan
I vote a)
Though I will understand if others want to tweak some wording, I'm hoping we managed to collect everyone's thoughts in the redraft.
Martin,
On Wed, 2024-03-27 at 20:32 +0100, Jonathan Neuhauser wrote:
==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
Jonathan
Inkscape Board of Directors mailing list -- inkscape-board@lists.inkscape.org To unsubscribe send an email to inkscape-board-leave@lists.inkscape.org
Let me retry to send the attachment. Sorry for that!
Am 27.03.24 um 20:32 schrieb Jonathan Neuhauser:
==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
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 c.
I propose to strike paragraph 6.e. from the policy.
Reasoning: if the project decides to give hardware way, it happens solely at our discretion and after careful consideration. I’d like for us to reserve any and all rights so that we can do as we see fit on individual case-by-case basis. Creating some guidelines or precedent in the policy will restrict our freedom to do so and I’m not comfortable with that.
For clarification: *I am not* saying that we shouldn’t give hardware away when the time or opportunity arises, *I am* saying that I don’t want to make any decisions or written concessions at this point.
Example: imagine a scenario where the hardware is no longer being used but we’d like to donate it to someone else instead of the contributor who has been using it up to this point. There shouldn't be any grounds to claim „but your policy said I could keep it“.
René
Am 27.03.2024 um 20:32 schrieb Jonathan Neuhauser jonathan.neuhauser@outlook.com:
==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
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 Wed, 2024-03-27 at 23:05 +0100, René de Hesselle wrote:
I vote c.
I propose to strike paragraph 6.e. from the policy.
Reasoning: if the project decides to give hardware way, it happens solely at our discretion and after careful consideration. I’d like for us to reserve any and all rights so that we can do as we see fit on individual case-by-case basis. Creating some guidelines or precedent in the policy will restrict our freedom to do so and I’m not comfortable with that.
For clarification: *I am not* saying that we shouldn’t give hardware away when the time or opportunity arises, *I am* saying that I don’t want to make any decisions or written concessions at this point.
Example: imagine a scenario where the hardware is no longer being used but we’d like to donate it to someone else instead of the contributor who has been using it up to this point. There shouldn't be any grounds to claim „but your policy said I could keep it“.
I'm not sure it says that. Or I mean it's not intended to say that.
"Kept" in this instance is supposed to mean "kept safe", and is not supposed to mean "owned". But you are right this is ambiguous. It's supposed to allow people who have the hardware the option of helping the project by keeping the hardware safe until it's needed. So we don't need to pay for a warehouse to store it all when it's not strictly being used.
I'll add a note and wait for the others.
Martin,
I'll vote (a) again, even if it looks a bit more restrictive than the previous one^^
On 27/03/2024 20:32, Jonathan Neuhauser wrote:
==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
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,
I also vote a), and the 7 days are over, so:
The motion passes.
Jonathan Neuhauser: a Josh Andler: (did not vote) Marc Jeanmougin: a Martin Owens: a René de Hesselle: c Tavmjong Bah: a Ted Gould: (did not vote)
Best regards
Jonathan
Am 27.03.24 um 20:32 schrieb Jonathan Neuhauser:
==== Background ====
The developer team would like to improve cross platform support, and one measure towards that goal is to improve the access to Windows and macOS machines for core contributors.
With merging the GTK4 branch, there is new interest in such a program.
Martin and I have drawn up a policy for this program, which is attached. It mostly combines my previous email with your comments, plus some context around it.
We've decided against excluding mice and keyboards, although I understand where the objection comes from. As other peripherals, such as color-correcting screens, stylus-like devices, etc. they may be relevant for improved hardware support (e.g.macOS specific keyboards, the touchpad and stylus included with Microsoft Surface keyboard covers etc.). I would, however, expect that a developer who returns a keyboard would at least wipe it a little bit!
Again, the policy is directed at proven and trusted contributors.
We'd like to test out the procedure of the policy, so if it passes, I'd ask the four people listed in the last email to request the hardware as per section 3.
==== Vote ====
a) Approve the attached hardware policy.
b) Don't approve the attached hardware policy.
c) Other: ....
Thanks in advance,
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 (4)
-
doctormo＠gmail.com -
Jonathan Neuhauser -
Marc Jeanmougin -
René de Hesselle