2026 usrse CON talk to propose#3
Open
yarikoptic wants to merge 22 commits into
Open
Conversation
SOUL.md (mission):
- Promote Reuse/Compose/Extend/Standardize to five verbs by adding
*Automate*; capture the meta-automation (AI-maintained harness) angle.
- Add the SciOps maturity ladder (Johnson et al., 2024) alongside
STAMPED (Macdonald et al., 2026): STAMPED = per-artifact, SciOps =
team-level operations. Spell out the 5-verb -> L1-L5 mapping; cite
the L3 exemplars (BIDS, NWB, DataLad, DANDI, brainlife.io) the
SciOps paper itself names.
- Fix STAMPED expansion to the canonical Self-containment / Tracking /
Actionability / Modularity / Portability / Ephemerality /
Distributability.
- Add "Many lenses, one stack" recurring framing (Architectural /
Procedural / Sharing / Compositional / Purpose / Maturity ->
MVC / STAMPED / FAIR / YODA / project-purpose / SciOps+AI-ladder).
- Add "Static-first vs. service-tied UI" framing and Hexagonal /
Ports-and-Adapters citation (Cockburn 2005), Smart UI anti-pattern
(Evans, DDD 2003), Service Layer / Anemic Domain Model (Fowler).
- Add "HI <-> AI policy spectrum" recurring framing (Reject /
Accept-with-disclosure / Spec-driven AI-generated / Autonomous)
with CON-portfolio mapping; cite ICMJE Jan 2026 and the
melissawm/open-source-ai-contribution-policies catalog.
- Section 5 canonical-citations gains entries for STAMPED, SciOps.
- Section 7 story-arc list adds MVC-at-stack-scale; the five-verb
spine entry now includes the SciOps level mapping.
INDEX.md (catalog):
- Register two new talks: 2026-usrse-con-talk.html (US-RSE'26 draft)
and 202x-mvc-stack.html (stub for a future MVC-focused talk).
- Topic-lookup section gains rows for MVC framing, Schema-driven UIs
("the Model materializes the View"), Validation harmonization
(con/validation), Multi-dimensional framings, Backend-coupled
service-tied-UI anti-pattern / Hexagonal contrast, Automate /
harness / meta-automation, Five-verbs <-> SciOps maturity levels,
HI <-> AI policy spectrum.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
Outline-only reveal.js stub for a future CON talk that argues the four
CON verbs (Reuse / Compose / Extend / Standardize) converge on
Model-View-Controller at the *stack* scale rather than the app scale.
Promoted from a 4-slide mini-section that lives inside the US-RSE deck.
What's in place:
- Title slide with [WiP] marker and pre-generated QR code (URL is
determined by filename per the talks-repo convention).
- "One thesis, two parts" + "Why at the stack scale" openers.
- Models section: dataset-layout / per-file / metadata / storage
stubs. Metadata stub spells out LinkML / pydantic / JSON Schema /
SHACL alongside HED / DUO / PROV.
- Views section: browse-the-archive / tabular / programmatic /
external-services / **schema-driven UIs** (vjsf -> DANDI meditor,
shacl-vue -> forms and research-group websites; cites Hanke et
al.'s LinkML metadata-driven workflow on ReproTube) / long-form
narrative.
- Controllers section: acquisition->layout / reproducible execution
/ logistics / data->derivative / **validation** ("the recursive
Standardize moment": con/validation harmonizes bids-validator +
HED + pynwb + zarr + nwbinspector + OME-Zarr, deployed in
dandi-cli, VisiData for triage).
- "Contrast: the 'service-tied UI' pattern" section (4 slides) names
Smart UI (Evans, DDD 2003), Anemic Domain Model (Fowler), Hexagonal
Architecture / Ports & Adapters (Cockburn 2005), GoF Adapter /
Strategy / Facade, Service Layer (PoEAA). Counter-pattern: static-
first archives, schema-driven UIs, JAMstack-style decks.
- "One stack, many lenses" section: 6-row table for Architectural /
Procedural / Sharing / Compositional / Purpose / Maturity, mapping
to MVC / STAMPED / FAIR / YODA / project-purpose / SciOps + AI-
coding ladder. Maturity row spells out SciOps L1-L5 and names the
paper's L3 exemplars.
- "Three things to do this week" closer.
QR code: pics/202x-mvc-stack-qrcode.png (generated with
qrcode/`qr` from URL the file will resolve to).
TODO markers in-file flag what each stub slide needs filled in when
promoted to a real talk.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
A draft reveal.js deck for the US-RSE'26 15-min talk and its
proposal-stage companion materials. The deck assembles a single
coherent argument out of slides reused from the existing CON corpus
(2022-nih-compcore, 2023-brain-dandi, 2023-bids-dicom, 2024-distribits-
datalad, 2025-distribits-YODA, 2026-ca-origami-retreat-aicoding) and
wires them onto a new five-verb spine.
2026-usrse-con-talk.html (the deck)
-----------------------------------
Title carries a [WiP] marker; pre-generated QR code references the
predictable datasets.datalad.org/.../<TALK-ID>.html URL.
The five-verb spine:
- Reuse: NeuroDebian + PyMVPA history; duecredit / citeproc-py;
con/duct (built on brainlife's smon); con/citations-collector as
the modern continuation of duecredit.
- Compose: DataLad sandwich mermaid + extensions diagram; small-
acquisition-and-compute units (ReproIn / HeuDiConv / NeuroConv /
con/nwb2bids / ReproStim / ReproNim-containers / con/duct);
registry.datalad.org federation stats.
- Extend: pkg-exppsy -> NeuroDebian -> Debian Med / Debian Science /
conda-forge; citeproc-py co-maintainership; BIDS Steering Group;
DataLad RUNCMD -> BEP028 BIDS provenance lift.
- Standardize: BIDS as a meta-standard (local BIDS-minder.svg);
schemas-as-first-class (LinkML / pydantic / JSON Schema / SHACL);
OBC consent layer; federated archives (DANDI + EMBER + OpenNeuro)
with a layered table for **common standards / infra (AWS S3 +
MinIO) / data logistics (git-annex) / processing (containers,
BIDS-Apps)**.
- Automate: where we automate (CI on every PR, daily-tested git-annex,
con/tinuous CI-log archival, auto-rebuilt ReproNim/containers,
ReproIn/HeuDiConv at the scanner, auto-mirrored dandisets,
con/validation+dandi-cli); cost = harnesses to maintain; meta-
automation move via con/skills + con/yolo; closing slide maps the
five verbs to SciOps L1-L5 with the paper's own L3 exemplars.
Plus:
- "Reuse, in reverse" 3-up (AnnexTube / mykrok / con/serve) with a
WiP Wayback-archive callout (con.github.io/serve/tools/web/
wayback-archive/) -- "local archive of the IA's archive of your
project's archive".
- HI+AI section: STAMPED (per-artifact) + SciOps (team-operations)
framed as complementary; AI-coding ladder presupposes SciOps L3;
L4 -> L5 gap is what AI closes for a small RSE center. New "HI <->
AI -- every project picks its own policy" slide with a 4-stance
spectrum (Reject / Accept-with-disclosure / Spec-driven AI-generated
/ Autonomous), CON-portfolio mapping (git-annex / DataLad+DANDI /
AnnexTube+mykrok+citations-collector / con/skills+con/yolo), and
ICMJE Jan 2026 + melissawm/open-source-ai-contribution-policies
citations.
- "Why it composes -- MVC at the stack scale" mini-section (opener
+ Models + Views + Controllers). Punchline: pick any cell and
swap it; the rest still works. The same block is the seed of the
standalone 202x-mvc-stack.html stub.
- Monday checklist (6 entries; one per verb plus Reuse-in-reverse,
with the Automate entry pointing at con/tinuous).
2026-usrse/talk-proposal-draft.md (the abstract)
------------------------------------------------
Tracks the deck:
- Five-verb framing in title and opening paragraph.
- Per-verb bullets including the new Automate bullet with the
SciOps L4 ("SciOps pipelines") attribution and meta-automation
pitch toward L5 (Optimizing).
- MVC-at-stack-scale bullet covers the architectural rereading.
- HI+AI bullet folds in the 4-stance policy spectrum.
- References add STAMPED (16), SciOps (16a), ICMJE Jan 2026 (16b),
and the melissawm OSS-policies catalog (16c).
- Connection-to-mission Automate bullet ties to SciOps L4/L5.
2026-usrse/projects-audit.md (companion audit)
----------------------------------------------
Gap-list and recommendation tracker comparing this deck against the
broader CON ecosystem (50+ active repos per `gh api orgs/con/repos`).
Records that recommendations 1-5 (con/tinuous, con/yolo+con/skills,
con/citations-collector, con/nwb2bids, OBC) have been applied; flags
the remaining marginal-namedrop candidates (con/external-services,
con/shub, con/noisseur, con/upptime, con/flux, datalad-installer,
fail2ban, psychtoolbox-3-debian).
QR code: pics/2026-usrse-con-talk-qrcode.png.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
Member
Author
|
pushed more changes and also envisioned supplemental talk on "stack level MVC pattern" also filed since unfortunately previews ATM are hard/impossible here. And I should concentrate on abstract alone -- the rest is nice to see how it would shape up but I wonder now if not to propose two talks, where first would be along the dimensions of the presenting historical perspective and actions like automation etc, and then next on MVC, diving more into tech aspects of structuring, integration etc. WDYT? |
yarikoptic
commented
May 11, 2026
A small Makefile in the venue directory so the talk proposal, BoF /
poster templates, README, and projects-audit can be read as HTML
(or PDF) instead of raw Markdown.
Targets:
- `make` -- build <name>.html for every *.md in the folder
(water.css for readable styling, self-contained
single-file output via pandoc --embed-resources).
- `make pdf` -- build <name>.pdf for every *.md, using whichever
PDF engine is on PATH (xelatex / lualatex /
pdflatex / wkhtmltopdf / weasyprint, first match
wins). Errors out with install hints if none.
- `make proposal` -- shortcut for talk-proposal-draft.html + .pdf.
- `make clean` -- remove generated artifacts.
- `make check` -- report which tools are on PATH.
- `make help` -- print the header comment as usage.
Per-file targets work too (e.g. `make talk-proposal-draft.pdf`).
Uses pandoc's GFM reader so the GitHub-flavored tables (the project-
audit status table, the HI<->AI spectrum table) render correctly.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
xcolor's default palette doesn't include "darkblue" / "darkgreen", so
xelatex bailed with:
! Package xcolor Error: Undefined color `darkblue'.
Pandoc passes HTML hex codes straight through to xcolor as
`\definecolor{lcN}{HTML}{...}`, so use CSS-standard hex values:
- darkgreen #006400 for linkcolor / toccolor
- darkblue #00008B for urlcolor
No `dvipsnames` xcolor option needed; works with any vanilla TeX
Live install.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
Pandoc passes the value of `linkcolor` / `urlcolor` / `toccolor`
directly as an xcolor *name* — it does not auto-recognize a bare hex
string and turn it into a `\definecolor` for you. So the previous
attempt (`-V linkcolor=006400`) still failed with
! Package xcolor Error: Undefined color `00008B'.
Robust fix: define the two color names in the preamble via pandoc's
`header-includes` variable, then refer to them by name.
-V 'header-includes=\definecolor{darkblue}{HTML}{00008B}\definecolor{darkgreen}{HTML}{006400}'
-V linkcolor=darkgreen
-V urlcolor=darkblue
-V toccolor=darkgreen
Works on a vanilla TeX Live xelatex; no `dvipsnames` / `svgnames`
options on xcolor needed.
Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
Re-flow the prose sections (Abstract, Connection to Mission) so each sentence sits on its own line. References left as one entry per line. List items: bullet label hoisted to its own line; subsequent sentences indented two spaces. This keeps GFM rendering identical (CommonMark continuation lines join into one paragraph) while giving git diffs a sentence-level granularity that survives copy-edits. No content changes; the rendered HTML / PDF from `2026-usrse/Makefile` is byte-equivalent modulo whitespace. Co-Authored-By: Claude Code 2.1.138 / Claude Opus 4.7 <noreply@anthropic.com>
yarikoptic
force-pushed
the
2026-usrse-con-talk
branch
from
9727465 to
bbb4110
Compare
Co-authored-by: Cody Baker <51133164+CodyCBakerPhD@users.noreply.github.com>
|
|
||
| - **RSE ↔ engineering industry.** | ||
| - **RSE -- engineering industry.** | ||
| Sustained collaboration with **Kitware** on NWB browse/analyze/visualize tooling — a textbook example of an academic RSE center partnering with a non-academic engineering shop. |
Collaborator
There was a problem hiding this comment.
@yarikoptic Can't make suggestion here since thinks line didn't change; recommend breaking into browsing, analysis, and visualization tooling
Otherwise the current PDF rendering violates the margins
Also they state that you should define all acronyms (besides, obviously, RSE) so maybe go full Neurodata Without Borders
Collaborator
|
Keep in mind talks include Q&A Main thing right now is to clip to 1 page abstract; find some of that historical filler that isn't 100% necessary, or reduce the specific scope of software to introduce Be wary of including 'too much' and thus losing focus on the message you want to convey to the US RSE community (this is not 'story telling time' nor 'group introductions' nor 'official productivity reports') Comparing to accepted US RSE talks (feat. Claude Opus 4.7)The risk of the current shape isn't "too historical, not enough software": it's the opposite. The five-verb spine The talks that worked in the group-history mode succeeded because they had one organizing idea (chartering, hospitality, peer mentorship, a Cursor pilot) and treated their tools as evidence for it. If you want a clearer historical-arc talk, the question to answer is: what's the one thesis a reviewer can paraphrase in a sentence after reading the abstract? Right now the candidates are:
For US-RSE'26, given the "Advancing Science in the Age of AI" theme, the cleanest historical-arc framing is probably five verbs + Automate-as-the-new-one + The CON portfolio gets more persuasive when fewer pieces of it are named, not more:
|
Clarified the description of the DataLad registry's functionality by changing 'without central platform' to 'without any central platform'.
Reorganized paragraphs for better clarity and flow, separating concepts related to DataLad and data acquisition tools.
Member
Author
well, that is kinda the theme I had in mind ;) then your claude I think got misguided by my leftovers here from the mvc talk slides sketch which are still here (I have now separate branch, I guess I need to clean up here) -- this abstract does not talk about MVC at all... don't know what to actually take from that AI slop of a review ATM, may be taking more obvious threading for historical arc. Let's see to shrink it, besides |
Collaborator
|
Then I guess I too am very confused by the massive dump of this +3300 PR I've crossed out the MVC/HI/AI portions but I still personally agree with the rest of the evaluation of the specific file: https://github.com/con/talks/blob/110f5213bfa8bc10fa75e6ccf56e3170cb72f163/2026-usrse/talk-proposal-draft.md There is a lot of muddying without a clear thread, point, or takeaway Just a bunch of random listings of random projects CON has been involved with over the years Thats my feedback (and #9) The main question is still why should someone want to hear this talk? What knowledge and information should they walk away with? |
…e-con-talk * gh-con/cody-suggestions: Refactor talk proposal draft for improved readability Clarify DataLad registry description Clarify collaboration details with Kitware in proposal
Member
Author
|
what about now? pdf |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
note: I marked it resolved but this was worth remembering:
Preview PDF in case I do not forget to update: https://www.oneukrainian.com/tmp/talk-proposal-draft.pdf