Krita/docs/meetings/2016 01 Deventer Sprint: Difference between revisions
(→Agenda) |
|||
| (12 intermediate revisions by 2 users 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://docs.google.com/document/d/1TWhg7xIx4H1aDwvoN9cE6ucRk-pCKVaA3W5Z1tCKC-I/edit 2nd version] | |||
== Preparations work == | == Preparations work == | ||
| Line 6: | Line 7: | ||
== Agenda == | == Agenda == | ||
# How to set up a Mac dev environment (Boud and Dmitry) | # [DONE] How to set up a Mac dev environment (Boud and Dmitry) | ||
# Group bug-fixing | # Group bug-fixing | ||
# Planning for the Kickstarter | # Planning for the Kickstarter | ||
# Planning for Krita 3.0 | # Planning for Krita 3.0 | ||
# 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? | ||
# [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? | |||
# [DONE] opengl (first priority!!!) | |||
# [DONE] Tags system and resources. People still report that their tags are lost/broken upon Krita restart/crash. | |||
# Documentation for newcomers (users '''and''' developers) | |||
# Bugs and tasks management. Should we make a bug-squad-team? | |||
== Future projects == | |||
# GPU-based layers and painting tools. What should it look like? | |||
# [DONE] Cloud storage for Krita resources and configurations. Subscriptions? | |||
# Scripting | |||
# New brush engines. We need something really new. Known possibilities: | |||
## Waterpaint brush | |||
## Impasto? or: | |||
## Real paint engine (bumpmap + height + bristles) | |||
## Quick brush (quick but not smooth when painting) | |||
## Marker brush (quick, but opacity is not variable) | |||
# Database of testing images from users. Is it worth it? | |||
== Collect Requirements to Kickstarter stretch goals == | |||
# [https://phabricator.kde.org/T116 Animated format support] | |||
# [https://phabricator.kde.org/T114 Guides and Rulers] | |||
# [https://phabricator.kde.org/T127 HUD for manipulating common settings on canvas] | |||
# [https://phabricator.kde.org/T166 Fuzzy Strokes] | |||
# [https://phabricator.kde.org/T109 Grid Docker] | |||
# [https://phabricator.kde.org/T112 Improve Palette Docker] | |||
Latest revision as of 22:53, 23 January 2016
2016 Krita Deventer Sprint
Preparations work
- List of bugs that need to be fixed in group (cannot be fixed by a single developer, need consultations and so on)
Agenda
- [DONE] How to set up a Mac dev environment (Boud and Dmitry)
- Group bug-fixing
- Planning for the Kickstarter
- Planning for Krita 3.0
- [DONE] Clean-up library mess (?). Library split after 3.0.
- New shortcuts. How to solve the problem?
- [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?
- [DONE] opengl (first priority!!!)
- [DONE] Tags system and resources. People still report that their tags are lost/broken upon Krita restart/crash.
- Documentation for newcomers (users and developers)
- Bugs and tasks management. Should we make a bug-squad-team?
Future projects
- GPU-based layers and painting tools. What should it look like?
- [DONE] Cloud storage for Krita resources and configurations. Subscriptions?
- Scripting
- New brush engines. We need something really new. Known possibilities:
- Waterpaint brush
- Impasto? or:
- Real paint engine (bumpmap + height + bristles)
- Quick brush (quick but not smooth when painting)
- Marker brush (quick, but opacity is not variable)
- Database of testing images from users. Is it worth it?