Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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 filters to distribute incoming email
Response time: As per policy (>> Write it up) 48h Business Hours.
Keep track of filters in this document: LINK
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:
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
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:
The following section
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:
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:
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 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
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 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 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
Any content published in this Channel must abide by TIOF's Hey Big Tech declaration.
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:
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
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/
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
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:
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.