All, I'm happy to present a new mini-project to the NH world: *ConfOrmContrib* ( http://code.google.com/p/conformcontrib/).
*What is it?* A collection of addins for ConfORM *Why?* Because I want to help ConfORM succeed. *Why?* Because it rocks *So, you're creating addins for a tool that hasn't even been released, that is itself an addin to another library?* Yes. *Why?* Because it's fun. *Why not just contribute patches to ConfORM?* I will keep doing that. So far, Fabio has been really open to my suggestions and has implemented most of my patches, after fixing them. I've also learned a lot from reading his code and especially his corrections. That will not change. *So...?* I'd like to be able to manage the cycle myself, without bothering Fabio, when changes to the core are not required. And I want to include as many patterns as possible, in particular those that help map legacy or DBA-defined schemas. And I want to use Mercurial in an OSS project. And did I mention it's fun? *Sounds interesting. How can I contribute?* You can send me your own addins and patches. Once we include at least one in the project, you can get commit access. My idea is to make this as open as possible. *What about upstream collaboration?* I keep a close eye on ConfORM progress. Whenever a piece of ConfOrmContrib is included in ConfORM, or becomes redundant with an equivalente feature, it will be deprecated and then removed to avoid duplication. Diego -- To unsubscribe, reply using "remove me" as the subject.
