Jump to content
Wiki Home
EPrints Home
Bazaar
Files
Main menu
Main menu
move to sidebar
hide
Navigation
Front Page
EPrints 3 Manual
EPrints Training Course
EPrints Glossary
Installing EPrints
How-to Configure EPrints
EPrints 3.2+ API
EPrints 3 Reference
EPrints Plugins
Wiki
All categories
Recent changes
Main Page
Help
EPrints Documentation
Search
Search
Appearance
Log in
Request account
Personal tools
Log in
Request account
Pages for logged out editors
learn more
Contributions
Talk
Editing
UK Hack Day September 2015
Page
Discussion
British English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
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 GitHub. Our aims were: * resolve open pull requests (https://github.com/eprints/eprints/pulls) * resolve known bugs (https://github.com/eprints/eprints/issues?q=is%3Aopen+is%3Aissue+label%3Abug) * close as many other Issues from GitHub as possible (https://github.com/eprints/eprints/issues) * flag/tag/milestone remaining Issues * write (better) documentation anything we resolve * scribble (in a structured way) on this: https://github.com/eprints/eprints/network We discussed some 'QA' type process for reviewing commits: * Check install * Visual code QA (are phrases in language-specific files? Are files structured in the right way) * Documentation check (and e.g. include example config in defaultcfg if using a param to control a plugin) * Will it break multiple archives running under one EPrints install? Work was also undertaken to make an easy-to-use (and quick to get going) virtual machine, using source from GitHub. This should allow us (the EPrints geek community) to get up and running and doing '''useful''' things very quickly! == Accolades == Adam spoke about adding technical-install accolades in the Bazaar: * one-click install * requires configuration (e.g. adding an API key, or turning come options on), with a control screen * needs additional resources on server (e.g. additional Perl packages)
Summary:
Please note that all contributions to EPrints Documentation may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
EPrints Documentation:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)