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

Update README.md #305

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #305

wants to merge 1 commit into from

Conversation

rouault
Copy link

@rouault rouault commented Oct 10, 2024

We don't want to encourage direct push to master, do we?

We don't want to encourage direct push to master, do we?
@nyalldawson
Copy link
Contributor

I think we need to rethink how this repo works. The issues approach makes it really hard to see what's accepted vs what's just proposed. I'd be in favour of moving to prs as proposals, accepted as rst for approved proposals. More like the approach gdal uses...

@rouault
Copy link
Author

rouault commented Oct 10, 2024

The issues approach makes it really hard to see what's accepted vs what's just proposed. I'd be in favour of moving to prs as proposals, accepted as rst for approved proposals. More like the approach gdal uses...

ah ah yes that was exactly my thoughts. But, without changing too much the process, just making sure that issues in https://github.com/qgis/QGIS-Enhancement-Proposals/issues are consistently labelled with "accepted", "implemented", "rejected", "draft" would be a huge way forward

@esnyder-rve
Copy link

What about just plain markdown versus rst? Are the "advanced" features of rst needed?

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