dear juanjo, this requires a more detailed analysis as there are content activities that needs to be done first within fi-next. fi-next as any other source of inputs to the fiware community requires to define its own position and then can bring it to the attention of the fiware tsc which will discuss, provide its view and then decide. for the sake of clarity, i as project coordinator, shall be the moderatorof the fi-next mail list together with you and then take proper actions in handling the content of the email. indeed while the project is daily working in content and produceing outcomes the tsc is for the overall management and the solely technical decision body (of course), but certainly not a daily working place and certainly cannot dictate what projects shall do, for sure can and must say what cannot become a fiware asset, and in general what is not fiware from a technical point of view. ciao, stefano On 10 February 2017 at 11:36, Juanjo Hierro <juanjose.hierro at fiware.org> wrote: > Dear all, > > This mail is trying to summarize the criteria to bear in mind when > determining which should be the list you send an email to. > > As you all know, FIWARE has been designed as an initiative which goes > beyond the scope of EU-funded projects. The FIWARE Foundation was created > to support the FIWARE mission whose members (individuals or organizations) > are engaged in FIWARE activities within a number of FIWARE Mission Support > Programmes [1] and build up somehow the FIWARE Community. > > Certain activities carried out by some FIWARE Community members might be > publicly funded but not necessarily. They may even be publicly funded > beyond the EU ... don't miss that there are some active members who are > working in expanding FIWARE outside the EU (e.g., Mexico, Chile, ...) and > why not, they may activate some local/regional public funding. There might > be different ways of funding the participation of members contributing to > any activity. Thus, for a given activity, there might be some members > contributing to it who are going on their own (i.e., as individuals) and > some others may be funded under certain project (fully private or partly > funded by the EU, some other national or even some non-EU funding > program). There might be all kind of combination. Soon, for example, we > may have people from NEC Japan who join the FIWARE TSC as representatives > of NEC, which has recently joined the FIWARE Foundation as Platinum > Member. Three organizations which might be working togther in the Data > chapter might be one going on their own, another one under the umbrella of > some EU-funded project and the third one under the umbrella of a project > funded in Germany. > > This is not different to what may happen in other existing open source > initiatives or industry initiatives (W3C, OASIS, OMG, IIC, ...) > > We have to be very scrupulous and keep separate the exchange of > information that is valuable for all members of the FIWARE Community > participating in a given Committee (e.g., FIWARE TSC, or FIWARE Mundus > Committee) or a given FIWARE Chapter and the exchange of information that > is project-specific. The first kind of exchanges should go through the > mailing lists created for that purpose (e.g., the FIWARE TSC mailing list, > the list defined to run discussions within a given FIWARE Chapter, the list > used to run discussions on FIWARE NGSI, ...). The > fi-next at lists.fiware.org mailing list should ONLY be used for exchange of > FI-NEXT specific info and run discussions that are only FI-NEXT specific > (e.g., how to organize a FI-NEXT review). > > To avoid bad practices, we have turned the fi-next mailing list into > full-moderation mode which means that ALL messages sent to the mailing list > will be moderated, even for members of the list. Please note that any > message sent to that list which is addressing matters that are relevant for > FIWARE activities (even if it is only part of the message) WILL BE > REJECTED. If you want to a) reach quickly your target audience and b) > avoid loosing your time (and ours) handling rejections, please think twice > what list you are sending messages to. > > Only after a period in which we find out that people is using the > fi-next mailing list properly we will drop out moderation for all list > members. Once this happens, if someone sends a message that breaks the > above criteria, he/she will become moderated as individual in the list from > then on. > > Cheers > -- > Juanjo Hierro > > Chief Technology Officer > FIWARE Foundation > [image: FIWARE Foundation] > email: juanjose.hierro at fiware.org > www: http://fiware.org > twitter: @JuanjoHierro @FIWARE > > > > ____________________________________________________________ > ______________________________ > > 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 > > FI-NEXT mailing list > FI-NEXT at lists.fiware.org > https://lists.fiware.org/listinfo/fi-next > > > -- *Stefano De Panfilis* *Chief Operating Officer * *FIWARE Foundation e.V.* Franklinstrasse 13A 10587 Berlin mob: +393357542567 skype: depa01 twitter: depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fi-next/attachments/20170210/e95dbeb1/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: FIWARE Foundation Logo edited.png Type: image/png Size: 5618 bytes Desc: not available URL: <https://lists.fiware.org/private/fi-next/attachments/20170210/e95dbeb1/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy