[Opensim-dev] breaking OpenSim.ini changes

[Melanie]

So you say I should spend hours on documentation which I already 
KNOW it will be obsolete within days?

That _is_ just what big corps do. 20% dev time, 80% doc time.

Melanie

Charles Krinke wrote:
> No, this is certainly not a big business development. It is an opensource development. 
> 
> And as such, our early adopters are our partners in this development.
> 
> This is a plea to you, Melanie, to write a few blog, wiki, or FAQ entries, or mentor someone to write them for you.
> 
> For an example, see Adam's blog where he has described his work on MRM along the way. And that is very good. It allows early adoptors to have a bit of an understanding of what has been created.
> 
> If you would merely consider writing down a few things once in a while, then I think this whole situation will get better for you.
> 
> Charles
> 
> 
> 
> 
> ________________________________
> From: Melanie <melanie at t-data.com>
> To: opensim-dev at lists.berlios.de
> Sent: Tuesday, May 19, 2009 9:05:11 AM
> Subject: Re: [Opensim-dev] breaking OpenSim.ini changes
> 
> Charles,
> 
> I develop out in the open, commit early and often. Most of these 
> past 100 commits were not meant to be used by anyone but myself and 
> Diva. It's a work in progress in a work area and documentation would 
> have been premature.
> 
> The asset system, since it now functions, can and will be 
> documented. But to demand big$$$business development and 
> documentation practices is not what opensim is about. Trunk is 
> supposed to be broken and usually is. Even if the brokenness only 
> consists in no one being able to use it. We can't document when it 
> is expected that everything will change again anyway.
> 
> This is a huge refactor. We had them before, where trunk was 
> unusable for months on end. This is another one of them. Please bear 
> with us.
> 
> Melanie
> 
> Charles Krinke wrote:
>> No, this is not talking about anything to death, Melanie. This is about writing down for others to read and understand at least *some* of what you are trying to accomplish.
>> 
>> This can be done via blogs, wiki paragraphs, FAQ, or other.
>> 
>> This feeling has been a long time coming, Melanie, and this is a plea for you to write down at least *some* of what you are doing so that there are clues for the early adopters to read and understand.
>> 
>> Charles
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Melanie <melanie at t-data.com>
>> To: opensim-dev at lists.berlios.de
>> Sent: Tuesday, May 19, 2009 8:47:55 AM
>> Subject: Re: [Opensim-dev] breaking OpenSim.ini changes
>> 
>> Well said. Trunk is supposed to be the developers' work area. If we 
>> can't use trunk as a work area anymore, maybe things should be in 
>> branches!
>> This is work in progress, and there will be breaking changes, and 
>> lots more. Documenting as we go it not an option, since we 
>> frequently have to go back and change things after the fact. Much 
>> easier to document when it's done than to keep remembering what is 
>> already on the wiki and where, and to update it whenever some small 
>> thing needs to be changed.
>> This is about code development, not about the general usability of 
>> trunk. Trunk is supposed to be broken, we have releases for people 
>> who expect things to JustWork(tm).
>> 
>> Now, let's get this work done and not talk it to death in committee.
>> 
>> Melanie
>> 
>> Nebadon Izumi wrote:
>>> I have to somewhat disagree here, not fully though, while i do agree perhaps
>>> there can be better ways of informing everyone, I do not agree with lumping
>>> all changes into 1 update, this is an Alpha level development project,
>>> whatever happened to Trunk is supposed to be broken.  My only suggestion to
>>> those who find difficulties at the time being midway through this refactor
>>> process, do not upgrade your regions beyond 9561 for the time being, and
>>> when the refactoring is complete we will sound the all clear whistle.  But
>>> for now expecting this to be perfect 1/2 through a giant refactoring is
>>> probably not something any of us should do.
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>> 
>> 
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev