Creating an organization for all charts

[pmairoldi]

Shouldn't we just create an organization for charts for ios, charts for android, and anything else related?

[danielgindi]

That's a great idea! @petester42 are you on board?

[pmairoldi]

Sure

[danielgindi]

Yeah I mean to tag @PhilJay :-)

[danielgindi]

I'm so busy today that I don't see what I read OR what I write

[liuxuan30]

lol I am baby sitting and typing on my phone in midnight.good idea

[Huang-Libo]

It's a great organization;-)

[PhilJay]

Sure thing, sounds like a good idea :-)

[PhilJay]

I guess it does not really matter who sets up the Organization but we should agree on a name

[danielgindi]

Yeah. Suggestions?

[PhilJay]

Well, "Charts" would probably be generic enough to describe everything and yet short and simple.
Not sure if it's an issue since the iOS part is already named that way.

[danielgindi]

Then the repos could be Charts/Swift, Charts/Android, Charts/SwiftRealm, Charts/AndroidRealm...

[PhilJay]

That could work, yes. But I'm not sure it's smart to rename the repositories concerning visibility?

[danielgindi]

Well whatever name we give them - we don't really need to change Cocoapod or Gradle names

[pmairoldi]

I think keeping the libraries names Charts is fine. We don't need to drop it and it aligns more with the actual name people will use in their code. As far as renaming goes, I'm pretty sure github redirects traffic to the new name automatically for some time.

[PhilJay]

Alright, sounds like we have a plan. Do you want me to create the organization?