[oor-dev] Fwd: OOR

[Peter Yim]

(re-directing this conversation to all OOR stewards and developers)
... please pick up the conversation from here. The solicitation goes
to everyone who is willing. =ppy



Dear Michael & All,


Thanks, Michael.

Great! I will include the OOR.NET re-direction/proxy-service in our
to-do list in my final lag of the transition from our existing servers
at the datacenter, to our long-term historic archival servers. (...
Although, for the time being, this is not at the top of the priority
list.)

While I will retain control of the zone authority (dns services) on
the OOR.NET domain, I will be happy if anyone is willing take over the
hosting of the OOR.NET index page (something similar to what we
have/had at: http://oor.net ) and to run the apache mod_proxy
configuration which was how we implemented the OOR.NET
re-direction/proxy-service for the various repositories (of course,
whoever that is, can choose to implement it differently as well). That
way, future configuration changes will not have to go through me/CIM3.
... Anyone? (ShinyaYamda or I, at CIM3, can help with getting that
going.)


Best regards. =ppy
--



On Thu, Dec 17, 2015 at 8:34 AM, Michael Gruninger
<gruninger at mie.utoronto.ca> wrote:
> Hello Peter,
> yes, we should continue the OOR initiative, considering all of the work with
> OntoHub and COLORE.
>
> - michael


> On 15-12-17 11:29 AM, Peter Yim wrote:
>>
>> Dear Michael, Till, Ken,
>>
>> Further to my last msg (below):
>>>
>>> [ppy] yes, if people decide to continue on with the OOR initiative. I do
>>> hope you and Till might take the lead and revive that initiative. ...
>>> Thoughts?
>>
>> Thoughts!?
>>
>> Thanks & regards. =ppy


On Mon, Dec 7, 2015 at 7:31 PM, Peter Yim <peter.yim at cim3.com> wrote:
> Hi Michael,
>
>> what is the final outcome of the migration/changeover of OOR-related
>> issues?
>
> [ppy] because of other more critical issues, as well as my travels, I still
> have not had the chance to fix the "oor redirect" issue yet; sorry. However,
> I have updated the http://oor.net index site to link people to the right
> repository locations.
>
>> In particular, will you still be managing the aliasing of the oor.net
>> headers?
>
> [ppy] yes, if people decide to continue on with the OOR initiative. I do
> hope you and Till might take the lead and revive that initiative. ...
> Thoughts? [Michael, Till, Ken]
> (... But if there is not enough desire or momentum to continue that,  I'd
> probably just sell that domain name and recover some of the investment . It
> took me years, some luck, a lot of effort and thousands of dollars then,
> before I was able to buy that domain name. )
>
>> As a reminder, we need to change the header for COLORE ...
>
> [ppy] Thanks. Is the http://oor.net index site pointing people to the right
> location for you now?
>
> Best regards. =ppy
> --


> On Dec 8, 2015 9:07 AM, "Michael Gruninger" <gruninger at mie.utoronto.ca>
> wrote:
>>
>>
>> Hi Peter,
>> what is the final outcome of the migration/changeover of OOR-related
>> issues?
>> In particular, will you still be managing the aliasing of the oor.net
>> headers?
>>
>> As a reminder, we need to change the header for COLORE
>> from the old googlecode header
>> https://code.google.com/p/colore/source/browse/trunk/ontologies/
>> to the GitHub header:
>> https://github.com/gruninger/colore/blob/master/ontologies/
>>
>> thanks,
>> michael