Move field-type-color to a separate repository and plugin

sealcode / sealious

An extensible, declarative node framework

25 stars 2 forks source link

Move field-type-color to a separate repository and plugin #204

Closed kuba-orlik closed 8 years ago

arkadiusz-wieczorek commented 9 years ago

We want to create new repository for non-standard field-types?

kuba-orlik commented 9 years ago

Well, there are a few options that come to my head:

create a repository for each exotic field-type we come up with
create one, unified repository that would contain multiple (possibly many) field-types
a combination of the above solutions - create a separate repository and npm package for each field-type, but create a new npm package that would enable to install them all in bulk.

Which do you think is the best?

arkadiusz-wieczorek commented 9 years ago

the weak point (many) field-types will generate many repositories in the first case it would be ugly mess
second option certainly wouldn't generate mess in our github page
third option is nice, but I don't like many small repositories

I propose to create one repository for all exotic field-types, because one field-type needs typically ~1kB. It's not big plugin or something like this.

kuba-orlik commented 8 years ago

the weak point (many) field-types will generate many repositories in the first case it would be ugly mess I think that having many repositories for an organization is quite common, so perhaps it's not something to dread.

Currently I'm considering two options:

create a separate repository for color field-type
move color field-type to the core repository

What do you think?

arkadiusz-wieczorek commented 8 years ago

I would like to add this field type to the core repository. :) Because field type it's very tiny element of whole Sealious API

kuba-orlik commented 8 years ago

https://trello.com/c/8WOnlGkz/16-move-field-type-color-to-core