Dandelion Theme?

[yeqbfgxjiq]

@lkngtn was thinking about how we can create a stronger narrative/story around this suite of applications. Referring to Kits as "Dandelion Orgs" woudl create a nice visual association between the process of forking the org to create something new and the process of dandelions spreading seeds.

Do we want to theme the Kit as a dandelion?

• my vote is yes

[lkngtn]

I was planning on using Dandelion for the moloch/grants kit due to the emphasis on the redemptions mechanism.

I like the idea of using flowers for naming templates/kits though, and suggest we pick another flower name and use the convention flower-kit for this repo. Maybe Poppy, Daisy, or Aster, or Sunflower

[yeqbfgxjiq]

I think this makes more sense for a Kit because the Kit is like a dandelion. It has the seeds for hundreds of other Kits. Creating it makes other things like it possible.

Also, while flowers are cool they don't add any additional information about what an app/project is or does. If the metaphor is appropriate, then we can add in flowers or anything else, but first the title/theme should be linked directly to what the app/project is/does.

[lkngtn]

Per the conversation on keybase, it may make sense to refer to this as a "KitKit" since it seems to be a kit/framework for creating kits/templates.

Also, while flowers are cool they don't add any additional information about what an app/project is or does. If the metaphor is appropriate, then we can add in flowers or anything else, but first the title/theme should be linked directly to what the app/project is/does.

I agree with this, I think part of the challenge though is that each dao kit/model broadly serves the same purpose (to help people collaborate/organize). Some may more closely resemble existing structures, for example the 1Hive model with Bees being the final authority resembles a "worker-owned co-operative", but there may be many variations on a worker-owned cooperative dao structure that have different processes. The Moloch/Grants kit sort of resembles a partnership but with bylaws which allow for exit at any time.

So if we try to link directly to what the project does we run into problems because 1) what it does is fairly unique but the closest reference is to legal structures, but these are specifically NOT legal structures, and 2) there may be name collisions since there are many variations that would closely map to the same legal structures.

So my thinking was that by picking a naming convention that is thematic but will not have naming collisions, we have a blank slate in terms of associating a use case / target user with each kit.

[yeqbfgxjiq]

Closing this because it's no longer relevant. I like how the dandelion-kit repo says: An organization template intended to enable organizations to form and dissolve quickly. That seems like a great fit for the dandelion theme :)