Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 121 Next »

Table of Contents

The root page DSPACE:Developer Meetings could not be found in space DSpace.

Meeting Schedule and Attendance

DSpace Developer meetings are a time when Committers and interested Developers can discuss new software features, upcoming releases of DSpace software, and generally plan out the roadmap of DSpace. All meetings are public. We welcome anyone and everyone to attend, speak their opinions or just listen in on the discussions. Please note that we archive all discussions (see Meeting Archives), as a service for those who are unable to attend.

DSpace Developer meetings take place on the following schedule:

  • Every Wednesday at 20:00 UTC in #duraspace IRC channel
  • All meetings are held for 1 hour (although, admittedly, discussion sometimes extends beyond that)

See the world clock to determine the meeting time where you live. If you are unsure how to connect to IRC, see our list of IRC Resources & Clients

This meeting schedule is also available via the DuraSpace Public Events Calendar (iCal, RSS Feed).

Meeting topics often include:

  • Recent updates on upcoming DSpace releases, bug fixes or features
  • Reviewing of recent reported issues/bugs/feature requests (see JIRA Cleanup Sessions for more info)
  • Occasionally we vote or make decisions on upcoming DSpace technology plans/roadmap (see Developer Voting Procedures for more info)

If you are unable to attend a meeting, please feel free to add your own notes/comments to the meeting's wiki page.

NOTE: Any developer is also welcome to ask questions or brainstorm ideas with Tim Donohue during the DSpace Office Hours held before the weekly Developers meeting in the same IRC channel.

Developers Meeting on Weds, July 18, 2012

Agenda

Regular Items

Discussion Topics

  1. Anything to follow-up on after last week's OR12 DSpace Developers Meeting?
    • Any TODO's needing captured? Any specific decisions worth noting? Or anything we need to vote upon or schedule for a future meeting?
  2. Discussion & Review of OAI 2.0 / XOAI work (from Lyncode) for 3.0. (OAI 2.0 Documentation, Pull Request #37, DS-1202)
    • This essentially would replace the current OAI webapp, with a new version which is based on Solr, is OpenAIRE & Driver compliant.
    • Do we replace the existing OAI module for 3.0? Do we make OAI modules in general "optional" to install? How do we want to manage this going forward?
  3. 3.0 Release - Reviewing larger features & planning the release
    • Are their particular features we want to schedule a special topic meeting around?
    • Should we be finding ways to split up review of all the existing features on the 3.0 Release notes page (or "rank" which ones need many eyes versus just a few)?
  4. 3.0 Questions (from helix84):
    1. Where should translations of individual modules like Discovery go? Including them in the main messages.xml currently works. This should be answered before freeze time, it already poses another barrier for commiting of translations, see DS-1049, DS-1054. This is a subproblem of i18n Improvements Proposal, but let us not divert this discussion too much to broad topics. ~~helix84
    2. DS-531: ETD-MS schema out of the box. Again, the larger problem is that our metadata schema should be brought up-to-date with DCMI, but maybe we could tackle this smaller issue of ETDs. I suggest we add a "thesis" schema with 5 fields mentioned in this table to support ETD-MS out-of-the-box. ~~helix84
  5. Need to review Guidelines for Committing based on GitHub/Git?
    • Thoughts on how we rework these polices to our new GitHub development environment (with Pull Request policies, etc.)?
  6. Other topics?

Additional Ongoing Topics

  1. How can we "catch up" with JIRA Backlog?
    • Do we need to "split up" the tickets & do quick reviews on our own? Or perhaps just split up tickets & do a very quick ranking & schedule ones with patches for 3.0?
    • Perhaps we schedule a "JIRA Backlog Bash" event (via IRC or similar) where we work together to decrease the backlog over a few days or a week (think of this like a "Test-a-thon" but instead we'd be working to just clear out the backlog as best we can).
  2. Brainstorming Features/Changes for 3.0. Can we work towards development teams around any of these projects?

Individual Status Updates

If you have status items to report, please enter them below at least 1 hour before the meeting starts.

Meeting Notes

JIRA Review, highlights/summary from OR12 mtg, brainstorms on releasing modules & install separately (Richard's MDS work, Lyncode's XOAI work)

Meeting Transcript

Action Items

Action items coming out of this meeting go here, if any.

Meeting Archives

Notes and Transcripts from all recent Developers Meetings are available off of the Developer Meeting Archives page.

  • No labels