Hi all,

As Chris Wilper already mentioned in an earlier email, he and I thought 
it would be a good idea to start sending regular reminders about DSpace 
and Fedora developers meetings to both of our respective developer 
listservs.  We hope this will help members of the respective communities 
to have a good awareness of what's going on at large, and will help lead 
to some good cross-team discussions down the road.

For those unfamiliar with the DSpace Developer Meetings, they take place 
every Wednesday at 20:00 UTC (4pm ET in USA) in #duraspace IRC.  These 
meetings are open to the public and entirely IRC chat based.  Topics 
usually focus on upcoming releases, status updates, discussions of new 
ideas/proposals, and reviews of any recent issues (from listservs or 
JIRA). Occasionally we will also hold a "Special Topic" meeting devoted 
towards in depth discussion of a single larger topic.  Anyone is welcome 
to join the discussion, or just sit in on the IRC meeting.

The agenda for tomorrow's meeting (Weds, Sept 29) is posted here:
https://wiki.duraspace.org/display/DSPACE/Developer+Meetings

This week is focused on updates around upcoming DSpace 1.7 release, 
along with a collaborative review of some recent posted JIRA issues.

The archived notes/transcripts from all our past meetings can be found 
here (transcripts/notes from tomorrow's meeting will also be available 
there after it has completed):
https://wiki.duraspace.org/display/DSPACE/Developer+Meeting+Archives

We hope you are able to join us!

Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to