[Fiware-lab-federation-nodes] How to handle Community Account expiration

[Chulani, Ilknur]

Dear Alfonso,

Thanks very much for initiating action on this! My suggestion would be to inform the users as early as possible, i.e. not wait till 10 days before the expiry.

Sometimes the main account holder of the SME is  on holidays or sick leave, etc., then they don’t get crucial messages like this in a timely manner. So the first reminder can be sent out even one or two months  before the expiry date. My two cents ☺

Thanks a lot again,

ilknur

From: fiware-lab-federation-nodes-bounces at lists.fiware.org [mailto:fiware-lab-federation-nodes-bounces at lists.fiware.org] On Behalf Of Pietropaolo Alfonso
Sent: Thursday, April 28, 2016 5:55 PM
To: fernando.lopezaguilar at telefonica.com
Cc: fiware-lab-federation-nodes at lists.fiware.org
Subject: Re: [Fiware-lab-federation-nodes] How to handle Community Account expiration

Hi Fernando,
my proposal was 10, 5, 0 days before the expiration in order to send 3 reminder. But of course we can change this number according to all of you needs and experience with users.


Alfonso

Il giorno 28 apr 2016, alle ore 16:32, FERNANDO LOPEZ AGUILAR <fernando.lopezaguilar at telefonica.com<mailto:fernando.lopezaguilar at telefonica.com>> ha scritto:

Inline

From: <fiware-lab-federation-nodes-bounces at lists.fiware.org<mailto:fiware-lab-federation-nodes-bounces at lists.fiware.org>> on behalf of Pietropaolo Alfonso <Alfonso.Pietropaolo at eng.it<mailto:Alfonso.Pietropaolo at eng.it>>
Date: Thursday 28 April 2016 at 16:01
To: "fiware-lab-federation-nodes at lists.fiware.org<mailto:fiware-lab-federation-nodes at lists.fiware.org>" <fiware-lab-federation-nodes at lists.fiware.org<mailto:fiware-lab-federation-nodes at lists.fiware.org>>
Subject: [Fiware-lab-federation-nodes] How to handle Community Account expiration

Dear Fernando, All,
I’d like to share with you an update regarding the issue about expiring/expired Community Account.

I raised such issue to Stefano (WP Leader) and in a few words his proposal is to ask users affected by the expiration if they want to continue using FIWARE Lab. If they reply, then we should give them 9 more month by default.

As I said, that is in a few words the proposal, but it is on us how to do that in technical terms… I'm sure there are different ways to reach the same goal.

For instance:

- Is there a chance to create a script that send automatic emails to all Community Users (those who are close to the expiring date) informing them that within 10, 5, 0…days their account expire and if they want to continue using FIWARE Lab they must open a ticket for the target node ?

This functionality is under development in the Skuld component. The only thing that we had to know is the time to send this information.

Looking forward to more proposal and technical tips from all of you.

I want to start and prioritize this discussion because I will be absent next week but this problem is becoming quite urgent.

Kind regards,
Alfonso


Alfonso Pietropaolo

Research and Development Laboratory
Engineering Ingegneria Informatica S.p.A. <https://imail.eng.it/ecp/Customize/www.eng.it>
Via Riccardo Morandi, 32 00148 Roma - Italy
Tel. 0683074834
Skype: alfopietro




________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160429/642a4d84/attachment.html>