Skip to content

Porting changes between Tahoma2D/OpenToonz #1118

@manongjohn

Description

@manongjohn

Since Tahoma2D and OpenToonz share the same general code base, it's not unexpected stuff will get ported between the two.

Technically speaking, no one really has any say or control on what gets ported, except maybe whomever is merging the PRs. Regardless, here are some guidelines to be respectful of the original developers and their work.

  1. Always give credit to the original developer by either of the following methods:

    • Add appropriate Co-Authored By information to the initial commit message.
      • Co-Authored-By: manongjohn <19245851+manongjohn@users.noreply.github.com>
      • Co-Authored-By: jeremybullock <79284068+jeremybullock@users.noreply.github.com>
    • For those who are git-savvy, create a patch from the original PR and use git am.
  2. If you are paying someone to port something over:

    • Offer to pay the original developer FIRST, especially if the developer is active.
    • If the developer is not active or they decline, then go ahead and pay someone else.
    • Please be fair with your offer, keeping mind the developer's original effort as well as porting may not be straight forward.
  3. New features/Enhancements initially developed in one, should wait to be ported to the other until after it has been officially released it in their next version.

    • T2D tends to release AFTER OT, so this is more of a concern when porting from T2D to OT.
    • Existing bug fixes, especially for crashes, do not have to follow this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions