-
-
Notifications
You must be signed in to change notification settings - Fork 359
What are some of your ideas on building an alternative to Meetup.com? #1
Comments
I feel like we should start by copying meetup's functionality (that are most familiar to organizers and attendees), then add features from there! |
I agree. Do we have any Meetup power users onboard? Maybe a list of features for starters. |
May not be a v1 requirement, but something that would be useful for discoverability would be a tag-like system where I can say "I'm interested in X, Y, and Z" and Organizers can say "We typically cover X, Y, and Z topics" Something like Github's Topics perhaps |
what the mvp looks like to me:
|
What @QuincyLarson said just saying it in my words: Seeing what alternatives have done best and kinda mimic it into this would make it great. |
This comment has been minimized.
This comment has been minimized.
I agree - we should start by stripping their features down to the bare essentials. |
adding to @keyserfaty's list, we should implement the queue/waitlist for highly demanded events :) |
Also:
|
Agree
Sounds like v2 to me |
maybe cancel RSVP could go into a V1, it is (soft)deleting the record, contact members is definitely a v2 |
another thing that could go to a v2 is a meetup.com compatible API for those apps that use meetup as a data source. (similar to those services that have an S3-compatible API for integration purposes) https://discordapp.com/channels/633401573002969128/633401573002969132/633416435019939874 |
Not saying an API is in the MVP, but Greenville, SC we have a simple event API tool to syndicate the Meetup.com and Eventbrite.com meetup event data to show a full tech calendar on hackgreenville.com and allow others to build apps using the open data. Moving off Meetup.com will basically break our tool until we have a way to scrap or hit an endpoint to get the same data. So, from our own "what will break when people move" perspective, a lack of an API, or at least rich snippets that can be scraped, will break some existing community tools developed by Code For Greenville. |
OK everyone - here is my bare bones description of what this tool needs to be able to do. We've already built some of this out here: https://study-group-directory.freecodecamp.org As a future participantI arrive at the home page. -> System will show a search box with "[ Where do you want to attend an event? ]" I can start typing a city, state, or country name, and it will autocomplete. -> System will show upcoming events in/around that location. I can click on one of the event names. -> The system will show the "show view" for that event's group, with details about the upcoming event, along with a button to RSVP. I can click the "RSVP" button. -> The system will prompt me to sign in. It will send me an email with a ticket and add me to the public list of event attendees. -> The day before the event, the system will email me again with a ticket and reminder. -> After the event, I will automatically get emails notifying me of subsequent events. As an organizerI can create a group. I can edit details about the group, including a Slack/Discord/Facebook/WeChat/WhatsApp link participants can join to discuss and coordinate events. I can create events, and set their location and capacity. I can cancel events. I can email the entire list of participants. I can ban a participant whom I believe is toxic or who has previously broken the code of conduct. I can add a venue sponsor to the event with a link to their website as a way of thanking them for hosting. I can add a food sponsor to the event with a link to their website as a way of thanking them for food. |
@allella that's cool. don't think you'll be able to replace meetup with this tool right away. sounds like an important feature but definitely not the first thing we should tackle. but sounds great for v2. |
Great idea to have the homepage dynamically surface events tailored to IP address. |
That would not work for people behind VPN. I would just prefer decent search engine based on typed location. |
I guess I should ask if the v1, or even v2, is intended to host non-FCC groups, or if this is for the FCC universe? |
@allella I guess any group, even non-coding related. |
Some features we need as organizers because some venues ask for this info (meetup currently has these, fields aren't required though)
|
Could also be v2, but organizers often will link to an organization landing page and specific event instances. Having public URLs would shortcut the "enter city", "find your group" steps if someone already knows why they are there. Also, having some structured markup, like event rich snippets, on the org and event landing pages would offer at least some basic API alternative until such time as an API could be built. I'd be motivated to assist with the event markup and API development since I volunteer to support tools that need a way to get at the event data through a script. |
@nhsz Yep I see those in a v2 probably |
Moved to #2 |
I'm sure all cities have different needs, but here's an idea of what we consider a "tech meetup" in Greenville, along with an API behind that holds info about all our organizations in the area, the organizers, where they post events, API endpoint keys for the event service they use. Might be a nice v2, v3 feature to allow each city to have a similar list of all the organizations by certain tags or categories. Basically, I'd be glad to replace our homegrown orgs and events data and APIs with a service that all cities could enjoy. |
Hey, I've built a good chunk of this already. Happy to chat about what I have. The intention is to release it as OSS and would like to collaborate on efforts |
EventoL is the platform that uses the Python Community in Argentina to managing their events |
Mobilizon from Framasoft is a french solution that aims to replace Facebook Events and MeetUp applications by a ethic, free and open-source solution (which could be self-hosted in the future). |
I think it just be first location based, through the Browser location API and in case of negative response, based on typed location |
Are we going to have a central document holding all the features we've agreed on, and what are the next steps/structure for building this? Pardon me if these questions are naive. First time collaborating on an open-source project, ever. |
How about using GitHub as a meetup platform? https://mobile.twitter.com/dev__adi/status/1183873754679537666 |
Love your suggestions @lorenanicole! Are we assuming accessibility (a11y) is obvious, or should we point it out explicitly?
|
this should be in v1 itself😐
I can reschedule/postpone events. |
I helped build Kickback (https://kickback.events/), an Ethereum-based platform which aims to reduce event no-shows. Essentially speaking, each attendee commits a small amount of money (e.g. $10) when they RSVP. If they turn up they get their money back. If they don't show up their money gets split amongst those who did. The money handling is secure, transparent and automated via a smart contract running on Ethereum. (Most recently we did 13 small events at the Devcon5 conference in Osaka and got an overall average turn-up rate of ~80% on Kickback). If we're building an alternative to meetup.com how about integrating with platforms like Kickback and/or incorporating such features? (You can even use our smart contracts directly: https://github.com/wearekickback/contracts). |
Hey hiddentao! Met your colleague at EthBerlinZwei and chatted ~1h. Keep up the great work, Kickback rocks! Let me just be slightly two faced here: adopting Dapps is not simple anyway - if you alone need gas to create state changing tx, "real" money will be always involved. If you on top have to "pay" something upfront (even if guarantees are that you get it back (minus gas?) ), I think that'll have a negative impact as well. Nevertheless I think that Kickback already demonstrates today what will be one of the best concepts tomorrow! |
@elmariachi111 You're absolutely right about the gas cost. This is something the Eth community at large needs to solve. Hopefully in the near future this will not a blocker for dapps. |
Brainstorms:
|
@maiya-22 The #implementation-details-discussions on Discord is pretty close to the second idea, at least for now. |
@maiya-22 also, accessibility was mentioned by these folks if you want to get a conversation issue going on that, or in an existing issue if it makes sense. List of those who identified as interested in accessibility in earlier comments. |
I'd love to help on accessibility stuff, thanks for the |
Should we offer some functionalities listed below ( I might be totally wrong ):
|
I would very much like for this to use ActivityStreams, so that all the instances of Chapter can federate with each other and possibly even federate with other ActivityStreams implementations such as Mastodon and PixelFed. |
If it doesn't start with an API, one will never be implemented without a full rewrite. |
@MarkAtwood there are very early conversations about interoperability between Collective instances in #36 and the API folks are mainly talking at #17 and pull requests like #46, so now is the chance to steer those conversations and/or point people to open-source things that already pave the way. |
Haven't seen this suggested yet, but some conversation in a local Slack group pointed out how useful it would be to have "collaboration" or "partner" groups. E.g. organizers could:
This could be both for managing multiple Chapters within a single organization (i.e. myself and 2 coworkers currently run independent meetups, all paid for by the company), or across organizations (i.e. I'd like to not have my events the same night as a couple nearby groups that many of my members also attend). |
@brianrichins it's a useful feature for sure and aligns somewhat with the proposed vision. We have a view of meetup "day of the month" for Greenville, SC to help organizers not plan a new meetup on a saturated day. Whether this is the responsibility of Chapter, or an app that ties into Chapters, can be determined as the product evolves. |
@brianrichins This would be a great feature to have for future releases. I could see this kind of coordination to be really helpful - especially for the example you gave, where different nearby chapters would want stagger their events so as not to draw one another's audiences. I don't think internal planning tools are high enough priority for our rougher MVP, though. |
I have enjoyed reading the discussions here. So many exciting ideas and directions we could go in. I am going to close this thread in favor of concentrating discussion over on #47 |
* chore: added speccy to docker compose dev environment * chore: added speccy to dev deps, added/updated scripts, fixed husky warning * test: added test for SomeComponent * docs: updated scripts and added testing * chore: setup jest testing
* basic app skeleton * update readme * remove body parser * tsconfig target esnext * nodemon -> dev dep * api route examples * custom typing for responseErrorHandler * oops fix speccy location * tslint -> eslint * add dockerfile, update installation instructions in README * emptyline at end of eslintignore * Revert "add dockerfile, update installation instructions in README" This reverts commit 8075dc4. * Revert "Revert "add dockerfile, update installation instructions in README"" This reverts commit cf502e5. * fix dockerfile and use npm ci * update readme, update nodemon watch files * add next to the docs * Add suggestions/fixes to skeleton (#1) * chore: added speccy to docker compose dev environment * chore: added speccy to dev deps, added/updated scripts, fixed husky warning * test: added test for SomeComponent * docs: updated scripts and added testing * chore: setup jest testing * no more dockerfile, update docs * add js and jsx extensions to configs * chore: removed unnecessary network, switched to using top level volume (#2) * Mvp/skeleton (#3) * fix(setup) Add note for linux users about docker-compose problem with PWD * fix(client) Use named functions for components * fix(setup) Turn of ts noImplicitAny * fix(setup) Use es6 imports in next config * fix(docker) Remove top level volumes * fix(setup) add newline to end of package.json
Continuing the conversation from Discord!
The text was updated successfully, but these errors were encountered: