The document provides information for teams participating in an open hack night to work on resolving issues for various modules, themes, and libraries used on a Drupal website. It outlines how teams can access remote servers securely over SSH using RSA keys, modify the Drupal codebase through their team accounts, resolve issues by selecting from a list of GitHub repositories, and submit pull requests once an issue is fixed for testing and merging into the source code.

1. Open Hack Night
Hacking the Site

2. Development Environment
● All development should traffic over the SSH
o SSH remotely logs you into a remote server securely
(providing a secure shell)
● A remote server provides HTTP service
o Drupal sites have been installed on this server
o Each team is bound to a single Linux system
account

3. Team Management
● Team accounts can be reached using fully-qualified
domain names
o team1.library.lafayette.edu
● The user for each team is mapped to the
team number
o openhacker1 for team 1
o openhackerN for team N

4. Team Management
● Team Access
o The systems administrator (me) requires RSA2 keys
from each team member
o These are the very same keys used on the compute
cluster within Computer Science

5. Team Management
● Team Access
o Generating RSA2 Keys
 Should you require an RSA2 key, one can be
generated
 https://help.github.com/articles/generating-ssh-keys/#
step-2-generate-a-new-ssh-key

6. Modifying the Site
● File directory structure
o The Drupal site itself consists of Modules, Themes,
and Libraries
 Modules
● /var/www/drupal/sites/all/modules
 Themes
● /var/www/drupal/sites/all/themes
 Libraries
● /var/www/drupal/sites/all/libraries

7. Resolving Bugs
● Issues exist for the following Modules
o islandora_dss_solr_facet_pages
● Issues exist for the site Theme
o bootstrap_dss_digital
● Issues exist for the following Libraries
o openseadragon
o pdf.js

8. Resolving Bugs
● Selecting an Issue
o https://github.com/LafayetteCollegeLibraries/islandora_dss_solr_facet_pages/issues
o https://github.com/LafayetteCollegeLibraries/openseadragon/issues
o https://github.com/LafayetteCollegeLibraries/pdf.js/issues
o https://github.com/LafayetteCollegeLibraries/bootstrap_dss_digital/issues
● Repositories have been forked
o Hence, each team need only work on the local
repository

9. Essential Git Operations
● git add file1 file2...fileN
o The modified files are prepared for the commit
● git commit -m ’Description of changes’
o A message is bound to the modified set of files
● git push origin stable
o The modified files are pushed to the remote
repository’s “stable” branch

10. Resolving Bugs
● Pull Requests
o Once a bug has been resolved, issue a “Pull Request”
o e. g. https://github.com/open-hack-night-team-1/pdf.js/pulls
● Testing and Merging
o Should the resolution be tested successfully, the
code can be merged into the source code base