-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Project Architecture #5
base: architecture
Are you sure you want to change the base?
Conversation
Co-authored-by: Shubham Sharma <shubhamsharma1172@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added few comments
|
||
## Users | ||
|
||
We should create individual user accounts for auditing purposes to later check who made what changes just in case of any anomalies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think admin accounts are adequate as of now ? We just need to create a login page or just link to the admin login page. New users we can add via django admin.
|
||
We should create individual user accounts for auditing purposes to later check who made what changes just in case of any anomalies. | ||
|
||
## Notifications Scheduler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this send post to all platforms ? This seems to be a new feature request. Ideally this will require a calendar and should have a different page.
The Application will be integrated as per the APIs defined in this Service layer and individual channel implementations will have the details | ||
about establishing connection and event related operations. | ||
|
||
This would make it easier to Plug N Play newer channels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 . Please update what all file needs to be added for this.
1. For updating the final details, on the Meetup Manager event page, the user will provide the date value of the Label to pick the talks for. | ||
1. This parser will then fetch the issues from GitHub with the `scheduled` label as well as the given `date` label - eligible proposals[1] | ||
1. Since all the GitHub issues will be following the template format, it'll be easier to parse the title, abstract and speaker details. | ||
1. It'll then store this information in the meetup manager `talk` table with a FK association to `id` in event table |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the database diagram in models.md
@GoelJatin Can you have a look at the review comments ? |
Co-authored-by: Shubham Sharma shubhamsharma1172@gmail.com
Added the details to the GitHub Parser and Notification channels idea