Skip to content
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

[Feature] KitX Project Development Auxiliary Utility #275

Closed
Tracked by #228
ChenPi11 opened this issue Jan 31, 2024 · 4 comments · Fixed by #278
Closed
Tracked by #228

[Feature] KitX Project Development Auxiliary Utility #275

ChenPi11 opened this issue Jan 31, 2024 · 4 comments · Fixed by #278
Assignees
Labels
enhancement New feature or request

Comments

@ChenPi11
Copy link
Member

🪦 Is your feature request related to a problem? Please describe.

I think Crequency need a development auxiliary utility to help maintainer develop KitX or other software.

🪧 Describe the solution you'd like

The utility needs to have the following features:

  • Package management
    Package management is important for multi-package software like KitX.
    • Version control.
      It should support check package version and report version-conflit problems when initializing.
    • Package setup.
      Like Git Submodule, but submodule is too weak(must have SSH pubkey) to initializing KitX, we can use development auxiliary utility to initializing subpackages(the utility support multi ways to get subpackages, but we MUST reserve submodule infomation).
  • Building, packaging and distributing packages.
    The utility should support building, packaging, distributing project packages(and subpackages). We should distribute source-code package and binary package for multi platforms. It should check building requirements and it MUST support the building of multi-program-language packages.
  • Source code linting
    It's a very import feature but we often neglecting. We can run linting in this way to launch multi languages' lint program.
  • Document generating
    It can generate documention like man manual in GNU/Linux. Generate a HTML documment or NLS support for include file is a good idea.
  • CI/CD support
    Support CI/CD is a good feature. We can use this to make CI/CD script easier.
  • Native language support
    The utility should have NLS support. Because it faces developers. We can use this to improve development efficiency.

🧾 Describe alternatives you've considered

No response

📎 Additional context

No response

@ChenPi11 ChenPi11 added enhancement New feature or request help wanted Extra attention is needed labels Jan 31, 2024
@Dynesshely
Copy link
Member

I have already been thinking on this thing, temporarily named cheese.

@Dynesshely Dynesshely self-assigned this Jan 31, 2024
@ChenPi11
Copy link
Member Author

This isssue can close after cheese config files merged into KitX source tree, thank you.

@Dynesshely Dynesshely changed the title Crequency Development Auxiliary Utility [Refactor] Crequency Development Auxiliary Utility Feb 7, 2024
@Dynesshely Dynesshely removed the help wanted Extra attention is needed label Feb 7, 2024
@Dynesshely
Copy link
Member

To accommodate this new auxiliary tool, I am re-architecting the KitX project.

@Dynesshely Dynesshely changed the title [Refactor] Crequency Development Auxiliary Utility [Feature] Crequency Development Auxiliary Utility Feb 7, 2024
Copy link

github-actions bot commented Feb 7, 2024

Tracked by #228 .

@github-actions github-actions bot added the tracking This issue is tracking by another issue label Feb 7, 2024
@Dynesshely Dynesshely changed the title [Feature] Crequency Development Auxiliary Utility [Feature] KitX Project Development Auxiliary Utility Feb 23, 2024
@Dynesshely Dynesshely removed the tracking This issue is tracking by another issue label Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants