Hi all,
Quick note that senaite.starter has moved into the SENAITE GitHub organization and is now GPL-2.0. Public commit history, no shop checkout, the usual.
For anyone who hasn’t run into it: senaite.starter is the package we used at RIDING BYTES (and sold as a paid add-on) to bootstrap a new SENAITE deployment. It’s a complete starter project rather than just a code template. You get a working buildout.cfg
for a production-style instance, a development.cfg that pulls SENAITE and its add-ons in from source for upgrade testing, an mkdocs documentation skeleton, a test layer wired up so bin/test works on day one, and an empty senaite.starter add-on inside
SENAITE’s controlpanel where your custom code lives. Clone, build, and you’ve skipped the part of the project where you stare at a blank buildout.cfg for an afternoon.
I’ll be honest: I should have done this earlier. The code itself was never really the point. What you got was a set of decisions — which buildout sections to pin where, how to lay out the dev config so you can swap into a checkout cleanly, how to
structure the tests so they survive a Plone upgrade, the conventions for where customisations live in the source tree. Decisions are at their best when more people are pushing on them, which doesn’t happen behind a paywall.
There’s also the consistency angle. We’ve been Core Developers on this project from day one, and the work we’re proud of is the work that’s already in the open. Selling a private starter on top of the same upstream codebase always sat a bit oddly with
that. Moving it upstream just fits better.
For anyone who bought the starter previously: your installs are unaffected, your support contracts are unchanged, and what’s in the public repo is the same 1.0.0 line you have. If you want to switch your buildout to track the upstream branch at some
point, ping us and we’ll sort the pin and run the regressions for you.
What I’d love to see now is the usual: issues, PRs, an argument or two on how the buildout sections should be split. If your own starter does something better than ours, send it — that’s exactly the kind of contribution the repo could use.
Repo: GitHub - senaite/senaite.starter: An installable SENAITE LIMS extension for individual customization purposes · GitHub
Background and a short video: SENAITE Starter is now open source - RIDING BYTES
Cheers, and happy to dig into any of it in the thread.
Ramon