-
Notifications
You must be signed in to change notification settings - Fork 38
Meeting Minutes
Mohammad Hassaan Mirza edited this page Apr 21, 2020
·
12 revisions
Date: 21/4/2020
Location: Zoom
Time Started: 4:10 pm
Time Ended: 4:45 pm
- Recapping Stretch 3
- Looking at what to do for Stretch 4
Status Update
- Stretch 3, completed. Auth mostly done for backend, looking at upvotes right now. Rajan is on that. At the moment, can only edit and delete stuff if you're auth.
- Auth token stuff has been resolved, Rajan has checked it and it works fine.
Ming and Brian to decide what day to lock repo. Friday being considered. 24/4/2020. Change front-end to send along auth token. Just handle the errors of that. - Demo for A2 to consist of Eric for front-end and Ming for back-end talking about each of their sides and future work. Demo slides to be done by Sunday of this week, 26/4/2020.
- Wrap up A2
Date: 15/4/2020
Location: Zoom
Time Started: 1:05 pm
Time Ended: 1:40 pm
- Recapping Stretch 2
- Looking at what to do for Stretch 3
Status Update
- William done middleware. When frontend does an auth call, it'll go through that.
- Waiting on frontend to change up their APIs to send auth tokens, so that everything doesn't break when merged.
- Primary focus this stretch: getting all the authentication stuff done. Once that's done, we can call it a day on features.
- Got structure of endpoint set up for user profiles. Hardcode in stuff and then remove it. Send the login along with the endpoint, so if a comment is made by a specific person, just add it in.
- Need to update posts endpoint to use the subthreads. No hosts associated with any subthreads. Ahmad attempting to update the Wiki. Update posts to include which subthreads. If that gets changed, front-end will need to do that.
- Jacob suggests adding the ability to send an Auth token, but don’t reject if it doesn’t have one, so that frontend can work on that without worrying about stuff crashing if other stuff hasn’t been implemented yet.
- Fine for Nidhi to focus on subthreaders for the remainder of this stretch.
- Next meeting will be to assess progress with Stretch 3
Date: 8/4/2020
Location: Zoom
Time Started: 1:05 pm
Time Ended: 1:35 pm
- Recapping Stretch 1
- Looking at what to do for Stretch 2
Status Update
- Backend has completed most issues assigned thus far, just have comment endpoints remaining. Elliot will be working on that, Liam extends his apologies as he will be busy elsewhere till Friday
- For Frontend, Eric has working on the comments Preloader, George working on Edit Post, Kungeng is working on subcomments UI, David working on edit preloader
- Nidhi will investigate with William what there is to do for authentication
- Main goals for this stretch will be: Completing all issues from Stretch 1, integrating authentication, and subthreaders
- Next meeting will be to assess progress with Stretch 2
Date: 6/4/2020
Location: Zoom
Time Started: 4:15 pm
Time Ended: 5:15 pm
- Checking progress with Stretch 1
Status Update
- Backend is tracking well, working on APIs for updating and deleting comments
- Frontend progress well, PRs merged for edit button and edit API call
- All issues that aren't completed with be moved to next stretch
- Jacob reports issues with CI/CD Heroku, might need to make a new account for merges. He will investigate
- Next meeting will be post-Stretch 1 deadline, so we will assess progress with that and see what needs to be done for Stretch 2
Date: 1/4/2020
Location: Zoom
Time Started: 3:15 pm
Time Ended: 4:15 pm
Members Absent: Nidhinesh Nand, Grace Cocks, Elliot Warner, Rajan Gupta
- Finalising new team structure
- Looking at how to progress forward with the project
Status Update
- Nidhinesh Nand, Eric Leung, and Lin Shi will be joining front-end, Rajan will be joining back-end
- Project will progress forward in 4 6 day sprints, starting 2nd of April and finishing 25th April, so as to leave a week for writing the A2 essay
- Issue structure will follow on from what Group 6 had, making large issues for features (back-end + front-end) and making - children issues for back-end work on that and front-end work on that respectively, blocking the issue until the children issues are complete
- Will categorise issues under Milestones on GitHub, with each stretch being its own milestone
- Will use the Projects tab on Github perhaps to categorise the issues as per Documentation Tasks and Code related tasks
- From future work laid out by previous developers, front-end will focus on implementing upvotes and hierarchal comments, the backend will work on implementing APIs for comments and sub comments
- Both teams will look at the above-detailed issues for Stretch 1
- Back-end will look at implementing what already exists for add update delete new, contributing where necessary, front-end will look at how to implement that
Date: 30/3/2020
Location: Zoom
Time Started: 4:10 pm
Time Ended: 5:15 pm
Members Absent: Elliot Warner, Rajan Gupta
- Elaborating on how to progress forward with work on the new repo
- Re-organizing team structure
Status Update:
- Discussing installing mongo to run the database
- Inviting people o the organisation in order to be contributing
- Issues on the Github page
- See if everyone’s in the organization or not
- Hassaan made overall project admin, Ming made back-end lead, Brian stays front-end lead
- From testing team: Summer joins front-end team, backend team welcomes Ahmad, Lin Shi, and Elliot. Rajan unconfirmed
- Splitting issues that are both backend and frontend so that people can have them split into backend and frontend
- Potential ideas for progressing forward on Threader:
- Need authentication
- Can post anonymously
- Upvoting if you’re logged in
- Posting images
- If you click reply, and sub reply, it chains to the end
- Making an s3 client in your backend, where you can store all of your image data
- Amazon user management
- Everyone needs to fork the repo properly
- Meet with people in Group 4 to ensure they are setting up the database correctly
- Find out from people in Group 6 what issues still need working on and which are mostly complete
- Start working on the issues
- How to fix organisation issues from last time
- Cleaning up the issues to make sure all label setting up is done correctly
Status Update:
- Have a couple of people from each team talking, the rest are all muted
- Going over the new repo
- Hassaan and William will be the Zoom meeting co-ordinators
- Meetings will be every 4 day
- Start this off on Monday
- Set up and look around the repo
- Have a meeting on Monday and discuss the features we wanna add, and where we wanna take the repo (We haven’t been added as members of the organisation yet)
- We have it well laid out as to what we wanna do, so we should walk in knowing what we’re doing
- Work for the first two weeks, which will likely creep into the third week. Then everyone will have the time of the whole report
- The new project doesn’t have a testing suite, so the testing team should split into front-end and backend.
- Wanna add login by using existing firebase stuff (Could use Google’s OAuth)
- Fork the repo
- Compile the code and run the application
- List things they find missing
- Ensure everyone reads documentation to follow
- Familiarise yourself with the OSS workflow
Date: Tuesday 17 March
Location: 303-155
Time Started: 12:06pm
Time Ended: 12:23pm
Members Absent: Thomas and Andrei
Status update:
- Grun Wua is almost ready to push delete method
- Kazuki has update post ready
- PRs for those coming soon - issues to be created
- Post detail page is close to finishing (may or may not be finished for demo)
- Joseph needs to do the styling model
- CI/CD deployed. There is a page on the wiki called DevOps
- Need to create an issue for connecting backend and deployment/Issue may have been approved
- NPM proxy issue needs one more approval
- We need to come up with a list of tasks needing to be done for demo and discuss what we will do in the demo
- No code on master for backend yet - hopefully by end of day today
- Cant test calls are being made since backend code isnt up
- Create issue to update endpoints - keep /api
- Documentation is basically done. Everyone to review and edit on Thursday
- Only 2 or 3 people max for demo - should discuss this tomorrow (Timo and Josh K)
To Do:
- Backend get everything done by this arvo so frontend can hook it up
- Post detail page needs to be done. If help required then ask.
Date: Wednesday 11 March
Location: 405-662A
Time Started: 12:11pm
Time Ended: 1:06pm
Members Absent: Joseph, Rodger, Angela, Tyger, Andrew, James
- We have a basic set-up but need to decide features
- James working on UI but he is absent
- Teams
- API
- Integration (link with API)
- Frontend
- MongoDB recommended because it is widely supported as compared to SQL
- Add, get and delete posts functionality
Workflow:
- From user POV:
- Login (feature for later, anon for the time being)
- Front-page which has existing posts (API for fetching existing posts) ---- /posts
- Specific posts - detailed view (API); post text and comments displayed ---- /posts/(id)
- ability to create a comment (create body) ---- /post/(id)/comments
- Create a post (API) - title, body, id assignment as it is not in DB
Task Allocation:
Everyone needs to be writing unit tests for their code. Testing done using 'Jest'
- Backend (4 to 5 people): Andrew, Grun Wua, Kazuki, Thomas, Tyger, Rodger
- Marshalling API calls to DB
- Frontend
- Page-by-page approach
- Front Page (2 to 3 people): Clayton & Josh K & Andrei & Angela
- Create Post Page (2 to 3 people): Ernest, Gavin & Allen
- Post Detail Page (2 to 3 people): Frank, William, Joseph
- Overarching concerns ie look and feel (2 to 3 people): James, Timo
- Page-by-page approach
- DevOps
- CI/CD (2 people): Tia & Samantha
- (Code standards)
- Deployment
- Documentation (1 to 2 people): Parie & Josh F
- Issue template
- Creating processes
- Manage the Wiki
- Code standards
- ReadMe
Other Details/Tasks:
- Detailed API spec (due Friday 13th March) - Backend Team
- Should go onto Wiki
- Backend API implementation
- Frontend API consumption
- UI implemented using mock data (due Saturday 14th March) - By Frontend team
- Issue per page
- AirBnB style guide to be used
- License:
- MIT
- Code of Conduct:
- Wiki Team to create
Date: Monday 9 March
Loaction: 405-662A
Time Started: 4pm
Time Ended: 5:04pm
Members Absent: Allen, Kazuki
- Make sure you are on the GitHub repo (Ask Timo for invite if you haven't already)
Project
- Has to be something that the next group who picks up the project can play with
- Web-App
- ReactJS + node.js
- Potential ideas:
- Straw poll but better -Timo
- Online code editor - Andrew
- Text decryption/encryption
- ~9 simple algorithms
- Easy for 20 people to work on
- App that allocates part 4 projects - Ernest
- Slack clone
- Easy to split up work
- Different components
- COMPSYS people have experience with backend side
- Easy to split up work
- Reddit clone
Issues to create
- Boilerplate (structure) of the project
- For both frontend and backend
- Features
- Upvoting
- Downvoting
- Tree structure (similar to reddit)
- Authentication
- Anonymity
- Profile
- Sharing content
- Uploading attachments
- downloading attachments
- Reddit permalinks
- Share to other platforms
- Database
- Set up SQL database
- Use an orm (lets you access database without worry about the type of database)
- Format in markdown
- Post pictures
- Subreddits
- Including private
- Monetization
- Payment portal
- Buy new fonts etc
- Can also use karma to buy
- Reddit gold-esque
Roles we need
- Backend
- Frontend
- Documentation