EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #04560

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: EPrints hack day - 10th September 2015, Southampton UK

This sounds super exciting - yes please!

Lizz

--
Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2014)
Technical Data Officer
The Library 4.10, University of Bath, Bath, BA2 7AY UK
Ext. 3570 (External 01225 383570)
E.Jennings@bath.ac.uk
Research Data Management: http://www.bath.ac.uk/research/data


-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of John Salter
Sent: 14 August 2015 11:53
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] EPrints hack day - 10th September 2015, Southampton UK

Hi,
Would you be interested in a community engaged EPrints hack day on September 10th, in Southampton (prior to the UK EPrints User Group on the 11th September)?

We would be concentrating on the EPrints core (rather than Bazaar packages) and I think that we could get close to the next release with this work – a positive/definite outcome, rather than a ‘some progress was made on some things’ outcome.
 
I know that there are varying levels of EPrints knowledge / ability on this list - the idea would be that people could work individually or together on issues to resolve them, and in the process become more skilled in EPrints wizardry. People with more in-depth EPrints knowledge would be present assist (whilst they themselves are working on more complex bugs/issues). If you are still new to EPrints then you could participate by working with others, and provide valuable feedback on the work taking place and the documentation created.
 
I hope we could achieve:
- 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 for anything we resolve
- ??? (you tell us!)
 
The skills you would need are:
- EPrints knowledge
- some Git knowledge (but we can help with this)
- ability to consume caffeine
- ??? 
 
If it's not practical to get to Southampton, I hope you would still be involved - maybe using https://gitter.im/eprints/eprints as a communication channel.
Would you be interested in joining us at this event - either locally or remotely?

Cheers,
John



*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/