(Note to moderators: I did my homework, and I know there is a very similar question, I'm putting on a different perspective. Please be somewhat more lenient to me. Yes, I'm asking for forgiveness not permission :])
In the past year, I wrote an application in order to deliver as my grad thesis. Its fine, and it works with some interesting aspects long forgotten in Web Applications (like chains or responsibility) for a very interesting environment (IBM's ProjectZero).
That said, I am just not willing to let this code rot. As such, I am planning to work on it and release as an open source framework. The application in itself is very specific and its likely to benefit from the fork, but I'd like to tailor it for a more general audience, so its best to fork the framework and let the application alone (for a while).
Although this one looks fine in theory, I'd like to ask you to help me with the big picture: Which aspects/milestones/tasks would you consider in order to fork a given codebase into a self-contained framework?
Is there any link and/or ideas? Consider there are mainly three aspects: - Legal Aspects (licenses for each dependency, et al); - Community Aspects (its interesting to gather and keep a community around it); - Code Aspects (writing tests, rewriting docs, things like that)
Thank you.