Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminology #1

Open
dbrgn opened this issue Jan 18, 2017 · 2 comments
Open

Terminology #1

dbrgn opened this issue Jan 18, 2017 · 2 comments

Comments

@dbrgn
Copy link
Member

dbrgn commented Jan 18, 2017

Right now, we call our fork the "Space Directory" but still refer to the API as "Space API".

Ideally, we can reach an agreement with the original SpaceAPI developer in order to take over the name. But in case this doesn't happen, how should we proceed?

If we use both names interchangeably, people will probably get confused. Should we use the term "Space Directory API" instead? That's a bit unwieldy.

Any ideas are welcome :)

@rorist
Copy link

rorist commented Jan 19, 2017

SpaceAPI is a good name, I think we should stick with it if possible.
If not, maybe we can add Hackerspaces in the name, as in HackerSpacesAPI.

@dns2utf8
Copy link
Member

I think this project should be the directory of SpaceAPI endpoints.
Providing easy to setup and maintain software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants