Open Event Project, Samples, Documentation and Artwork http://open-event-dev.herokuapp.com
License: GNU General Public License v3.0
Python 100.00%
open-event's Introduction
Open Event
The Open Event Project offers event managers a platform to help users organize events including concerts, conferences, summits and regular meetups . The components support organizers through all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily. The Open Event Project was originally started to support the organization of the FOSSASIA OpenTechSummit and is maintained by the FOSSASIA community.The Open Event boasts a diverse ecosystem and is composed of several components:
Components of Open Event Ecosystem
The Open Event Format Definition
The Open Event format enables the exchange of data between all components as well as with other services through a standardized Format. This open-event repository provides a sample implementation of the format. It includes JSON files for all relevant event information and binary data for images and audio files. The repository holds the JSON Schema sample implementation in the /sample folder, that is used across all projects for testing. We keep:
Zip files that include all JSON files with binary media data, And
The uncompressed files that can act as APIs substitutes to test applications.
The Open Event Server
The Open Event Server is the centralised backend powering most of the components of the open event ecosystem. The open event server exposes a well documented JSON:API Spec Compliant REST API that can be used by external services (like the Open Event Organiser App and the Open Event Frontend) to access & manipulate the data. Using the APIs of the open event server, it is possible for the other components of open event like the open event organiser app, and the open event frontend to enable organizers to manage events from concerts to conferences and meetups. The APIs offer features for events with several tracks and venues. Event managers can create invitation forms for speakers and build schedules in a Drag & Drop interface. The system provides API endpoints to fetch the data, and to modify and update it. Organizers can import and export event data in a standard compressed file format that includes the event data in JSON and binary media files like images and audio.
The Open Event Frontend
The Open Event Frontend as the name suggests, is a web app written in Ember.js which consumes the Open Event Server API to give the users a medium to interact with the several functionalities and features which the open event server offers, in an intuitive manner, with a moder UI/UX. It's responsive design allows effecient browsing on mobile web browswers along with large screen devices. While the open event server serves as the backend, all the users including administrators need to interact only with the frontend.
The Open Event Android App
The Open Event Android App is an android app which allows users to discover events happening around the world using the Open Event Platform. It consumes the APIs of the open event server to get a list of available events, and can get detailed information about them. It is possible to buy event tickets.
The app also offers other modern features such as easy check-in using QR codes. This app is meant for the users who intend to browse events and purchase tickets for them as an attendee.
The Open Event iOS App
The Open Event iOS App is the iOS counterpart of the Open Event Android app, currently in development. The app will eventually achieve the same functionalities as the Open Event Android app, and alloww users to discover event, book tickets, and will use the Open Event Server as the backend.
The Open Event Organiser Android App
The Open Event Organiser app is intended for the organizers and entry managers who intend for their event to be available in the Open Event Ecosystem. While the Open Event Android and iOS apps allow the users to browse the events happening around them, the organiser app allows creation and management of those events from an organzer's perspective with intuitive features like push notifications, ticket management, and check in using QR codes.
The Open Event Organiser iOS App
The Open Event Organiser iOS App is the iOS counterpart of the Open Event Organiser Android app, currently in development. The app will eventually achieve the same functionalities as the Open Event Organiser Android app, and allow the users to browse the events happening around them, the organiser app allows creation and management of those events from an organzer's perspective with intuitive features like push notifications, ticket management, and check in using QR codes.
Open Event Web App Generator
The Open Event Web App generator is an event website generator. The web generator application can generate event websites by getting data from event JSON files and binary media files, that are stored in a compressed zip file with an Open Event Format Specification. You can also access the application through a Rest API. Websites that are generated by the web app generator can be uploaded to any web location, e.g. on Github pages or any server.
The Open Event Android App Generator
The open-event-droidgen is a web application that is hosted on a server and generates an event Android app from a zip file in an Open Event Format Specification containing JSON and binary files.You can also access the application through a Rest API. Apps that are generated by the android app generator can be uploaded to the play store and be readily made available, which is of great convenience to the orgazers, as an organizer can generate a ready to publish app for his/her event.
License
This repository is licensed under the GNU General Public License v3.
To obtain the software under a different license, Please contact FOSSASIA.
This issue serves as a public record for the TODOs, plan of action to get open event android app compatible with FOSSASIA 2016 conference data formats. Please modify this post to notify changes.
This is something we discussed and which everybody agrees upon.
Set up a server to parse Google spreadsheets and convert to open event compatible data structure
Set up the Android app to improve UX and bug fixes. We have decided to use open-event app, it has 2 flavours: froid and googleplay if there are dependencies which are considered against open source principles we should use them only in the Google Play version and mock them out or use a compatible open source tool for froid
Set up crashlytics account for google play apk and beta testing as well for nightly releases.
Action Plan
Set up server for spreadsheets, expose same API Points as that of the open event format. (@creativepsyco & @rafalkowalski )
@mariobehling should give access to Gsheet sample data & data columns
GSOC 2016 is about to start. And a lot of coding activity will take place on the open-event repos in the coming months. It is good to have a roadmap of broad features we intend to add to these projects.
There are a number of speaker duplicates and each speaker entry is related to a talk. Fix: Merge separate speaker entries and ensure a one to multi relationship (one speaker -> several events)
Please define the following for your project
a) Feature List (add it to Feature.md)
b) Project Plan with possible milestones (Which features will be implemented at what time)
c) Technologies used
Since we are directly copying the json files from the sample zip into the assets folder of the android app , the samples need to have .json so as to be correctly recognised as json files. @mariobehling@aviaryan Could you please provide your views on this?
It turned out that the Open Event JSON was implemented differently in some parts. Please list in a table what differences exist, the reason for the difference and what can still be implemented in the Open Event JSON
So I am gonna jot down which fields in the API we need to change to become comaptible with re:data
HasGeek is a major organisation for tech events in India.
funnel is open source as well (written in python), and has a json API endpoint https://github.com/hasgeek/funnel
Funnel does not actually do everything that we aim to, but it does one important thing for tech events - a forum to submit talk proposals, and a uniform way to upvote/downvote them.
To collect data for events, we are using Google forms. This is a convenient solution, but we are currently not able to create multiple relationships, e.g. one speaker is doing to several talks or one talk has several speakers. Also in Google forms there is no way to have fields like "add more speakers".
Is there a way to handle this, e.g. a plugin for Google docs? What other options exist Limesurvey? Are there suitable event systems? What options are there to create our own lightweight service, e.g. a JS site? Pentabarf and Frab are solutions used by some older events in Europe, but they are not "straight forward" and design is outdated.
Since I last fixed it, some issues seem to have arised in the FOSSASIA samples. The error I got
when importing it into open-event-dev was the following. I will fix it and the subsequent errors if any and make FOSSASIA sample importable.
I searched on the internet, but couldn't find a satisfactory answer, Please suggest @championswimmer if we can even do this because most of the answers online suggest otherwise.
There is a line "background_url": "/images/background.jpg". This line should be moved above "logo" and renamed "background_image".
Call for papers only seems to have - "closing_datetime": null, - , but not an opening date, which is also necessary.
Question: Why does the creator need an ID? "creator": { "email": "[email protected]", "id": 1
Description field only seems to have text: Can we/How can we have rich-text/html in this field? (same applies to Call for Speakers and Code of Conduct.
Version is "0". How is that possible? "version": {
"event_ver": 0,
"microlocations_ver": 0,
"sessions_ver": 0,
"speakers_ver": 0,
"sponsors_ver": 0,
"tracks_ver": 0
Why do social links need to have IDs? What if social links of different events have the same ID number?
"id": 361,
"link": "https://twitter.com/eHealth_africa",
"name": "Twitter"
Please sort the order of the event JSON in the same logical order as the orga server wizard page, e.g. it is illogical to have the follow sorting:
"latitude": 52.51074,
"location_name": "Kemperplatz 1, 10785 Berlin, Germany",
"logo": "/images/logo.jpg",
"longitude": 13.37233,
Why do we need it? All data is already defined in Event JSON.
Compatibility JSON/API
In the app generators we want to use API endpoints and JSON files in the same manner. Currently I see that there is a difference between API and JSON as there are more JSON files than APIs, e.g. Session_Types. How does that work out?
Right now, only the lat and long of the venue is mentioned, it would be good if we had the address to so that it can be displayed directly in maps. Issue fossasia/open-event-attendee-android#564
We can have the app use the JSON file directly from Github, and we need to define at least a DEV JSON file and a PRODUCTION JSON file, where we test stuff out on the DEV JSON and then push out vetted changes to the PRODUCTION JSON file, so we don't break everyone's experience using the app.
I propose a json/ directory with a dev.json and prod.json in the root directory of each event repository. Does this sound reasonable, @creativepsyco@mananwason ?
Please define the following for your project
a) Feature List (add it to Feature.md)
b) Project Plan with possible milestones (Which features will be implemented at what time)
Proposed Milestones
These are code pieces where you must consider the time zone:
the event description json must declare in which time zone the event happens
the event description json must declare the time zone for the given event times (may be given in GMT)
the mobile device has a time zone (conference visitors tend to come from time zones different from the event time zone)
I believe that event dates shall be displayed in the event app according to the local time of the event. But that time may not be the same as the time zone of the device. The app shall be able to handle that.
I believe that a clear plan of features has not been put up anywhere. So I suggest we make a plan on the features we want in the final app and add them in the respective repo as tasks. This will allow us to take up those tasks and complete them in an orderly manner, thus increasing efficiency.
Please give your inputs on this. @mariobehling@leto@rafalkowalski@championswimmer
The idea is to have a basic app and fill the app with event data. Apart from that the app should have its own logo, color scheme and twitter wall generated through loklak. How can we achieve this goal?
There are a number of speaker duplicates and each speaker entry is related to a talk. Fix: Merge separate speaker entries and ensure a one to multi relationship (one speaker -> several events)
Mario suggested (#4) to integrate a Twitterwall, which presents latest tweets to the event. We discussed various places where the wall may appear (i.e. at a welcome screen, below a single event view or as spcial 'event wall' view). I would like to point out, how the tweet timeline data can be retrieved.
There will be library, provided by the loklak project which can be integrated as jar file
The library provides very simple methods to retrieve the timeline, like
Wall wall = new Wall(String query, int maxsize);
.. initializes the library with a query, which represents the search term that can be used to retrieve all tweets, like '#fossasia'. maxsize is the maximum number of messages that are cached in the timeline (= maximum message you want to display on the wall) that you can retrieve with the following method:
Timeline timeline = wall.getTimeline()
.. retrieves the actual view on the tweets, where timeline instanceof Collection<Message> is a sequence of messages. Inside each message you will find all tweet credentials, inclusive the user details. If this method is used, you must track yourself which messages have been arrived lately.
Message message = wall.getById(String message_id)
you can use the wall object as database and retrieve messages by their id. This is especially useful if you track arrival of new messages by id, but don't want to store the complete message referenced by them
The take/0 method would block until the next message arrives (== was tweeted) and then returns the message. Using the take/1 method, the blocking is terminated after at most millis millisecods. If more than one message arrived, then you must call take several times
int count = wall.available();
returns the number of messages that can be retrieved with take/0 without blocking
About images: you probably want to display user images or embedded pictures in the wall. The loklak library will provide direct download links for them inside the messages, but handling of downloads and caching of downloaded images must be done by yourself.
These methods should be sufficient to provide the wall data. If you need other access methods, please describe them. The actual library is not available right now, but this is the plan for it.
Now that the feature to export speaker images with their names as filenames is done, we should update the samples to reflect the same.
Eg > Change speakers/photo1.jpg to speakers/MattBlanc_1.jpg
How should we test the app? Currently, I see, that I receive a message "Done", but then it does not work or is wrong, e.g. instead of May 14, I see May 13, May 14, May 15 in the app. These are small things and should be first tested by the developer. How do you suggest to improve the testing?
Please define the following for your project
a) Feature List (add it to Feature.md)
b) Project Plan with possible milestones (Which features will be implemented at what time)
c) Technologies used
The sample zips in the repo for FOSSASIA16.zip is not what is generated from orga server's event export system.
The panel on the right displays the zip exported from event management from orga server.
The panel on the left displays the sample zip that we have in the repo.
This change in the directory structure breaks the generator, so we need to fix this.
Opentechsummit is coming on 5th may. We need to improve the app and the parser to make it ready for the event. @mariobehling can you provide some pointers for the api or the spreadsheet where we can get the data from?
Based on the work we have done so far, we have come up with a way to separate projects we would like you to work on now. I have tried to sum up different discussions. Please have a look at the following and give feedback and input. @leto Please confirm the following separation as well.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent