Krita/docs/meetings/2016 01 Deventer Sprint: Difference between revisions

From KDE Community Wiki
< Krita‎ | docs‎ | meetings
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
= 2016 Krita Deventer Sprint =
= 2016 Krita Deventer Sprint =
[https://notes.kde.org/p/krita-meeting-deventer-sprint Meeting Munites]
[https://notes.kde.org/p/krita-meeting-deventer-sprint Meeting Munites]
[https://docs.google.com/document/d/1TWhg7xIx4H1aDwvoN9cE6ucRk-pCKVaA3W5Z1tCKC-I/edit 2nd version]
== Preparations work ==
== Preparations work ==


Line 17: Line 18:
# Documentation for newcomers (users '''and''' developers)
# Documentation for newcomers (users '''and''' developers)
# Bugs and tasks management. Should we make a bug-squad-team?
# Bugs and tasks management. Should we make a bug-squad-team?
# Better communications what happens where. Probably, some official log? :)


== Future projects ==
== Future projects ==

Latest revision as of 22:53, 23 January 2016

2016 Krita Deventer Sprint

Meeting Munites 2nd version

Preparations work

  1. List of bugs that need to be fixed in group (cannot be fixed by a single developer, need consultations and so on)

Agenda

  1. [DONE] How to set up a Mac dev environment (Boud and Dmitry)
  2. Group bug-fixing
  3. Planning for the Kickstarter
  4. Planning for Krita 3.0
  5. [DONE] Clean-up library mess (?). Library split after 3.0.
  6. New shortcuts. How to solve the problem?
  7. [DONE] warnKrita and dbgKrita policy. Now we don't see important messages, e.g. real warnings. And see too many messages in unittests. How to solve it?
  8. [DONE] opengl (first priority!!!)
  9. [DONE] Tags system and resources. People still report that their tags are lost/broken upon Krita restart/crash.
  10. Documentation for newcomers (users and developers)
  11. Bugs and tasks management. Should we make a bug-squad-team?

Future projects

  1. GPU-based layers and painting tools. What should it look like?
  2. [DONE] Cloud storage for Krita resources and configurations. Subscriptions?
  3. Scripting
  4. New brush engines. We need something really new. Known possibilities:
    1. Waterpaint brush
    2. Impasto? or:
    3. Real paint engine (bumpmap + height + bristles)
    4. Quick brush (quick but not smooth when painting)
    5. Marker brush (quick, but opacity is not variable)
  5. Database of testing images from users. Is it worth it?

Collect Requirements to Kickstarter stretch goals

  1. Animated format support
  2. Guides and Rulers
  3. HUD for manipulating common settings on canvas
  4. Fuzzy Strokes
  5. Grid Docker
  6. Improve Palette Docker
Retrieved from "https://community.kde.org/index.php?title=Krita/docs/meetings/2016_01_Deventer_Sprint&oldid=45491"