[Hibernate] Re: Becoming an official XDoclet module

[Joel Rosi-Schwartz]

Good, I am pleased that you support the proposition. It would be fine by me whoever the committer was; my goal is to have a viable module and I am willing to support that which ever way is deemed to be most appropriate.

- joel

Ara Abrahamian wrote:

Well, Gavin once requested commit access to xdoclet's cvs for the
hibernate module. In that period of time we've been discussing an
approach for handling new modules without the need to put them in
xdoclet's cvs. Now I'm +1 on hibernate in xdoclet's core and opening cvs
access for its maintainer. So if Gavin agrees too I can candidate you
(or maybe Gavin himself, whomever you find more appropriate for this
role).

Ara. 

  

-----Original Message-----
From: Joel Rosi-Schwartz [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 06, 2002 5:15 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Becoming an official XDoclet module

I know that this has come up before in the forum and dev list, but I
think it is worth re-evaluation. I just did an experiment of adding
    

the
  

hibernate module to the latest XDoclet cvs source. It took all of 5
minutes to integrate the module into the Xdoclet build. The results
    

were
  

as I expected; the build went smoothly and all of the documentation
    

was
  

produced without any pain. So I am wondering if maintaining the
Hibernate module seperately is really worth the extra pain and effort
that is required.

As I understand it the main consideration is not having a maintainer
    

for
  

the module that has commit priviledges on the XDoclet project. I agree
that handling changes via patches is awkward. So what does it take to
get accepted as a module and as a commiter to the Xdoclet project? If
    

I
  

had assurances that Gavin and Ara were both willing to give me a bit
    

of
  

support as needed, I would be willing to take on being the maintainer.

- joel