「App:Library:LVGL:docs:Contributing」の版間の差分

提供: robot-jp wiki
ナビゲーションに移動検索に移動
4行目: 4行目:
 
!英文
 
!英文
 
!自動翻訳
 
!自動翻訳
|-
 
|
 
|
 
|-
 
|
 
|
 
|-
 
|
 
|
 
|-
 
|
 
|
 
|-
 
|
 
|
 
|-
 
|
 
|
 
|-
 
|
 
|
 
 
|-
 
|-
 
|
 
|
31行目: 10行目:
  
  
 +
 +
= Contributing =
 +
 +
== Introduction ==
 +
Join LVGL's community and leave your footprint in the library!
 +
 +
There are a lot of ways to contribute to LVGL even if you are new to the library or even new to programming.
 +
 +
It might be scary to make the first step but you have nothing to be afraid of. A friendly and helpful community is waiting for you. Get to know like-minded people and make something great together.
 +
 +
So let's find which contribution option fits you the best and help you join the development of LVGL!
 +
 +
Before getting started here are some guidelines to make contribution smoother:
 +
 +
* Be kind and friendly.
 +
* Be sure to read the relevant part of the documentation before posting a question.
 +
* Ask questions in the Forum and use GitHub for development-related discussions.
 +
* Always fill out the post or issue templates in the Forum or GitHub (or at least provide equivalent information). It makes understanding your contribution or issue easier and you will get a useful response faster.
 +
* If possible send an absolute minimal but buildable code example in order to reproduce the issue. Be sure it contains all the required variable declarations, constants, and assets (images, fonts).
 +
* Use Markdown to format your posts. You can learn it in 10 minutes.
 +
* Speak about one thing in one issue or topic. It makes your post easier to find later for someone with the same question.
 +
* Give feedback and close the issue or mark the topic as solved if your question is answered.
 +
* For non-trivial fixes and features, it's better to open an issue first to discuss the details instead of sending a pull request directly.
 +
* Please read and follow the Coding style guide.
 +
 +
== Pull request ==
 +
Merging new code into the lvgl, documentation, blog, examples, and other repositories happen via ''Pull requests'' (PR for short). A PR is a notification like "Hey, I made some updates to your project. Here are the changes, you can add them if you want." To do this you need a copy (called fork) of the original project under your account, make some changes there, and notify the original repository about your updates. You can see what it looks like on GitHub for LVGL here: <nowiki>https://github.com/lvgl/lvgl/pulls</nowiki>.
 +
 +
To add your changes you can edit files online on GitHub and send a new Pull request from there (recommended for small changes) or add the updates in your favorite editor/IDE and use git to publish the changes (recommended for more complex updates).
 +
 +
=== From GitHub ===
 +
 +
# Navigate to the file you want to edit.
 +
# Click the Edit button in the top right-hand corner.
 +
# Add your changes to the file.
 +
# Add a commit message on the bottom of the page.
 +
# Click the ''Propose changes'' button.
 +
 +
=== From command line ===
  
  
 
----
 
----
 
[https://robot-jp.com/wiki/index.php/App:Library:LVGL 戻る]
 
[https://robot-jp.com/wiki/index.php/App:Library:LVGL 戻る]

2022年6月22日 (水) 18:50時点における版

https://docs.lvgl.io/8.2/CONTRIBUTING.html

英文 自動翻訳


Contributing

Introduction

Join LVGL's community and leave your footprint in the library!

There are a lot of ways to contribute to LVGL even if you are new to the library or even new to programming.

It might be scary to make the first step but you have nothing to be afraid of. A friendly and helpful community is waiting for you. Get to know like-minded people and make something great together.

So let's find which contribution option fits you the best and help you join the development of LVGL!

Before getting started here are some guidelines to make contribution smoother:

  • Be kind and friendly.
  • Be sure to read the relevant part of the documentation before posting a question.
  • Ask questions in the Forum and use GitHub for development-related discussions.
  • Always fill out the post or issue templates in the Forum or GitHub (or at least provide equivalent information). It makes understanding your contribution or issue easier and you will get a useful response faster.
  • If possible send an absolute minimal but buildable code example in order to reproduce the issue. Be sure it contains all the required variable declarations, constants, and assets (images, fonts).
  • Use Markdown to format your posts. You can learn it in 10 minutes.
  • Speak about one thing in one issue or topic. It makes your post easier to find later for someone with the same question.
  • Give feedback and close the issue or mark the topic as solved if your question is answered.
  • For non-trivial fixes and features, it's better to open an issue first to discuss the details instead of sending a pull request directly.
  • Please read and follow the Coding style guide.

Pull request

Merging new code into the lvgl, documentation, blog, examples, and other repositories happen via Pull requests (PR for short). A PR is a notification like "Hey, I made some updates to your project. Here are the changes, you can add them if you want." To do this you need a copy (called fork) of the original project under your account, make some changes there, and notify the original repository about your updates. You can see what it looks like on GitHub for LVGL here: https://github.com/lvgl/lvgl/pulls.

To add your changes you can edit files online on GitHub and send a new Pull request from there (recommended for small changes) or add the updates in your favorite editor/IDE and use git to publish the changes (recommended for more complex updates).

From GitHub

  1. Navigate to the file you want to edit.
  2. Click the Edit button in the top right-hand corner.
  3. Add your changes to the file.
  4. Add a commit message on the bottom of the page.
  5. Click the Propose changes button.

From command line


戻る