{"id":19002313,"url":"https://github.com/linkerd/gsoc","last_synced_at":"2025-10-04T15:54:45.533Z","repository":{"id":151282897,"uuid":"239599589","full_name":"linkerd/gsoc","owner":"linkerd","description":"The home of GSOC or the Linkerd project.","archived":false,"fork":false,"pushed_at":"2020-05-04T18:02:05.000Z","size":59,"stargazers_count":4,"open_issues_count":0,"forks_count":5,"subscribers_count":10,"default_branch":"master","last_synced_at":"2025-01-01T18:42:39.375Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/linkerd.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-02-10T19:52:05.000Z","updated_at":"2021-02-18T09:52:17.000Z","dependencies_parsed_at":"2023-05-09T12:32:29.936Z","dependency_job_id":null,"html_url":"https://github.com/linkerd/gsoc","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/linkerd%2Fgsoc","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/linkerd%2Fgsoc/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/linkerd%2Fgsoc/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/linkerd%2Fgsoc/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/linkerd","download_url":"https://codeload.github.com/linkerd/gsoc/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240026551,"owners_count":19736202,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-08T18:14:37.015Z","updated_at":"2025-10-04T15:54:40.489Z","avatar_url":"https://github.com/linkerd.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Linkerd GSoC\n\nWelcome to the Linkerd GSoC program!\n\nThis repository contains everything you need to know about the program.\n\n## Resources\n\n* Official website: https://linkerd.io/gsoc\n* Linkerd slack (`#gsoc` channel): https://linkerd.slack.com\n\n## Request For Comments (RFC)\n\nAll GSoC students are required to submit a RFC for the GSoC project that they\nare interested in.\n\nThe RFC process is intended to provide a consistent and controlled path for\ncontributions to enter the Linkerd project, so that all stakeholders\ncan be confident about the project direction and maintainability of the codebase.\n\n### Before creating an RFC\n\n[before creating an rfc]: #before-creating-an-rfc\n\nA hastily-proposed RFC can hurt its chances of acceptance. Low quality\nproposals, proposals for previously-rejected features, or those that don't fit\ninto the near-term roadmap, may be quickly rejected, which can be demotivating\nfor the unprepared contributor. Laying some groundwork ahead of the RFC can\nmake the process smoother.\n\nAlthough there is no single way to prepare for submitting an RFC, it is\ngenerally a good idea to pursue feedback from the GSoC mentors beforehand, to\nascertain that the RFC may be desirable; having a consistent impact on the\nproject requires concerted effort toward consensus-building.\n\nThe most common preparations for writing and submitting an RFC include talking\nthe idea over on our\n[Linkerd Slack, #gsoc channel](https://slack.linkerd.io).\n\nAs a rule of thumb, receiving encouraging feedback from long-standing Linkerd\ndevelopers is a good indication that the RFC is worth pursuing.\n\n### What the process is\n\n[what the process is]: #what-the-process-is\n\nIn short, to get a major feature added to Linkerd, one must first get the RFC\nmerged into this repository as a markdown file. At that point the RFC is\n\"active\" and may be implemented with the goal of eventual inclusion into\nLinkerd.\n\n1. Fork the [GSoC repository](https://github.com/linkerd/gsoc)\n2. Copy `templates/rfc.md` to\n   `rfc/year/project-name/your-github-handle.md`.\n3. Fill in the RFC, starting with `Step 1` - Problem Statement. This is where\n   you demonstrate your understanding of the problem to be solved.\n4. Submit a pull request. As a pull request the RFC will receive feedback from\n   the larger community, and the author should be prepared to revise it in\n   response.\n5. Each pull request will be labeled with the most relevant reviewer, who will\n   lead its triage.\n6. Build consensus and integrate feedback. RFCs that have broad support are much\n   more likely to make progress than those that don't receive any comments. Feel\n   free to reach out to the RFC assignee in particular to get help identifying\n   stakeholders and obstacles.\n7. The team will discuss the RFC pull request, as much as possible in the\n   comment thread of the pull request itself. Offline discussion will be\n   summarized on the pull request comment thread.\n8. When all the feedback are integrated, update your pull request to complete\n   `Step 2` - Design Proposal. Put care into the details: RFCs that do not\n   present convincing motivation, demonstrate lack of understanding of the\n   design's impact, or are disingenuous about the drawbacks or alternatives tend\n   to be poorly-received.\n\nRFCs rarely go through this process unchanged, especially as alternatives and\ndrawbacks are shown. You can make edits, big and small, to the RFC to clarify or\nchange the design, but make changes as new commits to the pull request, and\nleave a comment on the pull request explaining your changes. Specifically, do\nnot squash or rebase commits after they are visible on the pull request.\n\n### The RFC life-cycle\n\n[the rfc life-cycle]: #the-rfc-life-cycle\n\nOnce an RFC is tagged as \"active\" then author may implement it and submit the\nfeature as a series of pull requests to the\n[Linkerd2](https://github.com/linkerd/linkerd2) repo. Being \"active\" is not\na rubber stamp, and in particular still does not mean the feature will\nultimately be merged; it does mean that in principle all the major stakeholders\nhave agreed to the feature and are amenable to merging it.\n\nModifications to \"active\" RFCs can be done in follow-up pull requests. We strive\nto write each RFC in a manner that it will reflect the final design of the\nfeature; but the nature of the process means that we cannot expect every merged\nRFC to actually reflect what the end result will be at the time of the next\nmajor release.\n\nIn general, once accepted, RFCs should not be substantially changed. Only very\nminor changes should be submitted as amendments. More substantial changes should\nbe new RFCs, with a note added to the original RFC. Exactly what counts as a\n\"very minor change\" is up to the team to decide.\n\n### Implementing an RFC\n\n[implementing an rfc]: #implementing-an-rfc\n\nEvery accepted RFC has an associated issue tracking its implementation in the\n[Linkerd2](https://github.com/linkerd/linkerd2) repository. The issue will be\nassigned to the RFC author.\n\n### Help this is all too informal!\n\n[help this is all too informal!]: #help-this-is-all-too-informal\n\nThe process is intended to be as lightweight as reasonable for the present\ncircumstances. As usual, we are trying to let the process be driven by\nconsensus and community norms, not impose more structure than necessary.\n\n## License\n\n[license]: #license\n\nThis repository is currently licensed under:\n\n- Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)\n- https://github.com/linkerd/linkerd2/blob/master/LICENSE\n\n### Contributions\n\nUnless you explicitly state otherwise, any contribution intentionally submitted\nfor inclusion in the work by you, as defined in the Apache-2.0 license, shall be\nlicensed as above, without any additional terms or conditions.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flinkerd%2Fgsoc","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Flinkerd%2Fgsoc","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flinkerd%2Fgsoc/lists"}