Amar Takhar created an issue: https://gitlab.rtems.org/rtems/programs/gsoc/-/issues/87
Assignee: Gedare Bloom ## Summary Next year we should use an epic to track GSoC proposals 1. Create a \`2026\` epic 2. Ask students to open an issue with their proposal and `#ticketnumber` the project they want to work on if it exists 3. We add it to the \`2026\` 4. When they do their proposal they'll be able to attach the link / file to the issue This will also get us free trakcing on our project issues of: 1. How many proposals we get 2. Who has worked on it over the years if the project has not been taken up I think in general it's better than editing a markdown file the epic can stay for the duration of GSoC until it's long over or the next year starts. We can also have a new graphql query for the epic to list open issues and that will be nice tracking of activity on our website. ## Steps to reproduce ### Pre-set options -- View it on GitLab: https://gitlab.rtems.org/rtems/programs/gsoc/-/issues/87 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
