tripkip wrote:I think the problem is that the recorder code is closed to begin with. Code cannot even be read so people looking for a per backend that they want to improve on will walk away. Put it on github and PR's will start flowing in guaranteed.
Hey tripkip
First of all: I'm not the owner of the code and I don't have the sources of the recorder.
I had some thoughts about what you say and please allow me to contradict.
- Nearly all of the bug reports and
- Nearly all of the improvement suggestions are concerning scheduler
- the scheduler and its interfaces are the ones to be addressed from third-party software, never the recorder
And in general, I think we should not think the way, "one has first to fulfill preconditions in order that I'm able to do sth.". Such an argument usually is an easy excuse not to do sth., and even not to start.
I think the opposite way:
- I CAN adopt and develop on the scheduler, the notifier and other components
- I just DON'T DO it right now...
That's the reason, why I was looking for developers and "movers" to do the first steps... describe, what is needed, how a dev. environment must be set up, how the first build can be done seccessfully and..
... to gather the team. As I know, with my professional life, I will fail to try alone.
No blaming, trip, but just my way of thinking... the "ten-two-letter-words": if it is to be, it is up to me.
I had just the request of two to three persons now to be promoted to the state of developers - but no more request since then nor questions. So I must see my approach as failed.
Just my two Pennies, after I thought some days about what you said.
Kind greetz - Chris