This repository is a place to propose and track and new internal projects or changes to existing internal projects under Creative Labs at UCLA.
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to uclacreatives@gmail.com.
Jump to: What is an RFC? | RFC Process
# | Title | Owner | Status |
---|---|---|---|
2 | Spotify Blend: Lots | @BryanPan342 | π· implementing |
7 | Weekly Inspo | @BryanPan342 | π· implementing |
14 | Student org-focused GitHub user manager | π‘ proposed | |
18 | Event-targeted social media manager | π‘ proposed | |
20 | Internal data visualization | @tylercxu | π‘ proposed |
21 | Interaction data monitoring | @tylercxu | π‘ proposed |
An RFC, or request for comments, is a document that details a proposed change to an internal project or an entirely new one (such as a web app, tooling, etc.) It also serves as a means of reviewing these proposals, discussing them, and tracking their implementation.
0000-template.md
to text/<rfc#>-<my-proposal>.md
, where <rfc#>
is the tracking issue number and <my-proposal>
is the RFC title.RFC: <rfc#> <title>
where <rfc#>
is the tracking issue number and <title>
is the name of your proposal. Then members of our team will review your RFC and offer comments and feedback. Be prepared to discuss your proposal and make changes to it if necessary.