Interesting term: scaling back. I do not think that it is scaling back.

What we merely want to do is remove some (old) stuff that makes the module complex, is incomplete and is not used very often (PayPal payments) and replacing a very old component: the calendar: a component we did not really touched in the last 6 years. 

The first change is obvious (until the DNN platform will provide a payment provider mechanism) and will leave some users behind, but provides a better platform for the rest and the future of Events. 

The second option is more complex, we have to find an Open Source component that will fit in the requirements for a real calendar (there are not that many around with enough functionality) or move to the RadScheduler of Telerik which is on the other end of the scale of functionality (and complexity).

Knowing that Roger is high level sales consultant in a world wide IT services company and works in general more than 40hrs per week and I have to run an IT company with 30 employees there is a ample room for free lance DNN work, let alone if we would be interested to do that (as persons we are not).

I have another suggestion: my company does DNN development work (that seems logical since we are a DNN Gold Certified Partner).

What we could do is paid work on the Events module for an attractive rate, with the condition that we can add the (paid) enhancements and changes to the core, so to the benefit of all.In fact this is what we just agreed with one of our clients who uses the Invenmanager module. We could also bundle enhancements so the investment for requiurements can be shared. We do not have to make big money on this work, that is not our (my) objective with the Events module, but it should pay for the time spend, since I have to make choices how my employee spend their time and we earn our money.

This way we can all profit: there is more time (budget) for enhancements of the Events module, the enhancements be part of the core module and will be maintained in new versions.

Is this a workable solution?

I sure hope you will not tie the Events module to the horrible Telerik-cancer that has plagued DNN in the past. Telerik is a big pile of proprietary code from a business that is well beyond it's peek (the asp.net proprietary web controls business). This will not end well. Diminishing profits and rising costs will send Telerik and it's restrictive terms-ridden bytes to the digital scrapyard in the very near future. I hear that DNN is moving away from Telerik because the terms have changed. Another proof that proprietary code represents high risks and a waste of time.