generated from ossf/project-template
-
Notifications
You must be signed in to change notification settings - Fork 52
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #431 from rubycentral/update-2024-10
Ruby Central: Update October 2024
- Loading branch information
Showing
2 changed files
with
36 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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,35 @@ | ||
# Update 2024-10 | ||
|
||
## Organizations | ||
|
||
Maintainer role and the new design (incorporated into the organizations feature) have been released to production. | ||
Onboarding design for organizations is in progress. | ||
|
||
### Maintainer Role | ||
|
||
* Released and live in production. | ||
* The feature seems to have gone over smoothly. | ||
|
||
### Organizations | ||
|
||
* The new design is live in production, with feedback overwhelmingly positive. | ||
* The organization view page is very similar to the Dashboard and will probably be ready in the next few days. | ||
* The onboarding model, supporting a user to create an organization, is largely working in development. | ||
|
||
### Next steps: | ||
|
||
* Apply the new design to the onboarding process. | ||
* Finishing design for public organizations profiles. | ||
* We hope to have onboarding ready by RubyConf in mid-November, where we plan to talk about the Organizations feature and ask people to sign on to a wait list. | ||
|
||
## Audit | ||
|
||
* We have responded to all of the immediately important audit findings. | ||
|
||
### Next steps: | ||
|
||
We plan to handle these items after RubyConf in mid November. | ||
|
||
* Complete the response document and return it to Trail of Bits to incorporate into the final report. | ||
* Work with ToB for the fix review. | ||
* Coordinate with ToB to publish the report. |