* Register for the Wiki via the EPrints LDAP server at [http://trac.eprints.org/ldap/ http://trac.eprints.org/ldap/]

* Register for the Wiki via the EPrints LDAP server at [http://trac.eprints.org/ldap/ http://trac.eprints.org/ldap/]

* If you have an a suggestion for an interest group, add it below

* If you have an a suggestion for an interest group, add it below

−

* Please add your name to an interest group that looks interesting.

+

* Please add your name to an interest group that looks interesting (see [[Training_Video:EPrints_Wiki_Basics]] for how to edit the wiki)

== On the Day ==

== On the Day ==

+

=== Jumping In ===

+

+

So, you have time to contribute and need to know how to get started. Here are your options:

+

+

* Pick an interest group below, and join it

+

* If you don't know how to join, contact one of the event organisers

+

** Adam Field

+

*** @gobfrey on twitter

+

*** af05v@ecs.soton.ac.uk

+

** Valerie McCutcheon

+

***valerie.mccutcheon@glasgow.ac.uk

+

*** 0141-330-2674

+

** Rachel Proudfoot

+

*** 0113 343 4554

=== Interest Groups ===

=== Interest Groups ===

Line 25:

Line 39:

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.

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.

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).

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).

* 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

Members

Line 64:

Line 87:

* Lizz Jennings (likely to switch between this and Group 1)

* Lizz Jennings (likely to switch between this and Group 1)

* Mick Eadie

* Mick Eadie

−

* Patrick McSweeney

+

* Patrick McSweeney (will lead the session ;o)

−

* John Salter

+

* John Salter (will assist with the leading of the session)

+

* John Beaman

−

==== Group 3: Community Contributions ====

+

==== 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.

+

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.'''

On the Day

Jumping In

So, you have time to contribute and need to know how to get started. Here are your options:

Pick an interest group below, and join it

If you don't know how to join, contact one of the event organisers

Adam Field

@gobfrey on twitter

af05v@ecs.soton.ac.uk

Valerie McCutcheon

valerie.mccutcheon@glasgow.ac.uk

0141-330-2674

Rachel Proudfoot

0113 343 4554

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.

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 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.

Open Access - drafting community requirements for a standard functionality in EPrints.

Independent Contribution

Participants are encouraged to join an interest group, but have the option of working independently on their own pet project or objective. Please put your name in the members list below, with a brief description of what you will be progressing.

Members:

Luke Skywalker (I'll be researching the Force)

Logistics

Each interest group should decide on the appropriate platform to use for communications and coordination.

Post Event

It would be appreciated if each team could produce a write-up of the days activities for the benefit of future events and to show the value of the day. It should be no more than 400 words and a bulleted list of outcomes. Feel free to post these on any blog or platform you wish, but Adam Field would quite like to gather them all together in a blog post about the day.