You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To provide clear information about the licensing of the website's content and code, we need to add a dedicated "Licensing Page" that reflects the use of the MIT License.
What will I do :
Create Licensing Page 2. Content for Licensing Page
Include a brief introduction explaining the importance of licensing.
Provide the full text of the MIT License.
Will Style the page to Follow the theme of the website.
Will Add "Licensing" in the Footer, To Navigate to this Separate Page in Legal section.
for ex like this :
please assign me this issue under gssoc'24
Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record
I have read the Contributing Guidelines
I'm a GSSOC'24 contributor
I have starred the repository
The text was updated successfully, but these errors were encountered:
Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.
There is no need to add a separate page for the MIT License since it is already present in GitHub repo. You can add a link to the License in repo in the footer and policy page.
Is there an existing issue for this?
Feature Description
hey @VaibhavArora314 @akbatra567 and @Ultimateutkarsh11
To provide clear information about the licensing of the website's content and code, we need to add a dedicated "Licensing Page" that reflects the use of the MIT License.
What will I do :
for ex like this :
please assign me this issue under gssoc'24
Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record
The text was updated successfully, but these errors were encountered: