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.

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

ResBaz 2017 #67

Open
DamienIrving opened this issue May 1, 2016 · 11 comments

Comments

Projects
None yet
6 participants
@DamienIrving
Copy link
Member

commented May 1, 2016

@BillMills We've started to get some interest in ResBaz 2017 already, so I'm thinking it might be time to create the relevant website repo (we can probably just call it github.com/resbaz/resbaz-2017 because it turned out not everyone started on 2016-02-01 last time anyway). Would the best thing to do be to simply take the code from this website and remove the _posts, or would you do things slightly differently next time around?

@DamienIrving

This comment has been minimized.

Copy link
Member Author

commented May 1, 2016

I'm also thinking that rather than having a separate "cookbook" wiki, we should just use the wiki attached to the new website repo.

@BillMills

This comment has been minimized.

Copy link
Collaborator

commented May 2, 2016

In principle yes, just removing everything from _posts (except I guess the template) would give you a fresh start for 2017 (plus maybe updating whatever is in index and config.yml).

How did this end up working out for everyone? As a maintainer I had a bit of a selection bias for hearing complaints and problems, but overall did the model work well? I would spend some time asking the sites what they'd like to see in future before standing up the 2017 assets.

@DamienIrving

This comment has been minimized.

Copy link
Member Author

commented May 2, 2016

I think we ironed out most of the issues along the way and ended up with a pretty good site, but you're right, I should ask for feedback first. I'll do that in my next newsletter.

@philippbayer

This comment has been minimized.

Copy link
Collaborator

commented May 2, 2016

It worked quite well for us in Perth!

Two points:

  • the geojson map rendering was very flaky - sometimes you had a gray map with the pointer, sometimes it didn't load at all, but it seems to have improved since then (sometimes emptying the cache worked, sometimes it didn't, sometimes it worked in Firefox vs. Internet Explorer, sometimes both didn't work)
  • I'd like to see a better time tabling system, it would be nice if I could add a bit of description to the schedule with a better way to display times
@matty-plumski

This comment has been minimized.

Copy link
Collaborator

commented May 2, 2016

I thought the template was elegant, and overall worked really well. Mainly due to ignorance and the fact that we had three streams, two of which required separate scheduleshttps://feb2016.resbaz.com/wellington#scheduleSection, I ending up designing most of the Wellington site in straight HTML – and this worked well for the most part (although my rustiness on git resulted in heaps of frivolous pull and merge requests – apologies for any flooded inboxes).

I played around with the formatting of the schedule a bit, mainly borrowing from the Dunedin sitehttps://feb2016.resbaz.com/dunedin#scheduleSection using bold tags and indentation, but agree if this could be incorporated into the core template that could be useful.

Cheers
Matt

MATT PLUMMER
CUSTOMER RELATIONSHIP COORDINATOR
ITS LEARNING AND RESEARCH TECHNOLOGY TEAM
VICTORIA UNIVERSITY OF WELLINGTON
+64 4 463 6493 | 021 2506957

From: Philipp Bayer [mailto:notifications@github.com]
Sent: Monday, 2 May 2016 3:22 PM
To: resbaz/resbaz-2016-02-01
Subject: Re: [resbaz/resbaz-2016-02-01] ResBaz 2017 (#67)

It worked quite well for us in Perth!

Two points:

· the geojson map rendering was very flaky - sometimes you had a gray map with the pointer, sometimes it didn't load at all, but it seems to have improved since then (sometimes emptying the cache worked, sometimes it didn't, sometimes it worked in Firefox vs. Internet Explorer, sometimes both didn't work)

· I'd like to see a better time tabling system, it would be nice if I could add a bit of description to the schedulehttps://feb2016.resbaz.com/perth#scheduleSection with a better way to display times


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/67#issuecomment-216098761

@TomKellyGenetics

This comment has been minimized.

Copy link

commented May 5, 2016

+1 for clearer guidelines on a schedule.

We struggled with that a bit in Dunedin but I'll admit we were a relatively small group of people running around like crazy. All worked out in the end but we didn't have a schedule much in advance as some sessions were filled last minute.

Otherwise no major problems but many of our attendees were so new too the tools we were presenting they had trouble picking from our streams. One recommendation I'd make for organisers is to make an effort to pick sessions ahead of time and make sure participants have some idea of each one will be. We had a general introduction to the day along with our keynote talks but more detail in writing on the Github site might help with this.

@weaverbel

This comment has been minimized.

Copy link
Contributor

commented May 17, 2016

I would actually have liked some info on what to put where - there seemed a whole lot of code that could not be touched and only a few spots where site-specific data could go. A short 'how to' ? Our template 'broke' because of some minor issue - which was a bit annoying. I thought it all looked really nice but the fear of updating (and breaking it again) was upon me ... We are already starting to plan for 2017 so I am happy to have a site up again soon where we could add in as we go instead of doing last minute scramble to get info on.

@DamienIrving

This comment has been minimized.

Copy link
Member Author

commented May 22, 2016

I'd also add that we should brand the 2017 website more generally as "ResBaz 2017". Most of the events will happen during or around "ResBaz week" in February, but for the sake of events that happen later in the year we shouldn't brand as exclusively Feb.

@DamienIrving

This comment has been minimized.

Copy link
Member Author

commented May 22, 2016

Thanks for the comments everyone. Over the next month (i.e. in time for the June newsletter on the blog) I'll work on getting a draft new site up taking into account your feedback regarding better guidelines for posting the schedule and also more 'how to' notes in general.

@weaverbel

This comment has been minimized.

Copy link
Contributor

commented May 22, 2016

Thanks also to @DamienIrving for being the organiser for all this - great work!

@TomKellyGenetics

This comment has been minimized.

Copy link

commented May 25, 2016

@weaverbel Sounds like same kind of issues as us, had a minor technical issues days before the event we didn't have time to fix in the rush. The extra info text for session headings stopped coming up when we clicked on them, led to much confusion as to much stream attendees should be in.

Not sure how we'd address this apart from learning from our experience and planning at the new sites this time around. Hopefully Dunedin will be a smoother with more people involved in organising, we were discussing running it with another academic dept (Comp Sci & Biochem) to spread the workload. Not sure if that model would apply to other sites, hopefully less hiccups all round the second time.

Otherwise fantastic job so far everyone, keep it up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.