Difference between revisions of "Krita/docs/meetings/2016 01 Deventer Sprint"

< Krita‎ | docs‎ | meetings
Jump to: navigation, search
(Agenda)
(Agenda)
Line 12: Line 12:
 
# [DONE] Clean-up library mess (?). Library split after 3.0.
 
# [DONE] Clean-up library mess (?). Library split after 3.0.
 
# New shortcuts. How to solve the problem?
 
# New shortcuts. How to solve the problem?
# 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?
+
# [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?
 
# opengl (first priority!!!)
 
# opengl (first priority!!!)
# Tags system and resources. People still report that their tags are lost/broken upon Krita restart/crash.
+
# [DONE] Tags system and resources. People still report that their tags are lost/broken upon Krita restart/crash.
 
# 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?

Revision as of 18:29, 21 January 2016

2016 Krita Deventer Sprint

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. 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. 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?
  12. Better communications what happens where. Probably, some official log? :)

Future projects

  1. GPU-based layers and painting tools. What should it look like?
  2. 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. Real paint engine (bumpmap + height + bristles)
    3. Quick brush (quick but not smooth when painting)
    4. Marker brush (quick, but opacity is not variable)
  5. Database of testing images from users. Is it worth it?

Content is available under Creative Commons License SA 4.0 unless otherwise noted.