Open cbh2000 opened 6 years ago
The purpose of this issue is to decide upon the scope of v1.0. It should not be used to discuss progress towards implementation.
An in-progress requirements document for Retrolux 1.0 lives here: https://goo.gl/6f1fqf
@cbh2000 Are there still plans to move this project forward, or has it been abandoned?
@mitch10e I paused development while I considered future options. I think it's still on, but I'm mostly hesitant about whether or not someone else will be able to maintain it when I'm gone. I'll wait until I know when I'm leaving to decide, but I think it's still on. There are no technical hurdles to overcome as far as Retrolux itself is concerned, I think it's just time to develop it that's needed at this point. I think that making Retrolux strictly an API wrapper and workflow around existing frameworks may be a good way to increase the chances of this being a successful project.
Retrolux v1.0 is currently being designed and prototyped. It's primary goals are:
Currently, we are working on redesigning the Builder API towards accomplishing goals 3, 4, 6, 7, and 8.