Replies: 1 comment 2 replies
-
|
Not sure I agree a new name is "needed"; this is often just a matter of definition and of users getting used to the name. We have some prior investment in the BioCypher name; people know it, our web domain is called like that, our Zulip chat, etc. Additionally, getting a domain registration for biotope seems difficult; all the regular domains (.org would be preferred) are taken (but there are no websites there). I count myself lucky that I managed to get the PyPI entry for biotope. That being said, using |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As more and more packages with relation to
BioCypherare introduced, an ecosystem around it is gradually forming and this ecosystem, at the time of writing, is often referred asBioCypher. The multiple uses of the name on both the ecosystem and the actual package is causing confusion and a new name is needed. @slobentanzer proposed to use the newly created project, the CLI interface for packages in the ecosystem,Biotopeas the name of the ecosystem.It's not uncommon for ecosystems to have the same name as their primary interfaces such as
.NET,dockerandanacondaso the use ofBiotopeseems sensible but the direction ofBiotopemay need to be adjusted a bit to better fulfills the purpose as an entry point of the ecosystem. Comments and concerns will be put here.Beta Was this translation helpful? Give feedback.
All reactions