-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Update the GSOC page with more info and make it look nicer #2911
Comments
/assign |
You cannot be assigned to this issue because you are already assigned to the following issues without an open pull request: #2884. Please submit a pull request for these issues before getting assigned to a new one. |
/assign |
Hello @krrish-sehgal! You've been assigned to OWASP-BLT/BLT. You have 24 hours to complete a pull request. To place a bid and potentially earn some BCH, type /bid [amount in BCH] [BCH address]. |
/assign |
Hello @tsu-ki! You've been assigned to OWASP-BLT/BLT. You have 24 hours to complete a pull request. To place a bid and potentially earn some BCH, type /bid [amount in BCH] [BCH address]. |
@DonnieBLT Could you please explain, what changes should be made to GSOC page? |
to make it look nicer, fill all of the years BLT did GSOC, add the links to the ideas pages, add links to more blog posts from the students, maybe if they are a user on BLT add their profile, also list who was a mentor for the year and if there are any public proposals link those proposals. Also link the leaderboard from last year and this year. |
@DonnieBLT BLT has been attending GSOC consecutively from 2020 till 2024? Also, which leaderboard should be linked to the page? |
yes, here are the past years - 2023 https://owasp.org/www-community/initiatives/gsoc/gsoc2023ideas |
@tsu-ki seems like you've taken over this issue, since i haven't done much work on this yet... I'll unassign me. |
/unassign |
@DonnieBLT can you please close this issue? I'm not able to assign myself another issue. |
/unassign |
Hey @tsu-ki, you can use /unassign. Just a quick note—please remember to mention the issue number in the PR description or commit message next time. This ensures the issue closes automatically when the PR is merged. It helps us avoid redundant efforts where others might start working on an issue that's already resolved |
@apoorvapendse thank you for informing me that, I forgot to add the PR number this time, I'll keep this in mind |
No description provided.
The text was updated successfully, but these errors were encountered: