This repository serves as the source of truth for planning and requirements of the event member management system.
Community groups often need to post their events across various social media networks. This is often a great deal of copying and pasting with minor edits. Tracking RSVPs across social media events is also manual effort that consumes a great deal of time yet is worth effort. Additionally, organizers need ways to identify which members come to which types of events in order to better gauge popularity and predict attendance for future events they may attend. Paid solutions exist to fulfill these needs, but many early communities lack the funds to pay for these services.
The Event Member Management System (which really needs a better name) is meant to allow community organizers to manage events across various social media and to get a better understanding of their members' attendance patterns without paying for a for-profit service.
This repository is meant to define requirements for the system regardless of software language or framework. For purposes of learning, we encourage anyone to implement these requirements in any method they desire, both in and out of CodeSeoul. Initially, CodeSeoul will target a single technical stack, but multiple, duplicate, even competing implementations are welcome.
- Basic sign up and login, along with basic user roles
- Admins can post events across major social media
- Admins can track RSVPs and attendance aggregated across social media
- Admins can track and report attendance over time to provide insight into better future events
- Community members can sign up directly and view their history
- Admins can prepare live streams for events
Do note that the key features may change as the system matures. This is intended to be a living document that will grow and evolve as the system and needs evolve.
All requirements are malleable. Pull requests and discussion via issues or our Discord are always welcome. Also, we are not perfect. If you find something wrong or believe something could be done better, we'd love a pull request. That includes the manner in which we're even defining requirements and structuring this repository.
- High-Level Feature List
- Data Model
- Technical Architecture
- User Personas
- User Flows
- Use Cases
- Wireframes and Mockups
This is a list of other services that have similar features to what we're targeting. Note that many of these services have features far beyond what is intended for this sytem. The intent is not to directly compete with them across all features but to use them as inspiration for our core goals.