[MPICH] who own(s) the copy right of MPICH2 ?

chong tan chong_guan_tan at yahoo.com
Tue Jun 19 19:42:08 CDT 2007


thanks rajeev, I got the list.  Actually, the lawyer for the company did.  I am trying
to shorten the list by removing thing I do not use, or built into our package.

thanks
tan

----- Original Message ----
From: Rajeev Thakur <thakur at mcs.anl.gov>
To: chong tan <chong_guan_tan at yahoo.com>; mpich-discuss at mcs.anl.gov
Sent: Tuesday, June 19, 2007 5:12:50 PM
Subject: RE: [MPICH] who own(s) the copy right of MPICH2 ?


src/mpe2/src/slog2sdk/src/images contains gif files from Javasoft that are used for some icons in Jumpshot. Hence the license from SUN in that directory.
src/mpi/debugger/mpi_interface.h contains some code from Jim Cownie (when he was at Etnus) for the debugger interface. That file has the copyright from Etnus/Dolphin.
You can find out these things by doing a grep -r in the top-level directory.
 
Rajeev




From: owner-mpich-discuss at mcs.anl.gov [mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of chong tan
Sent: Tuesday, June 19, 2007 5:44 PM
To: mpich-discuss at mcs.anl.gov
Subject: Re: [MPICH] who own(s) the copy right of MPICH2 ?


thanks bill.  
 
Anyone knows what SUN micro has to do with MPICH2 ?  From the licensing's 'obligation' doc, it looks like SUN provided an artwork to MPICH or MPICH2.
 
how about Dolphin Interconnect and Etnus ?    Etnus must be for interface to total view ?
 
tan
 


 
----- Original Message ----
From: William Gropp <gropp at mcs.anl.gov>
To: chong tan <chong_guan_tan at yahoo.com>
Cc: mpich-discuss at mcs.anl.gov
Sent: Tuesday, June 19, 2007 2:56:45 PM
Subject: Re: [MPICH] who own(s) the copy right of MPICH2 ?

MPICH1 contains the C++ binding originally provided by the University of Notre Dame.  MPICH2 does not use any of that code (it uses its own system to implement the C++ bindings) and does not use any LAM/MPI code. 


Bill


On Jun 18, 2007, at 4:11 PM, chong tan wrote:


I am in the final stage of productizing a code using MPICH for communication.
My Legal department gives me 6 pages of message/acknowledgement/obligation-to-use
message to be displayed when my code runs, plus 10 pages or more ack/leg messages
to be included/reproduced with the help/doc/training. 
 
I look at the list of copyrights owners, they are
- University of Chicago
- Argonne National Lab
- University Notre Dame
- The Ohio State University
- The trustee of Indianna University
- Clemson Univerity
- University of Mississipi
- University of Chicago, Ohio Supercomputer Center
- Massachusetts Institute of Technology
- SUN micro System
 
there is one particular message, for Trustees of Indiana University, Norte Dame University and Ohio State University, I think is on LAM/MPI:
 
"This product includes software developed at the Ohio Supercomputer Center at The Ohio State University, the University of Notre Dame and the Pervasive Technology Labs at Indiana University with original ideas contributed from Cornell University. For technical information contact Andrew Lumsdaine at the Pervasive Technology Labs at Indiana University.  For administrative and license questions contact the Advanced Research and Technology Institute at 351 West 10th St., Indianapolis, Indiana 46202, phone 317-274-5905, fax 317-274-5902."
 
 
I just want to ask those with the inside connection: Who should I cite as the copyright owner of MPICH2 in my software ?   I don't build MPICH with LAM, should I still ack the copyright owners of  LAM/MPI ?
 
thanks
 
tan
 



Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.







Shape Yahoo! in your own image. Join our Network Research Panel today!


      ____________________________________________________________________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20070619/05d46406/attachment.htm>


More information about the mpich-discuss mailing list