Difference between revisions of "Community Contributions Day November 2015"

From EPrints Documentation
Jump to: navigation, search
(Group 4: Best Practices and Processes)
(Group 4: Best Practices and Processes)
Line 78: Line 78:
 
Suggested subtopics - Impact, Open Access - drafting community requirements for a standard functionality in EPrints.  What else might we tackle on the day?
 
Suggested subtopics - Impact, Open Access - drafting community requirements for a standard functionality in EPrints.  What else might we tackle on the day?
  
[https://drive.google.com/file/d/0ByT5LhqMLV4JUTdNQ19CTklzVkU/edit?usp=sharing Google Doc link]
+
[https://docs.google.com/document/d/1pX0KKJ7tOH7BF3IBIjbG-EZccK2sCPmnr7IEo7zTQCQ/edit Google Doc link]
  
 
Members:
 
Members:

Revision as of 10:14, 12 November 2015

This page has been created in the run-up to the EPrints Community Contributions day on November 18th, 2015

Objectives

This event is intended to bring the all parts of the EPrints community together to improve the software and documentation. We hope to achieve:

  • code improvements
  • wiki curation
  • training and demonstration videos
  • community member interacting and training each other

Event Run Up

Things to do before the event:

  • Register for the Wiki via the EPrints LDAP server at http://trac.eprints.org/ldap/
  • If you have an a suggestion for an interest group, add it below
  • Please add your name to an interest group that looks interesting.

On the Day

Independent Contribution

If contributors have particular projects they want to work on on their own and post back to the group, then there's no need to join an Interest Group. Add you name below and a short text about what you plan to contribute.

Members:


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 (google hangout?), make decisions and assign tasks
    • What problem are we solving?
    • How will we work?
    • 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

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

Members:

  • Adam Field
  • Alan Stiles (alternatively contributing to Group 2)
  • Lizz Jennings (likely to switch between this and Group 2)

Group 2: Technical

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

Members

  • Jiadi Yao
  • Alan Stiles (alternative contributing to Group 1)
  • Lizz Jennings (likely to switch between this and Group 1)

Group 3: Community Contributions

This group will look at how barriers to community contributions (at all levels) can be lowered and community engagement can be promoted.

Members

  • Rachel Proudfoot

Group 4: Best Practices and Processes

This group is concerned with community best practices and processes in EPrints.

Suggested subtopics - Impact, Open Access - drafting community requirements for a standard functionality in EPrints. What else might we tackle on the day?

Google Doc link

Members:

  • Valerie McCutcheon ( I can lead this but happy for someone else to do it)

Logistics

Post Event