Editing Community Contributions Day November 2015 (section)

=== Interest Groups ===

Any contribution that can be made is welcome, whether it's a minor edit to a wiki page or a bugfix.  However, it may be profitable to run a number of discussion groups in the morning around areas of interest.  These discussion groups can then set up work to be accomplished in the afternoon.

* 10:00 - 11:00 Interest groups meet (skype, google hangout?), make decisions and assign tasks
** What problem are we solving?
** How will we work?
** What communication platform will we use? Skype, Google Hangouts, Google Docs, EMail?
** Who will do what?
* 11:00 - 13:00 Morning Contributions
* 14:00 - 16:00 Afternoon Contributions
* 16:00 - 16:30 Interest groups wrap-up and reporting.

Each interest group should have a leader who is responsible for chairing the initial meeting, making sure the logistics run smoothly and creating some kind of record of the day (blog post, wiki page, etc).


==== Group 1: Community Training Course ====

We're coordinating via a [https://docs.google.com/document/d/1CPegvGl9BO45E4ye5_Bpk7e3kurc_spEL3OcmGcUZyA/edit?usp=sharing Google Doc]

This interest group is concerned with the wiki page at http://wiki.eprints.org/w/EPrints_Training_Course.

Areas of Discussion
* Standard layout and content for training video pages
* Content of the training course
* Production of new content
* Linking to other wiki pages

Members:
* Adam Field (willing to lead the group)
* Alan Stiles (alternatively contributing to Group 2)
* Lizz Jennings (likely to switch between this and Group 2)
* Mick Eadie
* George Mamalakis (may also help in some bug reports in Group 2 and also help in creating some Bazaar packages we've already started)

==== Group 2: Technical ====

This interest group will be looking at Github, folding in pull requests and evaluating bugs.

Get on the google hangout now [https://hangouts.google.com/call/md4isxlevojprl6n3vpp2c3dtua https://hangouts.google.com/call/md4isxlevojprl6n3vpp2c3dtua]

Topics of Discussion
* Vagrant build - see: https://github.com/eprintsug/eprints-vagrant (Good work! EP-Kudos and a cream bun to Robert Doiel!)
* Categorisation of issues: https://github.com/eprints/eprints/issues
* Building a [[How to build a development environment from source control]]
* Having built an EPrints from source the Unit tests do not all pass...

Members
* Jiadi Yao
* Alan Stiles (alternative contributing to Group 1)
* Lizz Jennings (likely to switch between this and Group 1)
* Mick Eadie
* Patrick McSweeney (will lead the session ;o)
* John Salter (will assist with the leading of the session)
* John Beaman

==== Group 3: Community Contributions, Best Practices and Processes ====

This group will look at how barriers to community contributions (at all levels) can be lowered and community engagement can be promoted. We'll also look at community best practices and processes in EPrints. '''If you don't make the 10 o'clock meeting, don't worry, just come and join us at the Google Doc below.'''

Members

* Rachel Proudfoot - skype 'rachel_proudfoot'
* Valerie McCutcheon -skype 'mccutchv'
* Les Carr
* Adam Field (in and out, mainly in group 1)

'''Working Document (Google doc)'''
* [https://docs.google.com/document/d/1YYqeB0r5S8A9rYO9UZN-SoQLBLb2B7WQuP_WW3EKXEU/edit?usp=sharing Group 3 Capture document] - if you can't edit it, contact Rachel or Valerie

Possible subtopics - what do users want? 

* User friendly topic guide on wiki
* reliable version information (cf. [[Required_software]]) incl. wiki update
* Impact
* Open Access - drafting community requirements for a standard functionality in EPrints.