-
Notifications
You must be signed in to change notification settings - Fork 12
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
having 2 locations, one for *complete* one for *incomplete* proposals #3
Comments
I agree. Please. Also having to do stuff in a repo is a PITA, a wiki is a more suitable place. |
El lun., 28 ene. 2019 a las 10:03, Aleks-Daniel Jakimenko-Aleksejev (<
[email protected]>) escribió:
I agree. Please. Also having to do stuff in a repo is a PITA, a wiki is a
more suitable place.
You can comment, as you are doing now, in a repo. You can assign issues,
and close them from commits. You can't do all that with a wiki. Only
advantage in a wiki is that anyone can edit it, but you can also do that
here via a pull request.
I can flesh out the ideas and assign a suitable mentor, no problem at all
with that.
|
Wikis encourage microcontributions. There are many advantages that come from that. |
Except when you have to flesh them out to actually publish them, as is needed for the proposal. |
Then maybe proposal should be filed as an issue originally, and then committed when they're fully ready. |
That's another idea. I'll add it to #8 |
For examlpe me TLS proposal is more or less a rough idea, I am not able to mentor it.
I would be unhappy if we had to delete it because it is (maybe still) a valid idea. Maybe someone could pick up an incomplete proposal and mentor it.
The text was updated successfully, but these errors were encountered: