API design management

[bajiat]

From @kyyberi on November 3, 2015 17:2

Since we are supporting API design in apinf, we need to have management for the designs as well. Management is versioning, co-authoring, comparing designs (more than diff), sharing designs, collecting designs to groups.

Copied from original issue: apinf/platform#577

[bajiat]

From @kyyberi on November 3, 2015 17:9

and force to select license for the design.

[bajiat]

From @kyyberi on November 3, 2015 17:10

It could become sort of thingiverse for APIs...

https://www.thingiverse.com/

[bajiat]

From @philippeluickx on May 24, 2016 8:38

+1 on the versioning, we should add changelogs too then.

[bajiat]

From @philippeluickx on May 24, 2016 8:43

Created a new issue for versioning https://github.com/apinf/api-umbrella-dashboard/issues/960, so we can have 1 feature / 1 ticket

[bajiat]

From @philippeluickx on June 7, 2016 8:38

Createad a new issue for licensing https://github.com/apinf/api-umbrella-dashboard/issues/1056

[xylix]

@kyyberi Can you explain to me and Tulir what parts of this discussion are still relevant and what do they mean in practice? If these are still relevant we probably want to split it up into multiple feature issues.