Two sort of related questions.
1. I sent a support ticket in a couple days ago asking for advice on the safest way to update OO on Pantheon's platform. You've indicated prior that supporting Pantheon's for-profit business is not a goal...which I totally respect. But I'm happy to do the updates as needed...all I'm looking for is an expert's advice on how to manage the update process for the OO distribution when we're working within the git-driven Pantheon environment.
No reply from you as yet...so I guess question 1 is: how are you folks travelling? Is OO still a live project for you? Should I be depending on OO as a foundation for some new sites I'm building?
2. Let's suppose the answer to (1) is a bit ambivalent. It's tough out there and yes, this has been a labour of love and yes, it might be time to move on. That's completely understandable. Thank you for the tremendous work you've already donated to the Drupal community at large, and our beloved non-profit sector in particular.
The question is, can you dotpoint a transition procedure that points out any special code/patches that help hold the OO distro together? I'm not worried about all the normal configurations a U1 site builder should be able to handle. What I'm worried about is losing any bespoke patchwork.
Put it another way: if you guys walk away tomorrow, what we have left is: [Drupal core and an assembly of modules] + Configurations set through the UI + [unknown custom code/patches].
Can you quantify this last element? That will allow us OO users to figure out how to maintain our sites into the future.