Hi Marco,

Please see the email below. According to it, there will be a big change in
the account registration for FIWARE Lab usage.

Could you tell us what would be the easiest/fastest way to register a
"Community" account for all the 5 consortium members and all of the
selected startups to our program (cc 40-45 companies).

Thank you!

Adam Jermann - Digital Factory

---------- Forwarded message ----------
From: <no-reply@account.lab.fiware.org>
Date: Wed, Feb 11, 2015 at 6:27 PM
Subject: [FI-LAB] FIWARE Lab - Update of Term and Conditions and new user
policies
To: adam.jermann@digitalfactory.vc

Dear FIWARE Lab User, this email is to inform you of the on going process
to optimize resource usage in the FIWARE Lab (formerly known as FI-LAB). As
result of this process, a set of new policies will gradually apply to
FIWARE Lab accounts starting from 24/02/2015.
The main policies are summarized as follow:

• Users will be categorized in “Trial” and “Community”. Trial users
  will include the users accessing the Lab for testing the FIWARE
  technologies during a limited period of time. Community users will include
  users who have formally requested a longer term environment for working on
  the development of applications based on FIWARE technologies.
• Trial users will be provided with a limited set of resources and for a
  limited period of time (14 days) within a single node part of FIWARE Lab.
  To keep resources, Trial users who wish to have a longer term environment
  will need to apply (and obtain) and Community account (see point 3). After
  the expiration of their trial period, the account assigned to a Trial user
  is disabled and the associated resources released - any backup is up to the
  user. FIWARE Lab is not responsible for the loss of any data. Reminders are
  sent one week before the expiration and the day before. The total resources
  made available to Trial Users are documented at this link. However, the
  amount of resources assigned to Trial Users may vary depending on
  availability of new nodes and change of internal policies.
• Community users will be selected through an application process. The
  application process, which may result with a negative answer, will be
  handled with the eventual support of FIWARE Accelerator projects (see [1],
  [2]) that will identify users that are part of their acceleration
  programme. Users beyond the FIWARE Accelerator programme are also admitted.
  Users willing to become Community users will need to describe the
  application they are developing and the planned usage of FIWARE resources.
  Community users will be assigned a default FIWARE Lab node and will have
  access to it for a 9 month period unless the application process is
  renewed. This node is selected according to their preference and/or
  ascription to a given FIWARE accelerator project, each of which is linked
  to a default node. By issuing a request for additional resources, Community
  users may be able to access additional nodes if well motivated.
• If the total quota assigned to Trial users gets exhausted, requests to
  create a Trial user account that require management of cloud resources will
  be queued and notified once resources are available on a “first arrived,
  first served” basis.
• Users requesting a Public IP need to provide a verifiable identity
  information that will be handled by FIWARE infrastructure providers to
  ensure the possibly to track liable actions within the FIWARE Lab.
• Users will not be able to create new “Organizations” anymore beyond
  the organization linked to their account. FIWARE Lab allows to share
  access to the cloud environment set up by a given user by adding users to
  the organization linked to that user. As a consequence, existing
  organizations will be blocked from accessing cloud resources.

Should you not accept the new defined policies by 24/02/2015, your account
will be removed and your resources released. FIWARE Lab providers will not
be responsible for creating a copy of the data you stored in FIWARE Lab.
Additionally, we have added a few statements to adapt to the latest changes
in FIWARE Lab:

• The initiative formerly known as “FI-WARE” is now referred to as
  “FIWARE”
• The environment formerly known as “FI-Lab” or “FI-Lab” is now
  referred to as “FIWARE Lab”
• The communication with the support channels or other channels can be
  published .
• Calarification on the number of users that an individual may have

Please use this link to state whether you accept or not the new defined
policies if you haven’t done yet. You may be asked to login using your
current FIWARE Lab account: http://terms.lab.fiware.org/accept
Best regards,
The FIWARE Lab team
[1] http://www.fiware.org/accelerators/
<http://www.fiware.org/accelerators/> [2]
http://www.fiware.org/fiware-accelerator-programme/
--------------------------------
You are receiving this message because you are a
registered FIWARE Lab user. Should you wish to remove your account, you
need to follow four simple steps: 1. Log on FIWARE Lab 2. Click on the
dropdown menu next to your user name (upper right corner) 3. Select
"Settings" 4. Click on "Cancel account" and confirm
--------------------------------
You are receiving this message because you are a registered FIWARE Lab
user. Should you wish to remove your account, you need to follow four
simple steps: 1. Log on FIWARE Lab 2. Click on the dropdown menu next to
your user name (upper right corner) 3. Select "Settings" 4. Click on
"Cancel account" and confirm

–
Üdvözlettel,

Adam Jermann
Program Manager
Digital Factory Zrt.

P: +36 20 435 2604
S: adam.jermann
E: adam.jermann@digitalfactory.vc
W: http://www.digitalfactory.vc/

_______________________________________________
Fiware-ceedtech-coaching mailing list
Fiware-ceedtech-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-ceedtech-coaching

[Created via e-mail received from: Adam Jermann <adam.jermann@digitalfactory.vc>]