[Fiware-technical-committee] Updated guidelines on how to contribute

[JOSE MANUEL CANTERA FONSECA]

Hi,

Responses inline.

From: Fernando López <fernando.lopez at fiware.org>
Date: Tuesday 28 February 2017 at 16:09
To: JOSE MANUEL CANTERA FONSECA <josemanuel.canterafonseca at telefonica.com>
Cc: "fiware-technical-committee at lists.fiware.org" <fiware-technical-committee at lists.fiware.org>
Subject: Re: [Fiware-technical-committee] Updated guidelines on how to contribute


Dear José Manuel,

Thank you for the description that you have provided, I have a couple of questions/doubts:

- You are talking about to add the contributor name to a credits file, is there this file in the repositories or should be created when it was requested? Which content we should have on it?

>> The developer guidelines state clearly the presence of a CREDITS file, see:

https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Developer_Guidelines#External_Contributions

- Apparently, you are talking about issues management in the github repositories. Correct me if I am wrong but I do not remember some policy guide to define labels in repositories associated to FIWARE. The GE(r)i owners have to create the label "Welcome Contribution" or it will be created by the users when they want to create a new issue.
>> Those labels have to be created by GEri owners as they are responsible for determining what issues can be ‘welcome contributions’. Please check FIWARE Orion as an example of how to do this exercise.

Regarding the Chapter Active Contributor Expiration Policy, it seems that the only way to go out from active contributors is at the end of a year. Why do we do if a user decide to redraw his/her Chapter Active Contributor before this period of time?
>> Well, it will be every time there are elections to the TSC. I cannot envisage a real situation of active contributor withdrawal, that would make no sense.

Last but not lease, these sentence:

" It would sufficient to keep license headers" ->  "It would be sufficient to keep license headers"

>> fixed

" By doing so you are assigning to the copyright holder the ownership of your contribution" -> "By doing so, you are assigned to the copyright holder the ownership of your contribution"
>> I think the current sentence is correct. Please reread and check.

" In this case the contributor" -> " In this case, the contributor"

" First write a blog post which include the content and resources and then announce it" -> " Firstly, write a blog post which includes the content and resources and then announces it"
>> it is ‘announce’ and not ‘announces’ as it is expressed in imperative form.

" For doing so pull requests must be issued" -> " For doing so, pull requests must be issued"

rest of issues have been fixed.

Best regards,
   Fernando.-
On 27/02/2017 13:01, JOSE MANUEL CANTERA FONSECA wrote:
Dear all,

As per my action pending, I have updated the “How to Contribute” guidelines.

http://wiki.fiware.org/How_to_Contribute

The update has consisted of defining some guidelines on  active contributor recognition and expiration policies.

Please check and give feedback

Thanks, best




__________________________________________________________________________________________



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

- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy

- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE



Fiware-technical-committee mailing list

Fiware-technical-committee at lists.fiware.org<mailto:Fiware-technical-committee at lists.fiware.org>

https://lists.fiware.org/listinfo/fiware-technical-committee



--
−−−
Fernando López



FIWARE Cloud and Platform Senior Expert
FIWARE Foundation

[IWARE                 Foundation]

Franklinstrasse 13A
10587 Berlin

email: fernando.lopez at fiware.org<mailto:fernando.lopez at fiware.org>
www: http://fiware.org
twitter: @flopezaguilar @FIWARE
skype: fernandola


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170303/0ddaedc9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 251284 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170303/0ddaedc9/attachment-0001.png>