[Fiware] Conventions in managing requests to join FI-WARE subprojects in FusionForge

Juanjo Hierro jhierro at tid.es
Tue May 17 23:50:19 CEST 2011


Dear Pier,

   Thanks for asking.   Your questions are helpful indeed in order to
agree on common processes and procedures.

   Since your questions are valuable, I have decided to put the general
fiware mailing list in copy of my response

On 17/05/11 22:14, Garino Pierangelo wrote:
> Hi Juanjo,
>
>   sorry for another mail concerning admin, but it's just to avoid confusions in this first phases of the use by all of us of the FusionForge system.
>
> 1) I received today a (couple of) mail from a colleague (and another guy) to register to the Fi-ware project. I guess I receive the mails because I'm myself one of the admin to the overall project, but I believe that the management should be done by one of us only (in this case I believe it's you), while for the specific chapter project, i.e. fiware-i2nd, I'll be in charge of managing the registrations I receive. Is it correct as strategy?
   One of the goals we want to achieve by distributing Admin
responsibilities is avoiding bottlenecks and speed up processes as soon
as possible.

   Acceptance of requests to join the FI-WARE project in FusionForge can
be performed by any of the WPLs as well as Jose Jiménez, the rest of the
administrative/management team at TID or myself.   No matter who.   I
would say that the general formula is that WPLs are entitled to look
after people working at their WPs (no matter what company/organization
they work for) as well as people from their own companies.   When they
receive a notification to join the FI-WARE project by someone in one of
these two cases, I would suggest they apply the following rule: "I'll
wait for TID to solve this in the coming two hours or so.   If they
haven't accepted the request after that and I have time, I'll accept the
request on their behalf".

   I'll tell you something for sure.  I don't mind if you accept a
request earlier than me :-)   I wouldn't consider it a misappropriation
of rights at all.   I would indeed feel thankful for your help and
interest for collaboration.   We need to be "agile" and this can only
happen when each trust the other.    Besides, there might be situations
where you are in a better position to decide whether a given request
should be accepted or not (it may come from someone working in your WP
you know but I don't)
> 2) When you say that everyone in the world might request to register to fiware, do you mean that they will be accepted?
   No :-)
> If yes, I believe this will be for fiware project only, and not for the chapter sub-projects, is it right? If not, the only way to prevent 'foreign' people to access private document is to mark them as such, but in my view it would be a too weak strategy from the security point of view (what if we forget by accident to mark the document as private?), so I'd strongly prefer to limit access at least to the sub-project lists. Did I misinterpret something?
   We are basically on the same page ... When I made that comment, I
made it because:

a) I wanted you to be aware of this so that you don't blindly accept any
request.   A good practice would be indeed to check at least what
company/organization he works for.
b) it might not apply for the FI-WARE project or any other of the
current FI-WARE subprojects in FusionForge, but maybe in the future it
makes sense to create a project where we want to allow public access to
some particular stuff but register who has the access right.   It might
apply, for instance, to stuff linked to the FI-WARE Testbed
subproject.   But we'll see.

   One final word, though.   In our current documentation management
system, all documents are public by default.   You should mark them as
private explictly.   Be aware of this.   I will check whether the
default rule can be set up to make them private, but I'm not sure this
will be the case.

> Kind regards
> Pier
> P.S.: I'm periodically checking for new people registered in FusionForge, and adding those I know are involved in i2nd to my sub-project, even though they didn't ask yet to join (but I know they would...), so I avoid receiving most of the registration requests.

   If you find they have also request to join the FI-WARE subproject,
and TID has not yet accepted their request, don't hesitate to accept
their request to join that project, using your Admin privileges.

   Best regards,

