Opened 7 years ago

Closed 5 years ago

#3966 closed enhancement (notsugar)

Submit birthday on registration on SN server

Reported by: alsroot Owned by: alsroot
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: sugar-client Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

Dextrose-3 supports /desktop/sugar/user/birth_timestamp gconf setting.

Change History (12)

comment:1 follow-ups: Changed 7 years ago by alsroot

  • Resolution set to fixed
  • Status changed from new to closed

http://git.sugarlabs.org/server/client/commit/ec95f6fbfc8ec6ddfa30be42342332471a672d30

Submitting birthday will happen only on registration on server. So, to collect this data, [re]move db/user directory from server, users will register (with the same GUIDs that are sugar uids) with submitting new data.

new sugar-client is packages as sugar-client-1.2-28.1.i386 on
http://download.sugarlabs.org/packages/Server:/Factory/Fedora-14/

comment:2 in reply to: ↑ 1 Changed 7 years ago by alsroot

Replying to alsroot:

http://git.sugarlabs.org/server/client/commit/ec95f6fbfc8ec6ddfa30be42342332471a672d30

Submitting birthday will happen only on registration on server. So, to collect this data, [re]move db/user directory from server,

and restart it

comment:4 follow-ups: Changed 7 years ago by walter

Sorry to jump into this late, but can I ask why you are interested in storing birthdate? I would recommend that we store personal information about our users population (minors) only when absolutely necessary. This is a worrisome trend.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 7 years ago by alsroot

Replying to walter:

Sorry to jump into this late, but can I ask why you are interested in storing birthdate? I would recommend that we store personal information about our users population (minors) only when absolutely necessary. This is a worrisome trend.

From one side, it is feature required for downstream sugar used in .au, https://sugardextrose.org/issues/2360.

From another side, it is an optional feature of Sugar Network, similar to setting personal info in profiles on web sites.

comment:7 in reply to: ↑ 5 ; follow-up: Changed 7 years ago by walter

Replying to alsroot:

Replying to walter:

Sorry to jump into this late, but can I ask why you are interested in storing birthdate? I would recommend that we store personal information about our users population (minors) only when absolutely necessary. This is a worrisome trend.

From one side, it is feature required for downstream sugar used in .au, https://sugardextrose.org/issues/2360.

I am not familiar with the privacy laws in OZ, so I cannot comment on this.

From another side, it is an optional feature of Sugar Network, similar to setting personal info in profiles on web sites.

As long as there is a mechanism for leaving these data out, I thin we should be in the clear as regards US law. We absolutely want to err of the side of not any capturing personal data about our users. thx

comment:8 in reply to: ↑ 4 Changed 7 years ago by quidam

Replying to walter:

Sorry to jump into this late, but can I ask why you are interested in storing birthdate? I would recommend that we store personal information about our users population (minors) only when absolutely necessary. This is a worrisome trend.

AFAIK they are not connecting the information to the particular user. They need to know the age (storing the approximate birthdate is just an implementation detail) to make the stats useful, as several age groups are using the machines (including grown-ups).

comment:9 in reply to: ↑ 6 Changed 7 years ago by quidam

Replying to alsroot:

The issue that was fixed is uploading user data on stats uploading. So, after updating server side, there is no need in special treatment to get recent user metadata (including birthday).

All packages need to be updated from http://download.sugarlabs.org/packages/Server:/Factory/Fedora-14.

Many thanks, applying this now.

comment:10 in reply to: ↑ 7 Changed 7 years ago by alsroot

Replying to walter:

As long as there is a mechanism for leaving these data out, I thin we should be in the clear as regards US law. We absolutely want to err of the side of not any capturing personal data about our users. thx

Sugar Network itself is just a storage on a server with providing an API to get/set data. What will be or not sent to server is fully prerogative of particular client side. In other words, guaranties about not sharing personal data might be declared only for client side applications.

In this particular case, sugar-client is especially designed to be a deployment tool and this current version is being used only by .au and, thus, is being implemented only from this deployment perspective.

comment:11 Changed 7 years ago by quidam

  • Resolution fixed deleted
  • Status changed from closed to reopened

With last updates the system is failing to collect any stats. Please check https://sugardextrose.org/issues/2360#note-19 and 20.

comment:12 Changed 5 years ago by godiard

  • Resolution set to notsugar
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.