These are chat archives for fossasia/open-event-server

18th
May 2018
Mayank Vaidya
@mayank8318
May 18 2018 09:17
@rngadam Could you please review the following PR : fossasia/open-event-server#4695
issue : fossasia/open-event-server#4687
This is about normalizing the social links in the database.
Thank you!
Saurav Tiwary
@srv-twry
May 18 2018 14:44
@niranjan94 @SaptakS Can you please help here ? I setup the open event legacy server locally and compared it's feature set with the feature set of v2. I think all of the features have already been implemented in the v2. What are our next steps in this project ?
Please point out if I missed something.
Mayank Vaidya
@mayank8318
May 18 2018 14:45
@srv-twry +1
Bhavesh Anand
@bhaveshAn
May 18 2018 17:48
@mayank8318 @srv-twry @schedutron @poush Please review fossasia/open-event-server#4724
Abhinav Khare
@CosmicCoder96
May 18 2018 17:52

@srv-twry @mayank8318
Here are the things missing on the server side to the best of my knowledge.
1> Social Login for
— google
— facebook
— Twitter
2> Kubernetes logs in admin dashboard
3> Heroku server logs in admin dashboard
4> Notifications are not complete with their actions.
5 > on settings/applications api, integration with
-- facebook
— instagram
— twitter
— google plus

6 > Orders api needs modifications, if you check the legacy code and place a fake order which involves payment you will realise there are more states than a order can have than currently defined in the new server, with no support for a pending order. That needs to be there.
7> user roles are pending
8> Sales route in admin is pending
9> Message route in admin is pending
10 >Event Import api throws exceptions (https://github.com/fossasia/open-event-server/issues/4613https://github.com/fossasia/open-event-server/issues/4613)
11 > Event Export api throws exceptions (fossasia/open-event-server#4609)
12>Integration of i18n for data returned by server (fossasia/open-event-server#4514)

Bhavesh Anand
@bhaveshAn
May 18 2018 17:54
@CosmicCoder96 for the part of on settings/applications api, integration with
-- facebook
— instagram
— twitter
— google plus
I have just started working on it fossasia/open-event-server#4737 Please help to find next steps
Abhinav Khare
@CosmicCoder96
May 18 2018 17:58
@bhaveshAn I haven't worked enough with open event server to suggest specific code related steps. @SaptakS @shubham-padia @niranjan94 @poush can help you out with that :D
Bhavesh Anand
@bhaveshAn
May 18 2018 17:58
Okay !
Saurav Tiwary
@srv-twry
May 18 2018 17:59
@CosmicCoder96 thank you :smile:
Abhinav Khare
@CosmicCoder96
May 18 2018 18:01
@srv-twry Also elasric search .. the searching functionality is completely missing . (to be used on explore route of FE)
Saurabh Chaturvedi
@schedutron
May 18 2018 18:14
What are user roles?
Saurabh Chaturvedi
@schedutron
May 18 2018 18:34
I was thinking that, instead of having Hound review our work after we push our commits, why not have a pre-commit hook locally that can guide us with linting issues? That will remove friction from our workflow. Working with Hound often unnecessarily increases the number of commits (which can be squashed later, but that's extra work). @srv-twry @bhaveshAn and others, what are your thoughts on this?
Bhavesh Anand
@bhaveshAn
May 18 2018 19:04
Nice :+1:
Saurabh Chaturvedi
@schedutron
May 18 2018 19:57
Thanks @CosmicCoder96!
Mario Behling
@mariobehling
May 18 2018 20:14
@Kreijstal @bhaveshAn @maxlorenz @schedutron @srv-twry @mishuvs @mayank8318 @ritikamotwani @pradeepgangwar We had a good meeting today and it cleared up some questions. As a next step we need developers take responsibility of different areas in the server and frontend of open event V2. I have created a sheet with a list of main components we need to focus on. Please add your name into 7 fields - frontend or back-end into here now: https://docs.google.com/spreadsheets/d/1bvbk1NPTshVh9qXIhVslmUTjbPDP-dM7AqEcWcwUGaQ/edit#gid=994540942