I second the idea of considering registering <a href="http://ocaml.org">ocaml.org</a> with Google Apps. No amount of work we'll ever do will compete with the features they already have. I'm not concerned about lock-in since Google is not going anywhere anytime soon, and if it ever does there will be a million people figuring out how to export your data.<br>
<br><div class="gmail_quote">On Sun, Feb 10, 2013 at 1:41 PM, Sylvain Le Gall <span dir="ltr"><<a href="mailto:sylvain+ocaml@le-gall.net" target="_blank">sylvain+ocaml@le-gall.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2013/2/10 Anil Madhavapeddy <<a href="mailto:anil@recoil.org">anil@recoil.org</a>>:<br>
<div class="im">> Out of curiosity, why not do the opposite as I suggested?<br>
><br>
> I notice that all the proponents of staying on Google Groups use GMail,<br>
> and all the opponents don't. It seems reasonable to be subscribed to<br>
> Google Groups via the mirroring scheme that Google provides.<br>
><br>
> The search is quite straightforward. Use Google! "site:<a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a><br>
> opass" reveals the recent password-handling discussion, for example. This<br>
> seems like a problem we need to solve on all the lists, not just Core, so<br>
> I don't see why some should on Google Groups, and others on<br>
> <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a>.<br>
><br>
> If people are desperate for this functionality, I could always register<br>
> <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a> as a Google Apps service and host our lists via that.<br>
> However, I view Groups as something of a second-class service at Google,<br>
> and don't really trust it in the long term. Consider the Data Liberation<br>
> Front group at Google conspicuously skipping this service from their<br>
> "export your data" campaign.<br>
<br>
</div>I think that registering <a href="http://ocaml.org" target="_blank">ocaml.org</a> or <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a> as a Google<br>
Apps, can be a very effective way to build a pretty well managed<br>
architecture for websites, ML et al. Spend time on building server to<br>
test OCaml software, not managing spam and emails (I already did it<br>
for quite some time and I think it is not a very efficient way to<br>
spend my time).<br>
<br>
To be honest I don't see the point of merging the mailing list of<br>
Core, if the source code don't move as well to the very same server. I<br>
don't see why the argument that applies to ML would not apply to<br>
Source Code... If it is not broken, don't fix it.<br>
<br>
Concerning, the "long term" of Google Groups if anything should change<br>
you'll get a 6 months notice and will have plenty of time to move data<br>
to a new servers.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> -anil<br>
><br>
> On Sun, Feb 10, 2013 at 11:49:04AM -0500, Ashish Agarwal wrote:<br>
>> Personally, I prefer google groups over mailman too. The main reason being<br>
>> there is no easy way to search over mailman archives, which is a basic need.<br>
>><br>
>> If having our own archives is the only issue, maybe just subscribe<br>
>> <a href="mailto:core@lists.ocaml.org">core@lists.ocaml.org</a> to the current google group and disable direct posting<br>
>> to it. Thus, <a href="mailto:core@lists.ocaml.org">core@lists.ocaml.org</a> remains behind the scenes but we have all<br>
>> messages on servers under our control.<br>
>><br>
>> On Sun, Feb 10, 2013 at 5:47 AM, Anil Madhavapeddy <<a href="mailto:anil@recoil.org">anil@recoil.org</a>> wrote:<br>
>><br>
>> > We can set up a mirror to the <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a> mailing list as described<br>
>> > here;<br>
>> > <a href="https://support.google.com/groups/answer/46387?hl=en" target="_blank">https://support.google.com/groups/answer/46387?hl=en</a><br>
>> ><br>
>> > There are some unfortunate downsides to Google groups, but mainly down to<br>
>> > losing control of our archives (there's no facility to export them easily<br>
>> > to an mbox, for instance -- reconstructing it meant that the current<br>
>> > archives had to be scraped).<br>
>> ><br>
>> > Core's an important part of the future of OCaml, and we'd like to ensure<br>
>> > that we have a good central repository of the components that will make up<br>
>> > the OCaml Platform. Part of that is moving things to <a href="http://lists.ocaml.org" target="_blank">lists.ocaml.org</a>.<br>
>> > Spam is a concern, but we'll cross that hurdle when it becomes an actual<br>
>> > issue.<br>
>> ><br>
>> > -anil<br>
>> ><br>
>> > On 10 Feb 2013, at 10:42, Sylvain Le Gall <<a href="mailto:sylvain@le-gall.net">sylvain@le-gall.net</a>> wrote:<br>
>> ><br>
>> > > Hi,<br>
>> > ><br>
>> > > I am not sure about the real advantage of moving the list. The current<br>
>> > > one doesn't have obvious problem and using mailman for<br>
>> > > <a href="http://lists.ocamlcore.org" target="_blank">lists.ocamlcore.org</a> doesn't demonstrate me that mailman was better.<br>
>> > ><br>
>> > > Yaron, are you aware that using mailmam is probably more work day to<br>
>> > > day (not counting the amount of time you'll spend to do the migration<br>
>> > > itself). E.g, AFAIK spam filtering works pretty well on google groups,<br>
>> > > whereas it is almost absent in mailman... List archive is better<br>
>> > > presented on google group...<br>
>> > ><br>
>> > > I'll vote to stay on Googl Group, if my vote count.<br>
>> > ><br>
>> > > Regards<br>
>> > > Sylvain<br>
>> > ><br>
>> > > 2013/2/10 Sam <<a href="mailto:sdefabbiakane@gmail.com">sdefabbiakane@gmail.com</a>>:<br>
>> > >> Does this mean not using google groups anymore? If so, I'm rather sad<br>
>> > about<br>
>> > >> this. Having a decent web UI (which google groups does) lowers the<br>
>> > barrier<br>
>> > >> to participation by a lot. (And I, at least, much prefer it to getting<br>
>> > all<br>
>> > >> of the messages in my inbox.)<br>
>> > >><br>
>> > >> On Saturday, February 9, 2013 12:29:01 PM UTC+8, Yaron Minsky wrote:<br>
>> > >>><br>
>> > >>> Small correction: the new address would be <a href="mailto:co...@lists.ocaml.org">co...@lists.ocaml.org</a><br>
>> > >>><br>
>> > >>> y<br>
>> > >>><br>
>> > >>> On Fri, Feb 8, 2013 at 11:27 PM, Yaron Minsky <<a href="mailto:ymi...@janestreet.com">ymi...@janestreet.com</a>><br>
>> > >>> wrote:<br>
>> > >>>> Now that <a href="http://ocaml.org" target="_blank">ocaml.org</a> has an operational listserv, I'd like to migrate<br>
>> > >>>> this group over to a mailing list on that site, namely,<br>
>> > >>>> <a href="mailto:co...@ocaml.org">co...@ocaml.org</a>. My current plan is to migrate the list over in a<br>
>> > >>>> week. Does anyone object to simply auto-subscribing people who are<br>
>> > >>>> subscribed to this mailing list to the new list at <a href="http://ocaml.org" target="_blank">ocaml.org</a>?<br>
>> > >>>><br>
>> > >>>> y<br>
>> > >><br>
>> > >> --<br>
>> > >> You received this message because you are subscribed to the Google<br>
>> > Groups<br>
>> > >> "ocaml-core" group.<br>
>> > >> To unsubscribe from this group and stop receiving emails from it, send<br>
>> > an<br>
>> > >> email to <a href="mailto:ocaml-core%2Bunsubscribe@googlegroups.com">ocaml-core+unsubscribe@googlegroups.com</a>.<br>
>> > >> For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
>> > >><br>
>> > >><br>
>> > ><br>
>> > > --<br>
>> > > You received this message because you are subscribed to the Google<br>
>> > Groups "ocaml-core" group.<br>
>> > > To unsubscribe from this group and stop receiving emails from it, send<br>
>> > an email to <a href="mailto:ocaml-core%2Bunsubscribe@googlegroups.com">ocaml-core+unsubscribe@googlegroups.com</a>.<br>
>> > > For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
>> > ><br>
>> > ><br>
>> ><br>
>> > --<br>
>> > You received this message because you are subscribed to the Google Groups<br>
>> > "ocaml-core" group.<br>
>> > To unsubscribe from this group and stop receiving emails from it, send an<br>
>> > email to <a href="mailto:ocaml-core%2Bunsubscribe@googlegroups.com">ocaml-core+unsubscribe@googlegroups.com</a>.<br>
>> > For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
>> ><br>
>> ><br>
>> ><br>
>><br>
>> --<br>
>> You received this message because you are subscribed to the Google Groups "ocaml-core" group.<br>
>> To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:ocaml-core%2Bunsubscribe@googlegroups.com">ocaml-core+unsubscribe@googlegroups.com</a>.<br>
>> For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
>><br>
>><br>
><br>
> --<br>
> Anil Madhavapeddy <a href="http://anil.recoil.org" target="_blank">http://anil.recoil.org</a><br>
> _______________________________________________<br>
> Infrastructure mailing list<br>
> <a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
> <a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
</div></div></blockquote></div><br>