<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;">SDague has a good point. And it gets a bit more interesting when one considers the OSSearch module, which did become non-functional a few days ago and folks have been scrambling and struggling to get their regions back in operation.<br><br>It could be argued that bringing that active module, which is one small C# file into SVN might be to our advantage for the same reasons we are discussing here.<br><br>Charles<br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Sean Dague <sdague@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> opensim-dev@lists.berlios.de<br><b><span
style="font-weight: bold;">Sent:</span></b> Monday, February 9, 2009 11:30:59 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Opensim-dev] what are the core region modules? which are not?<br></font><br>
Dahlia Trimble wrote:<br>> When a module moves out of core and to forge, what process would be in place<br>> to make sure these modules remain compatible when possibly breaking changes<br>> are made to core? I use the IRC module in some of my regions and I wouldn't<br>> want to see it broken, and I like to stay close to head in all of my regions<br>> so I can be more aware of how development progresses. As such I would<br>> potentially vote -1 on taking IRC out of core until there is some way to<br>> maintain functionality as core evolves.<br><br>I'm personally all for moving thinks to an Optional space, but we have<br>to be honest with ourselves, moving a module to the forge means that<br>there is a better than 50% chance it's unusable in 2 weeks time. I<br>think for things we've considered "dead" that's fine, but I'd be<br>reluctant to push bits out that people do regularly use (like the irc<br>bridge). At least until
we have:<br><br>1. an easy way to build an out of core module build tree<br>2. network repository support for modules (ala what's in mono addins)<br>3. some type of versioning on module interfaces, so we can know if a<br>plugin thinks it can work with the current build<br><br>Otherwise we are more or less jetisoning a lot of features and reducing<br>the number of users that we can serve out of the box. The same logic<br>that would leave these modules in the tree is the same logic that keeps<br>all the extra stuff in bin/, to make it easy for the new user to get<br>started.<br><br>This shouldn't stop this current level of reorganization, which I think<br>is very useful. But is just a warning on next steps of removing things<br>from the tree.<br><br> -Sean<br><br>-- <br>Sean Dague / Neas Bade<br><a ymailto="mailto:sdague@gmail.com" href="mailto:sdague@gmail.com">sdague@gmail.com</a><br><a href="http://dague.net"
target="_blank">http://dague.net</a><br><br><br></div></div></div></body></html>