Rename to ZooniverseAPI

[edpaget]

@chrissnyder and I were talking about it this today, but we really think Panoptes and Panoptes-Front-End, should be renamed to ZooniverseAPI and zooniverse.org respectively.

I think this move would help our #hashtag #brand because it would mean when people are talking about this new thing at conferences they can say, "We have a new API and website, zooniverse.org, for building your own Zooniverse projects", instead of, "We have this new thing, Panoptes, which is ...".

[edpaget]

Also it would get rid of calling things 'Panoptes Projects' they would just be 'Zooniverse Projects', and it would remove the weird Foucault association I get every time I say the name (not sure if that's a problem for other people).

[chrissnyder]

:+1: on pretty much everything here

[vrooje]

:+1:

[camallen]

I assume you're talking about these repository names?

[adammcmaster]

I agree. Frankly I was surprised we kept the “panoptes” name when we went live. I always thought of it as just an internal codename for development.

On 14 Oct 2015, at 10:08, Campbell Allen notifications@github.com wrote:

I assume you're talking about these repository names?

— Reply to this email directly or view it on GitHub https://github.com/zooniverse/Panoptes/issues/1429#issuecomment-147984364.

[aliburchard]

:+1:

[chrissnyder]

@camallen Repo names, references in code, and more generally how we talk about the platform.

[camallen]

got it

[marten]

Seems like @astopy is using "panoptes" in AWS as a more broad term for "the api and related services"? Might be useful to think about what we call the collective group of apps (ie panoptes+nero+aggregation+$thing).