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 -- JuanjoHierroEmailSignature Juanjo Hierro Chief Technology Officer FIWARE Foundation FIWARE Foundation email: juanjose.hierro at fiware.org www: http://fiware.org twitter: @JuanjoHierro @FIWARE -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fi-next/attachments/20170210/17d63e54/attachment.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/17d63e54/attachment.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy