Yes, we can reuse github.com/nuttx to host the 3rd party library which stop the active development. But It's better to host the library by the different git to keep the full history for each project.
I think it could be used in projects in active development too. I have seen people take a git fork for application code that that they want to modify. Then they put their modifications on a branch of that fork. Then it is very simple to refresh the master branch of the application and rebase the modified branch. In that way, we can keep in sync with the active upstream project with only a little effort.
That is an advantage of keeping 3rd party code outside of the NuttX repositories.
The best would be to get the application code to take our changes upstream. That could be done with a simple PR from the fork. But in the event that they are unwilling to accept the changes upstream, keeping our changes on a branch of a local fork is still workable for us.
