-
Notifications
You must be signed in to change notification settings - Fork 491
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
Remove the Project Admin Portion from README #805
Comments
I would like to try this. Could you assign it to me?? Also, should I just put the Linkedin links below images or do you want any other links as well?? |
@subhamagrawal7 The image should redirect to GitHub Profile, while the name should be linked to LinkedIn Profile. I will provide the Linked-In links here soon, kindly confirm once again so that I can assign this to you. |
Hey I would like to work on this issue |
I will assign this to you if @subhamagrawal7 doesn't respond by evening. |
@haripriya9647 Am assigning this to you, are you a GSSoC contestant? |
Really sorry for the delay..was little busy yesterday...let me know if this issue still remains unresolved. |
@haripriya9647 You are working on this? |
Hey yes I am GSSoc participant and I am working on this issue. |
Can you provide me Linked-In links of rest maintainers ?? and in which channel projects discussion takes place?? |
Sure thing. For Discussion, we can use the GitHub discussion tab for now. Link - https://github.com/HarshCasper/Rotten-Scripts/discussions Harsh: https://www.linkedin.com/in/harshcasper/ |
Description
Remove the Project Admin Portion from the README file. As of now, my picture and details are displayed on the README as the Project Admin.
As the Project has grown, it would be better if the term "Project Admin" is replaced by "Maintainers". As of now, these are the official maintainers of the Project:
Create a new section in the README by replacing the existing one, and add all their details in a similar format that exists right now.
The text was updated successfully, but these errors were encountered: