Looks great. Thanks! Dan
On Tue, May 22, 2018 at 1:29 AM, Maxim Solodovnik
wrote:
> Done
>
> can be checked on demo-next
>
> On Mon, May 21, 2018 at 9:34 PM, Daniel Ascher <
> aplusad...@aplustutoring.com> wrote:
>
>> Yes. Thanks!
>>
>> On Sun, May 20, 2018 at 11:44 PM,
Done
can be checked on demo-next
On Mon, May 21, 2018 at 9:34 PM, Daniel Ascher wrote:
> Yes. Thanks!
>
> On Sun, May 20, 2018 at 11:44 PM, Maxim Solodovnik
> wrote:
>
>> Hello Daniel,
>>
>> Would it be OK to put link to the bottom of the
Yes. Thanks!
On Sun, May 20, 2018 at 11:44 PM, Maxim Solodovnik
wrote:
> Hello Daniel,
>
> Would it be OK to put link to the bottom of the "Settings" tab contents?
>
> On Sat, May 19, 2018 at 8:20 PM, Daniel Ascher <
> aplusad...@aplustutoring.com> wrote:
>
>> Yes, but if
Hello Daniel,
Would it be OK to put link to the bottom of the "Settings" tab contents?
On Sat, May 19, 2018 at 8:20 PM, Daniel Ascher wrote:
> Yes, but if a user is logged in to an OM instance, how does he or she
> locate the privacy policy? Maybe a link should
Yes, but if a user is logged in to an OM instance, how does he or she
locate the privacy policy? Maybe a link should be placed on this page?
On Fri, May 18, 2018 at 8:28 PM, Maxim Solodovnik
wrote:
> yes,
> Everything will look like on demo-next unless
yes,
Everything will look like on demo-next unless customized/localized :)
On Fri, May 18, 2018 at 9:09 PM, Daniel Ascher wrote:
> So glad! Thanks for letting me know. Where will the privacy policy appear
> with an individual instance of OM?
>
> Dan
>
> On Fri,
So glad! Thanks for letting me know. Where will the privacy policy appear
with an individual instance of OM?
Dan
On Fri, May 18, 2018 at 5:22 AM, Maxim Solodovnik
wrote:
> Here how it look like: https://om.alteametasoft.com:8443/next/privacy
>
> On Fri, May 18, 2018 at
Here how it look like: https://om.alteametasoft.com:8443/next/privacy
On Fri, May 18, 2018 at 2:20 PM, Maxim Solodovnik
wrote:
> Thanks a lot for work on privacy statement
> I'm going to take final text
> Apply some styles
> And update demo-next so everyone can perform
Thanks a lot for work on privacy statement
I'm going to take final text
Apply some styles
And update demo-next so everyone can perform final review
Will notify this thread
On Fri, May 18, 2018 at 12:44 AM, Daniel Ascher <
aplusad...@aplustutoring.com> wrote:
> Okay Maxim. So there is not change
Okay Maxim. So there is not change needed to the privacy policy document
itself, correct? You are going to make those changes/additions on the OM
site.
I will delete all of the crossed out text from the google doc. If anyone
else has another other suggestions about the privacy policy, please add
I'm afraid there might be misunderstanding here
I was talking about OM site (not OM admin area)
https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%204.0.x/site/openmeetings-server/index.html
Hi Maxim (and everyone). I think that's a good idea. Can you just add a
menu for Configuration->Privacy Policy?
Also, if the language in the google doc is now correct I will delete all of
the crossed out text. Let me know if anyone has any other comments,
suggestions, or objections.
Thanks to
16. Mai 2018 um 13:01 Uhr
Von: "Maxim Solodovnik" <solomax...@gmail.com>
An: "Openmeetings user-list" <user@openmeetings.apache.org>
Betreff: Re: new privacy regulations on the 25th May 2018
Hello All,
I would like to add short instruction to the site on how
lodovnik" <solomax...@gmail.com>
An: "Openmeetings user-list" <user@openmeetings.apache.org>
Betreff: Re: new privacy regulations on the 25th May 2018
Hello All,
I would like to add short instruction to the site on how to customize privacy
policy
Where should it go:
Hello All,
I would like to add short instruction to the site on how to customize
privacy policy
Where should it go:
1) Configuration->User Interface
2) Configuration->Customization
3) somewhere else
?
On Wed, May 16, 2018 at 4:26 PM, Peter Dähn wrote:
> Hi there,
>
> thanks
Hi there,
thanks for your work so far. I had a look too, and my little comment is
already included.
Not a native speaker, not a lawyer but looks good for me.
Greetings Peter
Am 16.05.2018 um 05:25 schrieb Maxim Solodovnik:
Done,
sorry for delay
was too tired yesterday night :))
On Tue,
Done,
sorry for delay
was too tired yesterday night :))
On Tue, May 15, 2018 at 11:43 PM, Daniel Ascher <
aplusad...@aplustutoring.com> wrote:
> Please take one more look. There are two remaining comments.
>
> Thanks. Dan
>
> On Tue, May 15, 2018 at 11:09 AM, Maxim Solodovnik
Please take one more look. There are two remaining comments.
Thanks. Dan
On Tue, May 15, 2018 at 11:09 AM, Maxim Solodovnik
wrote:
> Done
>
> hopefully someone else can also check this :)
>
> On Tue, May 15, 2018 at 10:03 PM, Daniel Ascher <
>
Done
hopefully someone else can also check this :)
On Tue, May 15, 2018 at 10:03 PM, Daniel Ascher <
aplusad...@aplustutoring.com> wrote:
> Please check latest changes. Dan
>
> On Tue, May 15, 2018, 9:25 AM Maxim Solodovnik
> wrote:
>
>> Done :)
>> Please let me know if
Please check latest changes. Dan
On Tue, May 15, 2018, 9:25 AM Maxim Solodovnik wrote:
> Done :)
> Please let me know if you have additional questions
>
> On Tue, May 15, 2018 at 6:28 AM, Daniel Ascher <
> aplusad...@aplustutoring.com> wrote:
>
>> Hi Maxim.
>>
>> I
Done :)
Please let me know if you have additional questions
On Tue, May 15, 2018 at 6:28 AM, Daniel Ascher wrote:
> Hi Maxim.
>
> I reviewed all of your changes and made some additional changes. So please
> take a look. There are a few questions I asked, which
Hi Maxim.
I reviewed all of your changes and made some additional changes. So please
take a look. There are a few questions I asked, which you'll see. I haven't
yet removed most of the crossed out words (the strikethrough things) in
case others want to review the document before we delete those.
Thanks Maxim. I will take a look. :)
Dan
On Mon, May 14, 2018 at 12:25 AM, Maxim Solodovnik
wrote:
> I did review of the whole document
> Would appreciate your comments/additions :)))
>
> On Mon, May 14, 2018 at 9:32 AM, Maxim Solodovnik
> wrote:
>
I did review of the whole document
Would appreciate your comments/additions :)))
On Mon, May 14, 2018 at 9:32 AM, Maxim Solodovnik
wrote:
> Hello Daniel,
>
> Thanks a lot for handling this I'll take a look ASAP
> Actually this privacy statement will be used for every OM
Hello Daniel,
Thanks a lot for handling this I'll take a look ASAP
Actually this privacy statement will be used for every OM installation
We do not collect or process user information
we are using it only for OM purposes: notifications, UI etc.
Privacy policy later on can be edited by end user:
Thanks Daniel,
Maybe I'll come up with some prototype ...
Will share it here
We run out of time :(
On Fri, May 11, 2018 at 9:17 PM, Daniel Ascher
wrote:
> Hi everyone. I will be away today and tomorrow but I will plan to look at
> this upon my return.
>
> Thanks! Dan
Hi everyone. I will be away today and tomorrow but I will plan to look at
this upon my return.
Thanks! Dan
On Thu, May 10, 2018 at 9:19 PM, Maxim Solodovnik
wrote:
> Thanks again Daniel,
>
> I believe all external links should be removed
>
> What is different:
> We are
>
Thanks again Daniel,
I believe all external links should be removed
What is different:
We are
1) not tracking user activity
2) not adding custom images to check if email was delivered
3) using email to invite user or notify about event
4) language/country is used to display OM in user native
No problem Maxim. I can do that. The only thing I need to know is what will
be different for OpenMeetings. For example there are many links in the
document that would need to point to something.
I will take a look and then let you know which questions I have. Also, if
there is someone who is an
Thanks a lot Daniel,
Maybe you can create basic "Privacy Statement" based on this [1] one
(public domain)
And we can polish it in mailing list?
I definitely wrong person for this :((
[1] https://help.github.com/articles/github-privacy-statement/
On Thu, May 10, 2018 at 11:44 PM, Daniel Ascher
Sure! Happy to help with this. :)
Please send me the text once it's ready and I'll review it and discuss
issues with the group.
Thanks! Dan
On Thu, May 10, 2018 at 12:36 PM, Maxim Solodovnik
wrote:
> Hello Peter, All,
>
> Just have added link to privacy policy to
Hello Peter, All,
Just have added link to privacy policy to register dialog (available at
upcoming build, will update demo ASAP)
Would appreciate is *Native English Speaker* can help with English privacy
statement
I'll try to create one based on this [1], but I would strongly prefer to
get help
Hi Maxim,
I've tested the current state. Seems to be done so far. One little thing
I hope... When I choose a purged user I have the possibility (button) to
restore that account. Db will be set deleted false... Doesn't make
sense, I think.
Purge themselves is a way to disagree (I didn't see
As per current implementation users can purge themselves
This can't be undone
Is this "a way to disagree" ?
On Thu, Apr 26, 2018 at 2:35 PM, Peter Dähn wrote:
> Hi Maxim,
>
> I will test it during the day
>
> Yes you are right... This need to be done during
Hi Maxim,
I will test it during the day
Yes you are right... This need to be done during registration. checkbox
and link to the privacy policy that need to be placed somewhere.
Agreement for data processing need to be double opt-in. Most likely via
E-Mail. I think an e-mail template
All your comments should be addressed in latest build available
Could you please re-check?
This question was not answered .
Additional question:
"Registration-Dialog need to have a button/step to agree the data
processing. And to this belongs a button to disagree."
I guess user should be
These errors seems to be caused by code changes after testing :(
I'll double-check it
IP addresses are cleaned up by periodic job.
Will also add clean by purge
Thanks for checking!
WBR, Maxim
(from mobile, sorry for the typos)
On Wed, Apr 25, 2018, 17:33 Peter Dähn wrote:
> Hi
Hi Maxim,
first test...
purge confirmation dialogue should be different from delete...
maybe "Do you really want to purge this item? This can't be undone!"
Something like that...
After purge I got an 500 internal error page...
openmeetings.log:
/ERROR 04-25 12:05:13.708
sure :)
just checking :))
On Wed, Apr 25, 2018 at 2:00 PM, Peter Dähn wrote:
> Good morning Maxim,
>
> I was alone in the office these days... unfortunatly there were no time
> left... But I red right in the moment the RUNNING.txt... all a bit
> different... ;-)
>
> I'm going to
Good morning Maxim,
I was alone in the office these days... unfortunatly there were no time
left... But I red right in the moment the RUNNING.txt... all a bit
different... ;-)
I'm going to text it now... give me a bit time... ;-)
Am 25.04.2018 um 04:41 schrieb Maxim Solodovnik:
Good
Good morning Peter :)
were you able to take a look at this issue?
On Mon, Apr 23, 2018 at 2:37 PM, Peter Dähn wrote:
> Hi Maxim,
>
> I will have a look right now.
>
> Greetings Peter
>
>
> Am 21.04.2018 um 18:17 schrieb Maxim Solodovnik:
>>
>> Hello Peter,
>>
>> this is partially
"Allow data processing" seems to be not applicable in such case
Users can purge themselves from the system
WBR, Maxim
(from mobile, sorry for the typos)
On Sun, Apr 22, 2018, 11:47 Morrell Aberdeen
wrote:
> How would it work for configurations in which the user
How would it work for configurations in which the user is not allowed
to self-register and user accounts are created by an Administrator?
On Sat, Apr 21, 2018 at 2:05 PM, Maxim Solodovnik wrote:
> Additional question:
> "Registration-Dialog need to have a button/step to
Additional question:
"Registration-Dialog need to have a button/step to agree the data
processing. And to this belongs a button to disagree."
I guess user should be able to register only if he/she agree to data processing
Registration should be impossible if user disagree
So I guess having
Hello Peter,
this is partially implemented
Could you please test current implementation using latest nightly build?
And maybe you can provide sample "personal data agreement" text?
On Wed, Apr 11, 2018 at 6:38 PM, Peter Dähn wrote:
> I try... ;-)
>
>
> Am 11.04.2018 um 13:11
I try... ;-)
Am 11.04.2018 um 13:11 schrieb Maxim Solodovnik:
Will write it as a requirement, will see what can be done here
Thanks a lot for the quick answers!
On Wed, Apr 11, 2018 at 5:34 PM, Peter Dähn > wrote:
ip-address is now a private date...
Will write it as a requirement, will see what can be done here
Thanks a lot for the quick answers!
On Wed, Apr 11, 2018 at 5:34 PM, Peter Dähn wrote:
> ip-address is now a private date... it have to be at least anonymised
> after 7 (maybe 14 days)... ipv4 addresses delete last 8
ip-address is now a private date... it have to be at least anonymised
after 7 (maybe 14 days)... ipv4 addresses delete last 8 recommended 16
bit (192.168.123.0 or 192.168.0.0) and ipv6 preserve first 48 -8 or
better 16 Bit (2a00:1234:56:: or 2a00:1234::) Maybe this could be done
automated
According to logs: you can set up history size in this
https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/webapp/WEB-INF/classes/logback-config.xml#L36
file
On Wed, Apr 11, 2018 at 2:31 PM, Maxim Solodovnik
wrote:
> According "Hash algorithm"
Hi Maxim,
I think this list is complete and you are right, this is a lot of stuff.
The option that you suggest sound much more feasible. From my point of
few this should be enough.
Hash algorithm need to be state of the art. IP-address in ConferenceLog
need to be cleaned.
I think this is
Hello Peter,
Here is the high level list of what need to done to "hard delete" user from
the system:
1. delete user
2. delete all user contacts (also users, so we might have recursion here)
3. delete user from all groups
4. delete user from room moderators
5. delete all
Hi Maxim,
hard delete as only option would be the easiest way (for the admin). One
doesn't need to remind "hard delete" at a given time... I think it need
to be implemented anyway. I thought just the ones that doesn't need to
take care about these regulation could keep things as they are
I'm afraid there will be no option to "final delete one record"
It will be: perform total clean-up and hard delete all soft deleted records
Or better to perform: hard delete as the only option?
On Fri, Apr 6, 2018 at 2:44 PM, Peter Dähn wrote:
> Hi Maxim,
>
> "soft" and "final
Hi Maxim,
"soft" and "final delete" should be enough I think...
It just need to be "findable" and described for new admins that provide
the service in the EU...
jira in a second...
Greetings Peter
Am 05.04.2018 um 17:47 schrieb Maxim Solodovnik:
Hello Peter,
This sounds like lots of new
Peter,
could you please file JIRA regarding this? (blocker)
So we can track the progress
On Thu, Apr 5, 2018 at 10:47 PM, Maxim Solodovnik wrote:
> Hello Peter,
>
> This sounds like lots of new testing :(
> Will try to find time and include it in 4.0.3/4.0.4
>
> (have very
Hello Peter,
This sounds like lots of new testing :(
Will try to find time and include it in 4.0.3/4.0.4
(have very limited time right now :( )
Will appreciated any help with testing
Would it be OK to perform "final delete" in clean-up widget? i.e.
delete will be "soft delete", then in if will
Hey there,
new privacy regulations will take place on the 25th May 2018 in Europe.
You could find informations about it by searching for General Data
Protection Regulation (EU) 2016/679.
To use openmeetings after the 25th of May (in Europe) there need to be a
few changes. We use
57 matches
Mail list logo