Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
ShortURL | Playbook | Assistant
The following section contains the list of official operational Handbooks that collect all Standard Operational Procedures (SOPs) for The IO Foundation network.
All SOPs need to comply with TIOF's Policies at all times.
These guidelines are to be followed by all TIOF Members at all times.
For specific handbooks relative to each of The IO Foundation's initiatives, please refer to their corresponding documentation space.
Handbooks are updated on-the-go as needs arise and comply at all times with TIOF's Policies.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
This document defines all the necessary elements that conform TIOF's Project Identity at large. It is a reference document to which all TIOF productions, internal and external, need to refer and adhere. For any doubts, please contact Team Comms.
Note: The Media Kit is a subset of the Project Identity, focusing on productions that are generated for external outreach.
Some working content to be moved here: https://docs.google.com/document/d/1_BjdBtldAhO8seNjivXqKjnwzXRYCcVA-fc90h1Z2XM/edit#
See reference document: https://github.com/TheIOFoundation/TIOF/blob/main/Project%20Identity/%5BTIOF%5D%20Comms%20%5BP%5D%20Branding%20Guidelines%20ENG%20v1.4.pdf
Montserrat, Calibri(?)
Website data: DESKTOP TEXT (General - Apply at ROW level) Text 12px Line Height 20px Letter spacing 1px Note: Some pages will have their own custom settings as needed.
GH Repository: https://github.com/TheIOFoundation/TIOF/tree/main/Project%20Identity
Google Drive: [TIOF] Repository/Project Identity
https://www.qrcode-monkey.com/#url
Configuration
https://{WEBSITE}
You can Copy & Paste the following values:
Foreground Color #4E5056
Eye Color #66B5C5 #F79552
Background Color #FFFFFF
Add corresponding logo
Select corresponding options
Set Quality to MAX (2000x2000 px)
Download ALL formats (PNG, EPS, SVG, PDF)
Name following TIOF’s file naming format. [TIOF] Comms [P] {Object} QR Code XXX v{version}
@@@Loading Hex
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Create Start.me page
If the organizers have a Slack
Register to their workspace - Invite all the necessary members to join
Create a
TIOF (to come meet TIOF)
Name #tiof
Description: Official channel in {EVENT} for The IO Foundation.
Private: No
Session channel (all members of the session)
Name: {session number} or similar
Description: {Name of the session} in full if ever possible
Private: No
Then add all the necessary people
Update topic to same as Description
Usage of the channels: Do not post anything private. You expect others to jump in and interact with them.
Invite people. It’s an opportunity to engage.
For the Start.me page
- A central place to communicate async with the session
- A way to speak 101 with the Speakers
-
Create all the above automatically BEFORE the session submission so that it can be introduced in the proposal text?
The idea is to have it on the session PAGE on the agenda directly.
- Backgrounds for the speakers
Team Coordinators to label Issues to be looked upon during the Sprint.
Speakers
Look for Bios on Salesforce
Look for pictures on G Drive
Event Promo image
1536px 1040px
See Canva
Venue settings
Event logo
See Canva
Reception Banner
See Canva
From MyData2020
Video briefing material for all session teams of MyData Online 2020 conference
https://docs.google.com/presentation/d/1SRy2AddaOSJUAtzqYek6xyh47HsjZT5gYQBseWXrrB0/edit#slide=id.ga5bf0d0012_0_504
List of Participants
Networking Methods
Connect with Organizers
Date & Time formats
https://webnus.net/dox/modern-events-calendar/all-date-formats/
Create group in Basaas & Add all necessary resources
Slack/Discord channels
Workspace G sheet
GitHub Repo/Project?
G Drive Storage folder
Event Page Set Up Instruction
Step 1: Provide Event Banner Image & Thumbnail
(Event Visual Guidelines in a separate attachment)
Step 2: Provide Event Title / Name
Step 3: Event Date, Event Start - End Times
Step 4: Location (Co-labs Starling or Glenmarie)
Step 5: Event Brief (Short description of event 1-2 paragraph, 160 words max)
Step 6: Event Description (Full description of event)
Step 7: Event Agenda
Format for agenda:
Step 8: Please provide sign up / ticketing URL if any
-------------------
Event Page Set Up Instruction
Step 1: Provide Event Banner Image & Thumbnail
(Event Visual Guidelines in a separate attachment)
See attached files
Step 2: Provide Event Title / Name Blockchain workshop: Create a Pet Shop on Ethereum
Step 3: Event Date, Event Start - End Times
Saturday 15th September 2018
Step 4: Location (Co-labs Starling or Glenmarie)
Co-labs Starling
Step 5: Event Brief (Short description of event 1-2 paragraph, 160 words max)
Step 6: Event Description (Full description of event)
Step 7: Event Agenda
Format for agenda:
Step 8: Please provide sign up / ticketing URL if any
Time
Agenda
Time
Agenda
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
The IO Foundation (TIOF) is a global for-impact NGO advocating for Data-Centric Digital Rights. Born from a fundamental concern about the state of Digital Rights in the world, its mission is to promote, protect and provide solutions for Digital Rights, thus aiming to bridge technological and humanitarian perspectives. As data becomes an increasingly powerful economic, political, and social force, programmers are emerging as the next generation of Human and Digital Rights defenders. Following its vision of a world where Human Rights and Digital Rights are one and the same, TIOF aims to raise awareness of the importance of Digital Rights in collaboration with other organizations, both from civil society and bodies of governance.
Acknowledgements to: Gabrielle Wong
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
This handbook provides you with the necessary information to prepare and run an email campaign (EDM).
See corresponding Lists for each Initiative in their own in Handbook. DCDR - BHR in Tech - CrowdShape - Project Lockdown - TechUp - UDDR
Clear, concise
INTRO
General greeting. Consider salutation level.
ABOUT TIOF
Introducing TIOF and the initiative in question.
WHY WE ARE REACHING OUT TO THEM & HOW THEY CAN PARTICIPATE
Explain the reason why we have reached out and how they can respond to the need.
CALL TO ACTION
What is it the beneficiary can do to respond to the need (actionable, URLs...)
PRESENTATION INFO / ATTACHMENTS
Optional. Include materials that sustain the above content.
SUPPORT US
Donate - Join
OTHERS
Announcements, other CTAs...
FOOTER
DCDR framework?
Channels (Social Media, etc.)
Unsubscribe
INTRO
ABOUT TIOF
WHY WE ARE REACHING OUT TO THEM & HOW THEY CAN PARTICIPATE
CALL TO ACTION
PRESENTATION INFO
This documentation page is under construction. Should you want to be notified once it's published, .
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Each Organization and Initiative has their own Slides Repository
A Presentation will be composed of 2 types of Slides
Repository Slides
Ad-hoc Slides
These are commonly used Slides that are templated to ensure consistency in image and messaging.
These Slides can only be edited in the corresponding Slide Repository by
[TIOF] Team UXUI > Design
[TIOF] Team Comms > Content
These are Slides that are specific for a given presentation and have little-to-no utility to be used as templates in the future.
Ask yourself the following questions:
Create a new Presentation (follow above for where and how to name it)
Visit the Slides Repo
Find the Slide that you need
Copy the Slide and Paste it in your new Presentation
A prompt will appear - Select Link
What happens if I can't find a Slide that I need?
Ask [TIOF] Team UXUI to create one for you.
These Slides can only be edited in the corresponding Slide Repository by
[TIOF] Team UXUI > Design
[TIOF] Team Comms > Content
Steps
Ask the above Teams to perform the requested changes
Update the Slide in the Presentation
Update the Slides as needed
Remember to use the available templates in the Slides Repository for each Ad-hoc Slide.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Version 1.3
This Memorandum of Understanding, hereinafter The MoU, is to be subscribed between
and
hereinafter collectively called The Parties.
The Parties agree to enter this MoU for the following purposes:
The Parties agree to enter this MoU committing to the following:
This non-binding MoU will enter in effect immediately from Signature Date, by and between:
The Partner, a company duly incorporated in The Partner's Country with registration number The Partner's Registration and having its registered address at The Partner's Address,
and
The IO Foundation, a non-profit duly incorporated in TIOF's Country with registration number TIOF's Registration and having its registered address at TIOF's Address.
The Parties enter voluntarily this MoU with the intention of achieving The Commitments guided by The Purposes.
By signing this Agreement, The Parties agree to comply with all the Terms.
2.1.1 The Parties wish to collaborate as described in The Purposes, while at all times diligently observing and implementing The Commitments.
2.2.1 This MoU shall be effective as of The Signature Date and shall be valid for an initial term of two (2) years and upon expiry, it shall be automatically renewed for further two (2) years period successively.
2.2.2 This MoU may nevertheless be terminated at any time by mutual consent of the parties, where either Party provides a one-month (30 natural days) written notice of termination.
2.2.3 In any case of discontinuance, the parties will honor agreed commitments either via the accepted arrangements or suitable alternatives negotiated at that point under this MoU.
2.2.4 Upon expiration or early termination, each party shall return to the other party all Confidential Information as defined in Section 2.6 hereof, and proprietary information, documents and reference material of the other party in its possession.
2.2.5 All such obligations and terms of this MoU that are required to survive the expiration or early termination of this MoU shall survive such event including, but not limited to, those described in Sections 2.5, 2.6 and 2.7 hereof.
2.2.6 The Parties may introduce changes or updates to this MoU, which will be agreed upon by all Parties before the next automatic renewal.
2.2.7 In particular, The Parties are encouraged to review their respective Purposes and Commitments so as to adapt this MoU to new objectives and/or circumstances in the following cycle.
2.3.1 The Parties have appointed liaison representatives as described in Section 1.1
2.3.2 These two representatives will take charge of all interactions between The Parties. for all communications related to activities related to this MoU.
2.3.3 Any notice of termination or request for amendment of this MoU are to be communicated by the initiating Party, from their official email, to the other Party's official email with CC to all representatives.
2.3.4 Any notice under this MoU will be in writing by the initiating Party and delivered by hand or by registered mail, email, facsimile transmittal or an express mail with a confirmation of receipt, to the other Party at the registered office or as may be substituted by the notice.
2.3.5 Any notices will be effective on the date of confirmation of receipt.
2.4.1 The Parties will endeavor to set a joint agenda for the year in January of each year in aid of implementing The Purposes.
2.4.2 In addition to the foregoing, and in aid of The Purposes, The Partner will engage in activities to support the annual agenda, such as described in The Partner's Commitments.
2.4.3 In addition to the foregoing, and in aid of the Purposes, TIOF will engage in activities to support the annual agenda, such as described in TIOF's Commitments.
2.5.1 Each party or its licensor shall continue to own the intellectual property developed by it prior to or independently of this MoU.
2.5.2 By entering into this MoU, the parties undertake:
(a) Not to use each other’s intellectual property without the prior express written consent of the other,
(b) To ensure the confidentiality of such intellectual property of the other within its respective organizations, and
(c) Not to use each other’s intellectual property other than for the Purposes of this MoU.
2.5.3 The parties agree that neither of them shall gain by virtue of this MoU any rights of ownership or any other interest, right, or title to copyrights, patents, trade secrets, trade marks, or any other intellectual property rights owned by the other party.
2.5.4 Except as otherwise explicitly agreed between The Parties, any and all works developed in the course of performing obligations pursuant to this MoU and all new inventions, innovations, or ideas developed by a Party in the course of performance of its activities under this MoU will belong to that Party who develops the same.
2.5.5 To the extent such intellectual property is created, the owning Party shall grant a non-exclusive, worldwide, royalty-free license to the other Party for the use of the intellectual property solely in connection with the activities under this MoU.
2.5.6 If The Parties undertake any joint development in the course of providing services under this MoU, any such joint development will be governed by a separate agreement to be negotiated in good faith by the parties prior to the commencement of any joint development efforts.
2.5.7 Solely in connection with the activities related to this MoU and its Purposes, and subject to all applicable branding guidelines, each Party grants to the other Party a nonexclusive, worldwide, royalty free, revocable license to use its logo/trademarks in activities and communications associated with this MoU.
2.6.1 For the purpose of this MoU, Confidential Information shall mean all information marked “Confidential” or under any similar legend indicating the confidentiality of the information or information which by its nature is confidential, except such information as is
(a) previously known to the receiving Party at the time of disclosure; or (b) independently developed by the receiving Party without reference to Confidential Information of the disclosing Party; or (c) disclosed to the receiving Party by a third party without an obligation of confidentiality; or (d) already in or subsequently part of the public domain (other than as a result of a breach of this MoU); or (e) required to be disclosed by the receiving Party by law, regulation, court order or other legal process.
2.6.2 During the term of this MoU, each Party may disclose to the other its Confidential Information.
2.6.3 The receiving Party shall hold such Confidential Information in strict confidence for the disclosing Party and shall not use it except in furtherance of the relationship set forth in this MoU, or except as it may be authorized by the disclosing Party in writing.
2.6.4 The receiving Party shall further be responsible for the compliance of the foregoing by its employees or agents.
2.7.1 Each Party represents and warrants that such Party has all necessary corporate power and authority, respectively, to enter into this MoU and to perform its obligations hereunder.
2.7.2 Each Party warrants to the other Party that all materials, data, information and other assistance provided by it shall not, to the best of its knowledge, infringe third party intellectual property rights and agrees to hold the other Party fully indemnified and harmless and at all times keep the other Party indemnified against any loss, damages, costs and expenses including attorney’s fees, which may be incurred as a result of any action or claim that may be made or initiated against it as result of any action on the part of the first Party.
2.8.1 All Parties will exchange, at the signature of this MoU, their corresponding Branding Kit / Media Kit.
2.8.2 Any press release, publicity or other promotional activity issued or engaged in by either Party regarding this MoU shall be reviewed and approved in writing by the other Party prior to release.
2.9.1 The Parties will be responsible for the manipulation, in accordance to the applicable legislation, of any user data obtained, or otherwise manipulated, resulting from this MoU.
2.9.2 TIOF observes a Code of Conduct for all of its activities.
2.9.3 The Partner may suggest the use of a different Code of Conduct for the activities co-organized with, but not limited to, TIOF for activities under this MoU. Such Code of Conduct will be agreed upon by all Parties on a separate document.
3.1.1 The Parties understand that nothing herein shall be construed as a binding contract between them.
3.1.2 In the event that The Parties seek to enter into a binding contract such an agreement shall be recorded in a written agreement, hereinafter “Definitive Agreement”, duly authorized by The Representatives of The parties ().
3.1.3 The Definitive Agreement(s) shall include details of the engagement, any additional roles/commitments and specific work that needs to be performed by each of The Parties.
3.1.4 The parties further understand that
(i) the activities intended by this MoU may not be successfully completed; and/or
(ii) the results achieved may not be as anticipated.
3.1.5 Except for breach of confidentiality obligations and intellectual property right infringement indemnification obligations, neither Party shall be liable for any indirect, punitive, special, incidental or consequential damages arising out of or in connection with this MoU, whether for breach of this MoU or in torts, including loss of business, data, revenue, profits or for any third party claims against the other whatsoever.
3.1.6 Further, The Parties acknowledge and agree that this MoU is a non-exclusive engagement and except as specifically agreed in a Definitive Agreement with respect to an activity, nothing contained herein shall be construed as preventing or restricting either Party from pursuing any opportunity with other entities without involving the other Party or to enter into similar alliance arrangements with other entities.
3.2.1 This MoU shall not be construed to be an agency or a partnership or joint venture or an employment relationship whether for tax or for any other purpose.
3.2.2 Neither Party shall be entitled to bind the other Party with any third Party by its actions, unless it has specifically obtained the prior written consent of such other Party to do so.
3.2.3 Each Party is an independent contractor, and no provision of this MoU grants either Party any express or implied right of authority to assume or create any obligations or responsibility on behalf of or in the name of the other Party, or bind the other Party in any manner or thing whatsoever.
3.2.4 This MoU is not a commitment of financial resources.
3.2.5 Any commitment by a Party to pay fees or other amounts to the other Party must be approved in writing, by the paying Party in advance.
3.2.6 Except as may be agreed by The Parties in an applicable Definitive Agreement(s), each Party will be responsible for all expenses incurred by such Party in connection with negotiation of this MoU and any promotion, marketing or other activities under this MOU. Each Party shall be liable to pay any tax attributable to it.
The laws of Malaysia shall govern this MoU. Both parties irrevocably submit to the exclusive jurisdiction of the Courts of Malaysia for any action or proceeding regarding this MoU including, but not limited to, those related to Sections IV, V and VI of this MoU.
3.4.1 Each Party warrants to the other Party that in performing their duties required under this MoU, they will comply with the applicable law and shall take no action which constitutes a violation of applicable law and which would subject the other party to penalties under applicable law.
3.4.2 Neither party shall assign or transfer this MoU without the prior written consent of the other party.
3.4.3 This MoU supersedes all prior oral or written communication, discussions and representations communicated between the parties hereto in respect of the subject matter of this MoU. Any modification to this MoU shall only be made by way of a written document duly executed by representatives of both parties hereto.
End of the MoU
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
This documentation page is under construction. Should you want to be notified once it's published, .
The IO Foundation (Mittetulundusühing The IO Foundation),
hereinafter TIOF
with registration number 80549272
hereinafter TIOF Registration
registered in Estonia
hereinafter TIOF Country
with official address Rataskaevu tn 2 Kesklinna linnaosa, Tallinn, Harju County, 10123 Estonia
hereinafter TIOF Address
with official email Contact@TheIOFoundation.org
hereinafter TIOF Email
represented by Jean F. Queralt
hereinafter TIOF PIC Name
with role in the organization Founder & CEO
hereinafter TIOF PIC Role
with official email JFQueralt@TheIOFoundation.org
hereinafter TIOF PIC Email
Malaysian Technical Standards Forum Bhd.
hereinafter The Partner
with registration number 200401016865 (655368-P)
hereinafter The Partner's Registration
registered in
Malaysia
hereinafter The Partner's Country
with official address MCMC Centre of Excellence, Off Persiaran Multimedia, Jalan Impact, 63000 Cyberjaya, Selangor Darul Ehsan, Malaysia
hereinafter The Partner's Address
with official email
Admin@MTSFB.org.my
hereinafter Partner Email
represented by
Partner PIC Name
hereinafter Partner PIC Name
with role in the organization
Partner PIC Role
hereinafter Partner PIC Role
with official email
Partner PIC Email
hereinafter Partner PIC Email
Support all Parties in the realization of their mission
Knowledge sharing
Potential development of educational programs
Explore opportunities for joint activities and training
Increasing exposure to the expertise each party brings in the areas of Communications and Multimedia Industry (CMI) development
Exchange information between both organizations with a view to share best practices and identify possible areas for co-operation
Participation of both organizations in industry events and congresses, etc. (e.g. for branding purposes) organized by both entities or where one has active participation
Participation from one Party in the other’s publications (e.g. articles, marketing material)
Explore potential research projects and corresponding funding opportunities
Explore potential engagement activities and corresponding funding opportunities
To join efforts to disseminate across each Party's network those events that the Parties may organize or participate in
To join efforts in finding ways to encourage the presence and active participation of Malaysian technologists in relevant standardization bodies, both domestically and internationally
hereinafter The Purposes
hereinafter collectively called The Purposes.
Common Commitments
Establish a stable communication channel between The Parties
Co-organize at least one event per year
Seek funding opportunities in areas of common interest identified by the Parties
hereinafter The Common Commitments
Partner's Commitments
Introduce TIOF to relevant working groups inside MTSFB
Provide opportunities for TIOF members to publish 2 articles per year in MTSFB's newsletter
hereinafter The Partner's Commitments
TIOF's Commitments
Actively participate in MTFSB working groups with at least one TIOF member
Monitor and submit if pertinent, MTFSB's Public Comments
Provide opportunities for MTSFB members and its network to use TIOF's TechUp Community for events and other activities
Provide, free of charge, a booth to MTSFB in its TechUp Community for exposure
Provide opportunities for MTSFB members and its network to publish 4 articles per year in TIOF's newsletter
Invite MTSFB members and its network to explore research opportunities for TIOF's DCDR Framework
Invite MTSFB members and its network to comment on relevant policy briefs submitted by TIOF to the Malaysian government
hereinafter TIOF's Commitments
hereinafter collectively called The Commitments.
Applicable jurisdiction Malaysia
hereinafter The Applicable Jurisdiction
For the Partner
PartnerRepresentative Name
PartnerRepresentative Title
PartnerRepresentative Signature
For The IO Foundation
Jean F. Queralt
Founder & CEO
TIOF Representative Signature
Signed on the
Signature Date
hereinafter The Signature Date
Version 1.2
This Memorandum of Understanding, hereinafter The MoU, is to be subscribed between
The Parties agree to the following relevant information:
This non-binding MoU will enter in effect immediately from Signature Date, by and between:
The Partner, a company duly incorporated in The Partner's Country with registration number The Partner's Registration and having its registered address at The Partner's Address,
and
The IO Foundation, a non-profit duly incorporated in TIOF's Country with registration number TIOF's Registration and having its registered address at TIOF's Address.
The Parties enter voluntarily this MoU with the intention of achieving the Purposes.
By signing this Agreement, the Parties agree to comply with all the Terms.
2.1.1 The Parties wish to collaborate as described in The Purposes, while at all times diligently observing The Responsibilities.
2.2.1 This MoU shall be effective as of The Signature Date and shall be valid for an initial term of two (2) years and upon expiry, it shall be automatically renewed for further two (2) years period successively.
2.2.2 This MoU may nevertheless be terminated at any time by mutual consent of the parties, where either Party provides a one-month (30 natural days) written notice of termination.
2.2.3 In any case of discontinuance, the parties will honor agreed commitments either via the accepted arrangements or suitable alternatives negotiated at that point under this MoU.
2.2.4 Upon expiration or early termination, each party shall return to the other party all Confidential Information as defined in Section 2.6 hereof, and proprietary information, documents and reference material of the other party in its possession.
2.2.5 All such obligations and terms of this MoU that are required to survive the expiration or early termination of this MoU shall survive such event including, but not limited to, those described in Sections 2.5, 2.6 and 2.7 hereof.
2.2.6 The Parties may introduce changes or updates to this MoU, which will be agreed upon by all Parties before the next automatic renewal.
2.2.7 In particular, The Parties are encouraged to review their respective Purposes and Responsibilities so as to adapt this MoU to new objectives and/or circumstances in the following cycle.
2.3.1 The Parties have appointed liaison representatives as described in Section 1.1
2.3.2 These two representatives will take charge of all interactions between The Parties. for all communications related to activities related to this MoU.
2.3.3 Any notice of termination or request for amendment of this MoU are to be communicated by the initiating Party, from their official email, to the other Party's official email with CC to all representatives.
2.3.4 Any notice under this MoU will be in writing by the initiating Party and delivered by hand or by registered mail, email, facsimile transmittal or an express mail with a confirmation of receipt, to the other Party at the registered office or as may be substituted by the notice.
2.3.5 Any notices will be effective on the date of confirmation of receipt.
2.4.1 The Parties will endeavor to set a joint agenda for the year in January of each year in aid of implementing The Purposes.
2.4.2 In addition to the foregoing, and in aid of The Purposes, The Partner will engage in activities to support the annual agenda, such as described in The Partner's Responsibilities.
2.4.3 In addition to the foregoing, and in aid of the Purposes, TIOF will engage in activities to support the annual agenda, such as described in TIOF's Responsibilities.
2.5.1 Each party or its licensor shall continue to own the intellectual property developed by it prior to or independently of this MoU.
2.5.2 By entering into this MoU, the parties undertake:
(a) Not to use each other’s intellectual property without the prior express written consent of the other,
(b) To ensure the confidentiality of such intellectual property of the other within its respective organizations, and
(c) Not to use each other’s intellectual property other than for the Purposes of this MoU.
2.5.3 The parties agree that neither of them shall gain by virtue of this MoU any rights of ownership or any other interest, right, or title to copyrights, patents, trade secrets, trade marks, or any other intellectual property rights owned by the other party.
2.5.4 Except as otherwise explicitly agreed between The Parties, any and all works developed in the course of performing obligations pursuant to this MoU and all new inventions, innovations, or ideas developed by a Party in the course of performance of its activities under this MoU will belong to that Party who develops the same.
2.5.5 To the extent such intellectual property is created, the owning Party shall grant a non-exclusive, worldwide, royalty-free license to the other Party for the use of the intellectual property solely in connection with the activities under this MoU.
2.5.6 If The Parties undertake any joint development in the course of providing services under this MoU, any such joint development will be governed by a separate agreement to be negotiated in good faith by the parties prior to the commencement of any joint development efforts.
2.5.7 Solely in connection with the activities related to this MoU and its Purposes, and subject to all applicable branding guidelines, each Party grants to the other Party a nonexclusive, worldwide, royalty free, revocable license to use its logo/trademarks in activities and communications associated with this MoU.
2.6.1 For the purpose of this MoU, Confidential Information shall mean all information marked “Confidential” or under any similar legend indicating the confidentiality of the information or information which by its nature is confidential, except such information as is
(a) previously known to the receiving Party at the time of disclosure; or (b) independently developed by the receiving Party without reference to Confidential Information of the disclosing Party; or (c) disclosed to the receiving Party by a third party without an obligation of confidentiality; or (d) already in or subsequently part of the public domain (other than as a result of a breach of this MoU); or (e) required to be disclosed by the receiving Party by law, regulation, court order or other legal process.
2.6.2 During the term of this MoU, each Party may disclose to the other its Confidential Information.
2.6.3 The receiving Party shall hold such Confidential Information in strict confidence for the disclosing Party and shall not use it except in furtherance of the relationship set forth in this MoU, or except as it may be authorized by the disclosing Party in writing.
2.6.4 The receiving Party shall further be responsible for the compliance of the foregoing by its employees or agents.
2.7.1 Each Party represents and warrants that such Party has all necessary corporate power and authority, respectively, to enter into this MoU and to perform its obligations hereunder.
2.7.2 Each Party warrants to the other Party that all materials, data, information and other assistance provided by it shall not, to the best of its knowledge, infringe third party intellectual property rights and agrees to hold the other Party fully indemnified and harmless and at all times keep the other Party indemnified against any loss, damages, costs and expenses including attorney’s fees, which may be incurred as a result of any action or claim that may be made or initiated against it as result of any action on the part of the first Party.
2.8.1 All Parties will exchange, at the signature of this MoU, their corresponding Branding Kit / Media Kit.
2.8.2 Any press release, publicity or other promotional activity issued or engaged in by either Party regarding this MoU shall be reviewed and approved in writing by the other Party prior to release.
2.9.1 The Parties will be responsible for the manipulation, in accordance to the applicable legislation, of any user data obtained, or otherwise manipulated, resulting from this MoU.
2.9.2 TIOF observes a Code of Conduct for all of its activities.
2.9.3 The Partner may suggest the use of a different Code of Conduct for the activities co-organized with, but not limited to, TIOF for activities under this MoU. Such Code of Conduct will be agreed upon by all Parties on a separate document.
3.1.1 The Parties understand that nothing herein shall be construed as a binding contract between them.
3.1.2 In the event that The Parties seek to enter into a binding contract such an agreement shall be recorded in a written agreement, hereinafter “Definitive Agreement”, duly authorized by The Representatives of The parties ().
3.1.3 The Definitive Agreement(s) shall include details of the engagement, any additional roles/responsibilities and specific work that needs to be performed by each of The Parties.
3.1.4 The parties further understand that
(i) the activities intended by this MoU may not be successfully completed; and/or
(ii) the results achieved may not be as anticipated.
3.1.5 Except for breach of confidentiality obligations and intellectual property right infringement indemnification obligations, neither Party shall be liable for any indirect, punitive, special, incidental or consequential damages arising out of or in connection with this MoU, whether for breach of this MoU or in torts, including loss of business, data, revenue, profits or for any third party claims against the other whatsoever.
3.1.6 Further, The Parties acknowledge and agree that this MoU is a non-exclusive engagement and except as specifically agreed in a Definitive Agreement with respect to an activity, nothing contained herein shall be construed as preventing or restricting either Party from pursuing any opportunity with other entities without involving the other Party or to enter into similar alliance arrangements with other entities.
3.2.1 This MoU shall not be construed to be an agency or a partnership or joint venture or an employment relationship whether for tax or for any other purpose.
3.2.2 Neither Party shall be entitled to bind the other Party with any third Party by its actions, unless it has specifically obtained the prior written consent of such other Party to do so.
3.2.3 Each Party is an independent contractor, and no provision of this MoU grants either Party any express or implied right of authority to assume or create any obligations or responsibility on behalf of or in the name of the other Party, or bind the other Party in any manner or thing whatsoever.
3.2.4 This MoU is not a commitment of financial resources.
3.2.5 Any commitment by a Party to pay fees or other amounts to the other Party must be approved in writing, by the paying Party in advance.
3.2.6 Except as may be agreed by The Parties in an applicable Definitive Agreement(s), each Party will be responsible for all expenses incurred by such Party in connection with negotiation of this MoU and any promotion, marketing or other activities under this MOU. Each Party shall be liable to pay any tax attributable to it.
The laws of Malaysia shall govern this MoU. Both parties irrevocably submit to the exclusive jurisdiction of the Courts of Malaysia for any action or proceeding regarding this MoU including, but not limited to, those related to Sections IV, V and VI of this MoU.
3.4.1 Each Party warrants to the other Party that in performing their duties required under this MoU, they will comply with the applicable law and shall take no action which constitutes a violation of applicable law and which would subject the other party to penalties under applicable law.
3.4.2 Neither party shall assign or transfer this MoU without the prior written consent of the other party.
3.4.3 This MoU supersedes all prior oral or written communication, discussions and representations communicated between the parties hereto in respect of the subject matter of this MoU. Any modification to this MoU shall only be made by way of a written document duly executed by representatives of both parties hereto.
End of the MoU
The IO Foundation,
hereinafter TIOF
with registration number
TIOF Registration
hereinafter TIOF Registration
registered in
TIOF Country
hereinafter TIOF Country
with official address
TIOF Address
hereinafter TIOF Address
with official email
TIOF Email
hereinafter TIOF Email
represented by
TIOF PIC Name
hereinafter TIOF PIC Name
with role in the organization
TIOF PIC Role
hereinafter TIOF PIC Role
with official email
TIOF PIC Email
hereinafter TIOF PIC Email
and
Partner Name
hereinafter The Partner
with registration number
Partner Registration
hereinafter The Partner's Registration
registered in
Partner Country
hereinafter The Partner's Country
with official address
Partner Address
hereinafter The Partner's Address
with official email
Partner Email
hereinafter Partner Email
represented by
Partner PIC Name
hereinafter Partner PIC Name
with role in the organization
Partner PIC Role
hereinafter Partner PIC Role
with official email
Partner PIC Email
hereinafter Partner PIC Email
hereinafter collectively called The Parties.
Partner's Responsibilities
Partner Responsibilities
hereinafter The Partner's Responsibilities
TIOF's Responsibilities
TIOF Responsibilities
hereinafter TIOF's Responsibilities
hereinafter collectively called The Responsibilities.
Partner's Purposes
Partner Purposes
hereinafter The Partner's Purposes
TIOF's Purposes
TIOF Purposes
hereinafter TIOF's Purposes
hereinafter collectively called The Purposes.
Applicable jurisdiction
Applicable jurisdiction
hereinafter The Applicable Jurisdiction
For the Partner
PartnerRepresentative Name
PartnerRepresentative Title
PartnerRepresentative Signature
For The IO Foundation
TIOF Representative Name
TIOF Representative Title
TIOF Representative Signature
Signed on the
Signature Date
hereinafter The Signature Date
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
[COVER PAGE]
ABOUT THE ORGANIZATION ABOUT THIS POLICY CODE OF CONDUCT SOLICITATION AND COMPETITION SELECTION DOCUMENTATION CONTRACT ADMINISTRATION
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
This document employs terms related to the DCDR Advocacy that can be found in the TIOF terminology.
For a structure of The IO Foundation, please visit
The IO Foundation's Organizational Chart
The IO Foundation's Organizational Nomenclature
Back to top
This document sets out the position maintained by TIOF in matters of Anti-corruption and Anti-bribery that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Human Resources Coordinator.
Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.
This document complements TIOF's Code of Conduct
This document does not form part of any Engagement Document and we may amend it at any time.
Back to top
This document directly applies to:
All TIOF Members
This document indirectly applies to:
The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all Contributors and will be used as part of the selection criteria when engaging with them.
This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
Back to top
When a submission/change is made on Qpage, a notification is sent to Slack to the corresponding #XXX-HR-Provisioning channel. Notifications will also reach the people involved in the position (their own personal email).
Member Provisioning Stages Sourcing When: When we open a position and go through all the existing leads to offer it to them. Team: Notification (?) Applicant: You have been selected for a new position + Basic Info
Applied When: When a new applicant applies for an open position. Team: Notification Applicant: Thx + Basic Info
Screening When: A candidate made first cut. Team: Applicant: Informed + extra info
Interview When: Team: Applicant:
Offer When: Team: Applicant:
Hired When: Team: Applicant:
Objective: Candidate evaluation
Day:
Selection of options based on Booking link.
Day: Monday
Rationale: Allows new candidate to be onboarded the following Friday.
Day: Friday (Last day of the week)
Rationale: Allows the new candidate to get ready during the weekend.
Day: Friday (Last day of the week)
Rationale: Closes down the relationship with the Member and turn page during the weekend.
Check the source documents.
Check the source documents.
Value | Criteria | Implication |
---|---|---|
Not even close
Reject
Not suitable candidate
Reject
Not too suitable
Reject or Accept
Suitable candidate
Accept
Total fit
Accept
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Source: From where the funding will come from
Opportunity: The funding opportunity itself.
Source is not in the blacklist
Source has been verified
Does not enter in conflict with Mission
Does not enter in conflict with Vision
Does not require compliances in quotas in TIOF of any sort
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
The following section provides a comprehensive list of Teams and their descriptions.
A full taxonomy of TIOF Teams can be found in the Organization's Taxonomy.
A full list of TIOF Members can be found in the Organizational Chart.
Interested in joining The IO Foundation?
Check the Open Positions in our Career Site.
Teams are used to structure communications across their members, for applications such as
Calendars
Group messaging
Teams are sometimes referred as Groups in certain platforms.
For more information. refer to each platform's documentation.
The following skills are expected and/or hoped from any TIOF Member:
Managing team members, coordinating tasks and ensuring smooth operations overall.
Ensuring that the initiative remains law-abiding at all times.
Specific Skills
Related Policies
Related Handbooks
Human resources are key to recruitment, onboarding, and internal communications. The human resources team allocates company policies and procedures, provides assistance in the form of coaching and mentoring, and facilitates the workforce.
Helping us find the best team members and assist them in their tasks.
Human Resources facilitates and manages the workforce, sets policies and procedures in place, and provides coaching/mentoring as and when needed. HR also includes 3 functions Recruitment, Onboarding and Community management. The Recruitment function includes advertising for open positions, interviewing and selecting appropriate candidates. The Onboarding process ensures that each new joinee gets an orientation to the Project and the general tools used for communication and task management. The Community management function ensures the engagement and involvement of all Project members through internal communications. The HR team is involved at every step with each team member and is always available to answer any queries or concerns.
Specific Skills
Related Policies
Related Handbooks
Helping grow our network of collaborators worldwide.
Specific Skills
Related Policies
Related Handbooks
The team that provides the architecture for the IT infrastructure based on the Project requirements, and is responsible for implementing and maintaining it.
Keeping the project tech gears properly greased.
"In charge of architecting, implementing and maintaining the necessary IT infrastructure for The IO Foundation and its projects. "
Specific Skills
Related Policies
Related Handbooks
Helping the project stay financially sound and transparent.
Specific Skills
Related Policies
Related Handbooks
The Resource Allocations Team supports the sustainability of Project Lockdown by developing revenue models and identifying funding opportunities. The team creatively sources and pursues leads that are aligned with the project's values and objectives.
Making it possible for this initiative to keep creating impact.
Specific Skills
Related Policies
Related Handbooks
The User Experience/User Interface (UX/UI) team is crucial to maintaining user experience across all project related platforms. The team ensures that the UX perspective is taken into consideration in different parts of the system planning and design.
Making eyesores a thing of the past & creating the best experience.
UX/UI Team's aim is to ensure a high user experience throughout the user journey and across platforms related to the project.
Specific Skills
Related Policies
Related Handbooks
The Communications team is in charge of promoting Project Lockdown's goals across various platforms. The Comm team must work to maintain user interaction, advocate PLD’s mission both externally and internally, and serve as a source of contact for the public and the media.
Bringing the project to various audiences for further outreach.
Team Comms aims to promote Project Lockdown and its mission across different platforms, interact with its users and serve as a point of contact with the public and the media.
Specific Skills
Related Policies
Related Handbooks
The Developers team is responsible for developing and maintaining code-related solutions to the project. The team must work to implement features that will successfully work as requested by other teams.
Making the application more awesome in both back-end and front-end.
The aim of the team is to develop and maintain solutions that relate to code, making sure that the features and ideas desired by the other teams get implemented and work in a stable and fruitful manner.
Team Description
Specific Skills
Related Policies
Related Handbooks
The Documentation team’s duties consist of preparing any written materials that are necessary to PLD. Working across all teams, the documentation team must collaborate with a variety of PLD volunteers in order to develop internal guidance documents, operation manuals, etc.
Helping make our project accessible and easy to understand for all.
The Project Lockdown Documentation team develops standard operating procedures, internal guidance documents, operational manuals, and many other types of written materials. We work with the TIOF director, the project manager, and all PLD teams to create, or assist in creating, written materials that are needed for our project.
Specific Skills
Related Policies
Related Handbooks
The research team is comprised of two separate divisions; Editors and Data Science.
The Data Science team’s main focus is on data-related projects at PLD. The team is responsible for researching new interventions against COVID-19, defining dataset layers, and establishing standards for codifying human-rights violations.
The Editors team is at the front-end of researching, verifying, and encoding data related to the NPIs that are being tracked. Using official government documents as sources (that are thoroughly verified), the team will research how government measures and legislation has affected the legal status of a territory.
Specific Skills
Related Policies
Related Handbooks
𝗧𝗲𝗮𝗺 𝗘𝗱𝗶𝘁𝗼𝗿𝘀: Researching sources, encoding data points and reviewing it for a solid database. Human Rights are at the forefront of everything we do on the editing team; we are Human Rights Advocates who research, verify, and encode data to provide up to date, accurate data that tracks all of the Non-Pharmaceutical Interventions (NPIs) implemented globally. We are responsible for researching every territory in detail to gain a picture of the legal status of the territory, and a comprehensive timeline of events in terms of government measures and legislation. We work at national, as well as divisional, or regional levels, to understand fully how a territory is responding to the Covid-19 pandemic. Sources are all verified and whenever possible, are obtained from official Government documents. All the information contained in the source relevant to our database is encoded and is then automatically displayed on the Project Lockdown website.
Specific Skills
Related Policies
Related Handbooks
𝗧𝗲𝗮𝗺 𝗗𝗮𝘁𝗮 𝗦𝗰𝗶𝗲𝗻𝗰𝗲: Shaping our data points to create positive impact. Team Data Science is comprised of dedicated and qualified volunteers in the fields of data science, human rights, and statistics. The focus of our work is on data-related projects at Project Lockdown. Currently, the Data Science Team is responsible for a host of work, ranging from researching new interventions against COVID-19 and to defining dataset layers, to establishing standards for codifying human-rights violations and reaching out to other researchers and COVID data users. The Data Science Team is constantly taking on new projects and establishing novel additions to Project Lockdown, as we work together to present the world with clear and transparently-sourced lockdown data.
Team Description
The Data Science team is comprised of dedicated and qualified volunteers in the fields of data science, human rights, and statistics. The focus of the Data Science team is on data-related projects at Project Lockdown. Currently, the Data Science Team is responsible for researching new interventions against COVID-19, defining dataset layers, establishing standards for codifying human-rights violations, reaching out to other researchers and COVID data users, and more. The Data Science Team is constantly taking on new projects and establishing novel additions to Project Lockdown as they work together to present the world with clear and transparently-sourced lockdown data.
Specific Skills
Related Policies
Related Handbooks
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Lead Collection >> Lead cleaning >> Opportunity Generation >> Exploration >> Closure (back to Opportunity Generation on an X basis).
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Migrate all contents from:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Date & Time Management
This document describes the tools used by TIOF members to manage their schedule, meetings and other time-related activities.
General Structure (Outdated)
For practical reasons, the deadline is established on recurrent 3rd Friday of the month.
This should provide ample margin to all TIOF Members to set their own schedule.
>> Compliant with Policy number XXX
The following are a list of platform and tools that TIOF Members have access to for their time management.
Used by individuals to store and reflect a member’s schedule.
Used by Department and Teams to reflect collective activities
Used to Intranet@TIOF to publish global organization activities
Used to Intranet@Project to publish global project activities
Used by Contact to publish public activities
Find infrastructure information about this platform here.
CALENDAR CODING???
Task: Blue
Red: Deadline
Purple: Guest schedule and details
Used to
Offer booking calendars
Converts any entry on Google Calendar into an alarm automatically.
Check some other member’s or Team calendar Every TIOF calendar is available INSIDE the organization (it can never be shared publicly to non-members).
How to proceed? Add the corresponding calendar with + and subscribe. Use the user’s account email or the specific calendar ID (see reference list).
What can I see? In general, you will only be able to see the free/bus status of a calendar, not the details. If you are a member of a particular event you will be able to see all the available information.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
In order to better understand the contents of this document, it is recommended that you are familiar with the following materials:
CI/CD Policy / Procedure
Member privileges
Base permissions: NONE
See JFQ Workspace
Please refer to the Tags Handbook.
Owner: TheIOFoundation
Repository Name: Follow convention
Description: Follow convention
Public / Private
Establish rule
Initialize this repository with:
Public
Private
Add Readme file
Grant your Marketplace apps access to this repository
Public
Private
None
Social Preview
ON Restrict editing to users in teams with push access only
ON Issues
>> Set up Templates
ON Sponsorships
>> Set up Sponsorships
OFF Projects
ON Preserve this repository
ON Discussions
Merge Button Section
ON Allow squash merging
ON Automatically delete head branches
OFF Sponsorships
ON Restrict editing to users in teams with push access only
OFF Preserve this repository
Merge Button Section
ON Allow squash merging
ON Automatically delete head branches
Create Labels
Use the Label management scripts for this.
>> See Global #Tags
Branches:
Set Nomenclature convention
Commits
Add proper COMMIT MESSAGE (description)
Issues
https://guides.github.com/features/issues/
Creating Issue templates
Pull Request
Creating PR templates
https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
Include the following items:
https://github.com/TheIOFoundation/ProjectLockdown/community
(sample repo)
Code of Conduct:
Make it to the Wiki
+ CoC as per Gihub here: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project#adding-a-code-of-conduct-manually
Current idea:
Very likely we are better off creating Teams per Team + Subteams per Permission Type
Example
[TIOF PLD] Team Devs
[TIOF PLD] Team Devs - Triage
[TIOF PLD] Team Devs - Write
[TIOF PLD] Team Devs - Maintain
[TIOF PLD] Team Devs - Admin
That way we can keep granularity as we can’t assign these Permissions on a user-basis if they are in a Team and doing so would make it more complicated to track who can do what.
Each label type should be represented by a specific color code according to their category. See table below.
Project
ORG
PLD
UDDR
BiT
Team:
(List of teams)
Level:
Coordinator
Deputy
Member
@@@Pending missing
Module:
PLD
API
DB
DEI
MAP
WEB
Version
Position
Staff
Volunter
Keywords
Collection of any other labels needed that may help
Priority
Critical
High
Medium
Low
Type
Bug
Enhancement
Error
Question
Need:
Position
Tool
Funding
Categories
Custom Fields
Lat
Long
Due Date
Documentacion sources
https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/about-labels
Project coding guidelines
Comments
Diagrams
Unit tests
https://guides.github.com/features/mastering-markdown/
https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md
https://medium.com/hackernoon/12-cool-things-you-can-do-with-github-f3e0424cf2f0
Use your official TIOF profile picture any time possible
(Mandatory for TIOF Staff)
You can have your own TIOF/PLD GitHub account if you will. It depends on you.
Bio (only allows 160 characters)
Organization
The IO Foundation
[TIOF] Project Lockdown
Location (optional)
Email: TIOF/PLD email
Link: Preferably LinkedIn others also can
Twitter: In applicable
Organizations:
Should appear automatically
To evaluate
Visual Markdown Extension
https://ckeditor.com/github-writer/
https://github.com/ohbarye/github-issue-creator
https://chrome.google.com/webstore/detail/quick-add-issue-to-github/mgamfhobfmlghohfjdiecjhddoigenkk
https://chrome.google.com/webstore/detail/awesome-autocomplete-for/djkfdjpoelphhdclfjhnffmnlnoknfnd
https://chrome.google.com/webstore/detail/github-hovercard/mmoahbbnojgkclgceahhakhnccimnplk
https://chrome.google.com/webstore/detail/better-pull-request-for-g/nfhdjopbhlggibjlimhdbogflgmbiahc
https://chrome.google.com/webstore/detail/file-icons-for-github-and/ficfmibkjjnpogdcfhfokmihanoldbfe
https://chrome.google.com/webstore/detail/refined-github/hlepfoohegkhhmjieoechaddaejaokhf?hl=en
https://github.com/marketplace/github-learning-lab
https://github.com/marketplace/gitlocalize
https://github.com/marketplace?query=signature
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
The preferred order is
TechUp Space
Google Meet
Proposed by 3rd party, in case of legitimate reasons (see Exceptions)
Please note that some platforms may not be acceptable for technical reasons.
The following platforms are not authorized to be used by TIOF Members
Please follow the instructions on the Documenting Interactions Handbook.
Current application: Google Docs
Please note that the Organization is seeking realistic alternatives to replace this product.
Where
Text
The following document is released under The IO Foundation’s Productions License for Text in accordance with its Intellectual Property policy.
Current application: Google Sheets
Please note that the Organization is seeking realistic alternatives to replace this product.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Send all releases to newsroom@digitalnewsasia.com
CC to Karamjit
Include
pixs of the spokepersons
visual of whatever event happened
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
[PROD] [ADM] [NOTICE]
Templates - DO NOT POST WITHOUT A TEMPLATE.
Review the instructions on top & remove when ready to publish
Follow each of the segments of the Template
If your Issue is ready, please make sure to label it as Stage: Ready
Project Lockdown adopts a sane label approach to provide more structure and clarity to the different project tasks that are published.
The more important Labels types are:
Need: Illustrates the nature of the need described in the Issue. Issues are primarily organized by Need.
Stage: Determines the implementation phase in which the Issue is at present time.
Module: Indicates which module is the Issue related to.
Other relevant Labels are:
Priority: Sets the corresponding degree of urgency to solve the Issue.
Keyword: Lists specific technologies that the Issue requires.
A complete list of Labels and their usage can be found on the wiki: How to participate > Labels
For code-related issues If you are not already, please familiarize yourself with GitHub's flow https://guides.github.com/introduction/flow/ Check the list of code-related issues: [Need: Code + Stage: Ready]
For other type of needs All Issues have instructions on how to proceed to implement them. Should you have any doubts, please open a Q&A Discussion. Check the list of code-related issues: [Need: Code + Stage: Ready]
You can find all necessary information to learn about Project Lockdown, its technical documentation and all you may need to collaborate in the initiative in our wiki: Project Lockdown:
We strive to provide all the information you may need. If there is anything you feel is incomplete or not sufficiently explained please reach out to us by opening an Ideas Discussion.
As a representative of Project Lockdown, Members enjoy the opportunity to participate in events. We do this through sessions in which we participate as well as events that we organize ourselves. This comes with the unavoidable responsibility of behaving in a way that respects the TIOF Internal Code of Conduct and also to “label” themselves adequately.
The following are nomenclature guidelines to follow by all Members participating in an event while representing Project Lockdown.
Name
[TIOF PLD] {Name}
Title/Position
Indicate your position in the organization or project team.
For instance:
Program Manager
Team UXUI Coordinator
Team UXUI
(avoid using “member”)
Organization naming
Your organization naming will depend on which organization unit you are attached.
If you are a member of TIOF
The IO Foundation
If you are a member of Project Lockdown
[TIOF] Project Lockdown
g0v Summit
Project Lockdown: Using data to assess the impact on human and digital rights as a result of Covid-19 related Government measures
Abstract:
Human and digital rights have been greatly impacted by the various Covid-19 related measures that governments around the globe have implemented. Project Lockdown provides a mapping platform and an open API to explore and better understand the effects on people's rights within a territory, and importantly across territories over time. This panel discussion explores the deep ramifications of government policies across populations, the differences and anomalies in implementations and how our tools provide precise, time-sensitive snapshots that can be used for advocacy and awareness-raising, and ultimately to hold government policy makers to account. In relation to human and digital rights, we will identify positive deviants and contrast the often stringent sudden 'lockdown' measures with the gradual phased approach to easing of measures, and subsequent knee-jerk re-implementations.
Bread & Net
Stimulating citizen awareness and action for rights during a global crisis
Format: Workshop
Language: English
Duration: 90 minutes
Presenters:
Ruha Thurairatnam (Project Manager)
Julie Green (Research Coordinator)
Jean F. Queralt (Global Coordinator)
Proposal:
The speakers will present Project Lockdown’s mapping platform and how to use it and will share demos of future developments and features. We will also take some time to hear from the audience and to discuss strategies for how you might use the platform, and what you might want from the platform to support your own work.
Objective:
We hope to offer our curated data on government measures in response to the COVID-19 pandemic for use by human rights and media organizations in the region. We would also like to explore potential collaborations with organizations in the region to further develop a dataset layer on contact-tracing apps and digital surveillance.
Event Workspace
Assess who can attend
Assess needs from Teams
Establish tasks
Slack
If the organizers have Slack workspace:
Join
Create a project channel
Invite Coordinators
Invite rest of Members as per assessment
Identify channels where we should have presence
GitHub
Make sure necessary Issues are created and TAGGED.
Switch from text intensive to Image-intensive
User PLD templated Google Slides
Slides prepared must come with NOTES
Prepare a backup replacement in your team
Slides to be approved by Comms & PM
Prepare fillers for
Extra time
Silences
Prepare audience infiltratio
Questions for Q&A that WE want to answer
Rehearsal
To change in current slides:
MORE CLARITY on the Rights orientation
Synopsys of MOTIVATION
Break monotony ->
Videos
Activities
Surveys
Audience participation
Post summary on website
Thank the organizers
Post on SocMed
Distribute participation in different fora
Ask Team Coordinators which events they would like to participate into.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Abstract
TIOF general Dev Guidelines
Project Lockdown specific Dev Guidelines
Additional information
Projects in TIOF use Milestones to establish relevant deadlines in order to structure their implementation.
Milestones are created and maintained by:
TIOF Management
Project Managers
Milestones are organized in 2 levels:
Organization-wide These Milestones apply across all the organization and are to be observed mainly by TIOF's organization core as well as Project Managers.
Project-wide These Milestones apply specifically to a given TIOF Project and are to be observed by all Project's Teams.
Templates
Labels
Pinned Issues
When creating a new Feature
Create a Root Issue
List all subtasks as Tasks Markdown)
Create the necessary Issues for each task and populate them with the necessary information as per template.
Add the Issue # to the Root Issue (@@@ Look into automating this. Should be doable.)
Pull Requests
Templates
Back to top
ShortURL | Playbook | Assistant | Slides Repository
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
A note on localization Each document may have been translated into different languages. Check the Language Marker in the file name. Structure
This is the general document, which establishes the global guidelines of Comms in the whole organization.
Project-Specific SOP Each Project has its own guidelines/SOP that are to be followed on top of the Global Guidelines and establish particular parameters that only apply to that Project.
Adding new presence platforms Update the corresponding document (section “List of platforms”)
Content Guidelines
As Project Lockdown begins outreach to its target audience, it’s important for the voice and tone of the PL’s social media presence to be consistent and accurately convey the project’s values and objectives.
What is Voice?
“...voice is the purposeful, consistent expression of a brand through words and prose styles that engage and motivate. It’s true: The personality of your brand is determined, in large measure, by the words you use and the sentences you write.”
Target Audience
The target audience consists of users searching for clarity, objectivity, and reliability. The voice of PL on any platform should respond to these goals.
Voice & Tone
The voice of Project Lockdown remains the same, while the tone can change a bit depending on the subject matter being addressed. To avoid confusing messaging, the following is what PL should not sound like, no matter the context:
Playful: The subject matter of PL is serious, and social media communications should respect this. Witty: PL aims to provide information and empower users through knowledge - there’s no need to infuse messages with superfluous personality that doesn’t add to this objective. Persuasive: PL is a neutral, bi-partisan platform and it’s crucial that social media communications make this clear.
When writing for Project Lockdown, we should sound:
Helpful and responsive, but not overly personal Objective and matter-of-fact, but not cold or curt Honest and clear, but not blunt or robotic
For Example:
Helpful and Responsive
Tweet this: Project Lockdown has updated the platform with several new features based on user feedback: (list features).
Not this: Hurray! New features are up on Project Lockdown, check it out.
Objective and Matter-of-Fact
Tweet this: The latest data compiled shows a number of countries in Asia scaling back on COVID-19 lockdown measures including China, where the virus was first reported.
Not this: Should China have scaled back lockdown measures so soon? Data shows restrictions already being lifted in the pandemic’s epicenter city of Wuhan.
Honest and Clear
Tweet this: South Africa, Nigeria, and Kenya have implemented martial law in the past 36 hours.
Not this: Increased restrictions are being reported in Africa.
Twitter Best Practices
“Brands come to Twitter to be what people are talking about right now. And because people are in a discovery mindset when they’re on Twitter, your brand or business is likely to leave a lasting impression.”
Twitter is an ideal platform for communicating concise, relevant content to users in an approachable way that allows for maximum user engagement. To best utilize Twitter for Project Lockdown, we want to keep the following Do’s in mind:
Do:
Post consistent, relevant information Write out abbreviations. Ex. NPIs (Non-pharmaceutical Interventions) Respond in a timely matter to user questions or comments Incorporate the PL voice in each Tweet and response Tweet like you speak to others in a professional context to avoid being overly robotic or personal Always link to relevant information on the PL site Clarify questions or information when needed and redirect potentially biased responses to neutral data sources
Don’t:
Respond in a confrontational manner to user questions or comments Use confusing jargon or terminology without elaborating or clarifying Link tweets to unverified or potentially unreliable information Ignore communications regarding the potential in inaccuracy of information on the product: PL is open to suggestions and corrections Infuse tweets with the personality of the individual tweeting or replying Use emojis or humorous GIFs
Style Guide
To ensure consistent and clear copy, adhere to the following grammar mechanics and best practices:
Basic Rules
Use active voice instead of passive Be mindful of all users, who have varying prior knowledge and come from different backgrounds Keep it simple and consistent Maintain a neutral, unbiased voice
Pass to Dooly Playbooks
Register data
Create necessary media, store in its own Channel folder in Repository > Project Identity
Always use the main account to be the Owner of the account.
Create Shortlink (@@@See Handbook)
Add Shortlink to AboutUs (@@@See Handbook)
Create corresponding Media Channel Procedures Wiki page when necessary (@@@See Handbook)
HR Communications (HRCom)
Iconography:
Each
Organization in the TIOF Network
Initiative
must have
Introduction to audiences
Presentations [Slides]
A repository of slides + ShortURL
Naming
[{ORG} {INITIATIVE}] Comms [I] Slides Repository {LANG} {VERSION}
ShortURL
https://TIOF.Click/{ORG/INITIATIVE}SlidesRepo
A general introductory presentation + ShortURL
Naming
[{ORG} {INITIATIVE}] Comms [P] {ORG} Organization Presentation {LANG} {VERSION}
[{ORG} {INITIATIVE}] Comms [P] {INITIATIVE} Initiative Presentation {LANG} {VERSION}
ShortURL
https://TIOF.Click/{ORG/INITIATIVE}Presentation
Presentations [Video]
Source of page: https://docs.google.com/document/d/1fjgsKHfU7qQC2Q0dkLtVuMRnnCI3_XAInawCvQvgsAs/edit#
For more i
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
The following is a complete list of channels in which The IO Foundation has presence.
IMPORTANT
The IO Foundation uses the below listed channels, and only these. Any other channel not listed in this page cannot be considered official and TIOF does not take responsibility for anything posted or shared in it.
Likewise, personal channels owned by TIOF Members do not represent the organization's views.
For any information on how to use these channels, please refer to their corresponding Handbook.
Should you find any other channel impersonating The IO Foundation, please do not hesitate to let us know: Contact@TheIOFoundation.org
The following is a list of internal channels used exclusively to communicate among TIOF Members.
The following is a list of official channels through which The IO Foundation posts and shares content derived from its advocacy and its initiatives.
The IO Foundation has profiles in other platforms, sometimes in preparation for its use, sometimes to avoid impersonation.
The following is a list of official channels where The IO Foundation has presence without regularly posting content.
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
https://docs.google.com/spreadsheets/d/1Q4CSDg3Vg-M7I5pENX1pxPDJckT8H0E2Rrxz2QTZb2g/edit#gid=0
Link to Requisition form: https://docs.google.com/forms/d/e/1FAIpQLSfUOuTHpqLD1i7XDXmgvN1se1-9WfL_FcNKwCCnQg9_rzGqQQ/viewform
Go to TIOF main repo Labels: https://github.com/TheIOFoundation/TIOF/labels
Create new Tag, following existing code convention (Naming, color, description)
Dry run Tag replication to all TIOF repos with github-sync.js
node github-sync.js labels -s TheIOFoundation/TIOF -t TheIOFoundation --token [INSERT TOKEN] --dry-run
If all correct, execute Tag replication to all TIOF repos with github-sync.js
node github-sync.js labels -s TheIOFoundation/TIOF -t TheIOFoundation --token [INSERT TOKEN]
Enjoy
Name | URL | Usage |
---|---|---|
Documentation | ||
---|---|---|
Channel | Full URL | ShortURL |
---|---|---|
Channel | Full URL | ShortURL | Status |
---|---|---|---|
Channel | Full URL | ShortURL |
---|---|---|
Channel | Full URL | ShortURL |
---|---|---|
This documentation page is under construction. Should you want to be notified once it's published, .
Field | Description | Responsible | Source |
---|
Icons
Name of the tool
Slack
VBout
Slack
Join Slack
Youtube
Rumble
GAB
Github Sponsors
Telegram
Minds
N/A
tumblr
N/A
N/A
Locals
N/A
Medium
N/A
MeWe
N/A
Gettr
N/A
Twitch
N/A
Odysee
N/A
Open Collective
N/A
Patreon
N/A
Meetup
PENDING
N/A
Eventbrite
N/A
Humanitix
N/A
Gitcoin
N/A
Giveth
N/A
Substack
N/A
DemocracyLab
PENDING
N/A
Codeberg
N/A
HasGeek
N/A
Parler
N/A
Crunchbase
N/A
Peatix
N/A
TIOF Career Site
https://Join.TheIOFoundation.org
Handshake
N/A
Upwork
PENDING
N/A
Monster
PENDING
N/A
Name | Name of the product | Purchaser | CRM |
Icon | Icon | Purchaser | Storage |
What | What does it do? | Purchaser | Request |
Why | Why is it useful? | Purchaser | Request |
Where | Where to find it? | Infrastructure | Dashboard |
CTA | Call To Action | Purchaser | Template |
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
Channel types
Templates
Request
Playbook
This page provides all the information necessary to understand and execute a Campaign.
ShortURL | Playbook | Assistant
NOTICE
Campaigns are used to inform the network about relevant information or entice a reaction from it.
Training will be implemented as soon as the Campaign and its materials are ready.
Standardized materials to execute the Campaigns are available in the repository.
Follow the instructions in each Campaign's SOP.
Field | Description | Responsible | Source |
---|---|---|---|
This documentation page is under construction. Should you want to be notified once it's published, .
Code | Name | Description |
---|
If a new type of Campaign is deemed necessary, it can be requested through the .
Approval and implementation will be discussed primarily during the yearly . Should there be any emergency, if can be requested to be discussed during an upcoming .
Who
Who has been featured
Proposer
Request
What
What does it do?
Proposer
Request
Where
URL of the release
Proposer
Request
CTA
Call To Action
Comms
Template
Notifications |
[TIOF] NIP | Notification of Internal Product | Informing that a new product is available. |
[TIOF] NMR | Notification of Media Release | Informing that TIOF has been featured in media. |
[TIOF] NUE | Notification of Upcoming Event | Informing about an upcoming event (from TIOF or 3rd party). |
[TIOF] NIA | Notification of Important Announcement | General announcement deemed important. |
[TIOF] NSHOUT | Notification of Shoutout | Giving a shoutout. |
[TIOF] NEO | Notification of External Opportunity | Informing of a opportunity that has presented from a 3rd party. |
Calls |
[TIOF] CFADV | Call for Advisers | Seeking for members for the Board of Advisers. |
[TIOF] CFDIR | Call for Directors | Seeking for members for the Board of Directors. |
[TIOF] CFINT | Call for Interns | Seeking interns. |
[TIOF] CFEMP | Call for Employees | Seeking to fill up an employee position. |
[TIOF] CFVOL | Call for Volunteers | Seeking volunteers. |
[TIOF] CFF | Call for Feedback | Seeking for feedback from our beneficiaries. |
[TIOF] CFD | Call for Donations | Seeking financial an in-kind support. |
[TIOF] CFL | Call for Leads | Seeking information on a topic, a connection, etc. |
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
ShortURL | Playbook | Assistant
NOTICE
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
This Handbook responds to the following Policies:
Information Management
Intellectual Property
This document provides all the guidance to produce documentation for The IO Foundation and its initiatives.
In this documentation, the term Entity refers to either:
The IO Foundation
An organization member of The IO Foundation's Network
An initiative run by any of the above
The IO Foundation relies on the following tools to provide its documentation services:
In the interest of consistency, The IO Foundation structures its documentation following this structure:
About Provides all the information needed to understand this Entity and its objectives.
Introduction Explaining what this Space is about.
Theory of Change Explaining what is the identified problem and what is the proposed solution.
Business Plan Explaining the details on the Business Plan for this Entity.
Status A quick overview to the current implementation status of this Entity .
Repository Explaining the structure of the repository hosting this Entity .
Media Kit Providing all the necessary Comms information for this Entity .
Terminology Providing definitions for all the specific terms used in this Entity.
Frequently Asked Questions Answering some of the most common doubts related to this Entity.
Join Us Explaining how to join and collaborate with the Entity.
Support Us Explaining how to support the advancement of the Entity.
Acknowledgements Indicating specific recognitions to notable contributors to this Entity.
Media Archive Listing the mentions this Entity has had in media over time.
Institutional Provides all the information relative to organization and guidance for this Entity.
Research Provides all information relative to research undertaken in this Entity.
Operations Provides all the information relative to the implementation of this Entity.
CUSTOM Depending on the needs of the Entity, custom sections will be made available. An explanation of these will be provided in the Introduction page of the Entity.
Some variations may happen depending on the specific needs of the Entity.
Equally, each of these sections may have sub-sections according to the specific needs of the Entity.
Please refer to the corresponding Space Structure section on the corresponding Entity.
Most pages offer a Quickbar at the top providing with relevant shortcuts to:
The ShortURL for the page
The Playbook linking this page
The Tarian Assistant for this page
ShortURL | Playbook | Assistant
When one of the shortcuts is not an active link, the information may be missing. Please report it.
Indicates in which
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
Once a page is Ready, its icon signals the type of information it contains and the audience it is meant for.
When listing a number of items in a sequence, avoid using a coma (,) before the last one.
Example
Preferred: Tom, Luisa and Jenny when to first to the mountain, then to buy ice cream and finall back home.
When listing a series of items, do not end them with punctuation unless it's a question. As a general rule, try to avoid exclamation marks.
Example
This is one item
This another item
Maybe this would be a third item?
I am sure this is the fourth!
Type | Product | Usage |
---|---|---|
Shortcut | Status | Description |
---|---|---|
Icon | Meaning | |
---|---|---|
Icon | Meaning | Description |
---|---|---|
Documentation Manager
Gitbook
Consolidates all the documentation across all the platforms.
Documentation storage
Github
Stores all the documentation.
Short URL manager
Bl.ink
Provides with reusable shortURL to important documentation pages.
Playbooks
Dooly.ai
Provides an easy way to access relevant documentation when taking Notes.
Assistant
Typebot
Provides an interactive interface to assist with tasks described in the page.
Active
This shortcut is ready to be used.
Shortcut
Inactive
This shortcut hasn't been configured.
Shortcut
Not applicable
This page does not have this shortcut type.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Useful Chrome extensions
Find something similar: https://chrome.google.com/webstore/detail/hoverify/bbpokcagpggnekcmamgdieebhpkjmljm
@@@ Link to TIOF' Repo
@@@Add
- Package.json
Comment using "scriptsComments": { "FIELD": "COMMENT" },
{ "name": "package name", "version": "1.0", "description": "package description", "scripts": { "start": "npm install && node server.js" }, "scriptsComments": { "start": "Runs development build on a local server configured by server.js" }, "dependencies": { "ajv": "^5.2.2" }, "dependenciesComments": { "ajv": "JSON-Schema Validator for validation of API data" } }
Source: https://stackoverflow.com/questions/14221579/how-do-i-add-comments-to-package-json-for-npm-install
- TIOF Labels
<a href="#top">Back to top</a>
# Project Lockdown specific Dev Guidelines
- PLD Labels
<a href="#top">Back to top</a>
# Additional information
<a href="#top">Back to top</a>
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
The following section describes in detail each and one of the positions existing in the organization for TIOF Members.
All TIOF Members are expected to have proficiency on the following tools and skills.
These Mandatory Skills need to be fulfilled by any TIOF Member candidate.
All TIOF Members are expected to have proficiency on the following tools and skills:
While these Desired Skills do not need to be fulfilled by any TIOF Member candidate, they will be considered as an advantage during their evaluation.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Locations: Patreon, Github Sponsors
🥉 Bronze TIOF Sponsor
€400 per month
Helps support TIOF in its advocacy. Company logo will be included in
TIOF website Funders page
Will receive quarterly newsletter with advocacy progress (optional)
🥈 Silver TIOF Sponsor
€800 per month
Helps support TIOF in its advocacy. Company logo will be included in
TIOF website Funders page
Will receive quarterly newsletter with advocacy progress (optional).
🥇 GOLD TIOF Sponsor
€1,600 per month
Helps support TIOF in its advocacy and hire staff on initiative/activity basis. Company logo will be included in
TIOF website Funders page
Materials related to the projects it helped fund
Will receive financial reports on the use of the donation (optional). Will receive quarterly newsletter with advocacy progress (optional).
💎 DIAMOND TIOF Sponsor
€2,400 per month
Helps support TIOF in its advocacy and hire staff on permanent basis. Company logo will be included in
TIOF website Funders page
Materials related to the projects it helped fund
Will receive financial reports on the use of the donation (optional). Will receive quarterly newsletter with advocacy progress (optional).
💖 CORE TIOF Sponsor
€3,200 per month
Helps support TIOF in its advocacy and hire staff on permanent basis. Company logo will be included in
TIOF website Funders page
TIOF website Main page
Materials related to the projects it helped fund (priority positioning)
Will receive financial report on the use of the donation (optional). Will receive quarterly newsletter with advocacy progress (optional).
🚧
Work In Progress
Pages that are empty will have a notice as shown below.
👌
Usable
👍
Ready to publish
Hot topic
Pages that have recently been created, updated
Requesting deletion
<OTHER> (See Page Type)
Published
🎯
DCDR Key concept
Contains concepts that are core to the DCDR advocacy.
Policy
Handbook
📢
Comms
Contains information relevant for communications.
Technical
Contains technical reference information.
.ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
This process document explains the file naming conventions for documents and media.
This document is used by all members of the TIOF organization when creating documents, setting them up for review, and storing them for access by teams or the entire organization.
This document is also to be used by project members when naming project files.
All files in the organization are to follow the standard file naming conventions.
This policy only applies to TIOF files created after the date of approval at the end of this document. A retroactive application of this policy may be implemented for existing documents, as necessary, in the future.
This document applies to internal TIOF files at the foundation level and at the project level.
This document does not apply to or cover the naming of shared drives. Standard names for shared drives are covered in a separate document.
The formatting for a file name, at TIOF level or project level, is as follows, with the optional parts in grey.
[ORG INITIATIVE] Team [Privacy Level] {DATE} {Organization Label} {Document Identifier} Content {Content Parameters} Language Version {SIGNED}.extension
Notes to evaluate
Prior to a document being finalized and stored, you can use version names
in the filename to indicate where the document is in the development cycle. Use these lifecycle indicators with the version number.
v0.1 In Progress (or IP - for a document in an early or late draft stage)
v0.1 In Review (or IR - for a document people are reviewing or commenting on)
v1.0 Routing (meaning routing for approval/signature)
For all files, the title must reflect and include the name of a standard type of file used in the organization. Standard file types, including standard documents used in TIOF, are stored in an approved list. See your manager/coordinator to access the approved list.
Team Finance
Important considerations:
When scanned together, Invoice and Receipts are to be duplicated at file level. When paid together (which is not encouraged), each invoice is to be duplicated at file level.
Examples
Team UXUI
The file naming format is the same for images except the following must be added, altogether in one set of brackets and separated by dashes, after the title: Image Type, Color Scheme, Transparency, Size.
Note: The department code for images should always be Comms for Communications.
Example: [TIOF] COMMS [P] Sharon Smith ProfilePic [C-BW-T-S] XXX v1.0.jpg
SQ (Square)
Hex (Hexagonal)
C (Circular)
FC for TIOF Full Color Scheme
BW for Black&White
T for transparent
NT for Not Transparent
Small (equal to or smaller than 300 X 400 pixels)
Medium (between 300 X 400 and 600 X 800 pixels)
Large (greater than 600 X 800 pixels)
[TIOF DCDR] Research [I] Research Procedure ENG v1.0
[TIOF PLD] UXUI [I] UI Element Specification ENG v1.5
[TIOF PLD [P] Operational Framework Diagram ENG v1.0
[TIOF PLD] Devs [I] Sys Architecture Diagram XXX v1.3
[TIOF BiT] Finance [I] GPD for Evidence Survey in Malaysia Invoice ENG v1.0
[TIOF] ORG [C] Certification for Benevity ENG v1.0
How to Version Up a Final Document
Increase the decimal point (use a fractional number) for new documents in which changes were minimal or not of great importance.
Go to the next whole number for new versions that have a great number of changes or changes of significant impact
For the TIOF-level regulated (governing) documents (policies, processes, SOPs) , the final version numbering is determined by the Regulated Documents Coordinator.
For project-level regulated documents (policies, processes, SOPs) and all managed documents (at any level), reference the current document to know how to version up.
Note: For marketing and other publicity materials, such as brochures, consider leaving off the version number but adding the year in the optional date position.
Refer to eSignature the procedure to eSign a document.
If a document requires a signature, add the word SIGNED at the end of the document after the document has been reviewed and electronically signed.
The file extension is automatically added to the file by the application in which it is created. The file extension indicates the file type. Only certain file types are allowed to be used within the organization.
Acceptable File Types:
>> Make a taxonomy of accepted file extensions
See your manager, coordinator, or other TIOF executive for a list of acceptable file types.
The list of file types that are acceptable is not necessarily inclusive. But anything that is not on the list of acceptable files must not be used without prior permission of a TIOF director.
This approach is not devoid of limitations that need to be kept in mind:
The managing file system must allow long file naming
Certain characters may be not allowed in certain platforms (Windows has limitations, for instance)
The UI of the platform may truncate the filename and make it difficult to establish the context and content of the file.
All these limitations are understood and accepted by TIOF and dealt in the best of possible ways, such as providing its members with tools that minimize them.
Use initial caps to name documents and delimit words in a file name.
Correct: TIOF Core Branding Guidelines
Incorrect: TIOF code branding guidelines
Do not use underscores. They can make it harder to locate files
Wherever a code/acronym is used, it should appear in all caps
Keep file names short but meaningful and leave out articles such as “the,” “a,” “and,” etc.
Correct: PLD TopAccounts 2019
Incorrect: PLD Y 2019 The Top 100 Accounts Sales Data market share report
Dates, if used, should be at the beginning of the file name and must always be in the international date format: YYYYMMDD
Do not use these characters in a file name. They can cause problems with opening files, especially if the file is sent outside the organization.
Backslash: \
Forward slash: /
Underscore: __
Bar/Sidebar: |
Ampersand: *
Question mark: ?
Chevron brackets: < >
Financial symbols: £ or $
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
This document will guide you in the steps you need to undertake for your TIOF onboarding and access all the tools that the organization puts at your disposal.
The first step in your onboarding process will be to be assigned basic credentials (TIOF Member Account) to access TIOF's tools.
For the time being, The IO Foundation is using Google Workspace for Nonprofits.
TIOF will do the necessary to create your basic credentials. You will receive a new credentials email (titled "[TIOF] Your new TIOF Member Account") once they are ready, which will lead you to this document.
Your TIOF Member Account will be composed by:
Username
Default Password
Please note that the first step you'll have to accomplish is to CHANGE your Default Password.
You will be required to change your password:
IMPORTANT DO NOT CLOSE THAT WINDOW UNTIL INDICATED BY THESE INSTRUCTIONS
Please note that in the Next Steps you will be guided to create and access TIOF's Vault where you'll be able to safely store your passwords.
IMPORTANT DO NOT CLOSE THE PASSWORD UNTIL INDICATED BY THESE INSTRUCTIONS
Once you have changed your password, you can proceed with the Next Steps.
These are the next steps you are invited to undertake for your TIOF onboarding.
Estimated time:
Registrations: 30 minutes
Going around the platforms: +30 minutes
Term | Description | Values & Format | |
---|---|---|---|
Value | Usage | Charter of Accounts Code |
---|---|---|
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
| Playbook | Assistant
This documentation page is under construction. Should you want to be notified once it's published, .
The list of trained first aiders are made available on our .
This documentation page is under construction. Should you want to be notified once it's published, .
Go to .
To change your password: - Go to - Select the following parameters as in the image below
Platform | TIOF | You |
---|
Invoice
Payment
Debtor Statement
Loan to {TIOF Member Code}
Quotation
Sales Receipt
Bill
Bank Statement
Bank Statement Scan Page
Debit Advice Scan
Debit Advice Scan Page
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Your journey may be taking you to a location with a different time zone. Planning a schedule under those circumstances can be challenging.
Here are some best practices to ensure your activities are properly arranged.
In Google Calendar, it is possible to see 2 different time zones at the same time:
The Primary Time Zone, which formats your calendar events on screen.
The Secondary Time Zone, which will give you a sense of the equivalent time at destination.
Set Primary and Secondary time zones
Go to G Cal Settings - Time Zone
Select the appropriate Primary and Secondary
(If you have doubts locating the zones, use tools such as www.timeanddate.com)
Select “Display Secondary time zone”
Label the time zones as you see fit.
Select “Ask to update my Primary time zone to current location”
This will create 2 hour lines on the left of your calendar. You can then see how each event happens in both time zones.
When planning:
Force the use of the destination’s time zone by clicking on the “reverse arrows” you’ll see at the right side of the time zone labels.
This will force your calendar to readapt your schedule as if you were at the destination. It will make things much easier for you to look at your calendar from the time as you’ll experience it there.
Do all your general events management. If you have any doubt about how to do this, please consult the “Calendar management SOP for TIOF”. @@@
Once you are done with arranging your schedule, you can force back your Primary time zone by clicking again on the “reverse arrows”.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
This document employs terms related to the DCDR Advocacy that can be found in the TIOF terminology.
For a structure of The IO Foundation, please visit
The IO Foundation's Organizational Chart
The IO Foundation's Organizational Nomenclature
This Members' Handbook sets out the main policies and procedures that you will need to be aware of while being a Member for TIOF. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team HR Coordinator.
This Handbook does not form part of any Engagement Document and we may amend it at any time.
This document directly applies to:
All [TIOF Members] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)
This document indirectly applies to:
All [TIOF Contributors] (https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)
The policies and procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all Contributors and will be used as part of the selection criteria when engaging with them.
This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).
@@@[Insert introduction e.g. details about the business]
The IO Foundation and its members adhere to the following Code of Conduct
[TIOF] Team Human Resources has overall responsibility for this Handbook and for ensuring that its policies and procedures comply with TIOF's legal obligations. This is carried out by:
Guidance of the Board of Directors
Advisory provided by the Board of Advisers and the Board of Counselors of each project
Supervision of [TIOF] Team Management
Assistance by [TIOF] Team Legal
Application by all [TIOF XXX] Team Human Resources
The Members' Handbook is reviewed regularly to ensure that its provisions continue to meet our legal obligations and reflect best practices.
All Members should ensure that they take the time to read and understand the content of this Handbook and act in accordance with its aims and objectives. Managers and Coordinators must ensure all Members understand the standards of behavior expected of them and to take action when behavior falls below those requirements.
Whenever we process personal data about you in connection with our policies, we will process it in accordance with our @@@Data Protection Policy. We will only process your personal data if we have a lawful basis for doing so. We will notify you of the purpose or purposes for which we use it. Please see the Privacy Notice for further information.
We retain details of your home address and the emergency contact telephone numbers of the person or persons you would like us to contact in the event of an emergency, for example if you have an accident. This information will be requested when you become and active TIOF Member and you should advise us of any changes straight away. This information is held in confidence and will only be used when needed.
This information is mandatory for:
Directors
Advisers
Staff
Interns
This information is optional for:
Counselors
Volunteers
@@@Define Emergencies
This Members' Handbook enters in effect at the time of publication.
We reserve the right to revise, modify, delete or add to any and all policies, procedures, work rules or benefits stated in this handbook or in any other document.
Any written changes to this Handbook will be made available to all Members to make them aware of the new policies or procedures. No verbal statements or representations can in any way alter the provisions of the Members Handbook.
@@@Link to all Document Matrix & LMS.
This handbook was last reviewed in @@@Should be date of last PR.
Consultation is one optional phase of TIOF's productions lifecycle.
The IO Foundation is opening a comments phase for its Policy Brief on BHR in Tech for the Malaysian National Action Plan (NAP). The invited parties are those who shown interest by joining us to in our latest event where the document was presented and discussed as well as a selected group of individuals.
To remain updated, we invite you to subscribe to our newsletter or follow us on Social media.
Hey Big Tech!
How to participate
Use the Comments tool to share your thoughts.
We will review your inputs and decide which ones make sense in the context of our DCDR Framework and the Malaysian NAP.
Should your inputs be included in the document and your name will be added as collaborator.
Should your inputs not be included we will do our best to articulate the reasons that lead to that decision.
Please consider that in any case The IO Foundation will need to make the final decision as we will have to defend the Policy Brief upon the group working on the NAP.
Timeline Beginning of the comments: 7th October at reception of this email
End of comments: 14th of October @ 18:00
Finalizing of Policy Brief: 16th of October
Submission to BEEU, SUHAKAM and UNDP: 17th of October
Submission to further relevant parties: 24th of October and onwards
Detail the campaign
ORG
This bracketed prefix identifies the organization to which this file belongs as well as the specific project (if applicable) to which it applies.
TIOF TION-MY TION-US
INITIATIVE
<None> DCDR BiT TU CS PLD UDDR
Team
See Team labels.
Privacy Level
Enter one of the following usage types in brackets:
[C] = Confidential
[I] = Internal (not confidential)
[P] = Public
Confidential documents are internal documents that are not to be distributed outside of TIOF unless specifically approved by a manager. Confidential documents carry a special Confidentiality notice.
Internal documents are proprietary and not to be shared with anyone outside TIOF, but only among the members directly involved with or affected by their contents, unless specifically authorized. See TIOF Code of Conduct Policy for more information about sharing confidential information outside of TIOF.
P stands for Public. Public documents are developed to be shared outside TIOF or are deemed acceptable to be shared outside TIOF.
DATE
When DATE is formatted as YYYY-00-00 it means the file covers the whole YYYYear. YYYY-MM-00 it means that the document covers that corresponding MMonth. For Quarters:
YYYY-MM-DD
Organization Label
Document Identifier
Content
The title of the file, i.e. the title of the document, media, image, graphic, app, etc.
For a document, this would be the title of the document as it appears inside the document.
The title should reflect, in as concise a manner as possible, the subject of the document, media, image, etc.
See taxonomy by Team
Case: Regular
Content Parameters
Dependent on the file content. See each Team for details.
Language
Include a three-digit code for the language in which the document is written. Use only ISO 639-3 character codes that can be found using this link: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
Use XXX if there is no specific associated language, such as for diagrams, photos, or videos. See the TIOF Codes and Acronyms List if necessary.
Version
Enter the document version here.
v0.X: This is the format to use for DRAFT documents being developed, sent out for review, or routing for approval.
For documents in review: The draft number should start with a 1 point increase (0.1, 0.2, 0.3) from the last official draft, “official” meaning the last draft that was officially sent out to be reviewed for comments, as there can be more than one review cycle. (Within Google docs you can create as many ‘named drafts’ as you would like, but only increase the draft number in the filename for official reviews).
vX.X: This is the format for FINAL DOCUMENTS that have undergone review and are ready for approval (to use or to release to the public). Starting with V1.0
SIGNED
Examples of a final document that has been signed would be:
v1.0 SIGNED
v1.5 SIGNED
Upper case
extension
Lower case
Vaultwarden | We will send you an invite to your TIOF email to join the platform. |
Slack (Communications) |
Google Drive (Storage) | Optional yet recommended: (It will make your life a bit easier) |
Google Calendar (Calendar) | We will send you an number of invites to your TIOF email to join some calendars. |
Raindrop (Leads) | We will send you an invite to your TIOF email to join the platform. |
Basaas (Workspace) | We will send you an invite to your TIOF email to join the platform. |
Cuttles (Business Plan) | We will send you an invite to your TIOF email to join the platform. |
ContextMinds (Mind maps) | We will send you an invite to your TIOF email to join the platform. |
………………….. 202[1]
Dear [insert volunteer name],
Volunteer Agreement
This letter sets out what we can each reasonably expect from your volunteering role with The IO Foundation MTU ("Foundation", "our", "us", "we"). We appreciate you volunteering with us and we are committed to providing volunteers with a supportive environment. We hope that you will find your volunteer experience enjoyable and rewarding.
[insert company property you will be providing, eg. laptop].
[insert relevant platforms].
any use or disclosure which is authorised by us or required by law;
any information which is already in, or comes into, the public domain otherwise than through your unauthorised disclosure.
"IPR" means all vested and future rights of copyright and neighbouring rights, database rights, design rights, trade marks (including all goodwill), patents, rights in inventions, domain names, trade secrets, confidential information, know-how and any other intellectual or industrial property rights anywhere in the world, whether or not registered or registrable (including all registrations and applications for registration of any of the above) and rights to apply for the same and all rights and forms of protection of a similar nature or having equivalent or similar effect to any of these anywhere in the world.
"Foundation IP" means all IPR created by you (whether alone or with others) in the course of carrying out the Volunteering, including the IPR in all Works, and including all rights to sue for infringement thereof.
"Works" means all works of any kind (including but not limited to all software, drawings, designs, graphs, flow charts, reports and other documents in any media) created by you (whether alone or with others) in the course of carrying out the Volunteering.
"Data Protection Legislation" means any applicable laws and regulations relating to the use or processing of personal data including (i) EU Regulation 2016/679 as it forms part of the law of England and Wales by virtue of section 3 of the European Union (Withdrawal) Act 2018 (“UK GDPR”); (ii) any laws or regulations ratifying, implementing, adopting, supplementing or replacing the UK GDPR (including, in the UK, the Data Protection Act 2018 and the applied UK GDPR; and (iii) any laws and regulations implementing or made pursuant to EU Directive 2002/58/EC (as amended by 2009/136/EC) (including, in the UK, the Privacy and Electronic Communications (EC Directive) Regulations 2003); in each case, as updated, amended or replaced from time to time; and
the terms "Data Subject", "Personal Data" and "processing" shall have the meanings set out in the UK GDPR.
Please acknowledge that you understand the contents of this letter by signing, dating and returning the enclosed copy.
Yours sincerely,
On behalf of The IO Foundation MTU
COPY
I acknoweldge that I understand the contents of this Volunteer Agreement.
Signed …………………………
[insert volunteer name]
Date ……………………………
Appendix I
(Organisational Chart)
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
File Naming convention
Identity (Organization / Project)
Resources
Inventory(?)
Accounts & Contacts
Events
Projects
Research
Institutional
G Drive
Associate necessary shared folder
Create PERSONAL folder in HR account and provide READ-ONLY/COMMENT access to the user.
Verifications: User can see the folders.
Show Template repository
When creating the following objects
Account (check Type)
Contact
When creating the following objects
Calendar entry
YYYY-MM-Q1 |
---|
Go to and register using the LOGIN WITH GOOGLE button and your TIOF Member Account.
Go to Explore the folder structure and get familiar with where to find what.
Install the in your browser.
Install the on your mobile.
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
YYYY-MM-Q4
YYYY-MM-Q3
YYYY-MM-Q4
[insert volunteer name]
[insert address]
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
In the event of a TIOF Member being hired, the following tools need be prepared:
In the event of a TIOF Member going on leave, the following tools need by updated:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Any content published in this Channel must abide by TIOF's Hey Big Tech declaration.
URLs
Dashboard
Single image per post Visual size: 1200 x 627 pixels Format: .png
Single image per post Visual size: 1200 x 675 pixels Format: .png
Cover Image (6.25:1 ratio, 5MB max)
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
URLs
Dashboard
Recommended format: 400x96px | JPG, SVG, PNG | up to 1 MB
Recommended format: 480x480px • JPG, SVG, PNG • Up to 5 MB
Recommended format: 1936x668px • JPG, SVG, PNG • Up to 2 MB
Single image per post Visual size: 1200 x 675 pixels Format: .png
Cover Image (6.25:1 ratio, 5MB max)
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
The Slack platform is used exclusively for communications:
Between TIOF Members
Among the TIOF Community
Between other organizations via
Shared channels
Presence in their own Slack workspace
This section describes the object model used in TIOF's Slack implementation.
URLs
Dashboard
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
To add: Cryptocurrencies To add: Banking Handbook
FROM LEN TEMPLATE:
Note: Needs to be signed off by a Certified Public Accountant
INTRODUCTION
DIVISION OF RESPONSIBILITIES
CHART OF ACCOUNTS AND GENERAL LEDGERS
CASH REGISTRY
Include cards
Include cryptos (maybe use a general term as financial assets?)
CASH DISBURSEMENTS AND EXPENSE ALLOCATIONS
ACCRUALS
BANK ACCOUNT RECONCILIATIONS
PETTY CASH FUND AND REVOLVING FUND
ASSET MANAGEMENT
PERSONNEL RECORDS
Kept in electronic format inside the CRM or whatever other storage medium used at the time. Access and rectification (following HR regulations) allowed.
PAYROLL PROCESSING
END OF THE MONTH AND FISCAL YEAR CLOSE
FISCAL POLICY STATEMENTS
APPENDICES
Revenue Streams
SI Labels:
SII
SIII
SIV
Plant, property and equipment and intangible assets Property, plant and equipment are stated at cost less accumulated depreciation and any accumulated impairment losses and discounts due to decline. Depreciation is calculated using the straight-line method. Useful life ranges are for groups of property, plant and equipment, the following: Buildings Buildings for 10-20 years Facilities 10-30 years Machines and devices Means of production 5-15 years Transport equipment 5-10 years Other tangible fixed assets Inventory 2-5 years Furniture for 5-10 years Office equipment 3-5 years Land is not depreciated.
Each such expenditure or costs shall be reimbursed only if:
(i) with respect to costs in excess of EUR50 (or equivalent, based on the exchange reference described in Appendix B), individually, Adviser receives prior approval from the Organization’s CEO or CFO or other authorized executive for such expenditure or cost, and
(ii) with respect to costs in less than EUR50 (or equivalent, based on the exchange reference described in Appendix B), individually, provided Adviser furnishes to Organization adequate records and other documents reasonably acceptable to Organization evidencing such expenditure or cost.
(This can be processed by any of the staff)
Using the Cash Advance Request Form, the requesting person inputs the project name or number, the funding partner and lists the specific items and corresponding amount requested with its respective budget line item reference. The form shall be signed by the requesting party and the project officer / manager.
The C/A form then goes to the online portal. All required items shall be inputted.
Once submitted, it will be referenced based on the row within which it was submitted. It shall then be numbered based on the current year, following the last two digits of the bank account from which it was requested and the corresponding row. The numbering shall be implemented by the Finance and Admin team in the online sheet and in the actual form should it be printed. The number will be this format: 19-38-01 YY-BB-RR
The Finance Manager shall verify the amounts requested and sign off validation.
The CEO approves and signs off checks for the release of the funds online.
Required Documentation for this process: Cash Advance Form, Cash Advance Form submitted online, Check/Bank Transfer Documentation
Note: if the cash advance request is a payment for reimbursement, the same process follows however the corresponding documentation of the items for reimbursement must be approved from the filing level
(Must be completed by the requesting party not later than two weeks after the activity was completed)
All cash advances will be liquidated using the TIOF Liquidation form
All expenses must have a corresponding documentation or a corresponding explanatory note why documentation is not available
All expenses that do not have official receipt or official documentation must have a form of documentation i.e. TIOF Acknowledgement Receipt form signed by the external party receiving payment from TIOF
Liquidation Form must be signed by the requesting party of the cash advance and reviewed by the Finance Officer / Manager
It shall be submitted to the CEO or respective immediate head for final approval
All remaining cash shall be re-deposited to the TIOF bank account.
All reimbursements shall be processed following requisition of cash advance. Revolving Fund cannot be used to pay for cash advance reimbursements
Documentation Needed: Liquidation Form and corresponding official documentation, proof of return (deposit slip) of positive balance
This documentation page is under construction. Should you want to be notified once it's published, .
Any content published in this Channel must abide by TIOF's
This documentation page is under construction. Should you want to be notified once it's published, .
Any content published in this Channel must abide by TIOF's
This documentation page is under construction. Should you want to be notified once it's published, .
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This Handbook responds to the following Policies:
Structure:
Salaries:
All same provider than TIOF. Wise, in particular. All payments are done INSIDE Wise. TIOF Members need to have a Wise account for payments.
Accounts:
TransferWise
EUR (SWIFT possible but only in EUR)
TW Account Holder: The IO Foundation
IBAN: DE12 7001 1110 6050 9883 74
Bank code (SWIFT / BIC): DEKTDE7GXXX
Address
Handelsbank
Elsenheimer Str. 41
München
80687
Germany
USD (only from US)
Account Holder: The IO Foundation
Account number: 8310060238
Wire Routing Number: 026073008
ACH Routing Number: 026073150
Address
TransferWise
19 W 24th Street
New York
10010
United States
Access Control
Bank Statements
Cryptocurrencies Coinbase Commerce Ledger Nano