This document outlines an open hack night hosted by Lafayette College Libraries. It describes the objectives to resolve bugs through development and propose improvements through user experience design. Teams will be formed using Scrum methodology and roles assigned as team manager, product manager, designers, and developers. Participants will use Git and GitHub for version control and collaboration. The night will involve hacking the site structure as developers and hacking the site design as designers. Achievements will be rewarded with points for bug resolutions, documentation, and design deliverables.

1. Open Hack Night
Lafayette College Libraries

2. Overview
● Objectives
● Teams and Roles
o GitHub
● Tools
o Git
o Working with the Site
● Hacking
● The Results

3. Objectives
● Web Development (dev)
o Resolving Bugs
● User eXperience Analysis and UI Design (design)
o Proposing Improvements and Features

4. Objectives
● Resolving Bugs (dev)
o Select an identified bug
o Resolve the bug within your working environment
o “Push” your solutions to GitHub
o Issue a “Pull Request”
o Review your submission
o Prosper
● Identifying Improvements and New Features (design)

5. Objectives
● Resolving Bugs (dev)
● Identifying Improvements and New Features (design)
o Select a site feature or component
o Identify problematic cases for the feature
o Document the desired improvement or feature
o “Push” your document on GitHub
o Issue a “Pull Request”
o Prosper

6. Teams and Roles
● Looking Towards Scrum
o Scrum is a lean project management methodology
o Teams are self-organizing
o Roles are loosely structured
 Team Manager (Scrum Master)
 Product Manager (Product Owner)
 Designers
 Developers

7. Teams and Roles
● Suggested Roles
o Team Manager
 Presents solutions and design deliverables
o Designer
 Drafts analysis and design documents
o Product Manager
 Controls the quality of bug solutions
o Developer
 Implements bug solutions

8. Tools and Services
● Using GitHub
o Please see the presentation on GitHub usage
o https://docs.google.com/presentation/d/1CQbxwwPMscxUKsx_bOOYf
kbV3a9P2lDJcH7GdRR2Zxw/edit?usp=sharing

9. Tools
● Git (for Developers)
o git Operations
 git add
● Add changes to be pushed
 git commit
● Prepare the changed files for the push with a message
 git push
● Push the set of changes (a commit) to the remote base

10. Tools
● Git (for Designers)
o GitHub provides an interface for drafting documents
 GitHub Wiki
● Oriented towards technical documentation
● Not optimized for presentation
 GitHub Pages
● Documents drafted in the browser are pushed
● GitHub projects are then publicly accessible
o Templates are offered by GitHub for these pages
o One can further edit the CSS files for aesthetics

11. Hacking
● Hacking Site Structure (Developers)
o Issues are taken
o Changes are Committed and Pushed
● Hacking Site Design (Designers)
o Components and Features are Taken
o Documents are drafted and pushed
o The Wiki or Site is published and updated

12. Rewarding Points
● Bug Resolution
o 1 point for a “push”
o 4 points for issuing a “pull request”
o 6 - 12 points for the resolution of an issue
o 16 points for implementing new features
● Design

13. Assessing the Results
● Bug Resolution
● Design
o 1 - 6 points for wiki documentation
 More are possible
o 4 - 12 points for GitHub Pages
 16 - 24 for web design
o 8 - 16 points for design deliverables
o < 16 points for integration with bug resolution

14. Pedagogy and Philosophy
● Open Hack Night should remain open
o Lafayette College Libraries serve you in providing a
free (as in libre) and open and learning space
 Experiment with new technologies
 Do not limit yourself to solving bugs
 Don’t reinvent Bootstrap

15. Hacking
Commence!
Lost? Undecided? Just Join Us?
Join a Team and Take a Role!
Code Design
GitHub Tutorial GitHub Tutorial
Hacking Tutorial Design Tutorial