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 132 Next »

Table of Contents

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, October 10, 2012

Agenda

Regular Items

  • Forgoing JIRA review for now to spend time on 3.0 & Testathon. Specific JIRA tickets can be brought up as needed.

Discussion Topics

  1. 3.0 Release Testathon
    1. Any last things to clean up or take care of?
    2. SourceForge – should we still put release downloads up on SourceForge
      1. Pros: Sourceforge provides nice download stats/charts. GitHub doesn't (the best GitHub can do is give you a grand total).
        1. Also, it seems like there's no easy way to tell folks who find DSpace on SourceForge that the latest releases can be downloaded over on GitHub.
      2. Cons: It's another place to post releases to.
    3. DS-1277 : helix84 has suggested to have http://demo.dspace.org/ feedback form send to a different JIRA project.  Thoughts? Alternatives?
  2. 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 future. 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

Meeting Transcript

Action Items

(Action items 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

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.