On 17.07.23 13:12, Neil C Smith wrote:
I agree we should enable issues on the website repo, but should
possibly consider forms and labelling similar to the main repo to
guide the information we need, guide how people can help fix
themselves without opening issues (eg. how to propose edits via GitHub
UI)
right, we should probably do this now. We should mention in the text
that many issues like for example typos and formatting should be
directly solved via gh editor UI or a classic PR. The more help we get
from the community the better - esp in the doc area.
We essentially already have an issue tracker integrated in the website:
If the page says "this page requires review", it likely has some issues
to solve - another tracker is just more noise. It still basically works
like a wiki with some extra steps.
-mbien
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
