Repository hosting RFCs and documentation for the F# language design process, including proposals, discussions, and implementation tracking.
FSharp/fslang-design is the official repository for the F# language design process, hosting RFCs (Request for Comments) and related documentation. It provides a structured workflow for proposing, discussing, and tracking changes to the F# language and its tooling, ensuring transparency and community involvement in language evolution.
F# language contributors, maintainers, and community members interested in proposing or reviewing language features, tooling improvements, or style guide changes.
It offers a centralized, transparent process for F# language design, enabling collaborative RFC management and clear tracking from proposal to implementation, which helps maintain language consistency and community alignment.
RFCs and docs related to the F# language design process, see https://github.com/fsharp/fslang-suggestions to submit ideas
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The repository documents the F# Language Design Squad and emphasizes community participation in decision-making, as stated in the 'Who is in Charge?' section, ensuring openness.
It defines a clear process from idea submission via fslang-suggestions to RFC creation and implementation, with organized folders for open, preview, and released RFCs, facilitating tracking.
RFCs are archived under version-specific folders once implemented, as described in the README, making it easy to see what changes were made in each F# release.
Style guide issues are coordinated with Fantomas, with adjustments requiring implementability in the tool, linking design decisions directly to code formatting, per the 'Style Guide' section.
The README admits a 'backlog of approved ideas,' and the release train model means features are only implemented when ready, leading to potential delays in language evolution.
The workflow spans fslang-suggestions, fslang-design, and dotnet/fsharp, requiring contributors to navigate multiple repositories, which can be cumbersome and slow down contributions.
Most features rely on community or enterprise contributions, as noted in the 'Who is in Charge?' section, which might result in uneven progress or reliance on volunteer effort for critical changes.