<div dir="ltr">Tyler,<br><br>
Now to the technical nitty gritty, this involves filing a work request
ticket to our systems committee (SAC).[1] I don't mind helping here
and there, but can't see me leading this process this year. There are
some important issues to be worked out - shell access for site updates,
admin contacts, urls paths etc. Holler if you need help with the
ticket. Will Simon be the main contact from your end?<br><br>>>Yep i'm looking after it from our end<br><br>>>What should I be requesting in the trac ticket?<br><br>>>Should we continue this off list?<br>
<br>Cheers<br><br>Simon<br><br><div class="gmail_quote">2008/9/24 Tyler Mitchell (OSGeo) <span dir="ltr"><<a href="mailto:tmitchell@osgeo.org">tmitchell@osgeo.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 22-Sep-08, at 10:30 PM, Tim Bowden wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
the established pattern from 2006-2008,<br>
which means we should use:<br>
<a href="http://www.foss4g2007.org/" target="_blank">http://www.foss4g2007.org/</a><br>
</blockquote>
<br>
Wasn't there some discussion on the marketing list ages ago about this?<br>
The concern was future domains could be hijacked. Sorry, I can't point<br>
to the reference atm. If we always use <a href="http://foss4g.org/year" target="_blank">foss4g.org/year</a> then we escape<br>
this issue. <a href="http://foss4g.org/" target="_blank">foss4g.org/</a> would always point to the next/current conf as<br>
appropriate.<br>
</blockquote>
<br></div>
I don't recall the outcome of the earlier discussion, but it's safe to say that the only reason <a href="http://foss4g.org/20xx" target="_blank">foss4g.org/20xx</a> hasn't been used the past two years was because we didn't own <a href="http://foss4g.org" target="_blank">foss4g.org</a> until recently. I got this done a couple months ago, so we're all set now. It simply wasn't an option and 2007 wasn't going to wait for it to get ironed out first.<br>
<br>
By using a different domain each year, we are somewhat forking focus on FOSS4G as an ongoing event. Of course a few aliases never hurt, but I have a hard time believing that anyone ever specifically yearned for the year as part of the URL.<br>
<br>
Now to the technical nitty gritty, this involves filing a work request ticket to our systems committee (SAC).[1] I don't mind helping here and there, but can't see me leading this process this year. There are some important issues to be worked out - shell access for site updates, admin contacts, urls paths etc. Holler if you need help with the ticket. Will Simon be the main contact from your end?<br>
<br>
Tyler<br>
<br>
[1] <a href="http://trac.osgeo.org/osgeo" target="_blank">http://trac.osgeo.org/osgeo</a><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Foss4g2009 mailing list<br>
<a href="mailto:Foss4g2009@lists.osgeo.org" target="_blank">Foss4g2009@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/foss4g2009" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g2009</a><br>
</div></div></blockquote></div><br></div>