This relates to #16.

Need to check the feasibility of issuing a custom template to Meetup API's to trigger the mail with google form link.

Currently the readme contains very less information about the lets build program. We should add a section there mentioning it in detail.

Home Page

Top Carousel

The idea is to have infinitely scrolling cards, which would contain a card for an upcoming event and the other cards would contain images from previous meetups (currently containing placeholders) or anything for that matter .

Grid Of Meetups

This Grid contains upcoming and past meetups marked with a chip / flag (currently not present).

Each card in this grid should contain very minimal amount to data (Date, Time, Etc). Each card contains a Location Button which on clicked takes the user to Google Maps.

Event Page

Top Card
The top card would contain basic details about the event.

Speakers List

The Speakers are listed out in this beautiful card like format, the accent color for the speaker (currently red) will be extracted from the image.
If a user on the image of the speaker, the search ui would be shown up and other talks form the speaker would be shown off.

Google Maps

This Container shows the location of the meetup.

The Like / favourite Button
The like button should add this meetup a list of "favourite" , also the like button should add this meetup to the users calendar!

Try the app.

Git.

Leave your Thoughts, Ideas, Suggestions down below

When I hit refresh, the JSON changes:
first fields for various refresh states:
venue, date, desc

The back story:
New events can be written to the db by the admins via the admin panel.
There will be an optional flag to make it live on meetup.

The problem:
This requires publishing the event via meetup apis. However, since this is a call to an external API, we'd normally have to get a paid plan to do that.

Proposed solution: Trading time for money.
Here's how we can totally legitimately get an integration like that going without moving to a paid plan.

• New events are pushed by the admin console to the firestore db.
• Another always on system, such as a raspberry pi, is running an application that is monitoring the firestore as well
• This application (could be a node server or kotlin native), uses the firestore like a client application. Just watching the db for changes like anyone else.
• This application, when it observes that an entry has been made to the db, kicks off the api call to meetup on its end. Bypassing the need for an external api call from firebase directly.
• Whatever the result of the api call is, is written back to the db so the firebase application is aware of the result.

Drawbacks
While the pi does stay up 90% of the time, it's possible that the net's down, or there's a power cut or something else has taken the pi offline.
This is actually automatically dealt with, since the next time the pi comes back online, it will read the db and make the api call at that time.
Since the firestore is the single source of truth, this isn't going to go out of sync though we may need identifiers on it such as 'meetup api call in progress' to know if there is going to be a delay.
Therefore, under normal circumstances if we're not rushed, this delay of maybe hours? Shouldn't matter.

Discussion
This is one proposed solution to staying on a free plan and still achieving everything we wanted.
I maintain a pi that's always on anyway, so I could easily host this.

Thoughts? Ideas? Code to propose?

This relates to #16.

The ask here is to automatically trigger a google form creation as soon as a event is inserted into Firebase DB.
Make sure the form url is not exposed before we actually host the meetup for that month.

The license is yet to be added. What would the license be? MIT or GNU GPLv3?

Following are some of the suggestions received:

For all meetups

• GDG MAD twitter handle - To get in touch with us with queries, feedback or gif wars.
• Topic description - Each talk should have a description to explain better what will be covered in the talk.
• Banner image url - URL to the speaker bio banner we create
• Tags for sessions - Each session can have tags eg: mobile, design, ml, etc.

For Past meetups:

• Feedback url - URL to submit event feedback
• Photos - Photos of the events : either direct urls or a link to view them all
• Session materials - Link to view / download the presentations, codelabs covered in the sessions.

The ReadMe does not contain the sample JSON response. We should add it there.

We'd like pages to be loaded with React suspense.
Best to take one component at a time and see how it works out from there!

This relates to #16.

Changes requested:

1. Add a description text field for each talk session.
2. Add related tags for each talk session. For e.g.
   If the talk is related to some kotlin feature, then the tags can be mobile, android, kotlin, feature.
3. Ability to edit a previous/current event.
4. If possible use of service worker to do some background task. In this case creating an event in Meetup. More details here #6.

@nikhil-thakkar & @AniketSK as we are no longer maintaining the repo should we archive / delete this repo? Some of the dependency keep sending me emails about vulnerabilities.

Hi All,

I have created the Home page. Currently it holds the dummy data.

Please have a look and share your thoughts and suggestions. Refer the screenshot.

It has a Upcoming event and Previous events. You can also download the app from below link.

Link: https://drive.google.com/open?id=1tFGLinZoHExrygzZkgh2pQLOOIsrQn7P

This relates to #16.

Check the feasibility of folder creation using Google Photos API for each month's event. This is where all the events photos would be uploaded for the particular month.

This relates to #9.

Web - #17
Google Form - #18
Google Photos - #19
Meetup API to send custom mail - #20

Hi the information in desc field of the API response can be cut down, it includes text formatting which I feel is not necessary