search

GetTogetherComm / GetTogether

Event manager for local community events
https://gettogether.community
BSD 2-Clause "Simplified" License
473 stars 89 forks source link

Strategy documentation reference? #34

Open LeeteqXV opened 6 years ago

LeeteqXV commented 6 years ago

a) is there a strategy document(ation) somewhere? b) how are strategic elements identified and pulled out of "normal issues"? (and tagged/grouped?) c) Examples/Most pressing strategic clarifications:

  1. Distinction btw. this platform and CMS related to collaborative features. Should this system attempt to "be everything needed for effective communication and organisation of event content, or is it smarter long-term with an integration strategy? (API's)

  2. Security/Logins/Account features related to reputation management. (partially overlaps with collaboration features)

mhall119 commented 6 years ago

a) There isn't a defined strategy yet. So far it's been mostly "Do what meetup.com can do" but in a way that's open and free b) I've setup milestones for the next release (0.2.0) and a longer term goal (1.0.0) that I'm using to strategically target feature work

c.1) I don't want it to become a CMS, I want to keep it structured and focused on events planning & promotion. That said, I'm in favor of federation and open APIs, and won't say no to more of them.

c.2) GetTogether shouldn't be in the business of identity management. Currently it uses GitHub and Google authentication, and I'd like to to use Facebook and Twitter also. But I don't want it to become the source of authentication.