Phabricator Structure (don't close) (DO READ!)
Open, Unbreak Now!Public

Description

Flow of a feature:

  1. First goes into Krita: Abyss
    1. Here artists with ideas can leave their idea(but do notify us first).
  2. Then someone who is interested, will take this task(assign it to themselves). (You absolutely need to be commited to making the feature work)
  3. It will be moved to Krita: Next Features if
    1. Figure out usecases(idea gathering)
    2. Done when: A post is made with consolidation of ideas and requirements.
    3. First architecture is designed and gui is designed.
    4. Done when: When we have a mockup that people can agree on.
    5. Code the feature(needs coding)
    6. Done when: reviewed and merged into master.
  4. If feature is implemented, merged, and there has been a mail to the mailing list(!Important!)
  5. Assign Krita: Manual and #krita_testing . (So that it can be documented, and get a test-by-fire)
  6. When those are done. Move to Krita: Releases , where it'll be put into a 'make noise' column.
  7. Final resting place in column of release that it was in.

Other boards:

Related Objects

Mentioned In
Krita
woltherav updated the task description. (Show Details)Aug 30 2016, 1:59 PM
eliasp added a subscriber: eliasp.Apr 17 2017, 4:27 PM

If you want to make sure, every Krita contributor read this document, you might just want to use a Legalpad document instead, then set the "Editable By" policy of Krita to a custom policy which has the corresponding Signers of Legalpad document configuration set.