Difference between revisions of "Hackfest2018 Kiel Topics"

From Inkscape Wiki
Jump to navigation Jump to search
 
(36 intermediate revisions by 7 users not shown)
Line 4: Line 4:


* Inkscape 1.0 release:
* Inkscape 1.0 release:
** Testing
** Testing: Establish a testing team. (jnweiger)
** Bug fixing
** Bug fixing: [[1.0_Release_Bug_Fix_List]] (Patrick, Mc)
** Release notes (Maren)
** Release notes (Maren)
** Translations (focus on Spanish, Brazilian Portuguese, and Indonesian, Maren)
** Release news/press management (Vectors?)
** Discuss (and possibly put into place) a web interface (hosted or self-hosted) for Inkscape-related translations
** Translations
* Improving developer documentation.
*** 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)
** 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.
* Improving user documentation.
* Improving the extension API, especially for physical output (lasercutting, vinyl plotting, ...) (doctormo)
** Prepare 1.0 documentation (Patrick)
** Update Tutorials.
* Improving the extension API, especially for physical output (lasercutting, vinyl plotting, ...) (doctormo, Max, jnweiger)
** Hatching (Tav)
** Hatching (Tav)
** Improve/merge the lists of extensions
** Improve/merge the lists of extensions
* Extension Manager, maybe the gimp way?(jnweiger, max, doctormo)
** extensions packaging (jnweiger, Patrick)
** visibility, overview of many lists -> https://inkscape.org/de/gallery/=extension/
** announce extensions, locations, rss feed
* Licensing GPL 2 -> GPL 3 (Tav)
* Licensing GPL 2 -> GPL 3 (Tav)
** Ask developers.
* File menu [[Files: Output]] (Tav)
* File menu [[Files: Output]] (Tav)
* SVG 2 strategy (Tav)
* SVG 2 strategy (Tav)
* Recruiting of new developers
* Recruiting of new developers
* improve first-user experience
** Extensions seems to be a popular path.
** Encourage people to write extensions.
* Improve first-user experience (Max,  )
* <s>[https://gitlab.com/inkscape/inkscape/merge_requests/250 invert y-axis]</s> DONE
** <s>Work on guides (Thomas)</s> DONE
** <s>Work on 3D boxes (Thomas)</s> DONE
** Testing
* Package dependencies (Mc ?)
** libcroco: get our changes upstream (Tav)
* ...
* ...

Latest revision as of 17:26, 12 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
      • 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 DONE
    • Work on guides (Thomas) DONE
    • Work on 3D boxes (Thomas) DONE
    • Testing
  • Package dependencies (Mc ?)
    • libcroco: get our changes upstream (Tav)
  • ...