René's URL Explorer Experiment

{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://mission.managed-code.com/#org","name":"Managed Code · Mission","alternateName":"Managed Code Mission","url":"https://mission.managed-code.com/","logo":"https://mission.managed-code.com/icon-512.png","image":"https://mission.managed-code.com/og.png","sameAs":["https://github.com/managedcode","https://www.managed-code.com"],"email":"opensource@managed-code.com","description":"A patronage initiative: fund a team of maintainers to keep open source alive — with reserved capacity and real SLAs.","slogan":"Patrons of the digital commons."},{"@type":"WebSite","@id":"https://mission.managed-code.com/#website","url":"https://mission.managed-code.com/","name":"Mission by Managed Code","description":"A patronage initiative: fund a team of maintainers to keep open source alive — with reserved capacity and real SLAs.","inLanguage":"en","publisher":{"@id":"https://mission.managed-code.com/#org"}},{"@type":"WebPage","@id":"https://mission.managed-code.com/#webpage","url":"https://mission.managed-code.com/","name":"ManagedCode — Patrons of the Digital Commons","isPartOf":{"@id":"https://mission.managed-code.com/#website"},"about":{"@id":"https://mission.managed-code.com/#org"},"primaryImageOfPage":"https://mission.managed-code.com/og.png","description":"Fund a team of maintainers to keep the open source you depend on alive — reserved maintainer capacity, real SLAs, juniors trained in the open. A Managed Code initiative.","inLanguage":"en"},{"@type":"FAQPage","@id":"https://mission.managed-code.com/#faq","mainEntity":[{"@type":"Question","name":"How is this different from GitHub Sponsors?","acceptedAnswer":{"@type":"Answer","text":"Sponsorships are donations — under 40% of profiles ever get one, with no obligation. Mission is a contract: reserved maintainer capacity, a written SLA, and a named maintainer who owns your dependencies. The money pays salaries."}},{"@type":"Question","name":"Be honest — will anyone actually pay for this?","acceptedAnswer":{"@type":"Answer","text":"We don’t need everyone to. A handful of patrons funds a maintainer — we’re not waiting for the whole industry to come around, and we’d rather staff the commons for the companies who already get it. Enough is enough. Think of it as our stake in the future of the code we all ship on."}},{"@type":"Question","name":"Why not just donate to each project we depend on?","acceptedAnswer":{"@type":"Answer","text":"Because it doesn’t scale and it doesn’t add up. No enterprise can realistically send small tips to every dependency in its tree — and even if it could, scattered tips never reach payroll. Mission pools your patronage into a funded team and reserves capacity for the specific dependencies you name."}},{"@type":"Question","name":"What’s in it for Managed Code?","acceptedAnswer":{"@type":"Answer","text":"We get to pay the people who keep open source alive — maintainers, full- or part-time — and train juniors into the role. We’re already doing this work; it should be funded properly. If the people already doing it don’t, who will?"}},{"@type":"Question","name":"What counts as a maintainer-hour?","acceptedAnswer":{"@type":"Answer","text":"A focused maintenance hour on the dependencies you adopt: triage, review, fixes, security backports, releases, upgrades, reproductions, and answering your engineers. It is not a generic developer-hour pack; each grade reserves a planning band, and the final allocation is scoped in the SLA."}},{"@type":"Question","name":"What if you don’t maintain the library we need?","acceptedAnswer":{"@type":"Answer","text":"Normal case. You name the dependencies; we evaluate them, talk to upstream, and take them on. Patronage is shaped around your stack."}},{"@type":"Question","name":"Do we have to be a .NET shop?","acceptedAnswer":{"@type":"Answer","text":".NET is home turf — that’s where we’re strongest. Other ecosystems we take case by case. Tell us your stack and we’ll be straight about what we can own."}},{"@type":"Question","name":"Where is the team based?","acceptedAnswer":{"@type":"Answer","text":"Managed Code is remote-first, with EU business-day coverage first. US overlap, weekend rotation, and 24/7-style escalation are custom scope, not implied by the public grades."}},{"@type":"Question","name":"How is this different from a vendor support contract?","acceptedAnswer":{"@type":"Answer","text":"A vendor supports their product. We maintain open code anyone can use, with fixes pushed upstream. You get reliability without a walled garden."}},{"@type":"Question","name":"How do juniors fit in without slowing things down?","acceptedAnswer":{"@type":"Answer","text":"Mentorship works when it’s budgeted, not bolted on. Senior review and mentor time are part of the model; juniors learn on real issues, in public, but they are not the only owner of your incident."}},{"@type":"Question","name":"Where does the money go?","acceptedAnswer":{"@type":"Answer","text":"Maintainer salaries and junior mentorship. Patronage, hours, and outcomes are reported in the open, the same way we ship code."}},{"@type":"Question","name":"Is there a commitment — and can we cancel?","acceptedAnswer":{"@type":"Answer","text":"Maintenance only pays off when it’s continuous, so we ask for a real commitment to start — a quarter — long enough to actually adopt your stack. After that you’re never locked in: give notice, we hand off cleanly, and you walk. If the monthly reports don’t show value, you shouldn’t be renewing."}}]},{"@type":"Service","@id":"https://mission.managed-code.com/#service","name":"Open-source patronage","serviceType":"Open-source software maintenance, security and support","provider":{"@id":"https://mission.managed-code.com/#org"},"areaServed":"Worldwide","description":"A patronage initiative: fund a team of maintainers to keep open source alive — with reserved capacity and real SLAs.","offers":[{"@type":"Offer","name":"Junior-grade patronage","description":"A practical lane for a small stack: triage, reproductions, small fixes, and reports. Salary-grade retainer at roughly junior-grade payroll; exact capacity and SLA are scoped in the patronage agreement.","category":"Open-source maintenance patronage","availability":"https://schema.org/InStock","url":"https://mission.managed-code.com/#patronage"},{"@type":"Offer","name":"Mid-grade patronage","description":"The default operating lane: a named maintainer, enough capacity for real upstream work, sane SLA. Salary-grade retainer at roughly mid-level payroll; exact capacity and SLA are scoped in the patronage agreement.","category":"Open-source maintenance patronage","availability":"https://schema.org/InStock","url":"https://mission.managed-code.com/#patronage"},{"@type":"Offer","name":"Senior-grade patronage","description":"For critical dependencies: senior ownership, faster triage, security/backport planning, and mentorship budget. Salary-grade retainer at roughly senior-grade payroll; exact capacity and SLA are scoped in the patronage agreement.","category":"Open-source maintenance patronage","availability":"https://schema.org/InStock","url":"https://mission.managed-code.com/#patronage"}]}]}