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

Responsibilities:

• 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 interface