[Bioperl-l] Packaging Bio::Ext::HMM for CPAN, was Re: Problems with Bioperl-ext package on WinVista?

[Chris Fields]

On Aug 18, 2009, at 10:49 AM, Robert Buels wrote:

> Chris Fields wrote:
>> I think we should go ahead and remove Bio::Tools::HMM from 1.6.1,  
>> and I could attempt to push the initial Bio-Ext-HMM release after  
>> core 1.6.1 is out.  After that, I could then add Yee Man as PAUSE  
>> co-maintainer for those modules (which means Yee Man needs to sign  
>> up for a PAUSE account).  Any objections to that?
>
>
> Sounds like a good plan to me, if Yee Man agreed with it.  He would  
> be the primary CPAN maintainer of the package.  Maybe he should  
> actually be the first uploader too?  Then, it would show up under  
> his PAUSE account at the outset, and he would get better attribution  
> and visibility.
>
> Rob

At the moment BIOPERLML is the primary maintainer.  It's an 'umbrella'  
account for the bioperl group; a few others exist for stuff like DBI,  
Catalyst, etc I think.  Anyone who's designated a co-maintainer can  
release code onto CPAN.  Several of us can assign new co-maintainer  
status for modules, so the code doesn't get locked up if someone  
decides to abandon it.  We simply designate another co-maintainer if  
someone decides to take it over.

In fact, that's half the reason I would like to get the ext code out  
there again; either designate it as abandonware or set it up so that  
it can be reimplemented by someone with the tuits (maybe using biolib,  
for instance).

We have recently moved Bio::Graphics over to LDS as the primary,  
though, so this is all a point up for debate.

chris