Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add links and attachments to talk details #11

Open
cko opened this issue Sep 17, 2017 · 3 comments
Open

Add links and attachments to talk details #11

cko opened this issue Sep 17, 2017 · 3 comments

Comments

@cko
Copy link
Owner

cko commented Sep 17, 2017

the frab export (https://schedule.nixcon2017.org/en/nixcon2017/public/schedule.json) contains fields for links and attachments (e.g. slides of the talk). Both should be added to the talk details.
@maxhbr maxhbr assigned maxhbr and unassigned maxhbr Sep 20, 2017
@maxhbr
Copy link
Contributor

maxhbr commented Sep 20, 2017

These fields are currently not filled and the underlying datastructure is unclear. Will be implemented as soon as example data as present.

@maxhbr
Copy link
Contributor

maxhbr commented Oct 1, 2017

Links are filled for at least one talk:
2017-10-01_21 20 45
raw:

"links":[{"url":"https://bazel.build","title":"Bazel"},{"url":"https://gittup.org/tup/","title":"Tup"},{"url":"https://github.com/edolstra/nix-make","title":"Nix-Make"}],"attachments":[]

maxhbr added a commit to maxhbr/nixcon2017 that referenced this issue Oct 1, 2017
@maxhbr
fix cko#11: add links and attachments to talk descriptions
bf7464b
@maxhbr maxhbr self-assigned this Oct 1, 2017
@cko cko unassigned maxhbr Oct 11, 2017
@cko
Copy link
Owner Author

cko commented Oct 11, 2017 •
edited
Loading

As frab is a widely used conference management system, you can just have a look at another conference eg. FrOSCon or 33C3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cko @maxhbr