mesonbuild/meson

Recommend a standard coding style for meson.build files

Open

#2,608 opened on Nov 11, 2017

View on GitHubContributor guide
 (8 comments) (5 reactions) (0 assignees)Python (1,465 forks)batch import
documentationenhancementhelp wanted

Repository metrics

Stars
 (4,978 stars)
PR merge metrics
 (Avg merge 139d 13h) (51 merged PRs in 30d)

Description

It seems that there is no recommended standard for the coding style of meson.build files.

So in some projects the indentation is with two spaces, in other projects it's with tabs or four spaces, etc etc.

I think it's useful to have the same coding style in all projects, it makes contributing easier, it is also easier to copy/paste a snippet of code between projects.

Like the PEP 8 for Python: https://www.python.org/dev/peps/pep-0008/

Contributor guide

Research direction
Review existing coding style discussions in the Meson community and propose a PEP 8 like style guide for meson.build files.
Tech stack
python
Domain
build system
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Meson
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80