dev:hackfest:eg2013
This is an old revision of the document!
Evergreen 2013 hackfest ideas
Add ideas here, feel free to coordinate times with others.
Idea | Bug link | Time / timeslot | Interested people | Notes |
---|---|---|---|---|
Testing & sign-off walkthrough: learn how to help get new code into the next release | 1 hour / Morning | dbs | ||
TPAC hacking basics | 1 hour / Morning | dbs | ||
TPAC: Allow URLs in marc field 856 to be used | lp1133464 | ?? | paxed | Probably should follow the "TPAC hacking basics" bit |
Explore retiring 950.data.seed-values.sql for new data. IRC talk | 1hr | berick | ||
More Sample data (like concerto, etc.) for testing | E.g. lp1155771 | 2hr | berick | |
Improving auth security / bcrypt / etc | 2hr | berick | More like planning than development, but maybe.. | |
Move OS-based prerequisites to own Makefile.install | 2hr | Dyrcona | Split Makefile.install into separate files for Debian, Fedora, etc. Both Evergreen and OpenSRF | |
Building development images on Ubuntu. | 1hr | Dyrcona | If anyone is interested, I can show them what I do to make development VMs and install evergreen. | |
Write example unit tests, structured in a way that enables them to participate in a test framework. | The whole day | schan_yvr | There are three prototypical set of unit tests to write, based on the languages Javascript, Perl, and PL/pgSQL. The unit tests would serve as examples for developers to write their own to accompany their contributing fixes and features. |
dev/hackfest/eg2013.1364841873.txt.gz · Last modified: 2022/02/10 13:34 (external edit)