Anaconda-Platform
nbpresent should be called nb_present
All of our packages are called nb_...:
- nb_anacondacloud
- nb_conda
- etc.
My vote is for consistency
If done, it's probably better to do it now rather than later. It would represent a fair amount of work and broken links, as it's not just s/nbpresent/nb_present/... Docs, ci, metadata specs, etc. Also I'd have to insert a pause when saying it... En bee... Present.
My motivation was that the community pieces generally are nbwhatever, i.e. nbgrader, nbviewer, nbformat, nbconvert. But it would be a lot more work and prs to change all our other extensions, so i will defer if the decision is made...
Longer term, i would see nb_?present becoming its own organization, as there will be a number of things, eventually, that would natively be npm packages, even if they were initially conda/ Pypi: themes, layouts, effects, etc. However, these could be managed in an nb_present_contrib organization, with easier gate keeping than the core repo... But if i end up with the community management task in perpetuity, I'd like them all together.
On 15:38, Mon, Feb 15, 2016 Marcos Vanetta [email protected] wrote:
All of our packages are called nb_...:
- nb_anacondacloud
- nb_conda
- etc.
My vote is for consistency
— Reply to this email directly or view it on GitHub https://github.com/Anaconda-Server/nbpresent/issues/51.
Was doing some brainstorming today on other names... with or without underscores:
- chaplain (as in charley)
- soapbox
- lecturn
- pulp
- pulpit
- (micro)fiche
- dais
- sensei (has sense in it, but not be the right context)
I think nbpresent by itself big enough to break the nb_* paradigm... I see nb_* extensions as relatively tiny extensions to enhance the experience with the conda/anaconda ecosystem... nbpresent is something totally different, so in fact, I would encourage to keep the current name :wink:
