[Opensim-dev] Some thought about OpenSimulator Wiki future

[BlueWall]

On 08/05/2011 05:31 AM, Melanie wrote:
> It was decided to keep control of our own central repository and not
> delegate that to a code warehouse like github. It is a decision I
> stand by because I don't like or trust code warehouses.
> 
> Melanie
> 

+1

A couple of issues are:
"What if the company folds?", if you invest a lot of time and effort
into a project and the infrastructure you depend on disappears of the
face of the earth, how do you deal with that? How do you regroup the
community and re-establish a central point for information and distribution?

"What if another company buys the infrastructure, or the company just
decides to make changes in policy?", Example: Recently, many gmail users
added a Google+ profile to the accounts they have been using for years,
only to get banned by Google for using a pseudonym for a name. So, being
a user of an external service leaves one vulnerable to the future
policies of the service and anyone using the service risks .

Keeping 100% control of the infrastructure allows continuity for the
community for the life of the project.

> On 05/08/2011 08:27, Jeroen van Veen wrote:
>> How about moving opensim code to github and add something like Sphinx(but
>> then for c#) as documentation, where both documentation from source-code and
>> in wiki style can be mixed?
>> Advantage would be that versioning on the documentation is more flexible,
>> and most of the time the documentations software already provides a
>> professional looking template. Besides, you won't
>> need stuff like captcha's anymore. Just my two cents...
>>

The Allura project recently caught my eye. It is the system used by
Sourceforge (http://sourceforge.net/p/allura/wiki/Allura%20Wiki/) and
they have shared their code under the Apache License 2.0. If we were to
make some drastic departure from what we do now into some integrated
system, something like that make sense. We could retain our control of
the infrastructure without having to develop all of it ourselves. We
could also house all the 3rd party components under the same system. Not
advocating any changes at this point. But, just window shopping.


BlueWall