-
Description:
Currently, there are no specific contribution guidelines documented in a separate CONTRIBUTION.md file. This can cause confusion for new contributors on how to properly contribute to t…
-
## Description
I noticed a couple of areas in the contribution guidelines that could benefit from clarification:
Tagging Maintainers: In the "How to contribute" section, it mentions tagging for …
-
**Issue Title**: Add Contribution Guidelines Document (`CONTRIBUTION.md`)
---
**Description**:
To enhance collaboration and streamline the contribution process for the Doctor's Appointment Web …
-
Hello! @AbhiDiva96 ,
The contributing.md looks is not in a structured manner. Also some sections are missing. I can enhance it in a well structured manner with proper details and some additional s…
-
### What would you like to share?
I would like to see an update in documentation regarding ethical code of conduct of the contributors, people should not be solving the problems identified by someone…
-
* 기여 과정 간소화: 기여 과정이 비교적 명확하게 설명되어 있지만, 비개발 기여(예: 문서 개선, 버그 리포트)와 관련된 절차를 간소화하는 방법이 추가되면 좋습니다. 예를 들어, 이슈 트래킹 시스템을 통한 기여 절차를 한눈에 볼 수 있는 흐름도를 제공하면 기여자들이 쉽게 접근할 수 있습니다.
* CLA 설명 단순화: 기여자 라이선스 계약(CLA)이 …
-
As we keep deciding on how tests should be constructed, naming schemes, formatting tools, docstrings, etc. we should have a markdown text file (a "CONTRIBUTING.md") to define our guidelines for writin…
-
The Contribution Guidelines is not there yet and mabe we can piggy back on [the awesome manifesto](https://github.com/sindresorhus/awesome/blob/main/awesome.md)?
_Originally posted by @tpluscode in…
-
The current [project contributor guidelines](https://github.com/spiffe/spire/blob/main/CONTRIBUTING.md#contributor-guidelines-and-governance) are currently terse and don't describe a well-defined proc…
-
Because design features are subjective and the ideal solution differs from implementation to implementation. We'd like to create a basic **Design Guide** that shows preferred UI conventions. This idea…