-
Notifications
You must be signed in to change notification settings - Fork 303
Foundation Conversation kickoff #734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ashleygwilliams
merged 1 commit into
rust-lang:master
from
Mark-Simulacrum:foundation-convo
Dec 7, 2020
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
--- | ||
layout: post | ||
title: "The Foundation Conversation" | ||
author: The Rust Core Team | ||
release: false | ||
--- | ||
|
||
In August, we on the Core Team [announced our plans to create a Foundation](https://blog.rust-lang.org/2020/08/18/laying-the-foundation-for-rusts-future.html) by the end of the year. Since that time, we’ve been doing a lot of work but it has been difficult to share many details, and we know that a lot of you have questions. | ||
|
||
# The "Foundation Conversation" | ||
|
||
This blog post announces the start of the “Foundation Conversation”. This is a week-long period in which we have planned a number of forums and opportunities where folks can ask questions about the Foundation and get answers from the Core team. It includes both text-based “question-and-answer” (Q&A) periods as well as live broadcasts. We’re also going to be coming to the Rust team’s meetings to have discussions. We hope that this will help us to share our vision for the Foundation and to get the community excited about what’s to come. | ||
|
||
A secondary goal for the Foundation Conversation is to help us develop the Foundation FAQ. Most FAQs get written before anyone has ever really asked a question, but we really wanted to write a FAQ that responds honestly to the questions that people have. We’ve currently got a draft of the FAQ which is based both on questions we thought people would ask and questions that were raised by Rust team members thus far, but we would like to extend it to include questions raised by people in the broader community. That’s where you come in! | ||
|
||
## How to join the conversation | ||
|
||
There are many ways to participate in the Foundation Conversation: | ||
|
||
* **[Read the draft FAQ we’ve been working on][FAQ]**. It contains the answers to some of the questions that we have been asked thus far. | ||
* **Fill out our [survey]**. This survey is designed to help us understand how the Rust community is feeling about the Foundation. | ||
* **Ask questions during the Community Q&A periods**. We’ve scheduled a number of 3 hour periods during which the foundation-faq-2020 repo will be open for anyone to ask questions. There will be members of the core team around during those periods to answer those questions as best we can. | ||
* **Watch our Live Broadcasts**. We’ve scheduled live broadcasts this week where members of the core team will be answering and discussing some of the questions that have come up thus far. These will be posted to YouTube later. | ||
|
||
Read on for more details. | ||
|
||
## The foundation-faq-2020 repository | ||
|
||
We have chosen to coordinate the Foundation Conversation using a GitHub repository called [foundation-faq-2020]. This repository contains the [draft FAQ][FAQ] we’ve written so far, along with a series of issues representing the questions that people have. Last week we opened the repository for Rust team members, so you can see that we’ve already had quite a few questions raised (and answered). Once a new issue is opened, someone from the core team will come along and post an answer, and then label the question as “[answered]”. | ||
|
||
## Community Q&A sessions | ||
|
||
We have scheduled a number of 3 hour periods in which the repository will be open for anyone to open new issues. Outside of these slots, the repository is generally “read only” unless you are a member of a Rust team. We are calling these slots the “Community Q&A” sessions, since it is a time for the broader community to open questions and get answers. | ||
|
||
We’ve tried to stagger the times for the “Community Q&A” periods to be accessible from all time zones. During each slot, members of the core team will be standing by to monitor new questions and post answers. In some cases, if the question is complex, we may hold off on answering right away and instead take time to draft the response and post it later. | ||
|
||
Here are the times that we’ve scheduled for folks to pose questions. | ||
|
||
| | PST US | EST US | UTC Europe/Africa | India | China | | ||
|-------------------------------------------------|--------|--------|--------------------|-------------------------|------------------| | ||
| Dec 7th ([View in my timezone][dec7-session]) | 3-6pm | 6-9pm | 23:00-2:00 (Dec 8) | 1:30am-4:30am (Dec 8) | 3pm-6am (Dec 8) | | ||
| Dec 9th ([View in my timezone][dec9-session]) | 4-7am | 7-10am | 12:00-15:00 | 5:30-8:30pm | 8pm-11pm | | ||
| Dec 11th ([View in my timezone][dec11-session]) | 1-4pm | 10-1pm | 18:00-21:00 | 11:30pm-2:30am (Dec 12) | 2am-5am (Dec 12) | | ||
|
||
## Live broadcasts | ||
|
||
In addition to the repository, we’ve scheduled two “live broadcasts”. These sessions will feature members of the core team discussing and responding to some of the questions that have been asked thus far. Naturally, even if you can’t catch the live broadcast, the video will be available for streaming afterwards. Here is the schedule for these broadcasts: | ||
|
||
| | PST US | EST US | UTC Europe/Africa | India | China | | ||
|---------------------------------------------------|--------|--------|--------------------|-------------------------|------------------| | ||
| Dec 9th ([View in my timezone][dec9-broadcast]) | 3-4pm | 6-7pm | 23:00-24:00 | 4:30-5:30am (Dec 10) | 7-8am (Dec 10) | | ||
| Dec 12th ([View in my timezone][dec12-broadcast]) | 4-5am | 7-8am | 12:00-13:00 | 5:30pm-6:30pm | 8-9pm | | ||
|
||
These will be hosted on our [YouTube channel]. | ||
|
||
We’re very excited about the progress on the Rust foundation and we’re looking forward to hearing from all of you. | ||
|
||
[FAQ]: https://github.com/rust-lang/foundation-faq-2020/blob/main/FAQ.md | ||
[survey]: https://docs.google.com/forms/d/e/1FAIpQLSeciTU1hLi-Y5842fvWC2lhYRHvkWOtPbk39p72amGcGmZIaA/viewform | ||
[foundation-faq-2020]: https://github.com/rust-lang/foundation-faq-2020 | ||
[answered]: https://github.com/rust-lang/foundation-faq-2020/issues?q=is%3Aissue+is%3Aopen+label%3Aanswered | ||
[YouTube channel]: https://www.youtube.com/c/rustvideos | ||
[dec7-session]: https://everytimezone.com/s/213ef6bd | ||
[dec9-session]: https://everytimezone.com/s/f10ec849 | ||
[dec11-session]: https://everytimezone.com/s/3c5c1b75 | ||
[dec9-broadcast]: https://everytimezone.com/s/a0b6bb44 | ||
[dec12-broadcast]: https://everytimezone.com/s/8e88716f |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there was a typo in the Chinese timezone, it should be 3am-6am rather than 3pm-6am, right @ashleygwilliams ?
edit: sorry for tagging the wrong person
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Mark-Simulacrum
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you are correct @RageKnify! i will fix