<div>+1 from me as well.... I would, however, feel a little remorse at the idea of losing the <a href="http://www.openlayers.org">www.openlayers.org</a> :-/</div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 1/14/08, <b class="gmail_sendername">Eric Lemoine</b> <<a href="mailto:eric.c2c@gmail.com">eric.c2c@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">+1. I think it's good to start moving the OL infrastructure to OSGeo.<br>For the URLs I'd favor the regular OSGeo URLs.
<br><br>2008/1/13, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>>:<br>> +1<br>> This is a positive long term move.<br>> It should ease the integration between projects they are sharing the
<br>> same hosting resources and share the workload.<br>><br>> Paul Spencer wrote:<br>> > Chris,<br>> ><br>> > I think this is a good move to make for the project, and for OSGeo as<br>> > well.
<br>> ><br>> > I don't have any particular feeling about the structure of URLs and<br>> > would be fine with either structure.<br>> ><br>> > While I'm not involved personally in SAC, I would like to help and I
<br>> > can ask Shawn Barnes to help out with any migration support that you<br>> > need.<br>> ><br>> > Cheers<br>> ><br>> > Paul<br>> ><br>> > On 13-Jan-08, at 7:03 AM, Christopher Schmidt wrote:
<br>> ><br>> ><br>> >> OpenLayers is currently (graciously) hosted by MetaCarta. This has<br>> >> worked out quite well so far, but using MetaCarta hosting has meant<br>> >> we've had to 'roll our own' system for authentication -- and as many
<br>> >> people know, this particular system is rather hacky: an email to the<br>> >> PSC<br>> >> list to generate a new username, which requires manual intervention.<br>> >><br>> >> Part of the reason that I've never improved upon this system is that
<br>> >> I've always felt that it would be better to invest in moving to OSGeo<br>> >> infrastructure. For a while, this was difficult, but recently, OSGeo<br>> >> has<br>> >> found some solutiosn which make this technically possible.
<br>> >><br>> >> I'd like to suggest that we move to OSGeo infrastructure for hosting<br>> >> Trac and the Wiki as soon as possible. I'm less sure on the website<br>> >> and<br>
> >> mailing lists.<br>> >><br>> >> Benefits of moving svn + wiki:<br>> >> * Users can create their own userid -- or use their existing osgeo<br>> >> userid -- to login to either.
<br>> >> * Users creating tickets in trac will automatically get email<br>> >> notification<br>> >> on updates of their tickets.<br>> >> * It will be possible to register oneself as a "CC" on a bug without
<br>> >> exposing an email address to the public web.<br>> >> * Shared administrative resources with OSGeo -- which means that it's<br>> >> not just me who can update the server, but instead the set of people
<br>> >> who maintain the OSGeo servers<br>> >> * Shared OSGeo backup infrastructure. Currently, we're backing up<br>> >> OpenLayers internally to MetaCarta, and exporting data to OSGeo:
<br>> >> moving to OSGeo infrastructure allows for the bcakups to be<br>> >> maintained by the foundation.<br>> >><br>> >> The strongest one to me is that users will be able to create their own
<br>> >> accounts via an automated process - no humans involved. I think this<br>> >> is<br>> >> very important.<br>> >><br>> >> I have a couple of questions which I don't personally have an answer
<br>> >> to<br>> >> yet:<br>> >><br>> >> Currently, all OSGeo svn, trac, etc. live under URLs like<br>> >> <a href="http://trac.osgeo.org/gdal/">http://trac.osgeo.org/gdal/</a>
, <a href="http://svn.osgeo.org/gdal/">http://svn.osgeo.org/gdal/</a> . I do not<br>> >> know<br>> >> if it is possible to configure <a href="http://svn.openlayers.org">svn.openlayers.org</a> to point directly to
<br>> >> the OSGeo server, or if it would be preferred for administrative<br>> >> purposes to have it at <a href="http://svn.osgeo.org/openlayers/">svn.osgeo.org/openlayers/</a> . Obviously, even if<br>> >> it's trivial in an administrative way, it would be more in line with
<br>> >> the<br>> >> rest of the foundation-hosted projects to have the URL be<br>> >> <a href="http://svn.osgeo.org/openlayers/">svn.osgeo.org/openlayers/</a> . Assuming that there is sufficiently good
<br>> >> infrastructure setup to allow for users to migrate from one to the<br>> >> other, would it make sense to make the primary OpenLayers SVN URL be<br>> >> the<br>> >> <a href="http://osgeo.org/">
osgeo.org/</a> form?<br>> >><br>> >> Same question applies to trac.<br>> >><br>> >> I view these aspects of the project as 'internal' -- where SVN lives<br>> >> doesn't matter much, so long as it's correctly linked everywhere --
<br>> >> and<br>> >> would be in support of moving into the <a href="http://osgeo.org">osgeo.org</a> namespace for svn and<br>> >> trac, with appropriate redirects.<br>> >><br>> >> A similar question applies to mailing lists. Currently, these lists
<br>> >> are<br>> >> <a href="mailto:dev@openlayers.org">dev@openlayers.org</a> and <a href="mailto:users@openlayers.org">users@openlayers.org</a>. Moving to OSGeo<br>> >> infrastructure would probably mean moving these to
<br>> >> <a href="mailto:openlayers-users@lists.osgeo.org">openlayers-users@lists.osgeo.org</a> and <a href="mailto:openlayers-dev@lists.osgeo.org">openlayers-dev@lists.osgeo.org</a><br>> >> (and<br>> >> openlayers-trac and openlayers-commits.) Would it make sense to move
<br>> >> these, with proper redirects to <a href="http://lists.osgeo.org">lists.osgeo.org</a> for both the email<br>> >> addresses and the archives?<br>> >><br>> >> Speaking as (essentially) the sole maintainer of the machine that
<br>> >> <a href="http://openlayers.org">openlayers.org</a> is hosted on, I'd like to move off whatever we can to<br>> >> OSGeo infrastructure. As you can see here, one important piece of the<br>> >> infrastructure piece is left aside, and that's the sandboxes, website,
<br>> >> etc. I think the important aspect of those changes is related to the<br>> >> regular 'svn up' and rebuilding that happens. In the past, we've<br>> >> discovered that doing these in post-commit hooks is bad, because it
<br>> >> takes too long to commit (which would be een more true now with the<br>> >> NaturalDocs stuff). However, I think that we can devise a technical<br>> >> solution -- using a post-commit hook to write a revision number, and a
<br>> >> cronjob to check whether changes have been made and rebuild if so. I<br>> >> think this would allow us to move to OSGeo infrastructure for the<br>> >> website as well, though there would obviously need to be some
<br>> >> technical<br>> >> discussions for what we could do as far as doc regeneration, etc.<br>> >> goes.<br>> >><br>> >> This is not a motion yet: its a request for comments. I'm interested
<br>> >> in<br>> >> moving for a number of reasons, both technical and social. Although<br>> >> there are other people at MetaCarta with 'the keys' to the servers,<br>> >> I'd
<br>> >> like to move that out to the foundation -- and I see that we get a<br>> >> fair<br>> >> amount of benefit from that. I'm hopeful that others agree, and we can<br>> >> discuss the best way to move forward with the goal of making the
<br>> >> process<br>> >> smooth.<br>> >><br>> >> Feedback, comments, suggestions, concerns are welcome.<br>> >><br>> >> (Note that at the moment, I'm not looking for technical advice on the
<br>> >> way to set up redirects or anything like that: we can address that<br>> >> after<br>> >> we address whether, and how, we *want* to move first.)<br>> >><br>> >> Regards,
<br>> >> --<br>> >> Christopher Schmidt<br>> >> MetaCarta<br>> >> _______________________________________________<br>> >> Dev mailing list<br>> >> <a href="mailto:Dev@openlayers.org">
Dev@openlayers.org</a><br>> >> <a href="http://openlayers.org/mailman/listinfo/dev">http://openlayers.org/mailman/listinfo/dev</a><br>> >><br>> ><br>> > +-----------------------------------------------------------------+
<br>> > |Paul Spencer <a href="mailto:pspencer@dmsolutions.ca">pspencer@dmsolutions.ca</a> |<br>> > +-----------------------------------------------------------------+<br>> > |Chief Technology Officer |
<br>> > |DM Solutions Group Inc <a href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a> |<br>> > +-----------------------------------------------------------------+<br>> ><br>> >
<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > Dev mailing list<br>> > <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>> > <a href="http://openlayers.org/mailman/listinfo/dev">
http://openlayers.org/mailman/listinfo/dev</a><br>> ><br>> ><br>><br>><br>> --<br>> Cameron Shorter<br>> Geospatial Systems Architect<br>> Tel: +61 (0)2 8570 5050<br>> Mob: +61 (0)419 142 254
<br>><br>> Think Globally, Fix Locally<br>> Commercial Support for Geospatial Open Source Solutions<br>> <a href="http://www.lisasoft.com/LISAsoft/SupportedProducts.html">http://www.lisasoft.com/LISAsoft/SupportedProducts.html
</a><br>><br>> _______________________________________________<br>> Dev mailing list<br>> <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>> <a href="http://openlayers.org/mailman/listinfo/dev">
http://openlayers.org/mailman/listinfo/dev</a><br>><br>_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br><a href="http://openlayers.org/mailman/listinfo/dev">
http://openlayers.org/mailman/listinfo/dev</a><br></blockquote></div><br>