[Opensim-dev] Suggestion for project organization.

[Nebadon Izumi]

Well i should have been more clear, i guess what i mean is that the goal all
along was to move modules out of core into forge eventually, even the ones
that are already in core. At least that was my understanding and the reason
forge was ultimately created.  So the core is not over bloated with module
work.

Neb

On Tue, Jun 30, 2009 at 7:09 AM, Michael Cortez <mcortez at gmail.com> wrote:

> Nebadon Izumi wrote:
> > I would only agree to this if all modules are hosted on the forge,
> Why would you even want it moved out of it's current SVN repository?
> Perhaps I wasn't clear, but my intent would be those modules that are
> currently in the main repository would stay in the main repository.
> They would simply be moved to a different folder to make it a bit more
> clear as to separation of core vs core module vs optional module, and to
> make it easier for 3rd part modules to be dropped in.
>
> >  I also dont see how we can start doing something like this during a
> > giant refactoring of the code,
> Mostly because {guesstimating} 7 out of 10 of the modules are not being
> touched by the refactoring of user, inventory and asset services -- this
> is why I specifically did not include Server/Service modules in the main
> body of my suggestion.  Right now the primary candidates for movement
> would be everything that's within the Optional modules directory.
> Followed by the Replaceable modules directory, then a close examination
> of those modules in the CoreModules directory that if not present do not
> prevent OpenSim from running (I believe Wind, for example, would fall
> under this.)
>
> Additionally, for those modules that anyone sees as truly not belonging
> in the core, but are currently too highly coupled to move -- then during
> a big refactoring stage IMHO is the ideal time to look at what it would
> take to decouple them.
>
> Of course, as I indicated to Melenie -- there is no deadline for
> something like this.  Step 1, put the necessary structure in place --
> patch prebuild and include the appropriate directories in the build --
> to support new third party modules.  Step 2, for those modules that are
> dead easy to include, people with the time on their hands can submit
> patches to create the needed prebuild files and move the code.
>
> --
> Michael Cortez
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>



-- 
Michael Emory Cerquoni - Nebadon Izumi @ http://osgrid.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20090630/1dc0308f/attachment-0001.html>