On Dec 12, 2007 12:25 PM, Karl Chu <karl@gottabekd.ca> wrote:
> So are we in agreement then, that we should separate the "contrib" projects
> into their own modules, perhaps with their own version number?

Yes but there is more too it than mass. Even within the NHibernate
core, things are overwhelming. I'm not very confident poking around in
the core. There's a lot of namespaces and knowing each's purpose (for
example, what's an Engine?) and how they relate is unclear.

Thinking longterm, if we could refactor the namespaces so that they
had clear purpose and clear relationships, I think this would make the
project easier to use and easier to develop. I know this is in direct
conflict with the desires to maintain a similar codebase to the Java
version and to not break a public API, so this is not a trivial
decision to make. But I think the longevity of the project depends on
its maintainability, because that factor affects the ability to add
features, fix bugs, tune performance, document, etc.

... the opinion of someone who has only been involved for a few months
and doesn't pay attention to the Java version, for what it's worth.

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Nhibernate-development mailing list
Nhibernate-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nhibernate-development