Skip to content
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

Migrate rolling docs to github #11

Closed
wants to merge 1 commit into from

Conversation

aashish66
Copy link
Contributor

Please check my contribution whether I have done right?

Added Rolling docs to github
iamtekson

This comment was marked as duplicate.

Copy link
Member

@iamtekson iamtekson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aashish66, thank you for your contribution. But I think the idea is to add the meeting info into different file. My suggestion is to create one folder called rolling docs and inside, we create multiple files (maybe based on year; 2022.md, 2023.md) and add the meeting to that file. I am not sure about the exact steps. Maybe @kshitij-raj-sharma can guide.

@iamtekson iamtekson changed the title Update README.md Migrate rolling docs to github Jan 14, 2024
@kshitijrajsharma
Copy link
Contributor

@aashish66 it's good practice to reference the issue you are working on PR. You can edit the description and reference the issue with issue number ! For the Issue itself, Plan is to have wiki You can reference OSGeo Board meeting wiki over here : https://wiki.osgeo.org/wiki/Board_Meeting_2022-08-27 . Similarly we will have Meeting section on Github Wiki and maintain new page for meeting like the format Board is using ! And we can link them dynamically so that they will generate a new meeting page every month ! Let me know if you need more details, I can explain !

@aashish66
Copy link
Contributor Author

aashish66 commented Jan 15, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants