Skip to content

Conversation

@teslazonda
Copy link
Contributor

@teslazonda teslazonda commented Nov 30, 2025

Change Summary

Edited content in the docs/contributing directory to align with the Microsoft Writing Style Guide

  • testing.rst
  • build-vyos.rst
  • upstream-packages.rst
  • cla.rst
  • debugging.rst
  • development.rst

Related Task(s)

  • TBD

Related PR(s)

Backport

Checklist:

@teslazonda teslazonda changed the title Proofread upstream-packages.rst Proofread docs in the /contributing directory Nov 30, 2025

Please submit your patches using the well-known GitHub pull-request against our
repositories found in the VyOS GitHub organisation at https://github.com/vyos
6. Push to your fork and create a GitHub pull request:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we recommend making pull requests against the current branch?

* Python: Tabs **shall not** be used. Every indentation level should be 4 spaces
* XML: Tabs **shall not** be used. Every indentation level should be 2 spaces
* **Python**: Use 4 spaces per indentation level. Tabs **must not** be used.
* **XML**: Use 2 spaces per indentation level. Tabs **must not** be used.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any other languages commonly used in VyOS that currently have internal coding guidelines? For example, C is used extensively in VyOS, what guidelines are there for C programming at VyOS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant