In a message dated 11/5/2008 5:56:56 PM Eastern Standard Time, 
[EMAIL PROTECTED] writes:


> As part of a class project, I and my colleagues Diana Weaver and Kevin
> Ford plan to create a digital archive to record the history of
> MARC/Perl (i.e., MARC.pm and MARC::Record).
> 
> This archive would supplement existing resources such as CPAN,
> SourceForge, and the Perl4Lib mailing list archives by gathering
> together versions of the software and correspondence and accounts of
> its development.  The archive is meant to be a resource for community
> members and researchers to explore the communication, relationships,
> and group dynamics present in a serious open source project.
> 
> The archive will be available for all to use and explore.  As this is
> a class project, I cannot guarantee that it will be online
> indefinitely, but will make every effort to keep it available for use
> and harvesting for at least six months after its creation.
> 
> If anybody is willing to contribute material for this archive, please
> contact me.  We're particularly interested in individual accounts of
> the history of MARC.pm by users and contributors, copies of email
> correspondence about its development (assuming that all parties to the
> email agree that it may be contributed), and old versions of the
> modules that are no longer available on CPAN or SourceForge.
> 
> Thanks,
> 
> Galen Charlton
> [EMAIL PROTECTED]
> 

I have no problems contributing what I have around. I may have to do a little 
digging since some of the stuff is on an older laptop I no longer use 
regularly. But I did archive all the correspondence including examples and 
requests 
for assistance.

Have you considered what format you wiant to use for presenting the 
information?

-bill


**************
AOL Search: Your one stop for directions, recipes and all 
other Holiday needs. Search Now. 
(http://pr.atwola.com/promoclk/100000075x1212792382x1200798498/aol?redir=http://searchblog.aol.com/2008/11/04/happy-holidays
-from-aol-search/?ncid=emlcntussear00000001)

Reply via email to