GDPR

ladis

Hello, what about EPESI and GDPR? Any resolution? Nobody need it?

markos151

We all ( EU) need it, but EPESI seems to be dying

ladis

Hey guys,

thanks for good news! Unfortunately your replies are a bit off topic. It's nice to hear about Jasper and Semantic UI, but as markos151 wrote, all EU companies needs EPESI compatible with GDPR. So is this issue in progress?

We definitely stay conected, cause EPESI is great project and we're glad to still alive!

Ladis

praski

EPESI looks dying, but we are not.
I'm interesting in EPESI GDPR and maybe we should do it ourselves. But I'm not specialist for it and looking for people who want the same and may create a not commercial team for it.
First we should define what is require by GDPR (maybe not the same in every UE country)
Second which points are missing in EPESI.
Third - Can we do it without Telaxus?

Are there any willig for it?

Best regards
Praski

ghristov

Actually EPESI is not dying but developing further in the background. The team is restructuring and recruitment is being done. The system will soon be updated with new great Premium modules while meanwhile core system will migrate to new technologies still keeping backward compatibility.

I am saying it as an independent developer and associated with Telaxus LLC only as GitHub FOSS contributor to Epesi. Today Janusz Tylek - Telaxus CEO - offered me a seat in the Technical Advisory Board in recognition for my contribution to the project and for expanding it with Reporting and eXport modules.
The reporting module can be used to quickly deploy overview reports in Epesi based on data in the system with tables, charts, etc.
eXport module enables Epesi to print RB records (view/list) and reports to PDF on WYSWYG templates designed with JasperStudio. It also enables export of these to Word / Excel / Open office based on templates prepared directly in Word / Excel, etc.

jasiek

Like ghristov stated: Epesi is fine and well and we will of course continue developing new and improved versions.

We have several really good news coming up soon.
But first we will release an updated version of this version of Epesi.
In the meantime we will introduce new Reporting module created by Georgi Hristov - an independent developer and our partner and contributor to Epesi open-source on Github for a long time.
Then we will introduce a new version of Epesi 2.0 family with new and improved UI most likely based on:
https://semantic-ui.com/
There will be some backend improvements like caching, which will greatly speed.

Stay tuned!...

ghristov

@ladis - please share the requirements related to the GDPR and we will plan compliance.

Best regards,
Georgi

ladis

OK,

unfortunately it a bit depends on legislation of each country. Any way it must be done till 25 May 2018.
Good explanation you can found eg. on Wikipedia: https://en.wikipedia.org/wiki/General_Data_Protection_Regulation

As we discused in our company, for our needs (I hope for most companies, at least for this year, when this new regulation starts) Telaxus should declare somewhere (official website?), that EPESI is GDPR compatible. Than we can tell to possible inspection: "We're using EPESI and developer say, it's compatible with GDPR." It's like black box, nobody knows. And its posible to manage it till 25 May.

Necessary modificaton will be encript contact table, due this regulation. I think there's not many more issues. Question is logging all activities related with contacts, but we hope it could just know period, when and who had access to contacts. And it's now possible just with Login Audit module...

I hope easy understood my explanation. :-)

Ladis

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge