Hi Lars,
What I mean by the IP being collected, is it "might" be collected (unless
you are careful) by your reverse proxy or upstream providers. Even though
whatever protocol you might come up with might not collect it, it would
require you to purposefully NOT collect it though unintentional means,
Agree with Dan that a submit button on the about page (which previewed the
information that would be sent) is better than ET calling home.
Though we need to remain clear about the usage distinction of sharing with
developers and feeding a more public repo. Need to think a bit more.
On 28 June 2
Perhaps it could be modeled after the Drupal Update Stats module. This module
generates simple stats that can be seen here.
https://drupal.org/project/usage/drupal you can read more about it here.
https://drupal.org/node/329620
I'd also support a slightly more detailed optional submission as w
Okay thanks for feedback.
To clarify, for the "calling home" part we will only collect the DHIS 2
version (no IP, no Java version etc). In other words we will only register
that there exists a DHIS version out there with a given version. It will
not be possible to track it back to the IP.
Then, w
I agree with Jason on all counts so won't repeat them.
A mandatory "ET call home" feature would not and should not be generally
acceptable. Besides which its not too clear how, or more pertinently,
when, this exchange will happen. On first boot? Every boot. Periodically?
Anyway I don't like i
Hi Lars,
I think it is important to get it right from the beginning. following the
lead of other big open source projects. It is critical to remember that
many of the organisations using DHIS2 are governments, and there could be
some possible sensitivies about the DHIS core team collecting any sor
Hi,
thanks for the good questions and comments.
This information will be stored in some central system. The system will be
managed by the DHIS core team. That system will be made open source so that
anyone who feels like it could investigate it.
> Who would have access to the "sensitive" data l
Hi Lars and Jason,
Good idea, and good questions about security.
One way to approach IP address security is to not record them anywhere (and
make sure the central server to which the data is sent does not keep any log of
them.) If the central server doesn't know the IP addresses, they can't be
Hi Lars,
Sounds interesting. Wish I would have been there for the discussion. Sounds
like it might be possible, assuming the process and data is transparent,
and allow for an option to "opt-out" of collection of such data.
Having said that, I think we should be exceedingly careful. I assume that
Sounds interesting. Was there an idea of what the data would be used for?
On Jun 27, 2013, at 10:59 PM, Lars Helge Øverland wrote:
> Hi there,
>
> during the Uganda workshop last month we had an interesting suggestion from
> one of the participants.
>
> The idea is to let DHIS submit anonymou
10 matches
Mail list logo
