Hi,
I have been thinking of trying to get Djigzo to function as an
unofficial third implementation of the new NHIN Direct standard (which is
how most doctors in the United States will do direct messaging starting next
year)
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I do
not really have that much time to work on this, and if I do contribute I
want to verify that it is not in vain.
Are there examples of patches to Djigzo from the community that
have been accepted into the Djigzo tree? I need to determine, quickly if
this is a "collaborative" project or merely an "openly developed" project.
Thanks,
-FT
···
--
Fred Trotter
http://www.fredtrotter.com
This subject is relevant to my interests and uses for the product also.
I think there is enormous potential for this product in the healthcare
arena.
Travis Masonis
CCNA, CCDA, MCSE, CEH, Security+
Director, IT Infrastructure
Noyes Memorial Hospital
···
-----Original Message-----
From: users-bounces(a)lists.djigzo.com
[mailto:users-bounces(a)lists.djigzo.com] On Behalf Of fred trotter
Sent: Friday, July 30, 2010 11:27 AM
To: users(a)lists.djigzo.com
Subject: Regarding NHIN Direct
Hi,
I have been thinking of trying to get Djigzo to function as an
unofficial third implementation of the new NHIN Direct standard (which
is
how most doctors in the United States will do direct messaging starting
next
year)
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I
do
not really have that much time to work on this, and if I do contribute I
want to verify that it is not in vain.
Are there examples of patches to Djigzo from the community
that
have been accepted into the Djigzo tree? I need to determine, quickly if
this is a "collaborative" project or merely an "openly developed"
project.
Thanks,
-FT
--
Fred Trotter
http://www.fredtrotter.com
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users
Hi,
I have been thinking of trying to get Djigzo to function as an
unofficial third implementation of the new NHIN Direct standard (which is
how most doctors in the United States will do direct messaging starting next
year)
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I do
not really have that much time to work on this, and if I do contribute I
want to verify that it is not in vain.
I think that would depend on the patches, but if the patches and changes
and addition add to the usability of the product, I can't think of a
reason why they wouldn't be happily accepted and incorporated in the
product. If needed, we can work with you to make these changes.
Christine
···
On 07/30/2010 05:26 PM, fred trotter wrote:
Are there examples of patches to Djigzo from the community that
have been accepted into the Djigzo tree? I need to determine, quickly if
this is a "collaborative" project or merely an "openly developed" project.
Thanks,
-FT
--
dagdag is just a two-character rotation of byebye.
BTW, where is the code repository for the project? Would prefer to see
evidence of outside patches previously being accepted in the tree itself.
I am sorry to be so paranoid... but I have been burned before.
-FT
···
On Fri, Jul 30, 2010 at 10:50 AM, Christine <christine(a)christine.nl> wrote:
On 07/30/2010 05:26 PM, fred trotter wrote:
> Hi,
> I have been thinking of trying to get Djigzo to function as an
> unofficial third implementation of the new NHIN Direct standard (which
is
> how most doctors in the United States will do direct messaging starting
next
> year)
>
> However, I would want to get a confirmation that the Djigzo
> project will accept patches I make to the codebase for this purpose. I do
> not really have that much time to work on this, and if I do contribute I
> want to verify that it is not in vain.
>
I think that would depend on the patches, but if the patches and changes
and addition add to the usability of the product, I can't think of a
reason why they wouldn't be happily accepted and incorporated in the
product. If needed, we can work with you to make these changes.
Christine
> Are there examples of patches to Djigzo from the community
that
> have been accepted into the Djigzo tree? I need to determine, quickly if
> this is a "collaborative" project or merely an "openly developed"
project.
>
> Thanks,
> -FT
>
>
--
dagdag is just a two-character rotation of byebye.
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users
--
Fred Trotter
http://www.fredtrotter.com
George,
Interesting post on djingo forum.
Is it something we should be prepared for?
http://geekdoctor.blogspot.com/2010/03/introducing-nhin-direct.html
Hi,
I have been thinking of trying to get Djigzo to function as an
unofficial third implementation of the new NHIN Direct standard (which is
how most doctors in the United States will do direct messaging starting next
year)
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I do
not really have that much time to work on this, and if I do contribute I
want to verify that it is not in vain.
Are there examples of patches to Djigzo from the community that
have been accepted into the Djigzo tree? I need to determine, quickly if
this is a "collaborative" project or merely an "openly developed" project.
Thanks,
-FT
···
--
Fred Trotter
http://www.fredtrotter.com
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users
Hi Fred,
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I
do not really have that much time to work on this, and if I do
contribute I want to verify that it is not in vain.
We definitely accept patches to the codebase. Whether or not a patch or
new functionality will be accepted depends on a number of factors
a. The quality of the patch/feature (is it documented and tested)
b. Is the new feature beneficial to more users than just the submitter.
c. Can the patch/new feature be used license wise (the code should be
usable under an approved open source license and do not contain patented
code).
Most of the Djigzo functionality is pluggable. When a new feature is
only usable by a selective user group, it might be that the new feature
will not be enabled by default but should then be enabled by the end user.
There were currently only two minor patches submitted (one for the
virtual appliance running on systems with more than 2GB enabled and one
for running under MAC OS X). I think this is because most of Djigzo's
users are system admins and not developers. This however does not imply
that we do not accept any patches or new features. The majority of time
building and testing Djigzo has been spend on other things than writing
code (my estimate would be 40% writing code and 60%
testing/documenting). Testing the project in real life by Djigzo's users
and giving feedback on the documentation is as valuable as contributing
actual code.
The reason why subversion (version control) is not yet externally
accessible, is that security wise we are kind of paranoid and access to
subversion was until now not yet required nor requested. All source code
has however been available from day one from our website. If you require
access to subversion let me know and I will think of ways to make it
accessible yet keep it as secure as possible.
Kind regards,
Martijn Brinkers
fred trotter wrote:
···
Hi,
I have been thinking of trying to get Djigzo to function as an
unofficial third implementation of the new NHIN Direct standard (which is
how most doctors in the United States will do direct messaging starting next
year)
However, I would want to get a confirmation that the Djigzo
project will accept patches I make to the codebase for this purpose. I do
not really have that much time to work on this, and if I do contribute I
want to verify that it is not in vain.
Are there examples of patches to Djigzo from the community that
have been accepted into the Djigzo tree? I need to determine, quickly if
this is a "collaborative" project or merely an "openly developed" project.
Thanks,
-FT
--
Djigzo open source email encryption
Martijin,
All of this sounds great. It seems to me that this might be a
time for you to migrate to distributed development version control. I think
it -is- a security risk to give some random stranger like me subversion
access, but I think if you were using git or mercurial, then you would have
a much easier time dealing with folks like me, who merely want to have
a cohesive way to collaborate on your codebase.
I would recommend launchpad.net as a system that we in the Open
source healthcare industry have been gravitating to. Is something like that
a possibility? VCS access is not as important to me as merely having a
formal way to interface my bugs and feature requests and patches against
your running VCS. So even merely moving to sourceforge etc would help me...
Regards,
-FT
···
On Fri, Jul 30, 2010 at 5:34 PM, Martijn Brinkers <martijn(a)djigzo.com>wrote:
Hi Fred,
> However, I would want to get a confirmation that the Djigzo
> project will accept patches I make to the codebase for this purpose. I
> do not really have that much time to work on this, and if I do
> contribute I want to verify that it is not in vain.
We definitely accept patches to the codebase. Whether or not a patch or
new functionality will be accepted depends on a number of factors
a. The quality of the patch/feature (is it documented and tested)
b. Is the new feature beneficial to more users than just the submitter.
c. Can the patch/new feature be used license wise (the code should be
usable under an approved open source license and do not contain patented
code).
Most of the Djigzo functionality is pluggable. When a new feature is
only usable by a selective user group, it might be that the new feature
will not be enabled by default but should then be enabled by the end user.
There were currently only two minor patches submitted (one for the
virtual appliance running on systems with more than 2GB enabled and one
for running under MAC OS X). I think this is because most of Djigzo's
users are system admins and not developers. This however does not imply
that we do not accept any patches or new features. The majority of time
building and testing Djigzo has been spend on other things than writing
code (my estimate would be 40% writing code and 60%
testing/documenting). Testing the project in real life by Djigzo's users
and giving feedback on the documentation is as valuable as contributing
actual code.
The reason why subversion (version control) is not yet externally
accessible, is that security wise we are kind of paranoid and access to
subversion was until now not yet required nor requested. All source code
has however been available from day one from our website. If you require
access to subversion let me know and I will think of ways to make it
accessible yet keep it as secure as possible.
Kind regards,
Martijn Brinkers
fred trotter wrote:
> Hi,
> I have been thinking of trying to get Djigzo to function as an
> unofficial third implementation of the new NHIN Direct standard (which
is
> how most doctors in the United States will do direct messaging starting
next
> year)
>
> However, I would want to get a confirmation that the Djigzo
> project will accept patches I make to the codebase for this purpose. I do
> not really have that much time to work on this, and if I do contribute I
> want to verify that it is not in vain.
>
> Are there examples of patches to Djigzo from the community that
> have been accepted into the Djigzo tree? I need to determine, quickly if
> this is a "collaborative" project or merely an "openly developed"
project.
>
> Thanks,
> -FT
>
--
Djigzo open source email encryption
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users
--
Fred Trotter
http://www.fredtrotter.com
fred trotter wrote:
All of this sounds great. It seems to me that this might be
a time for you to migrate to distributed development version control. I
think it -is- a security risk to give some random stranger like me
subversion access, but I think if you were using git or mercurial, then
you would have a much easier time dealing with folks like me, who merely
want to have a cohesive way to collaborate on your codebase.
I have only briefly looked at GIT so I should spend some time to
investigate. I like the distributed approach. The only problem with it
currently is that there is no mature Eclipse (Java IDE) plugin yet (they
are working on one). I will investigate how hard it is to bridge between
SVN and GIT. It seems that git-svn can interface between SVN and GIT.
I would recommend launchpad.net <http://launchpad.net> as a
system that we in the Open source healthcare industry have been
gravitating to. Is something like that a possibility? VCS access is not
as important to me as merely having a formal way to interface my bugs
and feature requests and patches against your running VCS. So even
merely moving to sourceforge etc would help me...
I have been looking at Jira for bug/feature tracking
(Jira | Issue & Project Tracking Software | Atlassian). The main reason why I prefer
Jira is that it's using Java which I more comfortable with than python.
Jira is free for open source projects, well known and widely used.
Would Jira provide the features you require for bug/feature tracking?
Kind regards,
Martijn
···
--
Djigzo open source email encryption