mirror of https://github.com/goharbor/harbor.git
add new version info for contributing guide
Signed-off-by: Meina Zhou <meinaz@vmware.com>
This commit is contained in:
Meina Zhou
parent
3db3f3a62e
commit
c59e0b2aeb
|
|
@ -42,7 +42,6 @@ Here is the basic structure of the harbor code base. Some of the key folders / f
|
|||
```
|
||||
.
|
||||
...
|
||||
├── Makefile # Make file for compile and build code
|
||||
├── contrib # Contain documents, scripts, and other helpful things which are contributed by the community
|
||||
├── docs # Keep documents here
|
||||
├── make # Resource for building and setting up Harbor environment
|
||||
|
|
@ -56,46 +55,56 @@ Here is the basic structure of the harbor code base. Some of the key folders / f
|
|||
The folder graph below shows the structure of the source code folder `harbor/src`, which will be your primary working directory. The key folders are also commented.
|
||||
```
|
||||
.
|
||||
├── adminserver # Source code for the admin server component
|
||||
│ ├── api
|
||||
│ ├── auth
|
||||
│ ├── client
|
||||
│ ├── handlers
|
||||
│ ├── systemcfg
|
||||
│ └── systeminfo
|
||||
├── chartserver # Source code contains the main logic to handle chart.
|
||||
├── cmd # Source code contains migrate script to handle DB upgrade.
|
||||
├── common # Source code for some general components like dao etc.
|
||||
│ ├── api
|
||||
│ ├── config
|
||||
│ ├── dao
|
||||
│ ├── http
|
||||
│ ├── job
|
||||
│ ├── models
|
||||
│ ├── notifier
|
||||
│ ├── scheduler
|
||||
│ ├── rbac
|
||||
│ ├── registryctl
|
||||
│ ├── secret
|
||||
│ ├── security
|
||||
│ └── utils
|
||||
├── jobservice # Source code for the job service component
|
||||
│ ├── api
|
||||
│ ├── config
|
||||
│ ├── job
|
||||
│ ├── replication
|
||||
│ ├── scan
|
||||
│ └── utils
|
||||
├── ui # Source code for the harbor service component
|
||||
├── core # Source code for the main busines logic. Contains rest apis and all service infomation.
|
||||
│ ├── api
|
||||
│ ├── auth
|
||||
│ ├── config
|
||||
│ ├── controllers
|
||||
│ ├── filter
|
||||
│ ├── label
|
||||
│ ├── notifier
|
||||
│ ├── promgr
|
||||
│ ├── proxy
|
||||
│ ├── service
|
||||
│ ├── static
|
||||
│ ├── systeminfo
|
||||
│ ├── utils
|
||||
│ └── views
|
||||
├── jobservice # Source code for the job service component
|
||||
│ ├── api
|
||||
│ ├── config
|
||||
│ ├── core
|
||||
│ ├── env
|
||||
│ ├── errs
|
||||
│ ├── job
|
||||
│ ├── logger
|
||||
│ ├── models
|
||||
│ ├── opm
|
||||
│ ├── period
|
||||
│ ├── pool
|
||||
│ ├── runtime
|
||||
│ ├── tests
|
||||
│ └── utils
|
||||
├── portal # The code of harbor web UI
|
||||
│ ├── e2e
|
||||
│ ├── lib # Source code of @harbor/ui npm library which includes the main UI components of web UI
|
||||
│ └── src # General web page UI code of Harbor
|
||||
├── registryctl # Source code contains the main logic to handle registry.
|
||||
├── replication # Source code contains the main logic of replication.
|
||||
├── testing # Some utilities to handle testing.
|
||||
└── vendor # Go code dependencies
|
||||
├── github.com
|
||||
├── golang.org
|
||||
|
|
@ -116,7 +125,8 @@ Harbor backend is written in [Go](http://golang.org/). If you don't have a Harbo
|
|||
| 1.4 | 1.9.2 |
|
||||
| 1.5 | 1.9.2 |
|
||||
| 1.6 | 1.9.2 |
|
||||
| 1.6 | tbd |
|
||||
| 1.7 | 1.9.2 |
|
||||
| 1.8 | 1.11.2 |
|
||||
|
||||
Ensure your GOPATH and PATH have been configured in accordance with the Go environment instructions.
|
||||
|
||||
|
|
@ -131,9 +141,11 @@ Harbor web UI is built based on [Clarity](https://vmware.github.io/clarity/) and
|
|||
| 1.1 | 2.4.1 | 0.8.7 |
|
||||
| 1.2 | 4.1.3 | 0.9.8 |
|
||||
| 1.3 | 4.3.0 | 0.10.17 |
|
||||
| 1.4 | 4.3.0 | 0.10.17 |
|
||||
| 1.5 | 4.3.0 | 0.10.27 |
|
||||
| 1.6 | 4.3.0 | 0.10.27 |
|
||||
| 1.4 | 4.3.0 | 0.10.17 |
|
||||
| 1.5 | 4.3.0 | 0.10.27 |
|
||||
| 1.6 | 4.3.0 | 0.10.27 |
|
||||
| 1.7 | 6.0.3 | 0.12.10 |
|
||||
| 1.8 | 7.1.3 | 1.0.0 |
|
||||
|
||||
**npm Package Dependency:** Run the following commands to restore the package dependencies.
|
||||
```
|
||||
|
|
@ -155,6 +167,8 @@ PR are always welcome, even if they only contain small fixes like typos or a few
|
|||
|
||||
Please submit a PR broken down into small changes bit by bit. A PR consisting of a lot features and code changes may be hard to review. It is recommended to submit PRs in an incremental fashion.
|
||||
|
||||
Note: If you split your pull request to small changes, please make sure any of the changes goes to master will not break anything. Otherwise, it can not be merged until this feature complete.
|
||||
|
||||
The graphic shown below describes the overall workflow about how to contribute code to Harbor repository.
|
||||
|
||||
|
||||
|
|
@ -316,5 +330,4 @@ Documents are written with Markdown text. See [Writing on GitHub](https://help.g
|
|||
|
||||
## Design new features
|
||||
|
||||
You can propose new designs for existing Harbor features. You can also design
|
||||
entirely new features. Please do open an issue on Github for discussion first. This is necessary to ensure the overall architecture is consistent and to avoid duplicated work in the roadmap.
|
||||
You can propose new designs for existing Harbor features. You can also design entirely new features, Please submit a proposal in GitHub.(https://github.com/goharbor/community/tree/master/proposals). Harbor maintainers will review this proposal as soon as possible. This is necessary to ensure the overall architecture is consistent and to avoid duplicated work in the roadmap.
|
||||
|
|
|
|||
Loading…
Reference in New Issue