Sorry, I'm not part of the Steering committee, but I'm very interested in
understanding the principles. I would prefer Open Source solutions like
Alfresco over Google Apps for Document Management System. Obviously with the
respective security requirements. If it's in an internal network or on
Amazon, I don't really see the difference, why does this concern you? or
does this really concern you? I mean if it's in the home of someone, that
will concern me, but if it's running on Amazon or some other Cloud provider,
what is the problem? Wouldn't you prefer to use an OSS solution than Google
Apps?



On Mon, Jan 17, 2011 at 14:37, Florian Effenberger <
[email protected]> wrote:

> Hello,
>
> I received a request to connect an external Alfresco site to one of our
> domain names. Apart from the concern that the workflow hadn't been defined
> (why now Alfresco?), I'm a bit sceptical to connecting external servers to
> our domain name, because they are associated with us and thus cause
> liability issues.
>
> My "policy" would be:
>
>        * hosted services (like the blog, or probably Google Apps) should
> can be connected at LibO or TDF domain names if they are from trustworthy
> sources
>
>        * self-hosted servers can only be connected if they are in our
> infrastructure management and fit our security requirements
>
> Thoughts on that?
>
> Florian
>
> --
> Florian Effenberger <[email protected]>
> Steering Committee and Founding Member of The Document Foundation
> Tel: +49 8341 99660880 | Mobile: +49 151 14424108
> Skype: floeff | Twitter/Identi.ca: @floeff
>
> --
> Unsubscribe instructions: E-mail to
> [email protected]<steering-discuss%[email protected]>
> List archive:
> http://listarchives.documentfoundation.org/www/steering-discuss/
> *** All posts to this list are publicly archived for eternity ***
>
>

-- 
Unsubscribe instructions: E-mail to [email protected]
List archive: http://listarchives.documentfoundation.org/www/steering-discuss/
*** All posts to this list are publicly archived for eternity ***

Reply via email to