Re: [Dspace-devel] Feedback on migrating mailing lists off SourceForge
What happens to emails when someone a year from now sends an email to dspace-t...@lists.sourceforge.net, since a decade of random documentation suggests so, they've historically been subscribed, and used to just work? I'm guessing they'll get a bounce, can there be a message in the bounce? This listserv has migrated to dspace-tech@gg . com Or is there some forwarding option? I tend to like Mark Wood's tonic of rip the bandaid off now, so, migrate to GG, and decommission SF. Peter Dietz Longsight www.longsight.com pe...@longsight.com p: 740-599-5005 x809 On Mon, Aug 3, 2015 at 2:06 PM, Tim Donohue tdono...@duraspace.org wrote: Hi Graham, The Groups Migration API unfortunately only works for Google Apps Groups. It won't work for normal googlegroups.com Groups (annoying, I agree). See it's prerequisites: https://developers.google.com/admin-sdk/groups-migration/v1/guides/prerequisites (There's also no way to migrate a Google Apps Group to a normal googlegroups.com Group. So you cannot even use Migrations API as a pass through.) So, the only route to migrate messages into googlegroups.com is to send them via SMTP. Here's an example: https://github.com/wojdyr/fityk/wiki/MigrationToGoogleGroups Unfortunately, that's the route that seems to no longer take note of the Date: field. This is the same route that Fedora used when they moved from SF to GG. But, back then (mid-2013), GG *did* respect the Date: field even when sending archives via SMTP. Though Fedora had a different problem back in 2013, where all messages migrated under the same user -- if you browse the Fedora archives ( https://groups.google.com/forum/#!forum/fedora-tech) back to mid-2013 you'll find that all messages appear under a user named Fedo Raadmin (Fedora Admin). In my test migrations, all migrated messages retain the From: field (sender info) and all other fields *except* for Date:. Interestingly, the Date: field actually does get migrated properly, but it is no longer utilized in the browse interface for Google Groups (instead it seems to be using the date provided in the latest Received: header). That's the best solution I've managed to come up with thus far. If you know of anything else, I'd definitely be interested. But from my tests, sadly, I haven't been able to find any way around the Date: problem. - Tim On 8/3/2015 10:12 AM, Graham Triggs wrote: How are you planning to do the migration, as the Groups Migration API documentation suggests that it does take notice of the Date: field in the (RFC 822 formatted) messages? G On 3 August 2015 at 15:40, Tim Donohue tdono...@duraspace.org wrote: Hi Developers / Committers, As of yet, I've heard little feedback on the proposed mailing list migration. So, I'm assuming no one else has major objections to any of these options. Currently, I'm leaning towards just migrating all mailing lists + archives into Google Groups, even though the dates of archived messages will appear incorrectly (this is option #1 described below). We can then add a note to the Google Group description letting everyone know that earlier messages all appear under the same date. I have not yet scheduled a start date for this process, but I'd hope to have it completed by the end of August. I plan to migrate less active lists first, and save our most active lists (dspace-tech especially) for last. Obviously though, I'll let each list know prior to migrating that list. Please do let me know though, if you have any thoughts (or prior Google Groups migration experience to share). Thanks, Tim On 7/29/2015 2:27 PM, Tim Donohue wrote: Hi Developers, In case you haven't seen recent Developer Meeting notes, I wanted to update everyone here on recent working investing the migration of our DSpace mailing lists off of SourceForge (lists.sourceforge.net). As you may have heard, SourceForge had some major stability issues recently [1], plus there's been controversy around its practices [2], not to mention the fact that all our mailing lists have crashed twice this year already (Feb then last week). So, in some discussions on IRC, several of us feel it's about time to move entirely off SourceForge. This includes finding a new home for our mailing lists (including this one). Thus far, my concentration has been in looking to migrate us to Google Groups. While everyone has their favorites, I've personally found Google Groups easier to manage, and much easier to browse and search (than Mailman which SourceForge uses). Plus, many other open source projects in our space have jumped to Google Groups, including Fedora, Hydra, Islandora. DSpace also already uses Google Groups for the DSpace Community Advisory Team (DCAT) mailing list (and it's become the de facto standard within DuraSpace for new mailing lists, honestly). So, in a sense we'd be consolidating on GG. But, there is a big gotcha (hence
[Dspace-devel] DSpace Dev Mtg Tomorrow @ 20:00 UTC and JIRA Backlog Hour @ 19:00 UTC
All, Tomorrow (Weds, Aug 5) at 20:00 UTC, we have our weekly DSpace Developers Meeting in the #duraspace IRC channel. To determine your local time, check the world clock: http://www.timeanddate.com/worldclock/fixedtime.html?hour=20min=0sec=0p1=0 The agenda is posted on our Developer meetings page at: https://wiki.duraspace.org/display/DSPACE/Developer+Meetings The notes from last week's meeting are also available off of the Meeting Archives area of that page. As always, all our meetings are public. We welcome any developers or non-developers to attend or just read along with the chat discussions. If you are unable to attend, you can always add your own notes/thoughts on any agenda item to the above wiki page. == JIRA Backlog Hour == The hour prior to our Developers Meeting, we will be holding a JIRA Backlog Hour in #dspace IRC (note that it takes place in #dspace and NOT #duraspace). During this meeting, developers who are available will begin to work together to tackle our backlog of Received tickets/bug reports in JIRA. We'll be looking to do a quick analysis of tickets to help move them along through our workflow. Anyone is welcome to join us (and you are more than welcome to just join mid-meeting as well). It's a great way to learn about how we work together to support DSpace, and also a great way to contribute to DSpace software. Plus, you'll be helping all of us to determine which tickets (old and new) could use extra love attention. Our current JIRA Received backlog is at: https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+DS+AND+status+%3D+Received+ORDER+BY+key+ASC%2C+priority+DESC We hope to see you in IRC! Thanks, Tim Donohue Technical Lead for DSpace Project DuraSpace.org -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Special Topic Meeting: DSpace Services API project - July 23 @ 15:00 UTC
Hi Developers, Just a reminder that TOMORROW's Developer Meeting (Aug 5 @ 20:00 UTC) will be another chance to discuss your feedback on the Services API. So, please consider joining us for that meeting. https://wiki.duraspace.org/display/DSPACE/DevMtg+2015-08-05 - Tim On 7/28/2015 4:46 PM, Tim Donohue wrote: Hi Developers, Just a reminder that we'll be discussing your feedback on this Services API at TOMORROW's Developer Meeting (July 29 @ 15:00 UTC). If you have feedback that you'd like to be heard, please consider attending that Developer meeting in #duraspace IRC. You are also welcome to send feedback to this list, on #dspace IRC, or by contacting me directly. More info on the tomorrow's meeting can be found at: https://wiki.duraspace.org/display/DSPACE/DevMtg+2015-07-29 Thanks, Tim On 7/23/2015 11:47 AM, Tim Donohue wrote: Hi Developers, For anyone who was unable to attend this meeting, or wants to review the material, the video and slides from the meeting are available on the new Service Based API wiki page. The wiki page itself also contains the initial documentation around this API refactoring: https://wiki.duraspace.org/display/DSPACE/DSpace+Service+based+api As mentioned in the meeting, the next steps are to discussion this work in the next two Developer Meetings (Weds, July 29 @ 15:00UTC and Weds, Aug 5 @ 20:00UTC). Developers are encouraged to review this work and provide your honest feedback. You are welcome to send feedback to this list, on #dspace IRC, in upcoming meetings, or by contacting me directly. By early August, I hope that we can come to a consensus whether we'd like to help move this work forward ASAP in time for the DSpace 6.0 release (later this year). But, to do so, we'll also need more developers to get involved and collaborate on some of the final refactoring steps. Looking forward to hearing your opinions on this initiative! Tim On 7/14/2015 3:26 PM, Tim Donohue wrote: Hi Developers, On Thursday, July 23 from 15:00-16:00 UTC (11:00am-12:00pm EDT), we will be holding a Special Topic meeting to learn about and discuss the DSpace Services API project begun by @mire. The DSpace Services API is an in-progress, refactoring of the DSpace API layer to better support separation of concerns. Simply put, often, in the existing API, there is an intermingling of business logic and database logic which is difficult to maintain, debug and/or build against. One of the most obvious examples is how we deal with database software support (PostgreSQL vs. Oracle), but such intermingling of logic exists in many of our core classes. The DSpace Services API attempts to tease apart the database logic from the business logic into separate layers, while also adding support for Hibernate (http://hibernate.org/). The goal is to provide an easier to maintain, more modular API, while also enhancing how we deal with database logic in general (via Hibernate). While this work began as an internal experiment within @mire, it has quickly progressed into a potentially promising refactoring of the DSpace API layer. While the refactoring work is not yet complete, it is at a stage where others could contribute and/or collaborate on the work. It may even be considered for the upcoming DSpace 6 release, should it garner enough interest and collaborators to help move it forward rapidly. If this project sounds interesting to you, we encourage you to attend the meeting. We will record this meeting and make the video available for anyone who is unable to attend. The meeting itself will be held via Adobe Connect (connection details below), as it will include slides along with QA/discussion: *Date / Time:* July 23 from 15:00-16:00 UTC (See world clock for http://www.timeanddate.com/worldclock/fixedtime.html?msg=%22Services+API%22+Special+Topic+Meetingiso=20150723T15p1=1440ah=1your local http://www.timeanddate.com/worldclock/fixedtime.html?msg=%22Services+API%22+Special+Topic+Meetingiso=20150723T15p1=1440ah=1date/time http://www.timeanddate.com/worldclock/fixedtime.html?msg=%22Services+API%22+Special+Topic+Meetingiso=20150723T15p1=1440ah=1) *To join the meeting: * Go to https://educause.acms.com/duraspace (using any browser EXCEPT Google Chrome) Select 'Enter as a Guest' Enter your name and click 'Enter Room' Make sure your computer mic and speakers are turned on To participate we highly recommend running the Adobe Connect Test https://educause.acms.com/common/help/en/support/meeting_test.htm before the event. This test takes 30 seconds and will verify that your computer meets hardware and software requirements to use Adobe Connect and ensure a smooth start to the meeting. * Please note: if you get an error message on the last step Adobe Connect Add-in Test: Not Installed that is OK -- you do not need to install anything to connect to Adobe Connect. The first 3 steps to the test need to run successfully,
Re: [Dspace-devel] Feedback on migrating mailing lists off SourceForge
Hi Peter, Yes, once we've migrated, we'll bounce back any emails to old SF lists. We can customize the bounce message to tell them that the list has migrated, etc. We'll also hide all old SF lists (making them not visible to public by default), unsubscribe everyone and turn off any new subscriptions. So, we will be fully decommissioning SF lists once the new Google Groups lists are in place. (Again, I'll notify each list individually as this process gets started. So, until then all SF lists will be up and running obviously. I still haven't set an exact timeline yet, but I do hope to achieve this in August. I'll work towards more specific timelines soon.) - Tim On 8/4/2015 8:12 AM, Peter Dietz wrote: What happens to emails when someone a year from now sends an email to dspace-t...@lists.sourceforge.net mailto:dspace-t...@lists.sourceforge.net, since a decade of random documentation suggests so, they've historically been subscribed, and used to just work? I'm guessing they'll get a bounce, can there be a message in the bounce? This listserv has migrated to dspace-tech@gg . com Or is there some forwarding option? I tend to like Mark Wood's tonic of rip the bandaid off now, so, migrate to GG, and decommission SF. Peter Dietz Longsight www.longsight.com http://www.longsight.com pe...@longsight.com mailto:pe...@longsight.com p: 740-599-5005 x809 On Mon, Aug 3, 2015 at 2:06 PM, Tim Donohue tdono...@duraspace.org mailto:tdono...@duraspace.org wrote: Hi Graham, The Groups Migration API unfortunately only works for Google Apps Groups. It won't work for normal googlegroups.com http://googlegroups.com Groups (annoying, I agree). See it's prerequisites: https://developers.google.com/admin-sdk/groups-migration/v1/guides/prerequisites (There's also no way to migrate a Google Apps Group to a normal googlegroups.com http://googlegroups.com Group. So you cannot even use Migrations API as a pass through.) So, the only route to migrate messages into googlegroups.com http://googlegroups.com is to send them via SMTP. Here's an example: https://github.com/wojdyr/fityk/wiki/MigrationToGoogleGroups Unfortunately, that's the route that seems to no longer take note of the Date: field. This is the same route that Fedora used when they moved from SF to GG. But, back then (mid-2013), GG *did* respect the Date: field even when sending archives via SMTP. Though Fedora had a different problem back in 2013, where all messages migrated under the same user -- if you browse the Fedora archives (https://groups.google.com/forum/#!forum/fedora-tech https://groups.google.com/forum/#%21forum/fedora-tech) back to mid-2013 you'll find that all messages appear under a user named Fedo Raadmin (Fedora Admin). In my test migrations, all migrated messages retain the From: field (sender info) and all other fields *except* for Date:. Interestingly, the Date: field actually does get migrated properly, but it is no longer utilized in the browse interface for Google Groups (instead it seems to be using the date provided in the latest Received: header). That's the best solution I've managed to come up with thus far. If you know of anything else, I'd definitely be interested. But from my tests, sadly, I haven't been able to find any way around the Date: problem. - Tim On 8/3/2015 10:12 AM, Graham Triggs wrote: How are you planning to do the migration, as the Groups Migration API documentation suggests that it does take notice of the Date: field in the (RFC 822 formatted) messages? G On 3 August 2015 at 15:40, Tim Donohue tdono...@duraspace.org mailto:tdono...@duraspace.org wrote: Hi Developers / Committers, As of yet, I've heard little feedback on the proposed mailing list migration. So, I'm assuming no one else has major objections to any of these options. Currently, I'm leaning towards just migrating all mailing lists + archives into Google Groups, even though the dates of archived messages will appear incorrectly (this is option #1 described below). We can then add a note to the Google Group description letting everyone know that earlier messages all appear under the same date. I have not yet scheduled a start date for this process, but I'd hope to have it completed by the end of August. I plan to migrate less active lists first, and save our most active lists (dspace-tech especially) for last. Obviously though, I'll let each list know prior to migrating that list. Please do let me know though, if you have any thoughts (or prior Google Groups migration experience to share). Thanks, Tim On 7/29/2015
