[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers] submission of LibCVS -- Access CVS through a libr
From: |
Alaska Subedi |
Subject: |
Re: [Savannah-hackers] submission of LibCVS -- Access CVS through a library. - savannah.gnu.org |
Date: |
Sun, 10 Oct 2004 18:58:18 -0400 |
User-agent: |
Mozilla Thunderbird 0.8 (X11/20040928) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexander Taler wrote:
|
|>>>>>>"Alaska" == Alaska Subedi <address@hidden> writes:
|
| Alaska> I'm evaluating the project you submitted for approval in
Savannah.
|
| Thanks, I was wondering if it had got lost, I guess you're busy there.
|
| Alaska> You mentioned that you are planning to separate the projects. I
| Alaska> assume that you are planning to host the documentation
project here
| Alaska> at Savannah and the implementation at cvshome.org. But, both the
| Alaska> projects will have same name and it might create confusion.
LibCVS
| Alaska> Documentation / LibCVS-doc would be a good name.
|
| My plan is to separate implementation into one project per
| language (currently Perl, ObjectiveC, C, and Python), to ease
| licensing, ownership, and project management issues. In
| addition, I want an umbrella documentation project (this one),
| which provides a common API for the various implementation
| projects, and serves as a focus point for communication. Ideally
| the umbrella project would have the name LibCVS, and the
| implementation projects would be called LibCVS-Perl,
| LibCVS-ObjectiveC, etc. However, I would be happy with
| LibCVS-API (is this ok for you?) or LibCVS-doc for this project.
|
We have approved your project (libCVS) for inclusion in
Savannah. You will receive an automated e-mail
containing detailed information about the approval.
Regards,
Alaska Subedi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBab6JY8vzQGvqIccRAvtmAJ0e+Vd6if7pFjCJeLqMDDRishJFSACfVE8D
9CVC9yziUIp0WQBkfPF6MAw=
=ECrq
-----END PGP SIGNATURE-----