statute edit march 2020 #55
Conversation
statute.md
Outdated
| @@ -22,6 +22,10 @@ Berlin TWC has as its primary goal the empowerment of Tech Workers in their indu | |||
| The application and modification of this document must be driven by the principles of fairness, horizontality, inclusivity organizational scalability and safety of the members. | |||
|
|
|||
|
|
|||
| 1.3.1 | |||
|
|
|||
| The members of Berlin TWC should be considered equal among each other and equal to every other worker. A member is expected to show solidarity to other workers through the pursuit of the organization's goals. Each member contributes at the best of their intellectual, physical and economic capabilities. | |||
There was a problem hiding this comment.
I would change last line to be: Every member is expected to contribute to best of their knowledge and strength to the best of their ability
There was a problem hiding this comment.
I would also propose a definition: "A member is of good standing, if they have attended 3 events within the past 6 months". This would mitigate a situate where someone was involved/active say from June-December 2019 and then shows up in April 2020, without having attended anything in between.
There was a problem hiding this comment.
can you please review the sentence you proposed? I guess something went wrong with the copy-pasting?
There was a problem hiding this comment.
It will be changed into: "Every member strives to contribute to best of their knowledge and strength"
chobeat
force-pushed
the
proposals_for_second_draft
branch
from
9bb0992
to
5a28478
Compare
There was a problem hiding this comment.
I made one recommendation to make explicit, that online events are valid events, and also the formation of a steering committee. Boston and NYC both have 6 month election terms. The steering committee is responsible for representing Berlin TWC, and also doing the "janitorial" work, like updating the website/social media, to reflect the activities and interests of all members. I would also further suggest, by default steering committee events/meetings are open to all TWC members, but the expectation is that steering committee members host/attend them, and also publish notes etc.. This would be made easily possible with our new cloud.techworkersberlin (nextcloud) instance :)
statute.md
Outdated
|
|
||
|
|
||
| 1.3.1 | ||
|
|
||
| The members of Berlin TWC should be considered equal among each other and equal to every other worker. A member is expected to show solidarity to other workers through the pursuit of the organisation's goals. Each member contributes at the best of their intellectual, physical and economic capabilities. |
There was a problem hiding this comment.
Suggestion: Replace Each member contributes at the best of their intellectual, physical and economic capabilities. with Every member is expected to contribute to best of their knowledge and strength to the best of their ability
statute.md
Outdated
|
|
||
| ### 2 | ||
|
|
||
| 2.1 | ||
|
|
||
| A Berlin TWC Assembly is a meeting that is defined by a date, a location and an agenda produced by the Coordination Team (defined later). | ||
| A Berlin TWC assembly is a meeting that is defined by a date, a location and an agenda produced by the Coordination team (defined later). |
There was a problem hiding this comment.
a location (including online)
|
|
||
| 3.1 | ||
|
|
||
| A Team is created in an Assembly through vote. The responsibilities and capabilities of the Team must be clearly specified. These can be expanded or restricted through an Assembly Vote. The creation of a Team can be specified in the Agenda as a self-standing item or as part of a wider proposal. The vote for the creation of a Team can be held without inserting it into any Agenda if the discussion of a proposal suggests it as a necessity. The proposal for the creation of a Team must include its initial members. | ||
| A team is created in an assembly through vote. The responsibilities and capabilities of the team must be clearly specified. These can be expanded or restricted through an assembly vote. The creation of a team can be specified in the Agenda as a self-standing item or as part of a wider proposal. The vote for the creation of a team can be held without inserting it into any Agenda if the discussion of a proposal suggests it as a necessity. The proposal for the creation of a team must include its initial members. |
There was a problem hiding this comment.
So according to this, we could vote for a steering committee, for a 6 month duration period without any constitutional amendments? The past months there have been steering committee shadow meetings, and I would like to formalize who is in the steering committee, especially as we interface with many external organizations who want to jointly host events with us etc...
There was a problem hiding this comment.
I would say so. It's a special team with a lot of power, but I think we don't need to change this part. I would add it to the list of special teams though.
statute.md
Outdated
| @@ -117,7 +117,7 @@ The following teams hold a special status in Berlin TWC. They must exist at all | |||
| * Coordination Team: Concerned with organizing and moderate the assembly, accepting proposals for the agenda, communicating when and where the assembly will be held. The Coordination team is responsible for the accessibility of the assembly. | |||
| * Press Team: Authorized to speak with journalists and conduct interviews on behalf of Berlin TWC. Press team also maintains a list of contacts, for press releases in service of Berlin TWC and tech worker organizing as a whole. | |||
| * Relay Team: The Relay team is responsible to coordinate the interaction between Berlin TWC and other organisations and institutions. Any inbound request for collaboration must go through the Relay team. Ad-hoc teams can be created for specific projects. They can be entrusted with handling the communication between relevant institutions in the scope of said projects. In such a case, the ad-hoc team and the Relay team must agree on how to handle the interaction with other organisations in order to avoid overlaps and conflicts. | |||
|
|
|||
| * Steering Committee: The Steering Committee holds executive power and is in charge of defining the strategy of Berlin TWC. The responsibility of the Steering Committee is to translate the will of the Assembly into actionables steps, prioritize them and proactively engage other teams, enabling them to take action over the planned steps. | |||
There was a problem hiding this comment.
I'd merge/combine Steering Committee with "Relay Team" fwiw, and clarify further what responsibilities of Steering Committee are. Perhaps best to do in the meeting itself.
statute.md
Outdated
|
|
||
| 2.2.2 | ||
|
|
||
| Members that physically participate in the Assembly have the right to vote. A simple majority is sufficient to approve any decision, unless specified otherwise. The vote is collected by a show of hands. | ||
| Members that physically participate in the assembly have the right to vote. A simple majority is sufficient to approve any decision, unless specified otherwise. The vote is collected by a show of hands. |
No description provided.