Hi,
I don't know if I was not clear in my message but, in case we propose
to change the bylaws, this clearly means that we would need to first
propose to change the bylaws (and such a change would need to be
approved in the GA) and then only once the change is approved, we would
go for elections.
So, what we need to discuss at TSC level is what way to go between
the two options I mentioned (but I add clarifications to the second
point, in red):
* Rely on the bylaws, therefore go for election of 2 representatives
per chapter (we'll have now only 5) and then additional 3
individuals (platinum members choose who take their seats)
* Ask for a change in the bylaws (during the upcoming General
Assembly) so that we run for elections of individual
representatives, up to a number we find suitable, not linking them
to existing chapters. If the change is approved by the General
Assembly, we would go for the elections afterwards. Note that this
option means deferring the TSC renewal elections until after the
General Assembly.
For me, the remarks in red were implicit, but it's nice to hear
feedback which makes it clear that these points I thought were implicit
were indeed not so obvious.
What I don't see is why you (Stefano) bind elections of the TSC to
the GA and you claim we are "late" referring to the GA ... We are late
because we should have renewed the TSC after 12 months, but not because
we have to get the TSC elected at the GA, before or after. They have
never been coupled: I remind you that the TSC members are NOT voted by
the GA members but the FIWARE Chapter Active Contributors. The
rationale for our delay was that we changed the chapter structure more
or less when the elections had to come (nevertheless we probably should
have run it during December, we are definitively late).
In any case, we shall clearly go for elections now. Question is
whether organize them according to the existing bylaws or propose a
change on them and run then afterwards the GA decides what way to go.
This is what we have to decide now.
Cheers,
Juanjo
On 11/02/2018 21:24, Stefano De Panfilis wrote:
> dear juanjo,
>
> just to be on the safe unfortunately we cannot change the bylaws nor
> interpret them the way we would like.
>
> if we want to change the bylaws the correct, open and transparent way
> is that tsc has to discuss it, approve it, sent to the ga for
> approval, get its approval and then apply the new bylaws.
>
> whatever way we choose, the first step is the approval of the ga to
> have the new bylaws in place, i.e. the changes can only be applied for
> the elections in 2019.
> so, even if i believe a change in the composition of the tsc would be
> beneficial, this can only be according to the rules.
>
> i'd like also to tell you that to properly trigger the election
> process, according to the current rules, we are already quite late
> since the ga is called to be on 20 march 2018, and thus we are already
> in the 6th week before the ga and the 5th week before the ga starts on
> this wednesday.
> this means that by tuesdyay the list of candidates must be finalised.
>
> however, from the following bylaws excerpt there may be an escape
> legal mechanisms, at least i see it:
> Inline images 1
> as you can see the elections are every 12 months "at most". to respect
> the bylaws then we shall have the elections now according to the old
> rules, but then we can have new elections with the new rules as soon
> as the changes in the bylaws have been approved by the ga.
>
> this means that before the ga we have to master and finalise a
> proposal for bylaws change to the ga, which anyway shall be put at the
> attention of the ga 15 days before the ga meeting. so even adopting my
> proposal for the escape route we do not have so much time.
>
> i'll travel for berlin tomorrow morning. i expect to land there at
> 11:10 so i hope to be in time in our offices able to discuss this topic.
>
> ciao,
> stefano
>
> On 9 February 2018 at 18:23, Juanjo Hierro <juanjose.hierro at fiware.org
> <mailto:juanjose.hierro at fiware.org>> wrote:
>
> Dear all,
>
> Now with Veronika fully on board as our Scrum Master at the
> FIWARE Foundation, we would like to introduce a number of changes
> in our Way of Working (WoW) at the FIWARE TSC:
>
> * Veronika will send every tuesday after a FIWARE TSC, a draft
> agenda with link to pre-minutes for the following TSC
> * Members of the TSC will then be invited to propose additional
> topics until Thursday noon
> * Veronika will send a final version of the agenda and
> pre-minutes before Thursday EOB
> * People will have the opportunity to add input in the
> pre-minutes before the TSC
>
> Once every month, we will send a mail to the FIWARE ecosystem
> reminding that individual members and people working for FIWARE
> Foundation member organizations are invited to join and that they
> can follow discussion through the publicly available minutes.
>
> From now on and after the re-structuring of FIWARE chapters, we
> will organize our TSCs as follows:
>
> * 1st hour: report on progress from GE owners in the various
> FIWARE chapters plus the chapter on FIWARE Lab and deployment
> tools:
> o Context Management (Core) Chapter
> o Data/API Management, Publication and Monetization Chapter
> o Context Processing, Analysis and Visualisation Chapter
> o Interface with IoT, robotics and third systems Chapter
> o FIWARE Lab and deployment tools
> * 2nd hour: proposed topics
>
> We will be rotating among the chapters so each week we will
> focus on one. Topics/GEs to cover will be picked in advance.
> I'll come with a proposed calendar we all can review.
>
> We would like to start with the Context Management (Core)
> Chapter this next TSC: José Manuel will be in charge of that.
>
> Proposed topics for the second hour will change based on demand,
> but until Hannover-Messe we shall include an item to follow-up on
> progress of our Task Force regarding implementation of IDS
> architecture concepts: 20 mins will be booked for this.
>
> The FIWARE Foundation General Assembly is coming and one of the
> questions we shall solve is that of running new elections of the
> TSC seats. This will be one of the topics for our next TSC (2nd
> hour). We have two choices:
>
> * Rely on the bylaws, therefore go for election of 2
> representatives per chapter (we'll have now only 5) and then
> additional 3 individuals (platinum members choose who take
> their seats)
> * Ask for a change in the bylaws so that we run for elections of
> individual representatives, up to a number we find suitable,
> not linking them to existing chapters
>
> So we will discuss what way to go at next TSC. Your feedback in
> the meantime will be welcome.
>
> Cheers,
>
> --
> Juanjo Hierro
> Chief Technology Officer
> juanjose.hierro at fiware.org <mailto:juanjose.hierro at fiware.org>
> www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
> Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
> <https://twitter.com/JuanjoHierro>
>
>
>
>
>
>
>
>
>
>
> __________________________________________________________________________________________
>
> 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/FIWARE_Privacy_Policy>
> -
> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
> <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
> <https://lists.fiware.org/listinfo/fiware-technical-committee>
>
>
>
>
>
> --
> *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/fiware-technical-committee/attachments/20180212/78766d1f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 65319 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180212/78766d1f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foundation-logo.png
Type: image/png
Size: 8201 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20180212/78766d1f/attachment-0003.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy