Add a FOSDEM JSON schedule loader for the /p/matrix schema
#240
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reivilibre
force-pushed
the
rei/fd25_fosdempmatrix_format
branch
from
75e5986 to
08f7814
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of bothering with the Penta-compatible XML (which is authoritative, but incomplete as it doesn't contain personal information due to it being public) or the Pretalx API (not considered authoritative, doesn't have a Matrix User ID field either), this PR adds support for running the entire conference from one data source: the FOSDEM-specific
/p/matrixendpoint, which is in a custom format (schema included in this PR).This should keep the data flow within the conference bot much easier to track.