-
Notifications
You must be signed in to change notification settings - Fork 64
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
Girlscript Summer of Code Introduction/Tracking #7
Labels
Comments
Hey prince actually i am now in train can we connect at 10pm today so
kindly share me meet link and thanks for sharing the isssues✅
…On Fri, 10 May 2024 at 10:35 AM, Prince Gupta ***@***.***> wrote:
👋 Hi @urstrulynishkarsh <https://github.com/urstrulynishkarsh>,
I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be
collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great
for students to have a couple of standard readme files on the repo to
understand what the project is all about and some issues detailing what
they can contribute. This will help you to see increased engagement in your
repository as well.
As mentioned students get a chance to learn step by step, how to build
this project as well as invite mentors to collaborate and add features to
this repo. I will generate issues, which will provide guidance on how to
prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to
GSSoC'24. I recommend creating a new branch for every issue and opening a
pull request to track changes so we can effectively collaborate with each
other and merge changes when you and I feel like those changes are ready to
be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment
on this issue or any of the other issues that are generated.
I look forward to working with you [image:
![]() |
I am Agamjot singh. Under GSSOC'24, I would like to work on this issue. Pls assign me this!! |
Repository owner
deleted a comment from
Princegupta101
May 10, 2024
@agxmbedi This is the issue for tracking the GSSOC 24 issues. It's not a issue to work on. Please find another issues that aren't assigned |
Ok, thanks for the clarification.
…On Sat, May 11, 2024 at 12:27 AM asr2003 ***@***.***> wrote:
@agxmbedi <https://github.com/agxmbedi> This is the issue for tracking
the GSSOC 24 issues. It's not a issue to work on. Please find another
issues that aren't assigned
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2QB3T75M5D6GLTBWARK6TDZBUKAZAVCNFSM6AAAAABHP63KUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGEYTSNZUGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
👋 Hi @urstrulynishkarsh,
I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program
Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.
As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.
This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.
If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.
I look forward to working with you![:octocat: :octocat:](https://github.githubassets.com/images/icons/emoji/octocat.png)
The text was updated successfully, but these errors were encountered: