-
Description:
To encourage and streamline contributions to CofiBlocks, a clear and comprehensive CONTRIBUTING.md file needs to be created. This document will provide potential contributors with the …
-
### Summary
We used `lifecycle::badge` to indicate the stage of a function (e.g., experimental, stable, deprecated, superseded).
I found a past PR related to this topic:
https://github.com/in…
-
Flesh out contributing guidelines. Put any ideas here
* xref:
* https://github.com/uscuni/sgeop/pull/45#issuecomment-2419326859
* #4
-
# Rust API Guidelines Checklist
- **Naming** *(crate aligns with Rust naming conventions)*
- [ ] Casing conforms to RFC 430 ([C-CASE])
- [ ] Ad-hoc conversions follow `as_`, `to_`, `into_` co…
-
As talked about in [today's meeting](https://docs.google.com/document/d/1JY8FREBPCUUFpuv7-4B9EjeS2MLDpel0dbG5DFWrTns/edit), it would be good to have guidelines to help developers sandbox their applica…
-
### URL to the relevant documentation page
_No response_
### Description
Dette er guiden for bidragsytere som ikke er med i teamet.
### Proposed improvement
_No response_
### Additional informat…
-
**Description**
The lack of obvious guidelines for correcting error messages may leave the user confused as to how he or she should correct his or her input.
**Steps to Reproduce**
__________________…
-
**Description**
The lack of obvious guidelines for correcting error messages may leave the user confused as to how he or she should correct his or her input.
**Steps to Reproduce**
__________________…
-
In the past this was part of the configs, only allowing curves enumerated in the json data for the configs. At some point it got removed due to bugs in implementations, and also clients and servers be…
-
### Overview
Part of the content guidelines is a checklist for new writers / basics / other teams to use as a resource when doing content writing.
The current Checklist looks like this, and is on th…