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

Which specifications should be added or completed #6

Open
2 of 4 tasks
vhtq18w opened this issue Feb 23, 2020 · 0 comments
Open
2 of 4 tasks

Which specifications should be added or completed #6

vhtq18w opened this issue Feb 23, 2020 · 0 comments

Comments

@vhtq18w
Copy link
Contributor

vhtq18w commented Feb 23, 2020

Now we have only created a small part of UKUI project specifications, include:

  • issuse label specification.

In-progress or planned specifications include:

  • issuse report specification(report template)
  • license specification(which licenses should be used for the UKUI's projects)
  • code style spcification(unified c/c++ code style)

In addition, what aspects should we have specification? Such as:

  • What specifications should be written for unified documentation?
  • Which principles should be used when code have conflicts?
  • Does CI need specification?

I think it would be better to discuss a more detailed list.

liuxiran added a commit to liuxiran/community that referenced this issue Mar 22, 2020
add bug issue template and feature issue template

issue ref: ukui#6
liuxiran added a commit to liuxiran/community that referenced this issue Mar 22, 2020
add bug issue template and feature issue template

issue ref: ukui#6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant