Re: [Jmri-developers] Migration of this list to Groups.io - proposal

[Matthew H. <mat...@gm...>]

Dear all,

This list on SourceForge has now been placed in read-only mode - to
continue to participate in JMRI developer discussion, please see the new
list at https://jmri-developers.groups.io/g/jmri

Best regards,

Matt H

On Thu, 6 Dec 2018 at 11:47, Matthew Harris <mat...@gm...>
wrote:

> Dear all,
>
> Given that there has been a flurry of activity on this list, we will wait
> for that to calm down before placing this list in read-only mode.
>
> As a reminder, it is necessary for anyone wishing to follow/participate in
> JMRI developer discussion to manually subscribe to the new list via web at
> https://jmri-developers.groups.io/g/jmri/join or emailing
> jmr...@jm...
>
> This is due to SF no longer allowing us to access or export the subscriber
> list.
>
> Current plan is to switch THIS list (on SourceForge) to read-only mode
> some time around 20h00 UTC today (6th December).
>
> After that time, conversations should take place on the groups.io list.
>
> The list archive will remain here, but we will organise an import of the
> archive to groups.io in the meantime.
>
> Best regards,
>
> Matt H
>
>
> On Fri, 30 Nov 2018 at 23:44, Bob Jacobsen via Jmri-developers <
> jmr...@li...> wrote:
>
>> First, I’d like to thank Matt for thinking all this through.
>>
>> This sounds like a plan that we should implement sooner rather than
>> later.
>>
>> Bob
>>
>> > On Nov 29, 2018, at 1:32 AM, Matthew Harris <
>> mat...@gm...> wrote:
>> >
>> > Dear all,
>> >
>> > As some of you may recall, over the last few years, we've been
>> experiencing several issues with various aspects of the SourceForge
>> infrastructure which has resulted in us migrating the majority of our
>> development tool set away to other alternatives.
>> >
>> > Today, the last parts of the JMRI development tool set that still rely
>> on SourceForge are a few of our mailing lists, mainly this one and the
>> 'jmri-announce' list.
>> >
>> > Several months ago, due to reliability issues noticed with the Yahoo!
>> platform, we migrated the 'jmriusers' group from Yahoo! Groups to Groups.io.
>> >
>> > Around that same time, we also created a 'shadow' developers list on
>> Groups.io, which was configured to receive copies of all messages posted
>> here so as to already start building up an archive of recent activity.
>> >
>> > Our experience thus far with 'jmriusers' on Groups.io has been positive
>> so the time has now come to switch over fully to Groups.io for these last
>> remaining lists.
>> >
>> > Unfortunately, due to restrictions of the SourceForge platform, it's
>> not possible for us to retrieve a list of subscribers to the various JMRI
>> mailing lists, meaning that it will be necessary to manually subscribe
>> yourself to the new list on Groups.io.
>> >
>> > As a result, there will need to be a cut over period during which
>> conversations might end up happening on both lists (this has already
>> happened in a few cases) so we need to define a suitable timeline for the
>> cut over.
>> >
>> > My proposal for the cut over is as follows:
>> >
>> > - Encourage new sign-ups to the new jmri-developers list via web at
>> https://jmri-developers.groups.io/g/jmri or by email via
>> jmr...@jm...
>> > - Place this list into read-only mode after a grace period (say 1 week)
>> to minimise risk of conversations in both places
>> > - (Optionally) transfer archive of messages from this list
>> >
>> > Thanks to Bob, we've got a pretty much complete archive of the messages
>> from this list in a suitable format so it shouldn't be too much effort to
>> get this imported into Groups.io. Given that we've already been building up
>> an archive, we might end up with some duplicated messages and some out of
>> order, but I'd suggest that's more of an inconvenience than anything else.
>> >
>> > The new list is configured as a main list (
>> jm...@jm...) with sub-groups for specific purposes,
>> such as commit messages and infrastructure monitoring, to which you are
>> able to optionally subscribe.
>> >
>> > Please let me know any comments/remarks regarding this proposal so we
>> can determine the best route forward.
>> >
>> > Best regards,
>> >
>> > Matt H
>> > _______________________________________________
>> > Jmri-developers mailing list
>> > Jmr...@li...
>> > https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>
>> --
>> Bob Jacobsen
>> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>>
>>
>>
>> _______________________________________________
>> Jmri-developers mailing list
>> Jmr...@li...
>> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>
>