Code review comment for lp:~cprov/squid/snap

Revision history for this message
Alex Rousskov (rousskov) wrote :

I am not sure I follow your argument. Committing X into Squid source tree might create a sense of shared ownership (whatever that means), but does not automagically keep X up to date. This is especially true for any X that does not affect Squid build and mainstream functionality. For X to actually be kept up to date, somebody active within the Squid project needs to know and care about X enough to keep it updated. AFAICT, there is no such person for X=snapcraft. Please correct me if I am wrong.

Please note that I am not arguing for a separate/overlay Squid branch containing X. I am arguing for a separate project, wiki page, whatever. The Squid Project can recommend and even host that project/page, of course.

In other words, if somebody wants to maintain X that helps folks build Squid but does not need to be tightly integrated with Squid sources and does not have a long-term Squid person behind it, then X should be kept separate from Squid because keeping X separate would decrease overheads for maintaining it and avoid polluting Squid with stale stuff (in case it does become stale).

« Back to merge proposal