Open DavisRayM opened 4 years ago
Initially this seemed like an easy to do change to me(just renaming) a few things here and there. But I'm starting to wonder if this will require this repository to be archived and another created with all the name changes required ? In that way it will be a new start of sorts ? I'm honestly not leaning towards any of the approaches so far... Any opinions on how this should be done ? For this repository as well as kaznet-frontend
CC: @moshthepitt
@pld @ukanga @engwiri what are your thoughts on this?
Context: the "thing" formerly known as Kaznet is now internally known as Cerana
. SafetyNet is an instance of Cerana for LOTFA and Kaznet is an instance of Cerana for ILRI. Therefore it seems that we would need to move away from using "Kaznet". We are wondering what is the best way of doing that?
Where'd the name Cerana come from? Did we do research on other things w/that name, how it fits w/the market of users?
Technically, if we're committing to a name change, and we don't have a significant external number of users, changing the repo name sounds fine
Where'd the name Cerana come from? Did we do research on other things w/that name, how it fits w/the market of users?
Technically, if we're committing to a name change, and we don't have a significant external number of users, changing the repo name sounds fine
The name Cerana stemmed from a thread on slack here. I'm not aware if research was done on other things with that name or how it would fit with market users. Might be something we need to do before going forward with the repository name change maybe ?
EDIT: The name Cerana is used to refer to a bee (Apis Cerana)
Yes it is
Thanks @pld. Who should lead this research on the suitability of the name?
PM on project can coordinate that
PM on project can coordinate that
@jholmes525 looks like this might be you?
@moshthepitt hahaha thanks for this hot potato. My client LOTFA is very happy with the name SafetyNet. Not sure I'm best placed to look into what we name our products internally.
was this decided? I'm going to unfollow, @rowo is the person to discuss marketing decisions like these w/, but please break down the options, their feasibility, and the anticipated pros/cons before approaching him
I have two questions for whoever can answer: 1) Who would ever even see this name going forward? Seems more for internal use. 2) Does anyone have a paragraph description on Cerana/SafetyNet or repo formally known as Kaznet that's decoupled from any specific application/implementation of it?
Who would ever even see this name going forward? Seems more for internal use.
You mean Cerana, right? Yes that is just for internal use.
Does anyone have a paragraph description on Cerana/SafetyNet or repo formally known as Kaznet that's decoupled from any specific application/implementation of it?
@engwiri please build on top of "Cerana is a crowd-sourced data collection tool."
If this is just for internal use it doesn't really matter what we call it for marketing reasons. The more important thing is to define that second question so it can be marketed.
Kaznet
was the name specifically chosen for one of the flavors of this application. We should change the name of the repository and any mention ofKaznet
to the nameCerana
.