Bill Allombert writes ("Re: Support for non-free-firmware in project webpages"):
> On Fri, Jan 27, 2023 at 11:41:10AM +0000, Ian Jackson wrote:
> > Would an MR to be more explicit about the precise code location be
> > welcome?
>
> Actually I prefer bug reports against popularity-contest.
I presume that someone who wants to fix something with the web page
should do so starting with the source code from salsa, though ?
After all, I guess the website probably isn't running off
the .debs from stable ?
> This link used to point to a page hosted on alioth that provided links
> to the package page, BTS page and the alioth source repo.
OK, great, but I'm not sure precisely now what patch I should send -
ie, what ought to be in the page footer. Since you know the answers,
would you mind arranging that the popcon web pages contain the right
references ?
I think a reader (potential contributor) needs to know:
* Where to get the source code for the actually deployed instance[1]
* Where and in what form to send patches (or MRs, as the case may be)
Since in the general case, Debian services are managed by different
people in different ways, the reader won't be able to just guess the
answers to these questions.
[1] I think this means the git history, if the service source code is
maintained in git.
And the arrangements should be such that publication of the source
code for an updated deployment is automatic, rather than depending on
a manual release step (eg, an upload to sid). If deployment is done
via git, this typically happens for free, since it's easy to make the
deployments happen from a branch which is also public.
If the deployment is done some other way then perhaps the software
should have a "download my own source code" feature.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
