Islandoracon 2019

Latest Camp News

Islandoracon 2019 Has a Logo!

manez's picture
Submitted by manez on

One of the features of Islandora events is a themed t-shirt given to all attendees. Every camp has its own logo, and so does each conference. We recently held a logo design contest to award a free registration and an extra t-shirt to the Islandoracon attendee who came up with the best logo to represent our third conference. We've held this contest before, but this year saw a record number of entries, making for a very close result.

We are pleased to announce that the winner of the Islandora 2019 Logo Contest is Hillary Webb, from the Emily Carr University of Art + Design, with this design that takes the coasts as inspiration while nodding to Islandora's doe-eyed lobster mascot: 

"Lobster for the east coast and the Orca for the west coast, united by kelp and water."

Islandoracon will take place on the west cost, in Vancouver, BC, from October 7th - 11th. We hope you'll join us and proudly wear Hillary's design!

Introducing the Islandoracon Use-a-Thon

manez's picture
Submitted by manez on

Islandoracon has always had a 'hackfest' component, but we've yet to do the same thing twice. We're trying a new format this year to give all of our attendees a chance to work together, learn new things, and produce a tangible benefit for the rest of the Islandora community: The Islandora 8 Use-a-Thon.

How it works:

Islandora 8 is more tightly integrated with Drupal than Islandora 7, and very flexible, so many use cases can be solved with a combination of configuration and Drupal contrib modules. The Use-a-Thon will crowdsource use cases for things people might want to do with Islandora (i.e, a collection that can be viewed on a map; a collection with a commercial store component; a workflow for accepting and reviewing public annotations on objects). On Monday, October 7th, after we finish up the half-day workshops, we'll have a mixer at the Vancouver Public Library where attendees can form teams and talk about what use cases they would like to explore, either picking from the crowdsourced use-cases or inventing their own.

On their own, over the week of the conference, teams will take a use case and work to demonstrate how it can be done in Islandora 8 (with configuration and Drupal contrib modules), including documentation (“recipes,” for our shared Islandora Cookbook). Points will also be given for identifying gaps that may need further development work and creating issues to document those gaps.

On Friday, October 11th, we will gather again at the Vancouver Public Library where teams will have the morning to finish up their work and prepare a brief presentation describing what they have done. After lunch we'll watch presentations, pick winners and award prizes, and officially end Islandoracon. The rest of the day will be given over to an informal discussion of the future of Islandora (8, 9, and beyond) for anyone who wants to participate.

 

Rules:

  1. Entries should come from teams of at least two people.
  2. The entries should be presented in person by at least one team member.
  3. Only one entry per team.
  4. No person may be in more than one team.
  5. Screenshots should be rough-and-ready.
  6. Writing code is discouraged; we want ideas, documentation, and GitHub issues describing what needs to be built if your use case can't be done with what's available now.
  7. Participants must ensure that entries do not in any way infringe copyright or other intellectual property rights of any third party.

Points:

Use-a-Thon projects will be judged based on:

  1. The value of the contribution to the Islandora community (i.e, is this something others will use?)
  2. The difficulty of the use case
  3. Community use case versus coming up with your own (bonus for taking on something from the community)
  4. The amount of work completed (draft documentation, completed 'recipes,' GitHub issues submitted)

And, because we want to encourage you to make new connections at Islandoracon, we'll also award points for team composition:

  1. At least two team members who have not worked together before
  2. At least one team member with a developer background and one with a library or other non-dev background.
  3. Bonus point for teams of 3+

(Credit to Open Repositories for their Ideas Challenge and points for team composition)

Pages

Subscribe to Latest Camp News

Our Sponsors:

 

Host

  

Platinum:

Gold:

     

Silver:

Bronze: