Re: RFS: DPMT: python-hl7 0.2.0
Hi John,
On Wed, Jul 13, 2011 at 09:12:46AM -0500, John Paulett wrote:
> I am the upstream maintainer of python-hl7 [1] and have packaged it
> for Debian. I was hoping that a DD may be able to review the package
> with me and potentially sponsor the package [2]. I have worked with
> the DPMT before to maintain the jsonpickle package.
I had a look at your package (because it is relevant for Debian Med) and
as I told you before if you just have packages in python-modules team it
is perfectly fine to stay in this Vcs if you prefer to do so.
> The package is lintian clean and I have built it in a sid pbuilder environment.
I'm just using lintian -I -i which results in a
I: python-hl7: description-synopsis-might-not-be-phrased-properly
which can be fixed with a simple
$ svn diff
Index: control
===================================================================
--- control (revision 17834)
+++ control (working copy)
@@ -13,7 +13,7 @@
Architecture: all
Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
Provides: ${python:Provides}
-Description: Python library for parsing HL7 messages.
+Description: Python library for parsing HL7 messages
HL7 is a communication protocol and message format for health care data.
It is the de-facto standard for transmitting data between clinical
information systems and between clinical devices. The version 2.x series,
... I just noticed that I have no commit permissions in python-modules.
If some kind soul of this team would ask alioth admins to grant commit
permissions for DDs this could simplify things for inter-team
cooperation.
> Since this is a healthcare-related library, it could potentially fit
> under the Debian Med team, but due to the fact that the library is
> just a simple Python module and my existing familiarity with the the
> DPMT policies, I thought I would ask here first.
As I said: Whatever you prefer is fine.
Besides the nitpicking with the '.' above I wonder how the issue you
mentioned on the Debian Med list about licenses of XML files might be.
I neither have found such files in the code nor did I have seen
references in debian/copyright. If this is a non-issue I would go
on sponsering the package.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: