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 26 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/GMT 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.

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.

Developers Meeting on Weds, May 12, 2010

Agenda

  • Any Announcements / Additional Agenda Items?
    • Who all will be in Madrid at OR10? For those who will be around, DSpace Committers Mtg on Monday (July 5) afternoon.
    • Reminder, you can send agenda items for upcoming meetings to Tim
  • DSpace 1.6.1 Updates (Kim Shepherd)
    • 1.6.1 Open Issues: 1.6.1 Version in JIRA
    • Code Freeze date is Friday, May 14.
    • Planning for mini-testathon next week?
  • Discussion Topics & possible Voting:
    • Guidelines for Committing – draft attempting to describe our current code-committing guidelines. Do all committers agree this accurately describes our current best-practices?
    • Migrating Documentation from DocBook to Confluence for 1.7.0 release
      • There's been great initial work by Mark Diggory & Jeff Trimble to investigate this. It seems relatively straightforward, and both Mark & Jeff seem to be in favor.
      • We'd likely want to separate these official documentation pages from the normal wiki (they'd likely be in a different Confluence "Space"), so that they can be more tightly managed/watched. At least initially, it's likely only committers & other trusted DSpace community members/developers will have access to modify the official Documentation area of the wiki.
      • See DSpace Documentation Test as an example of how the 1.6.0 Documentation could look on the Wiki.
  • JIRA Catch-Up – starting with issue DS-517 (and getting as far as we can).

Meeting Notes

1.6.1 is on track, 1.6 code-freeze on Fri, "Guidelines for Committing" approved, migrating Docs to Wiki for 1.7

  • Updates on 1.6.1 from Kim
    • Code Freeze: Friday, May 14
    • Release Date: Friday, May 21
    • Everything seems on track, some issues may need to be pushed back if incomplete on Friday.
    • Mini-Testathon: Update http://demo.dspace.org with 1.6.1 for testing next week, before release date.
  • Guidelines for Committing – Everyone (who spoke up) seems to generally approve of these guidelines.
    • Robin Taylor will help us establish some clearer guidelines on JIRA usage to go with these
  • Migrating Docs to Wiki for 1.7
    • General approval that migrating official documentation to Wiki is a good thing – less work for Jeff Trimble (our docu guru), and gives opportunities for others to help in writing/editing our docs
    • Need to determine workflow for who gets access to edit these docs? Hopefully, we can allow anyone we generally trust not to add malicious/spam content (but they will need to request access from someone first)?
  • Post Meeting Discussion
    • Discussion on how to better utilize JIRA – reviewing of JIRA issues always seems to "fall off the plate" in these meetings. We never have enough downtime to perform these reviews
    • Perhaps add a new "Received" step (before "Open"), which will let us all know which issues still need reviewing. We could assign someone to review issues, or generally review them ad hoc – and keep meetings specific to only reviewing major issues or suggested patches/fixes for issues.

Action Items

  • Continue work to migrate docs to wiki for 1.7.0 – Jeff & Mark D are already leading this work
  • Robin Taylor will help establish JIRA usage guidelines and perhaps establish a new JIRA workflow

Meeting Transcript

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.