├── CODE_OF_CONDUCT.md ├── .github └── ISSUE_TEMPLATE │ └── question.md ├── LICENSE-MIT ├── README.md ├── LICENSE-APACHE └── FAQ.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # The Rust Code of Conduct 2 | 3 | The Code of Conduct for this repository [can be found online](https://www.rust-lang.org/conduct.html). 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/question.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Question 3 | about: Ask a question 4 | --- 5 | 6 | 12 | -------------------------------------------------------------------------------- /LICENSE-MIT: -------------------------------------------------------------------------------- 1 | Permission is hereby granted, free of charge, to any 2 | person obtaining a copy of this software and associated 3 | documentation files (the "Software"), to deal in the 4 | Software without restriction, including without 5 | limitation the rights to use, copy, modify, merge, 6 | publish, distribute, sublicense, and/or sell copies of 7 | the Software, and to permit persons to whom the Software 8 | is furnished to do so, subject to the following 9 | conditions: 10 | 11 | The above copyright notice and this permission notice 12 | shall be included in all copies or substantial portions 13 | of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF 16 | ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 17 | TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 18 | PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 19 | SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY 20 | CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 21 | OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR 22 | IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 23 | DEALINGS IN THE SOFTWARE. 24 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Rust Foundation 2020 Q&A 2 | 3 | ⭐️ [**Read the summary of questions and answers so far in our FAQ!**][faq] ⭐️ 4 | 5 | After this summer's ["Laying the foundation for Rust's future"][aug-blog] blog 6 | post the [Rust Foundation Project Group] began the work to setup a new home for 7 | the Rust Project. We're getting near the end of the work, and we'd love to 8 | answer all the questions you have on the Rust Foundation! 9 | 10 | We welcome everyone to post their questions as [new issues][new], and the team 11 | will do their best to answer them! You can also check [the open issues][issues] 12 | to see what other people asked and the answers to their questions. If you can't 13 | open GitHub issues or want to send questions privately you can send them via 14 | email to . 15 | 16 | Please note that if an issue is labelled [`answered`] the team will not return 17 | to it, so if you have a follow up question, please post it as a new issue. 18 | 19 | ## FAQ 20 | 21 | Periodically, we'll be summarizing the set of questions and answers on the 22 | issue tracker and collecting them in an [FAQ][faq]. 23 | 24 | ## Maintainer Q&A 25 | 26 | The members of the [Rust Core Team] will answer questions from the members of the 27 | Rust Team starting from December 2nd. 28 | 29 | ## Community Q&A Sessions 30 | 31 | Members of the Rust community will be able to ask questions of the [Rust Core Team] by filing issues on this repository during the following time periods: 32 | 33 | | | PST US | EST US | UTC Europe/Africa | India | China | 34 | |-------------------------------------------------|--------|--------|--------------------|-------------------------|------------------| 35 | | Dec 7th ([View in my timezone][dec7-session]) | 3-6pm | 6-9pm | 23:00-2:00 | 4:30am-7:30am (Dec 8) | 7am-10am (Dec 8) | 36 | | Dec 9th ([View in my timezone][dec9-session]) | 4-7am | 7-10am | 12:00-15:00 | 5:30-8:30pm | 8pm-11pm | 37 | | Dec 11th ([View in my timezone][dec11-session]) | 10-1pm | 1-4pm | 18:00-21:00 | 11:30pm-2:30am | 2am-5am (Dec 12) | 38 | 39 | 40 | ## Live Broadcasts 41 | 42 | In addition to this repository, we’ve scheduled two “live broadcasts”. 43 | These sessions will feature members of the core team discussing and responding 44 | to some of the questions that have been asked thus far. Naturally, even if you 45 | can’t catch the live broadcast, the video will be available for streaming 46 | afterwards. 47 | 48 | | | | PST US | EST US | UTC Europe/Africa | India | China | 49 | |---------------------------------------------------|----------------------------|--------|--------|--------------------|-------------------------|------------------| 50 | | Dec 9th ([View in my timezone][dec9-broadcast]) | [Watch on YouTube][live-1] | 3-4pm | 6-7pm | 23:00-24:00 | 4:30-5:30am (Dec 10) | 7-8am (Dec 10) | 51 | | Dec 12th ([View in my timezone][dec11-broadcast]) | [Watch on YouTube][live-2] | 4-5am | 7-8am | 12:00-13:00 | 5:30pm-6:30pm | 8-9pm | 52 | 53 | ### Things to keep in mind 54 | 55 | Please keep in mind that the Foundation is still in its final stages of being 56 | set up. This means that we are not able to talk about sponsors or specific 57 | details of legal documents at this time. 58 | 59 | Additionally: none of the members of the [Rust Core Team] are lawyers, but we 60 | have been working closely with lawyers. Many questions may end up touching on 61 | legal issues; the [Rust Core Team] will do its best to communicate its 62 | understanding, but we'd like to keep disputes of the law out of this forum to 63 | the extent that we can! 64 | 65 | [Rust Foundation Project Group]: https://www.rust-lang.org/governance/teams/core#project-foundation 66 | [Rust Core Team]: https://www.rust-lang.org/governance/teams/core 67 | [dec7-session]: https://everytimezone.com/s/213ef6bd 68 | [dec9-session]: https://everytimezone.com/s/f10ec849 69 | [dec11-session]: https://everytimezone.com/s/3c5c1b75 70 | [dec9-broadcast]: https://everytimezone.com/s/a0b6bb44 71 | [dec11-broadcast]: https://everytimezone.com/s/8e88716f 72 | [aug-blog]: https://blog.rust-lang.org/2020/08/18/laying-the-foundation-for-rusts-future.html 73 | [issues]: https://github.com/rust-lang/foundation-faq-2020/issues 74 | [new]: https://github.com/rust-lang/foundation-faq-2020/issues/new?template=question.md 75 | [faq]: https://github.com/rust-lang/foundation-faq-2020/blob/main/FAQ.md 76 | [`answered`]: https://github.com/rust-lang/foundation-faq-2020/labels/answered 77 | 78 | [live-1]: https://www.youtube.com/watch?v=OmEcRWyT6Ak 79 | [live-2]: https://www.youtube.com/watch?v=42ZWHYWv9Ic 80 | -------------------------------------------------------------------------------- /LICENSE-APACHE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | -------------------------------------------------------------------------------- /FAQ.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions 2 | 3 | * [Overview of the foundation](#overview-of-the-foundation) 4 | * [What's the name of the foundation?](#q-name) 5 | * [Why an independent foundation?](#q-why-independent) 6 | * [Who will the sponsors of the foundation be?](#q-sponsors) 7 | * [Purpose and scope](#purpose-and-scope) 8 | * [What is the purpose of the Rust foundation?](#q-purpose) 9 | * [What is the initial scope of the foundation?](#q-scope) 10 | * [Will the foundation hire every Rust contributor?](#q-hiring) 11 | * [Who will have control over the Rust trademark?](#q-trademark) 12 | * [Is supporting events like the Rust All-Hands in scope for the foundation?](#q-all-hands) 13 | * [Location of incorporation](#location-of-incorporation) 14 | * [Where are we incorporating?](#q-location) 15 | * [Why are we incorporating in the US?](#q-usa) 16 | * [Will the foundation being based in the US prevent contributing to Rust?](#q-usa-contributors) 17 | * [Will the foundation only hire in the US?](#q-usa-hiring) 18 | * [Will there only be one Rust foundation long term?](#q-multiple) 19 | * [Governance structure of the foundation](#governance-structure-of-the-foundation) 20 | * [Why will the Rust Foundation be a 501(c)(6)?](#q-501c6) 21 | * [How will the foundation structure its board, bylaws and operations?](#q-bylaws) 22 | * [Will all the documents, rules and bylaws be available publicly and versioned?](#q-versioned-bylaws) 23 | * [As an individual, can I donate money to the Rust Foundation?](#q-individual-donations) 24 | * [As an individual, can I become a member of the foundation?](#q-individual-membership) 25 | * [As an individual, can I volunteer for the Rust Foundation?](#q-individual-volunteer) **✨ New answer! ✨** 26 | * [Will Rust maintainers have a voice in the foundation?](#q-individuals) 27 | * [Will the foundation share insights into its finances?](#q-finances) 28 | * [Will the board members and officers be compensated?](#q-board-compensation) 29 | * [Will there be rules in places to prevent financial abuse?](#q-financial-abuse) 30 | * [What prevents organizational capture of the foundation?](#q-organizational-capture) 31 | * [Will the foundation revisit the trademark policy?](#q-trademark-policy) 32 | * [Relationships of the foundation](#relationships-of-the-foundation) 33 | * [What's the relationship between the foundation and the project?](#q-rel-project) 34 | * [What's the relationship between the foundation, the infrastructure and crates.io?](#q-rel-infra) 35 | * [What's the relationship between the Rust Foundation and other foundations?](#q-rel-foundations) 36 | * [How will the Rust foundation participate in Rust conferences?](#q-rel-conferences) 37 | * [Will the foundation share its experience with others?](#q-sharing-experience) 38 | 39 | ## Overview of the foundation 40 | 41 | 42 | **🤔 Q: What's the name of the foundation?** 43 | 44 | 💁 A: The name of the foundation will be "Rust Foundation"! 45 | 46 | 47 | **🤔 Q: Why an independent foundation?** 48 | 49 | 💁 A: After spending a significant amount of time researching potential umbrella organizations, we decided that our best option was to incorporate an independent entity. Rust is a technology and community that is value driven and we simply didn’t find an organization that we felt was aligned with our community goals. This does mean more work for us, especially upfront, but we think the tradeoff is worth it. 50 | 51 | 52 | **🤔 Q: Who will the sponsors of the foundation be?** 53 | 54 | 💁 A: We’re not able to answer this question yet. There will be a public announcement sometime in January. 55 | 56 | ## Purpose and scope 57 | 58 | 59 | **🤔 Q: What is the purpose of the Rust foundation?** 60 | 61 | 💁 A: The Rust foundation’s purpose is to enable Rust maintainers to do their best work happily. The Rust core team believes that the best Rust will be made by happy maintainers, and focusing the Foundation’s efforts on maintainers will provide for a better Rust for all. 62 | 63 | The Foundation’s structure includes active project members on the board who will guide the Foundation’s efforts to best serve the needs of the Rust project. 64 | 65 | 66 | **🤔 Q: What is the initial scope of the foundation?** 67 | 68 | 💁 A: The central goal of the Foundation is to enable Rust contributors, especially those that are volunteering and not supported by their employer. To that end, the Foundation will offer training, software, and structural support for contributors to the Rust project. Contributors are engaged in all kinds of activities, ranging from writing software code to moderating forums to translation, and each needs a distinct form of support. We expect that the Foundation will be able to start providing support for the activities within the first year. A few examples of ways the Foundation could support contributors: 69 | 70 | * Access to a lawyer if a team needs legal advice, such as on how to handle DMCAs for the crates.io team, or resolving licensing questions from the compiler team 71 | * Paying for tools and services a team needs, like a video calls platform for a team that wants to run sync meetings or a helpdesk tool for help@crates.io. 72 | * Supporting efforts to grow and diversify Rust’s leadership, such as Increasing Rust’s Reach 73 | * Running the annual survey to provide insights to the teams on what the wider community wants to see from the project. 74 | 75 | To be clear, those are just examples that the future board of directors will need to decide whether to approve or not, and it’s definitely not an exhaustive list. The role of the foundation is to serve the project, not the other way around: Rust contributors should see the Rust Foundation as a helpful resource to empower their work. If a team needs something they’ll be encouraged to reach out to the foundation to solve their needs. 76 | 77 | In terms of assets, the Foundation will own and steward the trademarks. It will also own crates.io and the project’s infrastructure, but the operations and decision-making for those will continue to be in the hands of the current teams. 78 | 79 | 80 | **🤔 Q: Will the foundation hire every Rust contributor?** 81 | 82 | 💁 A: No, but it may hire for a few specialized roles, such as infrastructure and on-call work. However, we do plan to incentivize and encourage companies to hire people to work on Rust (not just in Rust). 83 | 84 | One of the primary goals for the Foundation is to help folks get paid for their work on Rust. We think that’s critical for the long-term sustainability of the project and a core part of our mission. However, we don’t think the right way to do it is to have the Foundation hire a bunch of people directly. 85 | 86 | Why not hire folks? For one thing, we don’t think a Foundation would be able to pay them what they’re worth or support them in the way they should be supported. We would have to hire human resourcing people, managers, figure out peoples’ design goals and career path, and do all the other things that a good employer does, and that is not practical. 87 | 88 | So, if we’re not hiring people, what are we doing instead? Our plan is to provide incentives that encourage companies to hire Rust developers. One way we are doing this is by providing discounts on the membership fees for every existing team member employed by a sponsor to work full time on the project. We also plan to create a place for team members to note they’re available to be hired to work on the project. (If you have other ideas for how we can incentivize companies to give people paid time to work on Rust, we’d love to hear them!) 89 | 90 | Part of the strength of open source is that it is a great way to enable people from many companies, with many needs, to actively collaborate. If you have everyone working in one company (even a Foundation), you will do a good job solving that company’s problems, but you may totally overlook other kinds of problems. Bringing in that pluralist set of viewpoints is precisely what Rust is all about. 91 | 92 | 93 | **🤔 Q: Who will have control over the Rust trademark?** 94 | 95 | 💁 A: Mozilla is the current owner of the Rust trademarks and they have committed to transferring it to the Foundation at its incorporation. 96 | 97 | 98 | **🤔 Q: Is supporting events like the Rust All-Hands in scope for the foundation?** 99 | 100 | 💁 A: Yes! Events targeted at maintainers are definitely in scope, and we’d love to go beyond just a yearly All-Hands. One example from the past is impl days, and we’d enjoy running it again. 101 | 102 | ## Location of incorporation 103 | 104 | 105 | **🤔 Q: Where are we incorporating?** 106 | 107 | 💁 A: The Rust Foundation will be incorporated as a US 501(c)(6) organization in the state of Delaware. We explored a number of alternatives, including Canada, Switzerland, Belgium, and the EU, but ultimately decided that the US would be our best choice. 108 | 109 | The Rust project has contributors and users from all over the world, and one of the pillars of our work has been to ensure Rust keeps being a global project. We consulted leaders of other foundations and our own lawyers, and the conclusion we reached is that no matter where the foundation is located in the world there will always be a subset of people who might have trouble interacting with the Foundation. 110 | 111 | There is no location that we can incorporate in that would effortlessly make us global by default. We will constantly make sure it represents and includes people from all over the world, not just the US: ensuring a foundation is global is not something we can do at the start and then forget about it, it’s a continuous effort. 112 | 113 | 114 | **🤔 Q: Why are we incorporating in the US?** 115 | 116 | 💁 A: We had some questions over the years that asked whether a potential Rust foundation will be outside of the US. For that reason, we spent time researching alternative locations. We came to the conclusion that the US was the best choice given our constraints. While there are good reasons to pick other locations, the potential benefit of those locations did not outweigh the costs. 117 | 118 | Our goal for the foundation is to make the incorporation location matter as little as possible for accessing its services and being represented by it. Participation in the project is currently accessible -- and the IP policy for the project is set by a US corporation today too. There are no concrete blockers to contributions to the project due to the Foundation’s location. 119 | 120 | Based on our research, in most cases the problems caused by an organization being in a specific country are operational; there are no insurmountable barriers put forth by legal restrictions. We are committed to investing the time into building operational practices that ensure global participation is not only possible but prioritized. 121 | 122 | 123 | **🤔 Q: Will the foundation being based in the US prevent contributing to Rust?** 124 | 125 | 💁 A: There are no current or anticipated impedances to contribution to the Rust project for any set of entities. Rust’s original steward, Mozilla, was also incorporated in the U.S., so the transfer of intellectual property and trademark to a 501(c)(6) in the U.S. doesn’t materially change anything. The lack of impedance to global contribution is derived from the completely open and public development and design of the Rust project, but to get more in depth on this would veer dangerously close to legal analysis, which we want to avoid because we are not lawyers. While not definitive, and not necessarily representative of the Foundation’s perspective, [this post by GitHub](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/) is a good introduction to the topic for folks that are interested. 126 | 127 | 128 | **🤔 Q: Will the foundation only hire in the US?** 129 | 130 | 💁 A: The foundation will hire globally, not only in the US. As part of choosing the location, we prioritized research into the options for how to manage this effectively. One common strategy is to use a Global Professional Employment Organization (PEO), which is an intermediary company that specializes in managing employees and employment laws around the globe. Ultimately, of course, the foundation is responsible for deciding on these sorts of operational details. 131 | 132 | 133 | **🤔 Q: Will there only be one Rust foundation long term?** 134 | 135 | 💁 A: There is certainly nothing preventing a future where there are a plurality of Rust Foundations, though, at least for the moment I, personally, see more cost than benefit. It is worth considering the challenges it could bring to fundraising were there to be more than one place to donate; We think it'd be unfortunate to have multiple Foundations competing with each other for funding. Additionally, every new individual foundation would have operational overhead, which would divert money from Foundation causes. Then there is the potential overhead of having to coordinate efforts across multiple Foundations, or, if we were to fail to coordinate, the overhead of managing the lack of consensus . In my head it’s a classic distributed systems vs monolith tradeoff. We don’t know what the future will hold, but we can say that the Core Team definitely discussed this possibility, and we agreed that if it were to be something folks decided was the right call, it would need to be done thoughtfully, and likely be several years in the future. 136 | 137 | ## Governance structure of the foundation 138 | 139 | 140 | **🤔 Q: Why will the Rust Foundation be a 501(c)(6)?** 141 | 142 | Practically speaking, the distinction between 501(c)(3) and 501(c)(6) matters the most when it comes to US-specific paperwork filed with the IRS. Creating a 501(c)(6) is much faster (it doesn’t require nearly as much authorization from the IRS) and it gives us more flexibility. It does mean that donations from US individuals are not necessarily tax deductible, but this only matters to a small audience (US taxpayers who do itemized returns and for whom the donation does not qualify as a business expense). For companies in the US, donations are deductible either way. 143 | 144 | The more interesting question is the story around constituencies and priorities. 145 | 146 | A 501(c)(3), also called a Public Charity, is a group of people with an “exclusively charitable interest”. The definition of this is where a lot of the difficulty with the IRS comes in, as it’s up for interpretation and that interpretation is driven by previous cases and outcomes. You can read more about these [here][irs-501c3]. While it would be completely possible to make the case for a 501(c)(3) - making the case, and continuing to make the case would be a lot of effort for what we determined was very little benefit. 147 | 148 | A 501(c)(6), also called a Trade Association, is an association of people with a common interest. Historically, most open source software foundations have defined that interest as the successful adoption of the technology, often with an implicit assumption that that adoption be by for-profit corporate entities. 149 | 150 | In the case of Rust, we are taking a different approach. While the above definition is common, it is by no means legally required by the 501(c)(6) designation. What is legally required is that the association's “activities must be devoted to improving business conditions of one or more lines of business”. The public policy idea here is that society benefits from industry practitioners gathering to improve their craft. 151 | 152 | The practitioners here are the users and maintainers of Rust, and the craft is using Rust. The interesting part is deciding what “improving business conditions” means. In our case, we are very explicitly defining our common interest as the health, vibrancy, and sustainability of the Rust open source organization as being the most direct way to improve the craft of using Rust. We think we are in a moment where folks are questioning the economic and organizational models around open source and are looking for a change and we’ve had enthusiastic reception from potential sponsors! 153 | 154 | [irs-501c3]: https://www.irs.gov/publications/p557#en_US_202001_publink1000200022 155 | 156 | 157 | **🤔 Q: How will the foundation structure its board, bylaws and operations?** 158 | 159 | 💁 A: We’re still finalizing all the details around the foundation, and we plan to have the legal documents approved by the end of the year. Once that happens we’ll announce everything around how the foundation works. 160 | 161 | Still, there are a few things we can say now: 162 | 163 | * The board will have representatives from both sponsor companies and project directors. 164 | * The project directors will be drawn from active Rust team members. 165 | * In true Rust spirit, we are structuring things so as to encourage active collaboration between the sponsor representatives and the project directors. For example, the draft by-laws require that all motions be approved with both a majority of project directors and a majority of sponsor representatives. 166 | 167 | Something else that’s very important to us: we want the workings of the Foundation to be accessible to everyone. To that end, we are planning to release not only the “legal bylaws” but also “human readable” versions (translated into multiple languages), as well as “guidebook”-like materials to help folks understand what it means to be a part of the foundation. 168 | 169 | 170 | **🤔 Q: Will all the documents, rules and bylaws be available publicly and versioned?** 171 | 172 | 💁 A: Transparency is a core value of the Foundation, and we do intend to make our documents available and accessible. We’re not sure that we’ll be able to provide diffs, but we’d like to do this. We’ll need to see if it is feasible! We are planning on publishing human-readable versions, including translations, and those should be much shorter and easier to compare. 173 | 174 | 175 | **🤔 Q: As an individual, can I donate money to the Rust Foundation?** 176 | 177 | 💁 A: Not yet but perhaps in the future. To start, we explicitly prioritized getting donations from companies over individuals. We believe that individuals -- especially those currently contributing to the Rust project -- already give so much to the project. While we have a number of corporate sponsors for Rust's infrastructure already, we have not been able to sponsor the Rust project’s broader needs in a directed manner quite yet. We want companies to take responsibility for giving back to the Rust community and project for the value that volunteers bring; their sponsoring the Rust Foundation is one key way for them to do so. The question on [hiring contributors](#q-hiring) also talks about some of the other ways we’re encouraging investment in the Rust project from our corporate sponsors. 178 | 179 | 180 | **🤔 Q: As an individual, can I become a member of the foundation?** 181 | 182 | 💁 A: We have talked about expanding the set of members to cover Rust team members and maintainers, but we don’t have current plans to extend the membership to cover individual Rust users. That seems like a really nice thing to do, but it’s quite difficult to get right, and so we have opted to let the foundation decide if/when to pursue it. 183 | 184 | 185 | **🤔 Q: As an individual, can I volunteer for the Rust Foundation?** 186 | 187 | 💁 A: We should make it easy for people to figure out how to help. We feel that the best way to do this would be to avoid creating “foundation volunteers” vs “project volunteers”, and instead to just have the concept of “Rust volunteers”. 188 | 189 | It may be helpful to consider an example. In an earlier question, we mentioned our plan to produce human readable by-laws and translate them into multiple languages. Instead of having the foundation solicit its own set of translators, we contacted the Rust Community team who agreed to organize and staff this effort. (Big shoutout in advance to all the people who will help with this, along with the people who do translation for Rust in general: you all are the best!) 190 | 191 | 192 | **🤔 Q: Will Rust maintainers have a voice in the foundation?** 193 | 194 | 💁 A: Yes, absolutely Rust maintainers have a voice. The Foundation board will have a number of seats that are occupied by Rust team members and who are tasked with representing the project. Moreover, the current draft of the by-laws ensures that all decisions will require support from those directors and the directors appointed by the sponsors. 195 | 196 | One note: in a legal sense, the draft by-laws of the Foundation provide for both “corporate” and “individual” membership. As a temporary measure, this “individual membership” is defined as being equal to the core team. It is the core team’s intent to expand that set to cover the Rust teams more generally. Figuring out the right shape for such a process will require both time and broader consultation with the community as well as approval from the Foundation’s board, however, so we decided to defer that until after the Foundation is up and going. 197 | 198 | 199 | **🤔 Q: Will the foundation share insights into its finances?** 200 | 201 | 💁 A: Yes, the Foundation definitely intends to make financial transparency a high priority. You can expect regular reports that discuss what the foundation has done and financial details. 202 | 203 | 204 | **🤔 Q: Will the board members and officers be compensated?** 205 | 206 | 💁 A: We expect the Foundation to hire for a full-time paid leadership position, appointed by the board. The foundation will likely have other paid staff, that handle things like legal, accounting, and managing Rust’s infrastructure. We do not expect that board members will be compensated initially, but we did leave room for the board to authorize a stipend for volunteers that would not otherwise be able to make the time commitment. 207 | 208 | 209 | **🤔 Q: Will there be rules in places to prevent financial abuse?** 210 | 211 | 💁 A: When it comes to preventing financial abuse, long term operation of the foundation requires ‘defense in depth’. For general transparency we expect to be publishing regular reports with financial details. At the whole-board level (consisting of both project members and sponsor representatives), financial oversight is one of their responsibilities. Finally, an important piece of context is the concept of individual fiduciary duty: directors are always expected and legally bound to work in the best financial interests of the foundation. 212 | 213 | 214 | **🤔 Q: What prevents organizational capture of the foundation?** 215 | 216 | 💁 A: We have endeavored to construct the Foundation such that there are a plurality of voices on the board and those voices have power. 217 | 218 | Unlike many software foundation boards, the project itself will appoint a significant number of directors to the board to sit alongside the corporate directors, as we mentioned in the answer to [“Will Rust maintainers have a voice in the foundation?”](#q-individuals). 219 | 220 | Additionally, the board is structured in a way that has limits on the power that any one particular entity can have. While the bylaws are still in draft, they contain several rules to prevent organizational capture, for example: 221 | 222 | - Limits to the number of directors that can be employed by a single entity 223 | - Limits to the number of votes an entity has, if it there are multiple legal subsidiaries represented on the board 224 | - Quorum and voting decisions requiring majorities from both project directors and corporate directors 225 | 226 | 227 | **🤔 Q: Will the foundation revisit the trademark policy?** 228 | 229 | 💁 A: The foundation will be reviewing the trademark policy, but it will ultimately be up to the board to decide the terms that are selected. 230 | 231 | ## Relationships of the foundation 232 | 233 | 234 | **🤔 Q: What's the relationship between the foundation and the project?** 235 | 236 | 💁 A: The Foundation is set up to **support and complement** the existing Rust teams. It doesn’t have a role in accepting RFCs, for example, nor does it control the membership of the Rust teams. A good mental model is to think of the Foundation as a resource that teams can use to address their needs. [See this question](#q-scope) for some examples of the kinds of things we have in mind. The project also has strong representation on the foundation board. [You can read more about that here](#q-bylaws). We expect to be posting more on this topic, perhaps in a blog post or other document, but hopefully this gives you a good sense for the plan. 237 | 238 | 239 | **🤔 Q: What's the relationship between the foundation, the infrastructure and crates.io?** 240 | 241 | 💁 A: All the project infrastructure will be legally owned by the Rust Foundation, including the crates.io package registry. The foundation will pay for the infrastructure, but the infrastructure will be directed by the Rust teams. 242 | 243 | 244 | **🤔 Q: What's the relationship between the Rust Foundation and other foundations?** 245 | 246 | 💁 A: No plans at the moment! This will be for the Foundation itself to decide, but we’re excited for the possibility to have organizational relationships in the future! 247 | 248 | 249 | **🤔 Q: How will the Rust foundation participate in Rust conferences?** 250 | 251 | 💁 A: An amazing thing about the Rust Project is that we have developed many of the functionalities that you might expect in a Foundation on the Project side of things. Rust has a community team that has been stewarding the development of a strong network of community organisers, running conferences and spreading organisational experience. 252 | 253 | Developing this independent federation of community events is incredibly valuable. Were this not to exist, we could imagine needing a Foundation that would invest more heavily, but as it were- the Rust community has been [doing a fantastic job of this](https://blog.rustfest.eu/rustfest-project-announcement). 254 | 255 | We do expect that supporting the community team in stewarding this work would be in scope for the foundation. We are reminded of a skillshare between event organizers that they ran at the Rust Impl Days in Paris in 2018 - a “teach the teachers” workshop. Ensuring that the Rust Community team can continue to be fantastic leaders is directly aligned with the Foundation’s goal of supporting maintainers. 256 | 257 | 258 | **🤔 Q: Will the foundation share its experience with others?** 259 | 260 | 💁 A: As we worked to design the Foundation we spoke with many officers, directors, and lawyers from other software Foundations. Learning from others is a cornerstone of the Rust Project, and the Foundation effort is no different. Once fully established, we expect the Foundation to eagerly share experiences with others and continue to learn from others’ experiences in turn. 261 | --------------------------------------------------------------------------------