Creating an organization for all charts

Question

Creating an organization for all charts

pmairoldi opened this issue 7 years ago · 29 comments

pmairoldi commented 7 years ago

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

pmairoldi commented 7 years ago

Sure

Answer 1 · 2017-04-02T14:29:20.000Z

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

Answer 2 · 2017-04-02T14:44:08.000Z

Yeah I mean to tag @PhilJay :-)

Answer 3 · 2017-04-02T14:44:53.000Z

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

Answer 4 · 2017-04-02T16:57:41.000Z

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

Answer 5 · 2017-04-03T05:08:01.000Z

It's a great organization;-)

Answer 6 · 2017-04-03T09:02:33.000Z

Sure thing, sounds like a good idea :-)

Answer 7 · 2017-04-03T09:31:09.000Z

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

Answer 8 · 2017-04-03T11:08:27.000Z

Yeah. Suggestions?

Answer 9 · 2017-04-03T11:22:43.000Z

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.

Answer 10 · 2017-04-03T11:27:24.000Z

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

Answer 11 · 2017-04-03T11:43:22.000Z

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

Answer 12 · 2017-04-03T12:35:14.000Z

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

Answer 13 · 2017-04-03T12:50:00.000Z

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.

Answer 14 · 2017-04-03T15:32:08.000Z

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

Answer 15 · 2017-04-04T04:35:08.000Z

Are we going to name it "Charts"?

Answer 16 · 2017-04-04T08:23:00.000Z

That name works for me!

Answer 17 · 2017-04-05T01:50:18.000Z

Works for me too

Answer 18 · 2017-04-05T02:11:32.000Z

fine for me too

Answer 19 · 2017-04-05T04:56:28.000Z

"Username is already taken". Next suggestion?

Answer 20 · 2017-04-05T07:03:05.000Z

@danielgindi
Maybe you should create a Team in Organization for better authority control, so you need to set a name for the Team. 🙃

Answer 21 · 2017-04-05T07:16:45.000Z

@danielgindi
Supplement: Not one team, maybe two team,

Android Charts Team
(contain Android Charts project and Android ChartsRealm project),
iOS Charts Team
(contain iOS Charts project and iOS ChartsRealm project).

And maybe there will has a Web Charts Team someday.

Answer 22 · 2017-04-05T12:40:33.000Z

Maybe use Mobile Charts instead. It's free. Or contact GitHub to get the username. It seems to belong to an inactive user.

Answer 23 · 2017-04-07T12:24:24.000Z

Hi there Daniel,

Thanks for getting in touch with us. I've looked over the charts account and I'm afraid it's not dormant (not all activity on GitHub is public) or available for release under our name-squatting policy.

Sorry for the disappointment, please do let us know if you have any questions about this or anything else!

Thanks,
Steve

Answer 24 · 2017-04-07T12:24:50.000Z

I don't think that "MobileCharts" is entirely appropriate as the Swift version is available for macOS too ;)

Answer 25 · 2017-04-07T21:30:44.000Z

Ya I agree. Maybe like an adjective and then charts like "BeautifulCharts" or just like "ChartsOrg"

Answer 26 · 2017-04-09T10:13:15.000Z

Hmmm, or something to highlight the cross-platform features?

Answer 27 · 2017-04-11T19:05:20.000Z

MultiCharts? Even ChartsOrg is good enough as the "org" emphasizes it's not just one vertical

Answer 28 · 2017-04-24T00:38:16.000Z

ChartsOrg is fine by me