Replies: 1 comment 12 replies
|
Really appreciate the initiation of this discussion. Currently we have two main repos: IMO, As we have discussed, we will have bunch of templates by leveraging the multiple templates mechanism. For Python-only series, what I can imagine is at least three templates:
For Python Binding series, there are at least two categories:
Considering our requirements, seems there are two points we need to make decision:
BTW, we also need to check that the package name is available on PyPI. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Recently, we have been discussing the need for a consistent agreement on the repository naming method for our template instantiation solutions. In order to ensure efficient management and organization of our repositories in the future, I propose that we establish a standard naming convention.
The goal of this proposal is to streamline our repository processes and enhance clarity and accessibility for all team members. By adhering to a consistent naming method, we can avoid confusion, improve searchability, and facilitate seamless collaboration.
I would like to initiate a discussion on this matter to gather your valuable insights and suggestions. Here are a few points to consider:
I encourage everyone to share their thoughts, experiences, and any relevant examples. Let's work together towards a consensus on the repository naming method that will benefit our team and the overall project.
Thank you for your time and contributions.
All reactions