What's the point of the framework? I think the point is to have agreed-upon way of building things. Whether the framework is 3rd party or not is not very relevant, unless you're thinking about hiring new people. It's gonna take less time for new people to get familiar with how to build your thing if you're using a 3rd party framework, but really only if the framework is darn popular. If the framework is not popular, there's no reason to use it because new people will have to get familiar with it as well.
It seems like what you're doing is completely right, separating code into smaller independent modules. If an independent framework / engine comes out of it, there's nothing wrong with it. You may choose to publish it or to keep it private, and that's totally up to you - if you're not willing to market or support it, might as well keep it private.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What's the point of the framework? I think the point is to have agreed-upon way of building things. Whether the framework is 3rd party or not is not very relevant, unless you're thinking about hiring new people. It's gonna take less time for new people to get familiar with how to build your thing if you're using a 3rd party framework, but really only if the framework is darn popular. If the framework is not popular, there's no reason to use it because new people will have to get familiar with it as well.
It seems like what you're doing is completely right, separating code into smaller independent modules. If an independent framework / engine comes out of it, there's nothing wrong with it. You may choose to publish it or to keep it private, and that's totally up to you - if you're not willing to market or support it, might as well keep it private.