Skip to content

Conversation

@jkowalleck
Copy link
Member

@jkowalleck jkowalleck commented Jan 19, 2025

when a spec PR pops up without any previous discussion, then this usually disturbs me.

A PR w/o a proper issue means somebody skipped the most relevant part: give people a proper understanding of the "problem" and give them the freedom to think about possible solutions freely. Starting with a solution always narrows the view of everybody, and in almost all cases the proposed solution is not the best one.

to guide pull-requests, i propose the following PR template: #579

What do you think about the situation?

  • Should PRs without a ticket exist in our spec-repo?
  • What about the wording in the PR template? is it friendly enough to no guide people and not scare them away?

(Yes, I opened this PR without any discussion/ticket before. Ironic, isn't it? ;-))

Signed-off-by: Jan Kowalleck <jan.kowalleck@owasp.org>
@jkowalleck jkowalleck requested a review from a team as a code owner January 19, 2025 08:58
Signed-off-by: Jan Kowalleck <jan.kowalleck@owasp.org>
Signed-off-by: Jan Kowalleck <jan.kowalleck@owasp.org>
@jkowalleck
Copy link
Member Author

made some changes as discussed wit h the core working group.
will merge soon, as discussed with the core working group.

@jkowalleck jkowalleck merged commit 0cb0fcc into master Jan 19, 2025
12 checks passed
@jkowalleck jkowalleck deleted the introduce-PR-template branch January 19, 2025 20:53
n1ckl0sk0rtge pushed a commit to n1ckl0sk0rtge/specification that referenced this pull request Feb 11, 2025
Signed-off-by: Jan Kowalleck <jan.kowalleck@owasp.org>
n1ckl0sk0rtge pushed a commit to n1ckl0sk0rtge/specification that referenced this pull request Feb 11, 2025
Signed-off-by: Jan Kowalleck <jan.kowalleck@owasp.org>
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.

2 participants