On Mon, Sep 14, 2026 at 01:55:09PM +0200, Simon Josefsson wrote: > All, > > One of the reasons we are stuck making updates to our policies could be > the editorial layout of the policy: > > 1) One 2015-era early main document about the workflow: > https://go-team.pages.debian.net/packaging.html > > 2) One 2017-2019-era incremental addition to the earlier document: > https://go-team.pages.debian.net/workflow-changes.html > > The result is that neither is a self-contained document. > > It is complicated to propose any changes to the first document because > it reflect the 2015-era approach that was superseded by the second > document. > > It is complicated to propose any changes to the second document because > that document the 2017-2019 era of changes. > > How about if we merge the changes from the 2) document into the 1) > document and then remove the 2) document and links to it?
Please do. It will avoid a xkcd.com/927 ( competing standaards ) situation. > The new merged page would not reflect modern workflows fully, but that's > not the point. > > This first merge should only be editorial. No policy changes. > > If we make this editorial change, we would be better prepared to discuss > and make small targetted improvements to the workflow recommendations. > > We would have one central, easier-to-read, document explaining our > policy. I agree. And created https://salsa.debian.org/go-team/go-team.pages.debian.net/-/merge_requests/25 > When I started working on Go packages I found this historically > motivated framing confusing and unhelpful, and this slowed me down. > Nothing has changed in 2-3 years. Let us remove that burden from the next generation. > /Simon Groeten Geert Stappers -- Silence is hard to parse
