-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choose a package name #19
Comments
Deeeeeeecisions!! π¬π¬π¬ Iβd love to tweet this but we need a little more information about the project to go with the question. Would you be up for writing a mini blog post (5-10 sentences!) to explain what weβre aiming for and why we need a name? I donβt know if thereβs an easy way to embed a poll in Jekyll but that might be fun! Very simple google form maybe? Also, have you done any googling for these names? Or brain networks in python packages that already exist? We need to make sure they donβt overlap. I will say that we should definitely conform to the guidelines - no need to go rogue on the camel case etc. |
Great. Yes I will write up a blog post and check what's already been taken |
Could also include (Soooo many options!) |
Suggested this morning by a friend: turnip (=turing networks in python). No reference to brains unfortunately, but what a cute idea! |
Note to self: poll.ly is a good tool for polls to which voters can add suggestions |
The blog post is now up https://whitakerlab.github.io/blog/Boaty-McBrainNetworksInPython/ |
We have finally firmly settled on the new name |
Update:
Please help us choose a package name by voting and suggesting in this poll π β¨ πΈ
You can find a little background information on what we're doing and why we need to choose a new name in our blog
A naming convention for python packages and modules is reccomended in PEP 8
What do you think gang? Should we stick to our guns and go
BrainNetworksInPython
, compromise onbrainnetworksinpython
,bnip
,pythonbrainnetworks
,brainnetworks
,networkbrains
, or abandon propriety and gonetworknoggins
The text was updated successfully, but these errors were encountered: