You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.
Currently, we have two ports of upgrade module API:
preupg.script_api - a Python port,
common.sh - a Bash port.
Neither of names used here is good.
Whatever context these names might be encountered in (read: existing modules, man pages, our docs, our trackers), terms "API", "script" and "common" are all already implied. In fact, they are implied by almost any (Python) programming context: any Python or Bash programs can be called "scripts", Python module or a sourced Bash file already is an API and any API is "common" by definition.
We need to come up with better, usable and final name.
Following is what should be considered for the debate:
In future, we might want to expose outer preupgrade-assistant API (eg. to allow people write Ansible modules). That is, we might want to reserve preupg for that.
Name should be brief but specific.
Name should be informative, i.e. not include obvious words as mentioned above.
The text was updated successfully, but these errors were encountered:
One name I was thinking about is upm. This is based on the idea that if what preupgrade-assistant employs here is called "upgrade path", then the element forming that could be called "upgrade path module", ie. UPM.
Currently, we have two ports of upgrade module API:
preupg.script_api - a Python port,
common.sh - a Bash port.
Neither of names used here is good.
Whatever context these names might be encountered in (read: existing modules, man pages, our docs, our trackers), terms "API", "script" and "common" are all already implied. In fact, they are implied by almost any (Python) programming context: any Python or Bash programs can be called "scripts", Python module or a sourced Bash file already is an API and any API is "common" by definition.
We need to come up with better, usable and final name.
Following is what should be considered for the debate:
In future, we might want to expose outer preupgrade-assistant API (eg. to allow people write Ansible modules). That is, we might want to reserve
preupg
for that.Name should be brief but specific.
Name should be informative, i.e. not include obvious words as mentioned above.
The text was updated successfully, but these errors were encountered: