...
2. Would be pulling other people in the org - will approach people as needed or thought of
3. Highlight Hyrax WG releases, losing all the devs in the Hyrax WG, not putting forth more developers, - if you're not giving devs, give money. Can we do that -
combine "ask" - tying the usual contribution - state dependencies - here's all the stuff, if you like the contributions, you should give money or give dev time to support the roadmap
Informal contact or other kinds of messages to particular interests -
Ask goes out in March/ April -
Personal contact - approach to reach out to individuals at institutions - work within BTAA - IU, Mich, Northwestern - director to director peer pressure
A more targeted, personalized approach - contact list of who knows who and who can reach out to whom, have their UL reach out.
What are the aspirations for the year? -
Contribution WG - model
What we want to do with the money - shoot for that amount in the contributions (what we'll do with the money - what does it go to?)
What money will be used for - multi-year commitment ask
4. See notes in " " - need to build positions into that as well. Getting a lot of support as they get it together
5. 2.5% initiative - David Lewis from IUPUI - libraries should give 2.5% to community-based projects supporting infrastructure to open source - what percentage of instutions budget is the library archive https://scholarworks.iupui.edu/handle/1805/14063
Fedora, DuraSpace, Samvera - bundling that gift? Should Samvera community bundle that?