I vote a.

On Mon, 2024-06-10 at 20:55 +0000, Jonathan Neuhauser wrote:

Dear PLC,

= Background =

We have recently adopted the working group policy. The developer team has used the its last two meetings to settle on a charter draft, which now needs to be approved by the PLC for the developer team to become the developer working group. The submitted charter below is the consensus of these developer meetings.

The PLC’s task is now to evaluate a) whether the charter fulfills the requirements of a working group, and b) whether the responsibilities and interactions are well-defined, don’t intersect with the responsibilities of other working groups (currently: none) and align with the general needs of the project.

If approved, the charter is published on the working group’s subpage. We also authorize the dev team to change the “teams” in the “interactions” section with “working groups” if/when these teams become such in the future.

= Charter =

​Name of the Working group: Development team Purpose: Development of the Inkscape software Communication: approx. weekly meeting as video call, announced at least a week prior on the project calendar; regular communication via chat.inkscape.org in team_devel Decision making process: by consensus of a quorum of 3 or more people Initial members: Jonathan Neuhauser, Marc Jeanmougin, Martin Owens, Mike Kowalski, PBS, Rafael Siejakowski, René de Hesselle, Tavmjong Bah, Vaibhav Malik, Jabiertxof, Thomas Holder, Diederik van Lierop, Patrick Storz Membership criteria:  - New members need two significant contributions before requesting to join.  - After two years of inactivity, members can be removed.   Decision Making: • Manage and maintain the Inkscape git repository   - Deciding what gets merged   - Creating protected branches   - Managing user access levels  • Decide details on the build system  • Decide which developer platforms the project supports  • Decide which platforms to release and publish to the website  • Decide technical architecture and dependencies of the software  • Represent the Inkscape project with upstream and downstream projects for technical consultation  • Schedule, perform and publish all release stages   - Decide on freeze schedules  • Decide on paid development affecting the Inkscape git repository before going to the PLC

Responsiblities: • Manage the CI infrastructure and configuration • Act as the point of contact for vulnerability reporting • Onboarding new developers who want to contribute, provide developer mentorship (i.e. GSoC and Outreachy) • Maintain developer-facing documentation, including Getting Started developer resources  • Assess the stability of the release

Interactions with other teams or working groups:  • Coordinate with the Documentation team about relevant changes for releases, such as new or changed features.  • Coordinate releases with the Vectors team for publicity and official announcements  • Coordinate with the Testing team to maintain the bugtracker(s), make decisions about available issue tracker labels, priorities and schedules.  • Coordinate with the UX Team for changes in the user interfaces

= Ballot =

a) Create the developer working group by approving the above charter. b) Deny the creation of a Developer working group in principle. b) Request the following changes: __

If a majority requests changes, the Developer team will iterate on the charter and re-submit the vote.

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

Vote A.

In a future revision I'd recommend adding something like: "create a welcoming environment for new developers" or something like that. I think the Dev working group should be in charge of encouraging new code contributions. Also, I'll note that, and I'm not sure how I feel about this, that this isn't making room for a release team. I don't know with modern CI if that is relevant anymore, though traditionally it has been different groups of folks. I could see for instance where there was a release team that managed things like the stable branches and bug fix program, where the dev team would manage new development. We haven't really made a process (and this is new, that's okay) for if a new group wanted to be formed along with an update of another charter. We can cross that bridge when we get there. Ted On Jun 10 2024, at 3:55 pm, Jonathan Neuhauser jonathan.neuhauser@outlook.com wrote:

Dear PLC,

= Background = We have recently adopted the working group policy. The developer team has used the its last two meetings to settle on a charter draft, which now needs to be approved by the PLC for the developer team to become the developer working group. The submitted charter below is the consensus of these developer meetings. The PLC’s task is now to evaluate a) whether the charter fulfills the requirements of a working group, and b) whether the responsibilities and interactions are well-defined, don’t intersect with the responsibilities of other working groups (currently: none) and align with the general needs of the project. If approved, the charter is published on the working group’s subpage. We also authorize the dev team to change the “teams” in the “interactions” section with “working groups” if/when these teams become such in the future.

= Charter =

​Name of the Working group: Development team Purpose: Development of the Inkscape software Communication: approx. weekly meeting as video call, announced at least a week prior on the project calendar; regular communication via chat.inkscape.org in team_devel Decision making process: by consensus of a quorum of 3 or more people Initial members: Jonathan Neuhauser, Marc Jeanmougin, Martin Owens, Mike Kowalski, PBS, Rafael Siejakowski, René de Hesselle, Tavmjong Bah, Vaibhav Malik, Jabiertxof, Thomas Holder, Diederik van Lierop, Patrick Storz Membership criteria:

• New members need two significant contributions before requesting to join.
• After two years of inactivity, members can be removed.

Decision Making: • Manage and maintain the Inkscape git repository

• Deciding what gets merged
• Creating protected branches
• Managing user access levels

• Decide details on the build system • Decide which developer platforms the project supports • Decide which platforms to release and publish to the website • Decide technical architecture and dependencies of the software • Represent the Inkscape project with upstream and downstream projects for technical consultation • Schedule, perform and publish all release stages

• Decide on freeze schedules

• Decide on paid development affecting the Inkscape git repository before going to the PLC

Responsiblities: • Manage the CI infrastructure and configuration • Act as the point of contact for vulnerability reporting • Onboarding new developers who want to contribute, provide developer mentorship (i.e. GSoC and Outreachy) • Maintain developer-facing documentation, including Getting Started developer resources • Assess the stability of the release

Interactions with other teams or working groups: • Coordinate with the Documentation team about relevant changes for releases, such as new or changed features. • Coordinate releases with the Vectors team for publicity and official announcements • Coordinate with the Testing team to maintain the bugtracker(s), make decisions about available issue tracker labels, priorities and schedules. • Coordinate with the UX Team for changes in the user interfaces

= Ballot = a) Create the developer working group by approving the above charter. b) Deny the creation of a Developer working group in principle. b) Request the following changes: __

If a majority requests changes, the Developer team will iterate on the charter and re-submit the vote. 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