Difference between revisions of "Hackfest2018 Kiel Topics"

From Inkscape Wiki
Jump to: navigation, search
(Topics for Inkscape Hackfest 2018 in Kiel)
(Topics for Inkscape Hackfest 2018 in Kiel)
Line 41: Line 41:
 
* SVG 2 strategy (Tav)
 
* SVG 2 strategy (Tav)
 
* Recruiting of new developers
 
* Recruiting of new developers
* improve first-user experience (Max,  )
+
** Extensions seems to be a popular path.
 +
** Encourage people to write extensions.
 +
* Improve first-user experience (Max,  )
 
* [https://gitlab.com/inkscape/inkscape/merge_requests/250 invert y-axis]
 
* [https://gitlab.com/inkscape/inkscape/merge_requests/250 invert y-axis]
** work on guides (Thomas)
+
** Work on guides (Thomas)
** work on 3D boxes (Thomas)
+
** Work on 3D boxes (Thomas)
** testing
+
** Testing
 
* Package dependencies (Mc ?)
 
* Package dependencies (Mc ?)
 
* ...
 
* ...

Revision as of 10:26, 9 September 2018

Other pages: Hackfest2018 Kiel, Hackfest2018 Kiel Attendees.

Topics for Inkscape Hackfest 2018 in Kiel

  • Inkscape 1.0 release:
    • Testing: Establish a testing team. (jnweiger)
    • Bug fixing: 1.0_Release_Bug_Fix_List (Patrick, Mc)
    • Release notes (Maren)
    • Release news/press management (Vectors?)
    • Translations
      • Focus on Spanish, Brazilian Portuguese, and Indonesian (Maren)
      • How to translate extensions? (doctormo)
    • Discuss (and possibly put into place) a web interface (hosted or self-hosted) for Inkscape-related translations. (Weblate?) (Maren, doctormo)
    • Plan. Find release manager, Mc volunteers! (Mc)
  • Improving developer documentation. (Patrick)
    • Test the build instructions (in recent mails people reported some problems)
      • CompilingMacOsX (Thomas)
      • Mac Packaging - Find volunteer, signing (Inkscape can pay for certificate).
    • Bugfix reporting process (Mc, Patrick)
      • Move to GitLab.
      • Two trackers? One for users, one for developers.
      • Automatically close bugs... with email to submitter to reopen.
      • Establish a bug team.
      • Web interface.
      • List of experts.
    • Extensions API documentation, python, c++, gitlab... (jnweiger)
      • New API, document as one learns.
  • Improving user documentation.
    • Prepare 1.0 documentation (Patrick)
    • Update Tutorials.
  • Improving the extension API, especially for physical output (lasercutting, vinyl plotting, ...) (doctormo, Max, jnweiger)
    • Hatching (Tav)
    • Improve/merge the lists of extensions
  • Extension Manager, maybe the gimp way?(jnweiger, max, doctormo)
  • Licensing GPL 2 -> GPL 3 (Tav)
    • Ask developers.
  • File menu Files: Output (Tav)
  • SVG 2 strategy (Tav)
  • Recruiting of new developers
    • Extensions seems to be a popular path.
    • Encourage people to write extensions.
  • Improve first-user experience (Max, )
  • invert y-axis
    • Work on guides (Thomas)
    • Work on 3D boxes (Thomas)
    • Testing
  • Package dependencies (Mc ?)
  • ...