hack-a-way:hack-a-way-2024
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hack-a-way:hack-a-way-2024 [2024/09/12 08:27] – [Attendees] roganh | hack-a-way:hack-a-way-2024 [2024/11/18 17:00] (current) – [Discussions and Research] aneiman | ||
---|---|---|---|
Line 4: | Line 4: | ||
**Location**: | **Location**: | ||
- | The 2024 Hack-A-Way will is co-sponsored by [[https:// | + | The 2024 Hack-A-Way will is co-sponsored by [[https:// |
+ | |||
+ | Drivers to the event should park in the garage to the right of Hempstead Commons. | ||
+ | |||
+ | * [[https:// | ||
+ | * {{ : | ||
**Travel/ | **Travel/ | ||
Line 10: | Line 15: | ||
Volunteers will be available to drive participants from the airport to the hotel and provide transportation to dinner locations. | Volunteers will be available to drive participants from the airport to the hotel and provide transportation to dinner locations. | ||
+ | |||
+ | [[https:// | ||
**Lodging**\\ | **Lodging**\\ | ||
Line 16: | Line 23: | ||
Phone reservations: | Phone reservations: | ||
You must identify yourself as part of the **//NOBLE room block//** to get the block room rate. | You must identify yourself as part of the **//NOBLE room block//** to get the block room rate. | ||
- | |||
- | **//Please reserve your hotel room by September 11, 2024.//** | ||
**Dining information**\\ | **Dining information**\\ | ||
- | The hack-a-way sponsors will provide a light breakfast and lunch to all participants. NOBLE will provide | + | The hack-a-way sponsors will provide a light breakfast and lunch to all participants. |
+ | |||
+ | NOBLE will coordinate group participation evening meal options, but participants may also choose to dine on their own or with a smaller group. | ||
+ | |||
+ | * **Monday**: 7 p.m. dinner | ||
+ | * **Tuesday**: | ||
+ | * **Wednesday**: | ||
+ | * Optional: After-dinner excursion to [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | **Remote Participation**\\ | ||
+ | [[https:// | ||
====== Attendees ====== | ====== Attendees ====== | ||
Line 31: | Line 49: | ||
* Steven Mayo, PINES | * Steven Mayo, PINES | ||
* Susan Morrison, PINES | * Susan Morrison, PINES | ||
- | * Blake Graham-Henderson, | ||
* Scott Angel, MOBIUS | * Scott Angel, MOBIUS | ||
- | * Jaysal Patel, MOBIUS | ||
* Mike Rylander, Equinox Open Library Initiative | * Mike Rylander, Equinox Open Library Initiative | ||
* Gina Monti, Bibliomation, | * Gina Monti, Bibliomation, | ||
* Jason Stephenson, C/W MARS, Inc. | * Jason Stephenson, C/W MARS, Inc. | ||
* Andrea Buntz Neiman, Equinox Open Library Initiative | * Andrea Buntz Neiman, Equinox Open Library Initiative | ||
- | * Galen Charlton, Equinox Open Library Initiative | + | * Galen Charlton, Equinox Open Library Initiative |
* Stephanie Leary, Equinox Open Library Initiative | * Stephanie Leary, Equinox Open Library Initiative | ||
* Rogan Hamby, Equinox Open Library Initiative | * Rogan Hamby, Equinox Open Library Initiative | ||
Line 44: | Line 60: | ||
* Jason Boyer, Equinox Open Library Initiative | * Jason Boyer, Equinox Open Library Initiative | ||
* Jeremy Murray, Evergreen Indiana | * Jeremy Murray, Evergreen Indiana | ||
+ | * Michele Morgan, NOBLE | ||
+ | * Bill Erickson, KCLS | ||
+ | * Ken Cox, independent developer | ||
+ | * Martha Driscoll, NOBLE | ||
+ | * Christine Morgan, NOBLE | ||
+ | * Dan Guarracino, OWWL | ||
+ | * Elizabeth Thomsen, NOBLE | ||
+ | * Adam Bowling, Emerald Data Networks | ||
+ | * Josh Lamos, Emerald Data Networks | ||
====== Agenda ====== | ====== Agenda ====== | ||
Drop your scheduled discussions or project work here. | Drop your scheduled discussions or project work here. | ||
+ | |||
+ | ===== Monday ===== | ||
+ | * 7pm ET - Welcome dinner at [[https:// | ||
===== Tuesday ===== | ===== Tuesday ===== | ||
+ | * 8:30-9 a.m. Breakfast at the Hempstead Seminar Suite in the Hempstead Commons | ||
+ | * 9 a.m. | ||
+ | * Welcome from Brian Courtemanche, | ||
+ | * Introductions, | ||
+ | * 12 p.m. Lunch, also at the Hempstead Seminar Suite in the Hempstead Commons | ||
+ | * 1:00 p.m. Mobile App presentation | ||
+ | * 1:30 pm Outreach Meeting | ||
+ | * 2:30 p.m. Afternoon pick-me-ups | ||
+ | * 3 p.m. Dev meeting | ||
+ | * 6:30 p.m. Dine arounds (meet in lobby at 6:10) | ||
- | [placeholder] | ||
===== Wednesday ===== | ===== Wednesday ===== | ||
+ | * 8:30-9 a.m. Breakfast at the Hempstead Seminar Suite in the Hempstead Commons | ||
+ | * 9:30 a.m. Search filtering philosophy re: library groups and OUs (sleary, miker, abneiman, et al.) | ||
+ | * 11 a.m. Open RingCentral testing (2025 conference software) | ||
+ | * 11:30 a.m. Translations discussion (Zoom - hopefully recorded!) | ||
+ | * 12 p.m. Lunch, also at the Hempstead Seminar Suite in the Hempstead Commons | ||
+ | * 1:00 p.m. Git Discussions (45 minutes) | ||
+ | * 1:45 p.m. Releases (45 minutes) | ||
+ | * 2:30 p.m. Afternoon pick-me-ups | ||
- | [placeholder] | ||
- | ===== Thursday ===== | ||
- | [placeholder] | + | ===== Thursday ===== |
+ | * 8:30-9:00 a.m. Breakfast at the Hempstead Seminar Suite in the Hempstead Commons | ||
+ | * 9:00 a.m. Accessibility update (sleary) | ||
+ | * 11:00 a.m. Aspen/ | ||
+ | * 12:00 p.m. Hack-a-way end | ||
===== Discussion Topics ===== | ===== Discussion Topics ===== | ||
- | | + | |
+ | |||
+ | ** Git - scheduled 100pm ET Weds** | ||
* Git workflow - rebase vs. merge? (csharp) | * Git workflow - rebase vs. merge? (csharp) | ||
- | * GitHub: new Projects feature would make release organizing, Bug Squash, etc. much easier. (sleary) | + | * GitHub: new [[https:// |
- | * Scheduling translation work for point releases (abneiman) | + | * Build process, git tags versus branches (dyrcona) |
- | + | ||
+ | ** Releases - scheduled 145pm ET Weds** | ||
+ | |||
+ | * Scheduling translation work for point releases (abneiman) - ** scheduled 11:30am Wednesday - on Zoom & hopefully recorded ** | ||
+ | * Release team membership (redavis) | ||
+ | * Automated testing & QA processes (sleary & jsandberg--remote) | ||
+ | * Make the install procedure easier for first-timers [[https:// | ||
+ | * < | ||
+ | * Put 950.data.seed-values.sql through a shredder; or, make seed data manageable, maybe? LP#2077915 https:// | ||
+ | |||
+ | ** Sys admin ** | ||
+ | |||
+ | * DDOS mitigation. An increase of bot traffic in the last couple of years. NGINX leaky bucket helps but we are starting to see an issue with 10's of thousands of IP's hammering the front-end, instead of a single bad IP. LP#1913617 https:// | ||
+ | |||
+ | ** Mobile app - 100pm ET Tues ** | ||
+ | |||
+ | * Mobile app: how to build and test them, how they are put together and why, recent and future developments (Ken Cox) | ||
+ | * Adding filters to the new action triggers | ||
+ | * Aspen Discovery Layer breaks My Lists and Checkout History for mobile app users (Ken Cox) | ||
+ | |||
+ | ** Features / Future releases ** | ||
+ | |||
+ | * Where are we with [[accessibility: | ||
+ | * See the [[accessibility: | ||
+ | * Updating the [[https:// | ||
+ | * Dashboard (scottangel) | ||
+ | * Search filtering philosophy re: library groups and OUs (sleary, miker, abneiman, et al.) - **scheduled 930am ET Weds** | ||
+ | * Can we merge [[https:// | ||
+ | * I emailed the dev list. | ||
+ | * I pushed it Wednesday afternoon. (Dyrcona) | ||
+ | * Any interest in a Rust working group? | ||
====== Accomplishments ====== | ====== Accomplishments ====== | ||
=== Discussions and Research === | === Discussions and Research === | ||
- | * [placeholder] | + | * Tuesday morning - dashboard discussion |
+ | * Tuesday afternoon - mobile app demo / discussion; API discussion | ||
+ | * Tuesday afternoon - Outreach Meeting | ||
+ | * " | ||
+ | * Wednesday morning - search / library groups discussion | ||
+ | * We could teach library groups how to be hierarchical and live within OU tree; OR allow them to be outside of the hierarchy. | ||
+ | * Shelving location groups currently do not limit by selected OU which a typical user would expect | ||
+ | * UI solution: if they select a library group / shelving location, can the OU selector go back to the top and grey out? | ||
+ | * Relevant bugs: | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * Wednesday afternoon - translations in point releases | ||
+ | * Consensus: translations can go in the point release AFTER the code change (e.g. bugs in 3.14.5 with string changes will have updated translations in 3.14.6) | ||
+ | * Point release teams / builders will need to have a member with PO editor access to get the translation files - Galen, Jennifer P, Jason S, Blake are PO editor admins and can grant access | ||
+ | * New tags for LP: | ||
+ | * '' | ||
+ | * '' | ||
+ | * Current list of i18n bugs to be updated: [[https:// | ||
+ | * Wednesday afternoon - git discussion | ||
+ | * What is our merge strategy? Newer versions of git require you to state this: rebase/ | ||
+ | * Merge interfiles via commit date; rebase / cherry-pick just puts it on top. Merge retains original commit hashes but you lose the history of where your branch has everything on top of it. | ||
+ | * Currently a lot of us use rebase / cherry-pick, | ||
+ | * Is there a potential workflow solution to the problem of changed hashes? | ||
+ | * Also: every bug fix that's backported gets its own hash but this would require significant rethought of our internals. | ||
+ | * Git workflows documentation: | ||
+ | * Github is the only current realistic alternative | ||
+ | * Github supports a good PR-review workflow | ||
+ | * Github move would require: | ||
+ | * Ensuring core committers have rights to push to github repo | ||
+ | * Losing the working repo & collabs; all PRs on the main repo | ||
+ | * Integrating PO Editor with github | ||
+ | * Probably migrating from Launchpad to github Issues (not required though) | ||
+ | * Probably more rebasing of topic / bugfix branches; use of merge commits | ||
+ | * Still would need to settle merge vs cherry-pick; | ||
+ | * General consensus is stick with patch instead of merge | ||
+ | * Git tags: use these instead of branches? | ||
+ | * See patch from Jane Sandberg: [[https:// | ||
+ | * Currently doing this in OpenSRF but not Evergreen | ||
+ | * Only for release branches, not for main | ||
+ | * Probably best to start with the next top level release branch | ||
+ | * [[https:// | ||
+ | * Question: can we use this without being fully on github? Answer: yes, but we'd need to manually create LP items if we're not using GH Issues. | ||
+ | * GH Projects is less-terrible in the accessibility sense than a lot of other tools | ||
+ | * Wednesday afternoon - Release discussion | ||
+ | * We have been better at monthly releases but it is the same several people | ||
+ | * RelTeam needs: a core committer, someone who can build, someone who can test, someone who can do notes, someone to update the website / LP tags | ||
+ | * Github & using tags instead of branches would simplify this process. | ||
+ | * Redis & 3.15 vs 4.0 | ||
+ | * Would likely mean a heavier churn on OpenSRF than in the last few years | ||
+ | * OpenSRF 4.0 with Redis should go out ASAP so we can poke at it. | ||
+ | * Consensus: EG 3.15 in spring 2025 and EG 4.0 in fall 2025 | ||
+ | * Release teams - [[https:// | ||
+ | * Thursday morning - Accessibility discussion | ||
+ | * 70% of accessibility bugs fixed | ||
+ | * 60 in OPAC for 3.14 | ||
+ | * [[https:// | ||
+ | * Need to audit staff catalog and client | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * We expect to be ready for the April 2026 accessibility deadline. | ||
+ | * Susan & Andrea updated the [[https:// | ||
+ | |||
+ | === Bugs Reviewed or Submitted: (30) === | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | === New patches submitted: (17) === | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | === Sign offs: (3) === | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
- | === Bugs Reviewed or Submitted: (count) === | + | === Patches Pushed: (6) === |
- | * [placeholder] | + | * [[https:// |
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
- | === Sign offs/ | ||
- | * [placeholder] | ||
- | === New patches submitted: (count) === | ||
- | * [placeholder] | ||
- | === Patches Pushed: (count) === | ||
- | * [placeholder] | ||
hack-a-way/hack-a-way-2024.1726144060.txt.gz · Last modified: 2024/09/12 08:27 by roganh