move contributing and collaboration guide to .github #10
Conversation
|
cc: @expressjs/express-tc |
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
I dont like that added complexity of the admin repo. I was thinking we should make the .github repo the source for all we can. Honestly the name of the repo doesn't really matter as long as the docs are in the right place and the links are all correct.
My main concern with this current form is that we dont have a good concept in here of the difference between contributing to express vs all the other packages. I think we should keep this in a branch and open PRs against it here until we are satisfied. This whole consolidation effort was one of the main things I wanted to do soon, so let me just leave this comment here and circle back in a week or so.
|
Agree with Wes. Frankly, we have a backlog of updating the contributing guide, as well as the security policy -- something we delayed doing until after the audit was complete and we were in 2025. |
bjohansebas
force-pushed
the
add-contributing
branch
from
406cd82 to
59f2418
Compare
bjohansebas
changed the title
|
see also expressjs/discussions#353 cc: @expressjs/express-tc |
wesleytodd
left a comment
wesleytodd
left a comment
There was a problem hiding this comment.
Anything to pull this out of the express repo is good, but I do think the governence docs are not supported by GH to show in every repo, and also they apply for us to all three orgs, so we may be better off with that one in discussions than here.
Yeah, even opening it on GitHub so they support this, since they show it as if they were going to do it. |
wesleytodd
left a comment
wesleytodd
left a comment
There was a problem hiding this comment.
I am making a few edits to hopefully get this landed.
4 participants
This is part of adding the documentation that can be inherited from this repository.
Port of #18
See also expressjs/discussions#353