> My overall impression is that this is a bold attempt, but the document could > do > with some copy-editing to whittle it down, make it more focussed, and possibly > narrow the scope. E.g. perhaps Gitlab CI is too much in one go? Could that be > done further down the line in a follow-up DEP?
If you want editing advice debian-l10n-engl...@lists.debian.org is a great resource I would suggest: - make the "intro" less general. Set out a clear, short, list of objectives/goals/what you want to improve. This will also help with setting a clearer scope - make the "principals" more general (or keep them but dont call them principals -- they currently read like a set of implementation details), and explain how they help the project achieve the objectives. This will help you edit down the text below each 'principal'. You might also want to decide if these are mandatory, recommended or suggested. - (then see whether the other sections are still needed)
