Now that my project schedule is freeing up again (and most importantly, I'm finally free of my various university contracts / commitments over the past few years, with the rather onerous IP provisions those came with), my attention has again been turning towards what sorts of projects I may want to start working on in my free time going forwards.
The key operative principle though for any such projects I now take on is this:
From now on, any passion-projects I dedicate my free time to (and with full force) will necessarily only be ones that I fully control + own. Unfortunately, experience and hindsight have taught me that merely having something be open source (but still part of someone else's platform / hosted by some other funding org) is ultimately not the answer I once believed it to be.
Note: This is also NOT a firm commitment to actually embarking on building all of these things. But rather, just some open-air brainstorming, hoping that someone will build it all for me (and then not put it behind a hideous subscription-based paywall). Heck, maybe the mere act of brainstorming these designs then releasing them as blueprints to hopefully inspire a whole ecosystem of interfaces should be the actual project!
Enough framing boilerplate. Let's get down to the original topic for today's ramblings:
What my ideal "next-gen" photo management + editing tool solution should look like, were I to go through the effort to set one up.