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

26th
Jul 2016
Mario Behling
@mariobehling
Jul 26 2016 06:05
@aayusharora @the-dagger Thanks for reporting this. Please open issues and for FOSSASIA add the photos from here: https://github.com/fossasia/2016.fossasia.org/tree/gh-pages/img
@aayusharora As you remember the origin of these files was the open event scraper. As you were involved here, you probably can help to fix some of the issues quickly.
Aditya Vyas
@aditya1702
Jul 26 2016 07:01
@/all We have to write and submit the blog on wordpress for reviewing?
Mario Behling
@mariobehling
Jul 26 2016 07:09
@aditya1702 Writing to all will get your message to 42 people. Not sure about your question, just write an article as you have done in the past. As mentioned earlier - we have moved the blog to http://blog.fossasia.org/login
Please login their with your old user name and get a password reminder, if the password does not work
Aayush Arora (angularboy)
@aayusharora
Jul 26 2016 07:32
@mariobehling Yes I will do it :)
Manan Wason
@mananwason
Jul 26 2016 13:34
@niranjan94 @shivamMg @aviaryan Can you also add a version number in events that increments when any of the components(speakers, sessions, tracks etc.) changes ?
It would make the process even more efficient
Saptak Sengupta
@SaptakS
Jul 26 2016 17:39
@mariobehling in this issue fossasia/open-event-orga-server#1845 we need to find the images according to the event type, event topic. Should I then select the image according to the session_type?
Mario Behling
@mariobehling
Jul 26 2016 17:42
dont know what you mean
according to event topic
Saptak Sengupta
@SaptakS
Jul 26 2016 17:43
In the first point of the issue you said to show image based on the combination of event type, event topic, and subtopic
Mario Behling
@mariobehling
Jul 26 2016 17:45
you need to think this through as there are different possibilities. If the organizer does not choose an event type or topic find a generic image that is very general
if the user only chooses an event type choose something that works for this
Saptak Sengupta
@SaptakS
Jul 26 2016 17:46
Ok.. Let me check this out..
Mario Behling
@mariobehling
Jul 26 2016 17:46
if the user also chooses topic and subtopic - choose specific images that fit here
one of the goals of this to have a diversity of event specific images
Saptak Sengupta
@SaptakS
Jul 26 2016 17:47
ok.
Mario Behling
@mariobehling
Jul 26 2016 17:47
and make the site look more professional
session type is relevant for specific sessions. Which field is relevant for types and topics?
If this is not covered in the JSON and API, please file an issue
Saptak Sengupta
@SaptakS
Jul 26 2016 17:48
I think I have file an issue.. let me check..
Avi Aryan
@aviaryan
Jul 26 2016 20:28
Can you also add a version number in events that increments when any of the components(speakers, sessions, tracks etc.) changes ?
@mananwason I don't think it will give a measurable performance boost. Also the idea behind versions is that ... event_ver corresponds to Event API, speakers_ver to Speakers API and so.. When event_ver changes, it means Event API data changed, that's it.
Mario Behling
@mariobehling
Jul 26 2016 20:47
:+1:
Harshit Dwivedi
@the-dagger
Jul 26 2016 21:40
@aviaryan iirc the version is there to make sure whether the cached data on user's device is in sync with the data on the server.
So for example if you changed something in the samples but forgot to update the version.json, the app's data won't be updated automatically on launch and the user will have to trigger a manual refresh
There is no effect on performance in relation to version.json
Mario Behling
@mariobehling
Jul 26 2016 21:55

So for example if you changed something in the samples

The samples as it says are just samples, so we can all work now. The use case of updating data manually is extremely rare. The server will update version.json automatically. What is your use case? Why does the same information need to be implemented twice in two different locations?

Harshit Dwivedi
@the-dagger
Jul 26 2016 21:59
@mariobehling If server updates the version.json automatically, then its all good :+1: