# Home {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} This is our policies site where we publish all of our policies in one place, from the general terms of service and privacy policy all the way down to internal policies between team members and community members with maintainer or moderation roles. ### The basics * [Terms of service](/general/terms) * [Privacy policy](/general/privacy) * [Subprocessors](/general/privacy/subprocessors) * [Acceptable Use Policy for Hosted Services](/general/hosted-services-aup) * [Security policy](/general/security-policy) ### Organization and Legal Entity * [Imprint / Impressum](/meta/legal-info) * [Abuse and data privacy contacts](/meta/legal-info/abuse-and-data-privacy-contacts) * [Fiscal sponsorship status and information](/meta/fiscal-sponsorship) * [Branding guidelines](/branding-and-style-guide/guidelines) * [Style Guide](/branding-and-style-guide/style-guide) ### Community * [Community Code of Conduct](/community/code-of-conduct) * [Open-source Policies](/community/open-source) * [Linux DCO](/community/open-source/linux-dco) * [Licensing guidelines](/community/open-source/licensing-guidelines) * [Release policy and checklist](/community/open-source/release-policy-and-checklist) * [Community spaces](/community/community-spaces) ### About this site * [Content license](/meta/license) * [Policy changelogs](/meta/changelog) # Content license Content on our policies site, unless otherwise specified, is licensed under [the Creative Commons Attribution-ShareAlike 4.0 International license](https://creativecommons.org/licenses/by-sa/4.0). ### Attribution When you adopt our policies on your own, please credit us as such with the following format, replacing placeholders as required: {% code overflow="wrap" %} ```markdown Portions of this [policy name] are adopted from Recap Time Squad's [original policy]([link to policy, either live version or archived via Internet Archive/other service]), licensed under CC-BY-SA-4.0 (https://creativecommons.org/licenses/by-sa/4.0). ``` {% endcode %} You may customize how you attribute your adaptation to the original policy as long as it is linked to the original policy page and the license page to be compliant with the license terms. # Imprint / Impressum This page documents the legal information about our organization, who's the person who take ultimate responsibility and its legal entity. ## Accountability / BDFL Andrei Jiroh is our team lead and founder, as well as the SABDFL (self-assigned benevolent dictator for life) for most of the Recap Time Squad projects, and the primary contact for our organization regarding the HCB fiscal sponsorship agreement. You may contact him directly via email at `ajhalili2006@crew.recaptime.dev` for general inquiries about the organization and its projects. You can also reach out at `+63 994 325 9266` for WhatsApp, [Signal](https://signal.me/#eu/eETitzJEFcxSodsQW7D_ciZKW5XnDZUO1Quv59ZUcZ0HCPFqnvNNpJCqy63JKKpp) and [Telegram](https://t.me/RecapTimeSquadCrew). For abuse reports and data privacy related requests, see also [Abuse and data privacy contacts](/meta/legal-info/abuse-and-data-privacy-contacts). Please note that we do not accept video or voice calls, as written[^1]/asynchronous digital communications are much preferred. ## Legal/non-profit status See [Fiscal sponsorship status and information](/meta/fiscal-sponsorship) for a more detailed information about our legal/non-profit status as a fiscally sponsored organization. [^1]: If you need to send physical mail to his home address in the Philippines, please ask him for the details first. # Abuse and data privacy contacts Learn more about how to contact us regarding reporting abuse and data privacy ## Legal information Recap Time Squad is a fiscally-sponsored open-source multi-project/umbrella organization under [The Hack Foundation](https://the.hackfoundation.org/) (d.b.a [Hack Club](https://hackclub.com/)), a US 501(c)(3) non-profit with EIN `81-2908499`. [Andrei Jiroh Halili](https://andreijiroh.dev/), a natural-born Filipino citizen and Philippine resident, is our SABDFL (self-assigned benevolent dictator for life) and lead maintainer for projects under the organization and primary contact with the fiscal sponsor's operations team. Visit [Imprint / Impressum](/meta/legal-info) for the up-to-date imprint and legal documents about our organization. ## General abuse reports For regular abuse reports (general or service/API-specific ToS, legal takedown requests), email `abuse@recaptime.dev` with links and file attachments (if it is too large for email, links to file-based evidence are also enough) as evidence. ## Code of conduct violations For cases involving code of conduct violations in our technical and community spaces, you may reach out to our code of conduct support at `conduct@recaptime.dev` and it will be routed to our internal GitLab issue tracker focused on reports of misconduct. Community moderators and maintainers outside of Recap Time Squad HQ can also email us through the address to coordinate moderation actions and appeals. ## Intellectual property (IP) takedown reports For takedown reports involving possible copyright and trademark-related issues (both under the copyright laws in the US and the Philippines), please email them to `copyright@recaptime.dev` with the following: * Your legal name * Name of the rights holder or its authorized agent, alongside contact details such as email address, phone number and mailing address * Description of original work and links to infringing content * [512(f) acknowledgment, Good faith belief, Authority to act](#user-content-fn-1)[^1] (type "I attest, that you have a good faith belief that use of the material in this report is not authorized by the copyright owner, its agent, or the law; AND that, under penalty of perjury, you are authorized to act on behalf of the copyright owner; AND you understand, under 17 U.S.C. § 512(f), you may be liable for any damages, including costs and attorneys' fees, if you knowingly materially misrepresent reported material. Checking this box also confirms that you have a bona fide belief that the information and allegations contained in this report are accurate and complete, for purposes of the Digital Services Act.") * Your legal name again as a digital signature You can also opt to submit a copyright or takedown takedown request via the [Cloudflare abuse report form](https://abuse.cloudflare.com/dmca). Please note that we may publish your report alongside our response and actions taken on our own transparency reports, alongside being shared with third parties such as [Lumen Database](https://lumendatabase.org/). You should know that copyright/trademark takedown reports should not be used as a censorship tool to silence criticism and speech, nor block valid reuse under existing fair use and fair dealing laws. ## Data privacy inquiries [^1]: In the Philippines, you might be asked to get your takedown notice authenticated with a notary for identity verification and liability purposes. # Fiscal sponsorship status and information ## Basics Recap Time Squad is a [fiscally sponsored](https://hackclub.com/fiscal-sponsorship) [(Wikipedia page)](https://en.wikipedia.org/wiki/Fiscal_sponsorship) open-source organization, alongside its projects such as Community Lorebooks, by [The Hack Foundation](https://hackfoundation.org/) (d.b.a [Hack Club](https://hackclub.com/)), a US 501(c)(3) non-profit with EIN `81-2908499`. You can learn more about HCB (previously Hack Club Bank), the in-house fiscal sponsorship platform that Hack Club built and developed since 2018, at [the program landing page](https://hackclub.com/fiscal-sponsorship?ref=policies.recaptime.dev) or [its open source repository at GitHub](https://github.com/hackclub/hcb). ### Why fiscal sponsorship instead of forming a (non-profit) legal entity? We opt for the fiscal sponsorship route so that we can focus more on building and maintaining great open-source projects and initiatives rather than doing the legal paperwork of forming one (it's a complicated mess if you ask that in the Philippines context), in exchange for having financial oversight over our operations under the terms of fiscal sponsorship. ## The legal documents {% hint style="info" %} We don't typically provide anyone a copy of the signed agreement itself or bank account verification letter for privacy concerns (i.e., the mailing address itself of the primary organization contact on our side (aka our BDFL)) unless otherwise requested in written form via email. We can point you to the fiscal sponsorship agreement template that the HCB Operations team uses as part of their onboarding flow for new organizations. {% endhint %} * Confirmation letters: * Recap Time Squad: [meta repo](https://gitlab.com/recaptime-dev/squad/meta/-/blob/ee5ef6e5fb043503eaadfc5dcb7d5a03179b87a2/internals/fiscal-sponsorships/hackclub/confirmation-letters/fiscal_sponsorship_letter-recaptime-dev.pdf) (dated May 23, 2025) * Community Lorebooks: [meta repo](https://gitlab.com/recaptime-dev/squad/meta/-/blob/ee5ef6e5fb043503eaadfc5dcb7d5a03179b87a2/internals/fiscal-sponsorships/hackclub/confirmation-letters/fiscal_sponsorship_letter-lorebooks-wiki.pdf) (dated May 23, 2025) * The fiscal sponsorship agreement terms as of August 23, 2023: TBD # Policy changelogs ### May-June 2026 *Changelog entry author:* [*@ajhalili2006*](https://github.com/ajhalili2006) ### August 4, 2025 *Changelog entry author:* [*@ajhalili2006*](https://github.com/ajhalili2006) We moved to GitBook in terms of hosting the policies site, as well as to lessen our maintainer burden from updating Python packages responsible for the site itself. We'll keep things in sync with the Git history in the future, although we started fresh by creating a local orphan branch. With this move, we can revamp the policies website content and navigation at the same time, among other things, start writing a proper privacy policy and terms of service. ### Older entries ### July 15, 2025 - Code of conduct *Changelog entry author:* [*@ajhalili2006*](https://github.com/ajhalili2006) *(as of August 4, 2025)* We separated the appendix section of the community code of conduct into its subpage, alongside synchronizing its contents to the version published on our GitHub organization's health files repository. We also removed a dedicated page for the enforcement guidelines and instead rebuilt from scratch as platform and community-specific guidelines. ### Older content on the old branch * [`04baf43a`](https://mau.dev/recaptime-dev/legal/policies/-/commit/04baf43ae09408e98c0d27b63889cb01e9c9495f#0413b581cc7c224aa4a8018e44290698a06e36b9) - Add a changelog for this page * [`850332ab`](https://mau.dev/recaptime-dev/legal/policies/-/commit/850332abe108080778c3885fe340eeb81919d60b#0413b581cc7c224aa4a8018e44290698a06e36b9) - add `Last updated` to top of page. * [`a3d67880`](https://mau.dev/recaptime-dev/legal/policies/-/commit/a3d678806b231499035f564aa80b7ba5f700ff2e) - Update the content in the appendix for wider context * [`33109567`](https://mau.dev/recaptime-dev/legal/policies/-/commit/33109567b34936621e2919be75c78d9225ef3e85) - migrate content to `docs` directory for the introduction of Sphinx + Furo theme, alongside adding an appendix Older commits may be found in [our old policies repo](https://github.com/MadeByThePinsHub/policies/commits/master/CODE_OF_CONDUCT.md) on GitHub. # Terms of service {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} **Effective Date**: TBD | **Last updated**: TBD ### Terms By accessing this web site, you are agreeing to be bound by these web site Terms and Conditions of Use ("Terms of Use"), all applicable laws and regulations, and agree that you are responsible for compliance with any applicable local laws. If you do not agree with any of these terms, you are prohibited from using or accessing this site. The materials contained in this web site are protected by applicable copyright and trademark law. ### Privacy You agree to read and accept Recap Time Squad's [Privacy Policy](/general/privacy). ### Conduct By participating on Recap Time Squad projects and/or community spaces (including Recap Time Squad-branded ventures in any capacity), you agree to and abide by [our Community Code of Conduct](/community/code-of-conduct) and other policies enacted by staff and wider community, alongside any community-specific policies and rules on affiliate communities we participate. ### Jurisdiction Any disputes and complaints between you and Recap Time Squad are under the exclusive jurisdiction of the municipality of Marilao, Bulacan in the Philippines (where Andrei Jiroh, our BDFL, resides) and/or State of California in the United States (for matters relating to our fiscal sponsor). ### Definitions * **you** - The user of this website * **Recap Time Squad** - The open-source umbrella organization, their personnel and volunteers * **fiscal sponsor** - The Hack Foundation (d.b.a. Hack Club), a US 501(c)(3) non-profit (see also [Fiscal sponsorship status and information](/meta/fiscal-sponsorship)) ### Prior art / Credits Portions of this terms of service were adapted from the following sources: * [Miraheze Site Terms of Use](https://meta.miraheze.org/wiki/Terms_of_Use) ([permalink](https://meta.miraheze.org/wiki/Terms_of_Use?oldid=492660)), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). # Privacy policy {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} This page documents our privacy practices from what data we collect and why to how we handle and process them. ## Data we collect and why ### Information from web browsers and client If you're just browsing on our websites, we collect the same basic information that most websites collect. We use common internet technologies, such as cookies and web server logs. This is stuff we collect from everybody, whether they have used our services/apps or not. The information we collect about all visitors to our website includes the visitor’s browser type, language preference, referring site, additional websites requested, and the date and time of each visitor request. We also collect potentially personally identifying information like Internet Protocol (IP) addresses. We use this information from web browsers and other web clients for purposes of web analytics, service monitoring, security, and abuse prevention/mitigation. ### Information you provide through our services/apps If you create an account for our services/apps or use them with your existing social accounts via OAuth2 or OpenID Connect, we usually require you to provide some basic information about yourself. Unless you use social login, you will be asked for a non-disposable email address and password (or set up a passkey for passwordless authentication). You also have the option to give us more information if you want to, and this may include "User Personal Information." "User Personal Information" is any information about one of our users that could, alone or together with other information, personally identify him or her. Information such as a username and password, an email address, a real name, and a photograph is are example of “User Personal Information.” User Personal Information includes Personal Data as defined in the data privacy laws, such as EU General Data Protection Regulation (GDPR) and the Data Privacy Act of 2012 in the Philippines. User Personal Information does not include aggregated, non-personally identifying information. We may use aggregated, non-personally identifying information to operate, improve, and optimize our website and service. If you use our services/apps through existing platforms such as Discord bots, we receive technical and basic information about your account, such as username and user IDs, alongside interaction data from the platform. ### Information you provide through contacting us When you contact us through email or one of the available contact methods, we collect your name, email address, or [phone number used](#user-content-fn-1)[^1] for contacting us, the subject line, and the message body of the inquiry, alongside any attachments provided. When you contact us through a form, alongside collecting the necessary contact details about you, we also collect the information we need to process your request ### What we do not collect If you are a child under the age of 13 in most countries (or higher in some countries), you may not use our apps and services without parental consent. Recap Time Squad does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a user who is under the age of 13, we will, unfortunately, have to close your account and delete any data we hold and collected about you. ## Accessing your information You can access and edit/amend the information we have about you in your account settings and in the respective apps/services. You can also contact us to request a copy of your data across apps and services we run and maintain. On services with end-to-end encryption support, we only provide you account metadata by design. ## Data retention and deletion Generally, Recap Time Squad retains User Personal Information for as long as your account exists or as needed for our apps and services. You may request to delete portion of your data or everything ## Our use of cookies and trackers ### Cookies Like any website, we use "cookies" (and similar technologies, like HTML5 localStorage) to keep you logged in, remember your preferences and personalize your experience. We also use cookies to identify a device, for security and abuse mitigation reasons. You may disable either third-party and/or first-party cookies or manage them in your browser settings but by disabling or removing them from your browser, you may be signed out. ### Tracking and analytics ## Changes to this policy Although most changes are likely to be minor, Recap Time Squad may change them from time to time. When we make changes to this policy, you will be notified at least 30 days before being effective via email address on file and on our announcement bulletins in GitHub Discussions and Zulip Cloud organization. ## Credits Portions of this privacy policy are adapted from the following sources: * [GitBook Privacy Statement](https://policies.gitbook.com/privacy-and-security/statement) * [Miraheze Privacy Policy](https://meta.miraheze.org/wiki/Privacy_Policy) [^1]: In WhatsApp Business, this is shared with the team by default when you initiate a conversation with our business profile there. We'll not use this to send you promotional messages, but primarily be used for account ownership verification and security/recovery processes. In Telegram and Signal, your phone number isn't shared with us by default unless you opt to do so, depending on the respective apps' privacy settings and how you share them. Note that this also applies if you provided your number to us through the support email or when we added your number to our existing customer relationship management records on Help Scout and GitLab. # Subprocessors When we share your information with third-party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as described in our privacy policy).
Name of subprocessor Description of processingLocation of processing
The Hack Foundation (d.b.a. Hack Club)Fiscal sponsor (accepting donations via the HCB platform)United States
CloudflareHosting provider, web application firewall, tunneling/reverse proxy service, web analyticsUnited States
StripePayment processor outside the HCB platform (Open Collective, Liberapay, Ghost, etc.)United States
Help ScoutTicketing system for support requests and sponsors, support center site hostingUnited States
GitLabTicketing system for abuse and code of conduct reports via the Support Desk feature, code hosting, website hostingUnited States
FilloutFormsUnited States
TallyFormsTBD
When we bring on a new vendor or other subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. # Acceptable Use Policy for Hosted Services ### Subdomain services under Community Lorebooks **Last updated**: 2025-01-24 The `lorebooks.wiki` subdomain service is provided for the purpose of providing free subdomains primarily to documentation and wiki websites, but we do not limit them to anyone in the wiki communities. However, this does not mean they may be used for **any** purpose. Like [the Obl.ong domain service](https://codeberg.org/oblong/conduct/src/commit/main/README.md), we prohibit use of our service for any of the behaviors listed above as unacceptable, and for any of the following: * any activities that intend to or actually generate profits for shareholders or do not act in the public interest * any form of malware (which includes, without limitation, malicious code or software that may affect the operation of the Internet); * any form of botnets, spam, or phishing; * interfering with or disrupting servers or networks, or disobeying any requirements, procedures, policies, or regulation of networks; * harming minors in any way, including the distribution of child pornographic images; * distributing or hosting any adult content, including but not limited to, pornographic images or videos. * impersonating any person or entity, including, but not limited to, an official, forum leader, guide or host, or falsely stating or otherwise misrepresenting its affiliation with a person or entity; * using a domain name for activity comprising or contributing to piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting, or other illegal activity; * insighting or promoting violence against any person or groups of persons, which shall include but is not limited to LGBTQIA+ and/or disabled persons and minorities; * bullying, engaging in cyber bullying, or inciting others to bully; * harassing, or encouraging others to harass or harm others; * stalking; * abusive intent to cause fear or threaten violence; * hate speech (including homophobia, transphobia, queerphobia, racism, sexism, ableism, casteism, xenophobia, antisemitism, islamophobia, and other forms of bigotry); * content which may be illegal under United States law; * content containing Nazi symbolism, ideology, and the promotion thereof; * content which claims to forbid/disavow abusive or hateful conduct, but which permits "respectful" "discussions" of "unpopular opinions"/"controversial views" (dessert pizza is an unpopular opinion, trans folks' right to live a happy life is not, and hate is hate regardless of how dressed-up it is); * any other activity intended to organize, coordinate, or otherwise enable any of the above. Registrations are prohibited to parties that are, or associated with, recognized hate groups, or are otherwise engaged in hate speech. This list is not comprehensive, and we reserve the right to revoke any subdomain at any time. Recap Time Squad is not responsible for and does not actively monitor registrant's content, and therefore, cannot guarantee that content hosted on our subdomains does not violate this policy. Failure to enforce this policy or respond to a complaint does not constitute a waiver of our right to enforce it; nor does this policy create any obligations to users or any third-party beneficiary rights or private rights of action. ### Fediverse instance and Atmosphere account provider Last updated: TBD While our self-hosted fediverse instance and Atmosphere account provider (technically called Personal Data Servers in the AT Proto specs) is primarily used for Recap Time Squad projects and its team members, we also allow anyone to request for an invite code so they can either set up afresh or migrate their account data from other account providers (or migrate their social graphs and profile in the fediverse, since nomadic identity is still in the works on the spec and among implementers). Alongside the regular [ToS](/general/terms), [privacy policy](/general/privacy) and [Community Code of Conduct](/community/code-of-conduct), here are our AUP for both our fediverse instances and Atmosphere account providers operated by either Recap Time Squad and/or its team members: * The same prohibited content under Community Lorebooks' subdomain service also apply here. Note that since our PDS server runs on Uberspace, we prohibit any illegal content under German laws, alongside the usuals under both US and Philippine laws. * Do not abuse reporting tools as a censorship tool and flood-report with non-violative content to our moderation service. # Security policy {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} ### Reporting security issues Email `security@recaptime.dev` with details about the security issue in question. If you are also submitting security patches for our projects, we recommend emailing the patchsets to `~recaptime-dev/security@lists.sr.ht` or using confidential merge requests in GitLab SaaS. ### In scope vs out of scope We consider the following as in-scope of our security policy # Refund policy Understand how our refund policy works {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} **Last updated on July 20, 2025** [**(changelog)**](/meta/changelog#refund-policy) Our refund policy is roughly based on the default one in the Open Collective platform [(docs)](https://documentation.opencollective.com/giving-to-collectives/requesting-refunds/refund-policy), with some adjustments. Depending on how and where you donate or pay, we may be able to issue you a refund once it is reviewed by both our team and our fiscal sponsor. ## General guidelines {% hint style="danger" %} To minimize refund fraud, we only refund to the original payment method used if processed via Stripe on HCB, Open Collective, Substack, Ghost, and Lemon Squeezy or the original account if processed via PayPal. Other payment methods are unsupported at this time. Refunds may take up to 15 banking days to be credited back to you and show up in your bank statement. {% endhint %} We only review refund requests if they are covered under this policy (or if they're not covered but have specific guidelines similar to this). Once we receive a refund request, we'll try to respond within 1-2 weeks to allow us to investigate possible issues and check if the amount requested is correct. ### Timeline for refund requests Depending on the payment method used and payment processor, it may take up to 10-20 banking days for refunds to reflect on your bank or credit card statement if approved. If it takes longer than that, contact your bank for details. ## Covered vs not covered by refunds ### Covered * Donations and payments processed through Stripe on the following platforms in particular order: * HCB (your refund request will be forwarded to the HCB team for review) * Open Collective (email `sponsors@recaptime.dev` first so we can review your request) * Ghost and Substack ([contact Substack Support first](https://support.substack.com/hc/en-us/articles/8915992656660-What-is-Substack-s-refund-policy) if you are requesting refunds within 7 days after subscription, unless you requested more than 3 times) * Telegram Stars (we'll refund those stars back to the original account, although you may need to contact Telegram Support or Google Play Store/Apple App Store support for refunds) ### Not covered * Discord Server Subscriptions and Premium Apps - [see Discord's refund policy](https://support.discord.com/hc/en-us/articles/360012668071-Refund-Policy) and [contact Discord Support here](http://dis.gd/billing) * GitHub Sponsors - [contact GitHub Support here](https://support.github.com/contact) * Donations and payments via manual bank transfers (not through Direct Debit if processed through Stripe) # RecapTime.dev Community Code of Conduct Please review our code of conduct, as this will be applicable throughout both technical and community spaces. **Last updated on July 15, 2025** [**(changelog)**](/meta/changelog#code-of-conduct) {% hint style="info" %} The [Hack Club Code of Conduct](/community/hackclub-coc) applies to Recap Time Squad's community spaces (both inside and outside of Hack Club Slack and other places like open-source projects within [their GitHub organization](https://github.com/hackclub) and in-person events where our team members participate either as audience/participant, event staff/organizer, guest or sponsor) as part of our fiscal sponsorship status/agreement under HCB. In case a Hack Clubber (community member or otherwise HQ/HCB staff) is involved in a misconduct report, we may share your report with someone on the Hack Club side via email ([conduct@hackclub.com)](mailto:conduct@hackclub.com) or [the Shroud Slack bot](https://hackclub.slack.com/team/U07K4TS9HQE) anonymously unless you allow us to share your contact information with them or you reported the case yourself. {% endhint %} ### Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ### Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting, or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others’ private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ### Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ### Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ### Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement through [the published abuse contacts page](/meta/legal-info/abuse-and-data-privacy-contacts). All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ### Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: #### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. #### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. #### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. #### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ### Attribution This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at and licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0) license. Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity). For answers to common questions about this code of conduct, see the FAQ at . Translations are available at . ### Appendix *Moved to a separate page at* [Appendices for the code of conduct](/community/code-of-conduct/appendix) # Platform and community-specific rules/guidelines Alongside the Community Code of Conduct, we also enforce platform and community-specific guidelines and rules to complement ## Zulip *(Applies to the Recap Time Squad Zulip Cloud organization)* ## Discord *(Applies to the Recap Time Squad / Community Lorebooks Discord server)* 1. **Read the channel description and follow channel-specific guidelines**: 2. **Use of threads is recommended over replies**: ## Slack ### Hack Club Slack {% hint style="info" %} Applies to Recap Time Squad's dedicated Slack channels in Hack Club Slack; note that [the Hack Club CoC](/community/hackclub-coc) supersedes our own CoC, and cases of misconduct within Hack Club community spaces should be reported to the Moderation and Conduct subteam of the Community Team. {% endhint %} 1. Always reply in threads: 2. Do not remove any integrations or automations used in the channel: # Appendices for the code of conduct Frequently asked questions about our code of conduct, additional documentation and more. ## Violations affecting/coming outside RecapTime.dev If we receive a violation report that either affects or comes from other communities, we have limited moderation powers over what’s happening outside our spaces, either public or within internal channels. This is usually the case when reporting content from other homeservers in the fediverse, in which coordination between homeserver admins and mods is required. If that’s the case, a member from our moderation team will simply forward your case on your behalf anonymously unless you allow us to share your contact information with other moderators outside of our spaces. [See also this FAQ entry on the Contributor Covenant website](https://www.contributor-covenant.org/faq/#can-i-be-cited-for-a-code-of-conduct-violation-for-something-that-i-say-on-twitter-or-other-social-media-site) for context. In case of a previous issue that caught our attention (or was found during an investigation), we’ll look into it and evaluate any options. This doesn’t mean we’re “digging your grave” for your past mistakes and controversies (see above) unless it’s involving grave misconduct, especially involving current trusted community members (maintainers, moderators) and core team members. See also platform and community-specific policies {% content-ref url="/pages/nouPomUASzwCwPihKDSZ" %} [Platform and community-specific rules/guidelines](/community/code-of-conduct/platform-specifics) {% endcontent-ref %} ## Applicability to staff/core team on business/corporate matters The Community Code of Conduct also applies to our core team members and staff, as stated in this section, although laws on NDA enforcement and our fiscal sponsorship agreement with the HCB team may override/supersede this code of conduct in case of conflicts. ## Appealing to an enforcement action Anyone with an active enforcement action (i.e., bans, mandatory cool-offs) who believes that # Hack Club Code of Conduct The required standards of conduct for the Hack Club community & events. {% hint style="info" %} This version of Hack Club Code of Conduct was originally published last [September 27, 2024](https://github.com/hackclub/hackclub/commit/a48e26c157fad2166435843cf118a9bd6e822827), from [the meta repository](https://github.com/hackclub/hackclub). For updates, visit the latest canonical version at [hackclub.com/conduct](https://hackclub.com/conduct). In case a Hack Clubber were involved in a misconduct case outside of Hack Club's community spaces, please reach out to a community maintainer or a Recap Time Squad crew member first so we can coordinate it with the CoC Working Group. {% endhint %} ### TL;DR * Treat everyone with respect and kindness. * Be thoughtful in how you communicate. * Don't be destructive or inflammatory. * If you encounter an issue, please mail . ### Why have a Code of Conduct? Hack Club's community includes people from many different backgrounds. The Hack Club contributors are committed to providing a friendly, safe, and welcoming environment for all, regardless of age, disability, gender, nationality, race, religion, sexuality, or similar personal characteristic. The first goal of the Code of Conduct is to specify a baseline standard of behavior so that people with different social values and communication styles can communicate effectively, productively, and respectfully. The second goal is to provide a mechanism for resolving conflicts in the community when they arise. The third goal of the Code of Conduct is to make our community welcoming to people from different backgrounds. Diversity is critical in order for us to build a thriving community; for Hack Club to be successful, it needs hackers from all backgrounds. With that said, a healthy community must allow for disagreement and debate. The Code of Conduct is not a mechanism for people to silence others with whom they disagree. ### Where does the Code of Conduct apply? If you join in or contribute to the Hack Club ecosystem in any way, you are encouraged to follow the Code of Conduct while doing so. Explicit enforcement of the Code of Conduct applies to all official online Hack Club groups, in-person meetings, and events including: * The [Slack](https://hackclub.com/slack/) * The [Events](https://events.hackclub.com/), including [AMAs](https://hackclub.com/amas/), [Hack Night](https://hackclub.com/night/), & Zoom calls on Slack * The [GitHub projects](https://github.com/hackclub) * Club Meetings Anyone associated with HQ is required to follow and model the Code of Conduct in all situations, including places with explicit enforcement and in other spaces too. There is a higher bar for anyone associated with HQ. Other Hack Club groups (such as hackathons, conferences, meetups, and other unofficial forums) are encouraged to adopt this Code of Conduct. Those groups must provide their own moderators and/or working group (see below). ### Hacker Values These are the values to which people in the Hack Club community should aspire. * Be friendly and welcoming * Be patient * Remember that people have varying communication styles and that not everyone is using their native language (meaning and tone can be lost in translation). * Be thoughtful * Productive communication requires effort. Think about how your words will be interpreted. * Remember that sometimes it is best to refrain entirely from commenting. * Be respectful * In particular, respect differences of opinion. * Be charitable * Interpret the arguments of others in good faith, do not seek to disagree. * When we do disagree, try to understand why. * Avoid destructive behavior: * Derailing: stay on topic; if you want to talk about something else, start a new conversation. * Unconstructive criticism: don't merely condemn the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved. * Snarking (pithy, unproductive, sniping comments) * Discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. * Microaggressions: brief and commonplace verbal, behavioral, and environmental indignities that communicate hostile, derogatory or negative slights and insults to a person or group. People are complicated. You should expect to be misunderstood and to misunderstand others; when this inevitably occurs, resist the urge to be defensive or assign blame. Try not to take offense where no offense was intended. Give people the benefit of the doubt. Even if the intent was to provoke, do not rise to it. It is the responsibility of *all parties* to de-escalate conflict when it arises. ### Unwelcome behavior These actions are explicitly forbidden in Hack Club spaces: * Expressing or provoking: * insulting, demeaning, hateful, or threatening remarks; * discrimination based on age, nationality, race, (dis)ability, gender (identity or expression), sexuality, religion, or similar personal characteristic; * bullying or systematic harassment; * unwelcome sexual advances, including sexually explicit content. * Advertising or recruiting for events, companies, organizations, etc - unless specifically given permission by Hack Club HQ. * Posting spam-like content that disrupts the environment of the community. * Defrauding Hack Club, including HCB, by collecting funds or resources under false information, identity, or pretenses. This is treated as a **third offense** and could result in a call to **your school admin**. ### Moderation & Enforcement Please understand that speech and actions have consequences, and unacceptable behavior will not be tolerated. When you participate in areas where the code of conduct applies, you should act in the spirit of the "Hacker Values". If you conduct yourself in a way that is explicitly forbidden by the Code of Conduct, you will be warned and asked to stop, and your messages may be removed by community moderators. Repeated offenses may result in a temporary or permanent ban from the community. * On your first offense, you will receive a written notice from one of our community moderators. Depending on the degree of the reported behavior, you may be asked to apologize, either in public or directly to the party that you have offended. * On a second offense, you will be temporarily removed from the community. The period of the temporary ban may vary from 3 days to a month, decided based on the seriousness of the reported behavior. Please note that this ban **does not indicate that you are no longer welcomed in the community** - it represents an official warning for your behavior. * On a third offense, you may be asked to leave the community. Your account may be suspended for an indefinite amount of time, and you may be publicly identified. This procedure only serves as a general guideline for moderation & enforcement of our community conduct. Under all circumstances, the Working Group or Hack Club's staff members may take any action we deem appropriate, including immediate removal from the community. Being banned from the Hack Club community may also prevent you from participating in our community events, including but not restricted to: local club meetings, hackathons, or challenges. Please understand that we will not restrict your ability to contact the Code of Conduct working group under any circumstance. If you have any questions or concerns about our decision, please reach out to us directly. If your Slack account is under suspension, email us directly at . ### Working Group The Working Group is responsible for handling conduct-related issues. Their mission is to de-escalate conflicts and try to resolve issues to the satisfaction of all parties. For all projects related to and/or maintained by Hack Club HQ, the Working Group is made up of the [Hack Club staff team](https://hackclub.com/team/) and [Fire Dept](https://app.slack.com/client/T0266FRGM/C01D7AHKMPF). The specific team member(s) handling each violation depend on the location and nature of the issue. ### Reporting Issues If you encounter a conduct-related issue, you should report it to the Working Group using the process described below. **Do not** post about the issue publicly or try to rally sentiment against a particular individual or group. * Mail * Your message will reach the Working Group. * Reports are confidential within the Working Group. * Should you choose to remain anonymous then the Working Group cannot notify you of the outcome of your report. * You may contact a member of the group directly if you do not feel comfortable contacting the group as a whole. That member will then raise the issue with the Working Group as a whole, preserving the privacy of the reporter (if desired). * If your report concerns a member of the Working Group, they will be recused from Working Group discussions of the report. * The Working Group will strive to handle reports with discretion and sensitivity, to protect the privacy of the involved parties, and to avoid conflicts of interest. * You should receive a response within 48 hours (likely sooner). (Should you choose to contact a single Working Group member, it may take longer to receive a response.) * The Working Group will meet to review the incident and determine what happened. * With the permission of the person reporting the incident, the Working Group may reach out to other community members for more context. * The Working Group will reach a decision as to how to act. These may include: * Nothing. * A request for a private or public apology. * A private or public warning. * An imposed vacation (for instance, asking someone to abstain for a week from the Slack or a GitHub project). * A permanent or temporary ban from some or all Hack Club spaces. * The Working Group will reach out to the original reporter to let them know the decision. * Appeals to the decision may be made to the Working Group or to any of its members directly. **Note that the goal of the Code of Conduct and the Working Group is to resolve conflicts in the most harmonious way possible.** We hope that in most cases issues may be resolved through polite discussion and mutual agreement. Bannings and other forceful measures are to be employed only as a last resort. Changes to the Code of Conduct should be proposed by [creating an issue](https://github.com/hackclub/hackclub/issues/new) or making a pull request to this document. ### Acknowledgments This was adapted from [Go's Code of Conduct](https://github.com/golang/go/commit/aa487e66f869785837275ee20441a53888a51bb2). It is to be noted that many parts of Go's Code of Conduct are adopted from the Code of Conduct documents of the Django, FreeBSD, and Rust projects. # Open-source Policies As an open-source organization, we have adapted these open-source policies across our projects, alongside the Contributor Covenant (which forms our [Community Code of Conduct](/community/code-of-conduct)): * [Linux DCO](/community/open-source/linux-dco) * [Licensing guidelines](/community/open-source/licensing-guidelines) * [Release policy and checklist](/community/open-source/release-policy-and-checklist) # Linux DCO The DCO as our contributor license agreement ## Full text *(copied from* [*developercertificate.com*](https://developercertificate.com/)*)* ``` Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ``` ## How to sign the DCO ### Signing off on your commits On a per-commit or per-patch basis, simply add the following trailer in this format at the end of the commit message body. You can also use the `--signoff` flag on `git commit` and `git send-email` commands to speed things up. If you do prefer to manually sign-off your work, it should follow the following format in its own line. ``` Signed-off-by: Your Name ``` In case of multiple contributors in a single commit (perhaps squashing commits and merging them or when it is co-authored), you may need to add their sign-offs (and optionally add the `Co-authored-by` entries). ``` Co-authored-by: That Co-author Name Signed-off-by: Your Name Signed-off-by: That Co-author Name ``` In most cases, we do not require you to use your legal name when authoring and signing off on commits, but we do not allow any anonymous ID, or a fake name that misrepresents your identity, since we require each contributor to be accountable for their patches, especially on the copyright side of things. ### Privately sign off on contributions If you choose to privately sign off contributions like a regular contributor license agreement, you may do so through the form linked in the button below. Initiate private sign-off (requires GitHub/GitLab signin) You'll be required to authenicate with your GitHub or GitLab SaaS (aka `GitLab.com`) account so we can match your real life identity to your accounts for legal recordkeeping. Your legal name will be not shared with anyone unless it is for situations where it is legally required (i.e. donations and reimbursement requests through our fiscal sponsor). ## For maintainers Please consult CNCF's DCO guidelines (linked in the related resources section below) regarding the use of "real names", more specifically: > **A real name does not require a legal name, nor a birth name, nor any name that appears on an official ID (e.g. a passport). Your real name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution.** Currently, we're working on designing and planning for the Identity Proofs Toolkit project to help with lightweight identity verification using public profiles (inspired by Keyoxide and Keybase) without the need to require everyone to submit documents via Stripe Identity or rely on Hack Club's identity verification flow. ## Related resources * [The CNCF meta GitHub issue](https://github.com/cncf/foundation/issues/383) clarifying the real name policy and [their DCO guidelines](https://github.com/cncf/foundation/blob/main/policies-guidance/dco-guidelines.md) * Documentation for signing-off/DCO on other projects: [OpenStack](https://docs.openstack.org/contributors/common/dco.html) # Licensing guidelines Our policy on licensing projects and works at Recap Time Squad You have a project to ship or even get adopted under the Recap Time Squad organization, and have reviewed the release policy and checklist, alongside being ready to take the responsibility of an open-source maintainer. One of the requirements is **to have a `LICENSE` file in your repository/project.** This document answers "which license?" ## In a nutshell Our licensing policy for open-source projects is simple: as long as it is OSI-approved, can be maintained in the long term, and does not involve using the "fair source"/open-core model of licensing (unless cleared by the HCB team for dual-licensing or after refactoring), we can allow it to exist within our organization. Note that Hack Club, as our fiscal sponsor per the fiscal sponsorship agreement, will hold the projects' copyrights on our behalf, so be mindful of the license you'll pick. Switching licenses is possible but painful without a CLA (specifically a "copyright transfer" clause). {% hint style="info" %} **TL;DR** * Code (including core projects and anything involving backends/API): [MPL or AGPL, also Apache and/or MIT work too](#software) * Documentation, media, and other non-software: [CC-BY-SA-4.0 (or the regular CC-BY-4.0)](#documentation-and-media-files) * Snippets, data, boilerplate: [MIT might work, but we recommend sticking with CC0](#other-non-software-works) * Something else, special considerations, and edge cases (especially for non-Recap Time Squad project CLAs): file a meta issue and/or contact the HCB team {% endhint %} ## Software Default: MPL-2.0 or AGPL for substantial projects, although MIT and Apache can also be used. Dual-licensing between different OSI-approved licenses is discouraged but we don't mind if you need to (especially when needing the patent-specific provisions of the Apache license). Switching licenses is possible, but both challenging and should only apply on future releases/commits/contributions Technically, any OSI-approved licenses (alongside those cleared by Debian and Fedora Linux projects) alongside the aforementioned defaults should work for new or to-be-adopted projects at Recap Time Squad. But since some projects involve building backend services or are considered major projects, we use [Mozilla Public License v2 (MPL-2.0)](https://choosealicense.com/licenses/mpl-2.0/) and/or [Affero General Public License (AGPL-3.0)](https://choosealicense.com/licenses/agpl-3.0/). In some cases, like API libraries and tooling, we can use [Apache](https://choosealicense.com/licenses/apache-2.0/) or even [MIT](https://choosealicense.com/licenses/mit/). Note that while you can dual-license between them, it is often not recommended to do so due to possible legal headaches, especially for corporate users. You may let downstream users pick which license to follow (especially for forks) or use both, but remind them that upstreaming their patches will be licensed under both. If you need to use another license not mentioned here (either OSI-approved or otherwise), let's talk: TBD ### Considerations on copyleft licenses One of the downsides of copyleft licenses, especially the strongest among them all (the AGPL), is that ## Documentation and media files Default: CC-BY-SA-4.0 (CC-BY-4.0 also works) Occasionally, we publish substantial non-software content (e.g., documentation, media) that we want to give others permission to copy, modify, and distribute if they give us credit and don't use our trademarks, but they need to use the same license. That's what CC-BY-SA-4.0 is for. It works similarly to the GPL (just one-way compatibility if it's happened to be used on software works) as used on Wikimedia projects (including Wikipedia) and MIT for the plain CC-BY-4.0, but is designed for non-software works (e.g., license notice can be provided with a link rather than including a copy of the license text). If you need to use a more restrictive Creative Commons license (e.g., NC[^1] and ND[^2]) or another non-CC license (including dedicating to the public domain via CC0, see next section), let's talk: TBD ### Why the international licenses (unported/generic in v3 and below)? *(see* [*https://opensource.stackexchange.com/a/6553/21717*](https://opensource.stackexchange.com/a/6553/21717) *and* [*https://opensource.stackexchange.com/q/489/21717*](https://opensource.stackexchange.com/q/489/21717) *for context)* While we can opt to use the United States port/version of the Creative Commons licenses since our fiscal sponsor is US-based, we chose the international/unported/generic editions of the Creative Commons license suite to minimize headaches when clarifying someone's use of the licensed work outside the ported license jurisdiction. ## Other non-software works Default: CC0-1.0, but any CC or non-CC license should work (just ask) It's up to you to pick a suitable license for other non-software works, other than the good old CC licenses, but if you don't want to worry about that, dedicating it to the public domain through the CC0 license can be a great option. [CC0-1.0](https://choosealicense.com/licenses/cc0-1.0/) waives all copyright restrictions but reserves trademark and patent rights, making it an easy, unconditional license for Recap Time Squad material when: * burden to the user of maintaining copyright notices forever is large relative to the incremental value of using licensed material, and * there is no demonstrable business value from mandating the maintenance of copyright notices To use the CC0 license: * If you are going to make the whole project CC0 licensed, copy the legal code from [Choose A License website](https://choosealicense.com/licenses/cc0-1.0/) or from [Creative Commons](https://creativecommons.org/publicdomain/zero/1.0/legalcode.en) themselves and paste it in the `LICENSE` file at the root directory. * In the case of particular files or parts of content (e.g., code snippets in documentation) that should be released under CC0-1.0, note this precisely in the repository's README and at the top of the content in question (via code comments, etc.). * If the released material is rendered or published, e.g., as or in web pages, it can also be useful to include a CC-BY-4.0 notice there, e.g., "This documentation is released under CC-BY-4.0", with a link to or the project README's licenses section, depending on the complexity of the situation. * Note that there are zero copyright license requirements when using material released under CC0-1.0, but it is usually best practice to maintain license notices and attribution anyway, as you would for MIT and CC-BY software and non-software above. ## Non-Recap Time Squad projects Recap Time Squad projects utilize the [Linux DCO](/community/open-source/linux-dco) as our contributor license agreement for simplified compliance for contributors at the expense of requiring a referendum on license changes with all contributors and rewriting for those who disagree alongside consulting our fiscal sponsor to make license changes. While not the focus of this document, worth a mention: * If we have to maintain a fork of an open-source license for our use (or even contributing patches as a Recap Time Squad Crew member), simply follow the upstream license to lessen the legal burden. * If a project requires signing the CLA before contributing patches on behalf of the team (either for all contributions or on Enterprise Edition/non-OSS parts), we recommend consulting Andrei Jiroh first and notify the HCB team before signing the Corporate CLA. Alternatively, you can sign the CLA as a individual contributor but please notify us if you do. ## Credits Portions of this policy are adapted from [the licensing guidelines document](https://github.com/github/github-ospo/blob/dd1e5c8c2f05c880e587a6bf339aa806238fc837/policies/licensing.md) at [GitHub's OSPO (Open Source Office) repository](https://github.com/github/github-ospo), licensed under CC BY-SA 4.0 International license. [^1]: Non-Commerical [^2]: Non-Derivative # Release policy and checklist Ready to ship your open-source project under us? Review our release policy before the official hand-off. ## To open-source or innersource? By default, internal projects are considered innersource if the codebase/project sources are accessible only to the team; otherwise, they are open-source if a corresponding OSI-approved license is present. Please note that if you proceed, our fiscal sponsor will hold the copyrights to your project on our behalf. Be sure to consider this when reviewing our licensing guidelines. ### Regarding GitLab for Open-source Program Terms compliance Innersource projects that are private are considered ineligible for hosting on our GitLab SaaS namespaces. For compliance reasons, they should not be mirrored/hosted there unless manually cleared by Andrei Jiroh in coordination with GitLab's open-source program team. If you need to email them, remember to CC `~recaptime-dev/crew.recaptime.dev@lists.sr.ht` in your correspondence. While we can have one private project for purposes of security or moderation decisions (we choose to operate the moderation project in hybrid mode, meaning issues may be confidential, but publish those reports and stats there), we may need clearance from GitLab's open-source program team first or use a separate namespace for that. Alternatively, you can also host them at Tulir Asokan's Manimum GitLab instance under TBD. ## Contributions All contributions to a Recap Time Squad-hosted project are made under the project license in an inbound-outbound model under [the Linux DCO](/community/open-source/linux-dco) to simplify copyright license compliance without doing the admin paperwork on both sides ## Checklist * [ ] [Select an OSI-approved license](/community/open-source/licensing-guidelines) * [ ] Adopt the [Code of Conduct](/community/code-of-conduct) and [Linux DCO](/community/open-source/linux-dco) * [ ] Migrate any project-specific secrets from repository secrets settings to our centralized setup on Doppler or use `dotenvx` to manage encrypted secrets as part of Git history. * [ ] Add contributing guidelines/documentation at `CONTRIBUTING.md` ## Notes ### Why do we call the GitLab.com instance GitLab SaaS? We call the cloud-hosted GitLab.com instance GitLab SaaS to match the SaaS pricing, even though their handbook says otherwise. # Community spaces This page documents about the community spaces ## Forums * GitHub Discussions: * Daily.dev: * Reddit: TBD ## Chat * Zulip Cloud: [https://recaptime-dev.zulipchat.com](https://recaptime-dev.zulipchat.com/) * Discord: * Note that join applications is enabled whilst being an one-person operation in terms of community moderation. You can ask for the invite code/link that bypasses that via this form alongside in select projects' READMEs. * Telegram: TBD ## Socials * Atmosphere (via Bluesky Social and friends): `@recaptime.dev` * Fediverse: `@RecapTimeSquad@mastodon.xyz` * Instagram/Threads: `@RecapTimeSquad`, `@lorebooks.wiki` # Expenses and Reimbursements Policy What Recap Time Squad HQ (and ultimately HCB) can and cannot pay Since Recap Time Squad (and the projects underneat it) runs as a fiscally hosted organization under HCB by Hack Club, funds under our organization and the respective projects (if there's a dedicated HCB organization for it) must be used for expenses that aligns with Hack Club's mission, our open-source work and the non-profit regulations in the United States under the IRS. ## TL;DR * All expenses must comply with 501(c)(3) regulations and align with either Hack Club's mission or our open-source work. * Expenses cannot be paid in advance if it is not paid using the virtual team card issued from the HCB dashboard. * If a vendor requires partial payment for a reservation, a written invoice must be submitted that includes the reservation details and clearly defines a reimbursement policy. * Due to IRS regulations, HCB may be required to collect tax forms before issuing payment. * All funds are held in USD. When submitting an expense, the amount can be paid out in your local currency based on the exchange rate, and any applicable currency conversion fees may apply, mainly Wise transfer fees and/or SWIFT intermediary bank fees. ## Things We Can and Cannot Pay For ### Eligible Expenses In most cases, if it is open source work, it is generally approved. If it is not but aligns with Hack Club's mission, we (and the HCB team by extension) may ask for more context behind the expense or reimbursement request. When we ask for extra details, it's to ensure the expense meets legal and tax requirements. Generally speaking, you can use our funds held on HCB for: * Payments to contributors for completed work (via invoice) * Reimbursements for project-related purchases * Infrastructure costs (e.g., domain hosting, software subscriptions, servers) * Travel costs for project-related events * Most tech conferences and events around open-source work is eligible here, but for things like CES (Consumer Electronics Show) please let us know first. * Shipping, duty, and import fees related to your project * Please include proof of the item being shipped so we can confirm it’s project-related. ### Ineligible Expenses Recap Time Squad HQ funds held on HCB cannot be used for the following: * Personal expenses unrelated to the project (eg: rent, groceries, clothing) * Non-project related travel or entertainment * Donations to unrelated causes or organizations * Work that has not yet been completed (HCB cannot prepay for work) * Anticipated travel costs (e.g., flights, lodging, or other reservations booked before the travel has occurred) * Transferring funds to an LLC related to the project * While this is Open Source Collective-specific guideline, we also noting this in case we decided to set up a LLC to support the non-profit (the Mozilla way, not the reverse like the OpenAI way). * Expenses that do not align with Hack Club's mission (eg: unrelated business activities that do not support open source) * Expenses without a clear connection to the project's open source work * Giftcards (mainly due to fraud risk) In case the team card is used for these expenses, you will be required to flag it as a personal transaction from the transaction and reimburse the organization/project back the funds use. If you can't pay back within the next 30 days, please let us know so we can note it but you will be expected to return the funds back as soon as possible (to avoid having trouble with the accountant and auditor). ### Need help with eligibility checks? **When in doubt, please reach out first before spending to save on headaches later on.** You can ask us in `#TBD` Zulip channel, [`#hcb-org-ops` Discord channel](https://discord.com/channels/1309180322138816583/1311351336767324371) ([`#hcb-ops` for Alumni Society maintainers](https://discord.com/channels/1442799920649207889/1455279425540067449) in the Alumni Society Discord server). Alternatively, you may file a issue in the meta issue tracker on GitLab SaaS (also: Alumni Society) or GitHub (also: Alumni Society) or at the dedicated HCB issue tracker on [YouTrack Cloud](https://youtrack.recaptime.dev/projects/HCB). ## Credits / Prior Art Portions of this policy were inspired from [Open Source Collective's expense policy](https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/expense-policies-and-limitations), tweaked and adjusted for our setup under a 501(c)(3) legal entity instead of a 501(c)(6) one ([see related Discord thread](https://discord.com/channels/1241017531318276158/1455260321588576428) regarding license/credits at Open Collective/OFi Community Discord server). # Staff SSO Usage Policy Your RecapTime.dev Staff SSO account is a Google Cloud Identity organization account managed independently from the one that Hack Club uses both at the HQ and for eligible HCB organizations. It is being planned to utilize Authentik (the same system that powers Hack Club Nest Identity) as our primary authentication service for both public-facing and internal services over the coming weeks and months. ## Technical details and limitations Currently, we set up our own Google Cloud Identity organization for purposes of SSO SAML in apps like Tailscale and Cloudflare Zero Trust/Access and use of the Google Cloud Platform, and not for Google Workspace apps (we're currently in our fiscal host's waiting list for their Google Workspace organization at the moment). The plan is we will migrate to Cloudflare Access once we officially onboarded there after the needed migration work. If you need an app to have SSO SAML enabled, please file a issue in [the InfraOps issue tracker](https://gitlab.com/recaptime-dev/infra/ops/-/issues) using the Access Requests - Authentication Setup description template (issue form for GitHub). ## Terms of use You must only use your Staff SSO account, alongside [your crew/community email address](https://support.recaptime.dev/category/18-roundcube-webmail), for official and work related use only. As a crew member or community maintainer at RecapTime.dev HQ, it’s your responsibility to report any suspected login attempts and account security issues to Andrei Jiroh and keep your login credentials stored in a safe place, preferrably in [a password manager we use](/staff/1password-and-vaultwarden). Any use of it will also be governed by the Community Code of Conduct, alongside this one. ## Privacy Policy *This privacy policy is specific to how we manage Staff SSO.* # 1Password and Vaultwarden Usage ## 1Password Our 1Password for Teams account (`recaptime-dev.1password.com`) is provided at no cost as part of [the 1Password for Open-source program](https://github.com/1password/for-open-source), with benefits such as: * developer integrations through managing SSH keys and signing Git commits, authenticating CLIs with biometrics, and securing secrets throughout projects * free password manager across your devices for open-source work at Recap Time Squad and friends (you may use your Employee vault for personal use but it's strongly discouraged) Team organizations in 1Password can have up to 10 regular users and 5 guests, so slots are limited at the moment (and the break-glass account can't be used daily due to the risk of abusing elevated permissions). If you need to login to our socials, we can issue you a share link scoped to your `@crew.recaptime.dev` address for just-in-time access. ## Vaultwarden Our Vaultwarden organization (hosted on our instance at `vault.recaptime.dev` at Hack Club Nest) is available for those who use Bitwarden, although the credentials stored there may be outdated due to our use of 1Password. # Branding guidelines Understand how to properly use our brand assets and more {% hint style="warning" %} **We're working on this page at the moment.** This is not the final version at the moment, but we're working hard on ironing out possible issues and covering edge cases behind the scenes. If you see this notice at the homepage, that means the entire policies site is being worked on right now but we publish working drafts to production to allow us to collect feedback early on during policy developments. {% endhint %} ## Brand colors Our official brand colors are derived from our brand icon/logo with the following hex codes: * `#bff6f9` * `#f8049c` * `#fdd54f` ## Brand kit **For team members with Canva team access**: You can access our brand kit [here](https://www.canva.com/brand/kAELnLoO9cY) or by searching for `Recap Time Squad` it in the Brand Kits section of the Canva app. You might need to switch teams if you use your personal account instead of signing up/in via your `@crew.recaptime.dev` email address. **For everyone else**: We're working on publishing our brand kit for public use in the future, but in the meantime, please come back here for any updates. # HCB-specific branding guidelines How to talk about our fiscal hosting status, among other things As one of the fiscally hosted organizations by Hack Club, we have HCB-specific branding guidelines on how to properly mention our fiscal sponsorship status to anyone, not just prospective sponsors and donors but for legal purposes. {% hint style="warning" %} For the official guidance on how to use HCB brand assets alongside our own HCB badges through [Community Lorebooks' Badges API service](https://github.com/lorebooks-wiki/badges-api/blob/main/docs/hackclub-badges.md) (or the official ones) from the HCB team, visit [hcb.hackclub.com/branding](https://hcb.hackclub.com/branding). When in doubt, don't hesitate to reach out to Andrei Jiroh the HCB team for clarification and assistance. {% endhint %} ## Stating fiscal sponsorship status ## On using "fiscal host" vs "fiscal sponsor" ## Using proof of fiscal sponsorship documents {% hint style="info" %} When we say "proof of fiscal sponsorship", we mean the fiscal sponsorship agreement itself between us as the organization (and the projects under it) and the HCB team, alongside the IRS determination letter, confirmation letter, and bank account verification letters. {% endhint %} # Style Guide {% hint style="danger" %} This is currently left blank at the moment while we are developing this behind the scenes. {% endhint %} ## See also