New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language rework #350
Language rework #350
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've one doubt of my own, and one you woke up.
Filling in the form, and sending it to the sentry server, that's two separate steps.
Indeed I'm talking of the latest Python2, not the latest Python, and we do need spend some energy to move on to Python3, some time.
@mfrasca Nontheless, it is evident it has been sent, as the response is from someone who wouldnt otherwise be able to. |
Background information: |
@mfrasca Otherwise I can try to rewrite that, possibly feature it somewhere else? |
if you would be able to restate that, yes, please. |
actually, the point is more when the user double clicks on the
|
we currently have Python docstrings associated to these preferences (particular case), but we don't show them in the user interface, you only get to see them with |
oops, sorry, I made a mistake, by renaming before merging. will be back soon. |
@mfrasca "We are required" sounds reluctant. Saying why is preferable. |
well, it's two different things we are talking about:
Also, the point is that users provide information in two moments: about your text,
but all this text in a pop-up ... ? (but I still need to check if I can anonymize the workstation name) |
@mfrasca "In compliance with EU GDRP laws, access to all user-identifiable information must be explicitly given by you. Registered or not, you can opt into sending user feedback automatically. This can be used to identify you because the username you pick could possibly be the same, or similar to, the name of your computer/workstation. No attempt will however be made to reconstruct this association, and it is not stored" Questions, |
point (1) could be sufficient indeed, just hash the server_name before formatting the logging record. so if the user registers, they're identifiable. unregistered users would be anonymized. |
it stays (probabilistically) unique, we can't revert the hashing, and if the user does register, then it's the user explicitly telling us.
|
so you're suggesting we add a pop-up to the 'register' button, where extra confirmation is required, and what about this: "In compliance with EU GDRP laws, access to all user-identifiable information must be explicitly given by you. Registering comes down to the same as sending an email to ghini@anche.no and telling us who you are. We will reply to you, and we will occasionally send you news, possibly once or twice a year. Registered or not, you can opt into automatic bug reporting, which alerts us of error conditions in the software. Such automatic user feedback is not associated to you unless you register. We don't do user-profiling, we don't share any information with third parties, we only care for software quality." |
"Telling us who you are" in what capacity? Who is "us"? Don't muddle it in with a newslist, make that a different thing to explicitly click. If I want one thing, I get one thing, If i want two things, I get two. No one thing has to be accepted to get another. |
what about this then? currently I don't do anything close to user registration as done by companies, I just receive registrations, send an acknowledgement, and delete the registration, since the info is now in my email system. there isn't any database, except the one for automatic bug report, and that is anonymised now. |
It is turning into a unclear block of text, try: "Registered or not, you can opt into sending user feedback automatically. Send anonymous user feedback [ ] The following information will be collected In compliance with EU GDRP laws, access to all user-identifiable information must be explicitly given by you. Sign up for newsletter [ ] The following information will be collected It is sent to you unencrypted, so your interest in Ghini can be tracked to your e-mail account. Register as a user on Ghini to de-anonymize user feedback [ ] The following information will be collected, and not shared with anyone This is sent encrypted, and can be used to identify you because the username you pick could possibly be the same, or similar to, the name of your computer/workstation. No attempt will however be made to reconstruct this association, and it is not stored beyond ?" |
I guess the * is required. Which would make everything else optional, and I think that covers it. Mouseovers can explain things more clearly. I think maybe a divider here and then the tech contact and additional questions below it would be good, because now it looks like one registers contact email. Edit: One of the e-mails I got was:
Which suggest detailing the info sent and confirming it explicitly is important for newsletters. |
formatting the table, we are within Gtk+, and use glade files. you probably want to have a look at the sources for this dialog window (bauble/plugins/garden/institution.glade). doing it in columns as you suggest, one would need split in no less than 8 homogeneous columns, something like this: when we move to gtk3, then we will have a map widget, which will allow uses enter the coordinates by clicking on a dynamic map. I'm not so sure why tooltips are in the code (py) and not in the interface definition (glade). but we do have tooltips and that lets us keep labels short enough. no need for lengthy stuff like "contact info for developer communication". institution name is "compulsory" in the sense that if you don't fill this in, the dialog window will show up again next time you start ghini. there's a text explaining this. email address is currently next to registration button (and I want to keep it like that) because if the user gives an email address, then registration is possible, otherwise the button stays dormant. I don't really want to mention "ghini newsletter" because I'm afraid I can't make expectations come true. I write from time to time, when I have time, when I get news related to the garden in question, but there's no newsletter. the thing coming closest to a newsletter could the RSS feed, at https://ghini.github.io/feed.xml and yes, maybe we could advertise it here, or add the link to the help menu. registering on the public map, that we could indeed offer straight away in this dialog box. I'll think about it, thank you for all this constructive feedback! have you checked the letters? they are online, I'll make sure they are offered for translation. |
@mfrasca Translated. Could you make me an admin on Weblate? Then I can upload screenshots, add the plugins and so on. |
Hi @comradekingu , what is it that you can't do without being admin on weblate? screenshots, I already had someone mentioning them as an expected help, but I do not have the time for this too. what about plugins? and the so no? anyhow, you are admin now. |
@mfrasca There are some plugins you can turn on to have strings remain fuzzy when replaced and so on. I know it is possible to have a setup where "English" is just a branch that edits the upstream source files. I don't do anything drastic like that, but it is really nice to have permission for smaller things. |
I'm all ears, but it's night time here, just elaborate, explain, sounds interesting. |
Says Python 2 though, not 3. Is that intentional?