Reading your post earlier and got me thinking: are there more then one community type? As in ...
There are FOSS communities which members find each other for FOSS sake.
But a more divers sort of community often gathers around the application.
For example, the OSMand community consists of cartography enthousiasts AND developers and everyone in between.
Although I like your app (intention and application, no scope creap etc) it doesnt unite users around a common goal. Which doesnt matter much because its still usefull.
Another example would be:
Recently a website to convert student tests scores to grades started to ask money. If a FOSS app would provide this the community would consist also of teachers and test grading people.
Off topic slightly but for music VLC for Android is even better compared to its desktop sibling for the same purpose.
I mean VLC for desktop will play anything and I dont deny how powerfull it is but afaik:
it doesnt rescan automaticaly for added and removed music like a watchfolder.
No native dark mode yet, yes a ton of dark mode themes, but they all are geared to video and lacking the medialibrary with album browsing.
Must admit, those fields are precisely the ones I use in my filenaming convention. Other DMS put that in their databases but alas that's just trading one stack for another.
Other ones put it in XMP metadata of the pdf themselves. But I guess the work involved would be similar.
I don't need formatting but it doesn't get in the way either. So I am not bothered by it.
Also pdf and especially PDF/A standard is widely used for archiving and compliance regulation concerning archival and preservation.
If you want text the same tactic goes: just export in bulk to txt instead of pdf
My main point is:
Why would you want a mail specific stack of hosting, storage, indexing and frontends? If it's all plain text anyway so the regular storage solutions for files come a long way.
There is an entire industry (which has its own disadvantages) to get communication artefacts out of those systems and put it in document management systems or other forms of file based archival.
I had roughly the same goals ( archive search 2 decades of mail) but approached it completely different:
I export every mail to PDF with a strict naming convention.
Backend: No mailserver, just storage and backup for files.
Search: based on filenames FSearch and Void tools Everything. I could use local indexing on pdf content.
I think he meant save the actual notes themselves.
Often necessary for sync engines to replicate the notes to other devices and manage version control.
at the beginning of the music library a lot of "no artist name" "no album name" entries, so the foldername isn't used at all.
a lot of artist with their own entry with just one album and one song because the actual albumartist collaborated on one song with them and the mp3 resides in the same folder but they got split in the library.
if the player doesn't show music which isn't part of Playlist.
So my conclusion is their are even 3 types and corresponding mangement:
A music player which "just plays whatever is in a directory". Very handy for people having a media folder with artist folders and album subfolders.
For the type of people, like myself, who focus more on tidy and disciplined storage of files instead of managing ID3 metadata etc
I don't know, but I guess the reason why it isn't done yet is because nobody perceives it as a problem.
It would require a repository plugin to install plugins I think.
But it all comes down to plugin distribution and deployment. Mostly if you want something outside the default repository you can just upload it to your own install / stack. If a developer provide alternative download ways. Like a github release for example.
If an historical timeline uses this labeling system it can't omit the NT part though. Windows NiceTry came out in 1993 but also long after that MS had MS-DOS based editions (up until Windows Me iirc)
Reading your post earlier and got me thinking: are there more then one community type? As in ...
There are FOSS communities which members find each other for FOSS sake.
But a more divers sort of community often gathers around the application.
For example, the OSMand community consists of cartography enthousiasts AND developers and everyone in between.
Although I like your app (intention and application, no scope creap etc) it doesnt unite users around a common goal. Which doesnt matter much because its still usefull.
Another example would be: Recently a website to convert student tests scores to grades started to ask money. If a FOSS app would provide this the community would consist also of teachers and test grading people.