So let me summarize. Suppose for a moment that Trisquel is built in such a way that...
* Trisquel follows Debian testing (therefore also stable) main repository in a tight lockstep. Since Debian's main repository is composed of -wishfully- FSF cleared packages, there's no need to create a separate trisquel/main for it. Trisquel just taps on the original Debian main repositories worldwide and gets a free ride. There are a few exceptions though, like Debian personalization packages, which can be modified for Trisquel and transferred to a private trisquel repository with a higher priority. Note that maintaining a rolling Trisquel version is easier than it might first sound, because only a limited number of liberated packages that are in private Trisquel repository needs to be maintained.
* Selected packages from Debian contrib and non-free repositories are liberated (almost all the Trisquel effort actually goes here) and served in a private trisquel repository with higher priority.
* Security updates are also handled the same way: Tap on the Debian security updates for "main" repository, and manage your own security updates separately for the -rather small- private repository.
* Absolutely nothing, not a single thing, is done for personalizing Trisquel, except distro logos, perhaps a wallpaper, basic documentetion of distro-specific peculiarities, and documentation pertaining to changes. So Trisquel comes with all the bells and whistles of whatever desktop manager happens to be installed, and nothing more. That should cover most all users' functionality needs - system-wise as well as application wise. For instance I may prefer KDE or Xfce over MATE. If Trisquel is to be personalized, then it should be personalized for *all* DE's, because if it's done only at MATE level, then all that personalization work would have been meaningless for anyone who uses another DE. On the other hand, if personalization is done for all the possible DE's to cover everyone, then this would be a big waste of time and effort. So the best bet is not personalize it at all - leave it to whatever Debain defaults to.
* By this logic, also installer is the very Debian Installer, untouched, except logo and distro name modifications and -optionally- default apps list.
Thus, all the energy saved from non-essential work can now be spent on excelling the free drivers, finding better substitutes for popular non-free apps, polishing them -if need be- to the same level as their closed source counterparts, developing a knowlegde/solution base for utilising unfriendly hardware and protocols, etc. That is, now all the energy can go into providing a libre OS with the best possible free alternative solutions to closed ones. This is a huge work already, so I think all the energy should be concentrated there.
Now we have a distro that is statically released biannually, covering the in-between with a rolling testing release, with low release latency, with lowest possible extra work needed.
I don't claim that this is flawless or even well thought of strategy, but anyway it's a fresh approach to the main goal (of a libre and hopefully popular distro). The more tought poured on it, the better solutions will emerge.
