Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

Commit

Permalink
Change "collective" to "organization" in the README
Browse files Browse the repository at this point in the history
This makes the terminology match up with Quincy's pending vision statement
#47 (comment)
  • Loading branch information
allella authored Oct 17, 2019
1 parent 1002cd2 commit 8ff30a3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ You can use your own authentication tools. And all your user data will stay on y

To better communicate and more easily build an API and UI, we've decided on a collection of terminology to discuss about the Chapter project in a clear way:

- `collective` is one singular instance/deployment of Chapter. For e.g., Women who Code at the domain `chapter.womenwhocode.com`.
- `organization` is one singular instance/deployment of Chapter. For e.g., Women who Code at the domain `chapter.womenwhocode.com`.
- `user` is a person who authed to the chapter.
- `chapter` is a container for events, with a description and subscribers, and one or more admins who can manage it. For e.g., Women who Code NYC.
- `event` is a single meetup that users can RSVP to, has a specific location and time, and has organizers. For e.g., Women who Code NYC April Meet.
Expand Down

0 comments on commit 8ff30a3

Please sign in to comment.