-- Juanjo
>
>
> ________________________________________
> From: fiware-i2nd-bounces at lists.fi-ware.eu [fiware-i2nd-bounces at lists.fi-ware.eu] On Behalf Of Juanjo Hierro [jhierro at tid.es]
> Sent: Tuesday, May 17, 2011 6:40 PM
> To: Wolfgang.Steigerwald at telekom.de
> Cc: fiware-iot at lists.fi-ware.eu; fiware-tools at lists.fi-ware.eu; fiware-cloud at lists.fi-ware.eu; fiware-security at lists.fi-ware.eu; fiware-apps at lists.fi-ware.eu; fiware-data at lists.fi-ware.eu; fiware-i2nd at lists.fi-ware.eu; fiware at lists.fi-ware.eu
> Subject: [Fiware-i2nd] Problems accessing FI-WARE documents (including template for deliverables) available in documentation management tool
>
> Dear Wolfgang,
>
>    I copy all the project because my response to your question might be useful for all.
>
>    What happens to you is because:
>
>   *   you have not requested to join the FI-WARE project (you should request joining FI-WARE and the project linked to WPs you are involved in)
>
> OR
>
>   *   you have not send an email to your WPL asking him/her to register you in the FI-WARE project (and the project linked to the WP he/she leads)
>
>    This was explained in my previous message.
>
>    Probably the easiest method would be the first one.   You just need to get access to the project page (through http://forge.fi-ware.eu/softwaremap/full_list.php) and then click on the "Request to join" link you will find on the right side of your screen:
>
> [cid:part1.00070202.05070106 at tid.es]
>
>    Once you request to join, either one of the WPLs or some Admin from TID will grant you access (also explained in my previous mail).   Note for the Admins: you should grant access but assigning a "Senior Developer" role.
>
>    Note that EVERYONE in the world might register in our FusionForge instance (that's the way it works).   This ease administration and also enables third parties to approach us.   However, only FusionForge users that are registered in a project can access documents labeled as "private" to that project.   In the case of the referred documents, we decided to label them as private to the project.
>
>    Hope this helps,
>
> -- Juanjo
>
> On 17/05/11 17:48, Wolfgang.Steigerwald at telekom.de<mailto:Wolfgang.Steigerwald at telekom.de>  wrote:
> Hello Juanjo,
>
> even so I'm registered on FusionForge I receive "Permission denied"
>
> Best regards
>
>   Wolfgang
>
>
>
>
>
> Deutsche Telekom AG
> T-Labs (Research&  Development)
> Wolfgang Steigerwald
> Goslarer Ufer 35, 10589 Berlin
> +49 30 3497-2058 (Tel.)
> +49 391 53475396 (Fax)
> +49 171 5664350 (Mobil)
> E-Mail: wolfgang.steigerwald at telekom.de<mailto:wolfgang.steigerwald at telekom.de>
> www.telekom.com<http://www.telekom.com/>
>
> Erleben, was verbindet.
>
> Deutsche Telekom AG
> Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender)
> Vorstand: René Obermann (Vorsitzender),
> Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme,
> Timotheus Höttges, Edward R. Kozel, Thomas Sattelberger
> Handelsregister: Amtsgericht Bonn HRB 6794
> Sitz der Gesellschaft Bonn
> WEEE-Reg.-Nr. DE50478376
>
>
>
> Große Veränderungen fangen klein an – Ressourcen schonen und nicht jede E-Mail drucken.
>
>
>
> ________________________________
> Von: fiware-i2nd-bounces at lists.fi-ware.eu<mailto:fiware-i2nd-bounces at lists.fi-ware.eu>  [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Juanjo Hierro
> Gesendet: Dienstag, 17. Mai 2011 16:53
> An: fiware at lists.fi-ware.eu<mailto:fiware at lists.fi-ware.eu>; fiware-apps at lists.fi-ware.eu<mailto:fiware-apps at lists.fi-ware.eu>; fiware-cloud at lists.fi-ware.eu<mailto:fiware-cloud at lists.fi-ware.eu>; fiware-data at lists.fi-ware.eu<mailto:fiware-data at lists.fi-ware.eu>; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; fiware-i2nd at lists.fi-ware.eu<mailto:fiware-i2nd at lists.fi-ware.eu>; fiware-security at lists.fi-ware.eu<mailto:fiware-security at lists.fi-ware.eu>; fiware-tools at lists.fi-ware.eu<mailto:fiware-tools at lists.fi-ware.eu>
> Betreff: [Fiware-i2nd] Template for FI-WARE documents (including template for deliverables) available in documentation management tool
>
> Dear colleagues,
>
>    The document management tool is now finally configured so that we are now able to use it for sharing documents.
>
>    I'll send you a brief document describing how it works in order to upload/publish documents later this evening.
>
>    In the meantime, let me share with you the template we would like you to follow for creating FI-WARE documents.   You can download it from:
>
> http://forge.fi-ware.eu/docman/view.php/7/42/FI-WARE+Public+Document+template+11-05-17.doc
>
>    You may also find a template for meeting minutes useful.   You can download it from:
>
> http://forge.fi-ware.eu/docman/view.php/7/41/FI-WARE+Minutes+template+11-05-17.doc
>
>    Both documents are private, so that only users properly registered in the FI-WARE project in the FI-WARE FusionForge will be able to download them :-)   I hope this will persuade most of you to register in the FI-WARE project @ FusionForge if you haven't still done so :-)
>
>    A mail reminding to register with a detailed (updated) description of steps to be followed will arrive to you in the next message.
>
>    Best regards,
>
> -- Juanjo
>
>
>
> ________________________________
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
> ________________________________
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
>
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
>
> .
>

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware/attachments/20110517/c3267b40/attachment.vcf>


More information about the Old-Fiware mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy