discussion: should the package be renamed to avoid ambiguity?

[john-halloran]

Problem

• "sNMF" is already in use as an identifier for a technique called "sparse non-negative matrix factorization"
• Uptake of this older sNMF does not seem to be high, but there are a few sources for it, including papers as recent as 2022, and it's the current top result for the term on search engines and chatbots.

Proposed solution

• There are two potential solutions. One is to bet that sparse NMF will not gain much further traction and that we will become the dominant program associated with the acronym or that they will coexist, like PDF already does with the PDF file format
• The other option would be to formally rename the package something like stretched-nmf, which is the primary term used in the original stretched NMF paper. One pro of this is that it would be clearer from just the name what the package does. Only major con is that it's less elegant.

[john-halloran]

After thinking more, I feel positively about calling it stretched-nmf. The biggest obstacle (and this may be a killer) is that the original paper has a presumably unchangeable link to this github repo called diffpy.snmf, but maybe github alias that if you change the name. Not sure how that works.