<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://wiki.eprints.org/w/index.php?action=history&amp;feed=atom&amp;title=UK_Hack_Day_September_2015</id>
	<title>UK Hack Day September 2015 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.eprints.org/w/index.php?action=history&amp;feed=atom&amp;title=UK_Hack_Day_September_2015"/>
	<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=UK_Hack_Day_September_2015&amp;action=history"/>
	<updated>2026-04-21T04:50:42Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.31.8</generator>
	<entry>
		<id>https://wiki.eprints.org/w/index.php?title=UK_Hack_Day_September_2015&amp;diff=11357&amp;oldid=prev</id>
		<title>Libjlrs: Created page with '10th September 2015, Southampton, UK  A group of EPrints developers met to try and progress the core of EPrints, and help each other get up and running with committing changes to…'</title>
		<link rel="alternate" type="text/html" href="https://wiki.eprints.org/w/index.php?title=UK_Hack_Day_September_2015&amp;diff=11357&amp;oldid=prev"/>
		<updated>2015-09-11T09:47:38Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;#039;10th September 2015, Southampton, UK  A group of EPrints developers met to try and progress the core of EPrints, and help each other get up and running with committing changes to…&amp;#039;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;10th September 2015, Southampton, UK&lt;br /&gt;
&lt;br /&gt;
A group of EPrints developers met to try and progress the core of EPrints, and help each other get up and running with committing changes to GitHub.&lt;br /&gt;
&lt;br /&gt;
Our aims were:&lt;br /&gt;
&lt;br /&gt;
* resolve open pull requests (https://github.com/eprints/eprints/pulls)&lt;br /&gt;
* resolve known bugs (https://github.com/eprints/eprints/issues?q=is%3Aopen+is%3Aissue+label%3Abug)&lt;br /&gt;
* close as many other Issues from GitHub as possible (https://github.com/eprints/eprints/issues)&lt;br /&gt;
* flag/tag/milestone remaining Issues&lt;br /&gt;
* write (better) documentation anything we resolve&lt;br /&gt;
* scribble (in a structured way) on this: https://github.com/eprints/eprints/network&lt;br /&gt;
&lt;br /&gt;
We discussed some 'QA' type process for reviewing commits:&lt;br /&gt;
* Check install&lt;br /&gt;
* Visual code QA (are phrases in language-specific files? Are files structured in the right way)&lt;br /&gt;
* Documentation check (and e.g. include example config in defaultcfg if using a param to control a plugin)&lt;br /&gt;
* Will it break multiple archives running under one EPrints install?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Work was also undertaken to make an easy-to-use (and quick to get going) virtual machine, using source from GitHub.&lt;br /&gt;
This should allow us (the EPrints geek community) to get up and running and doing '''useful''' things very quickly!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Accolades ==&lt;br /&gt;
Adam spoke about adding technical-install accolades in the Bazaar:&lt;br /&gt;
* one-click install&lt;br /&gt;
* requires configuration (e.g. adding an API key, or turning come options on), with a control screen&lt;br /&gt;
* needs additional resources on server (e.g. additional Perl packages)&lt;/div&gt;</summary>
		<author><name>Libjlrs</name></author>
		
	</entry>
</feed>