-[Before you get started](#before-you-get-started)
-[Code of Conduct](#code-of-conduct)
...
...
@@ -24,7 +24,7 @@ Please make sure to read and observe our [Code of Conduct](http://mpegx.int-evry
## Community Expectations
OpenIMF is a community project driven by its community which strives to promote a healthy, friendly and productive environment.
OpenV3C is a community project driven by its community which strives to promote a healthy, friendly and productive environment.
The goal of the community is to develop a platform for delivery of the immersive media over the network. To build a platform at such scale requires the support of a community with similar aspirations.
- See [Community Membership](./community-membership.md) for a list of various community roles. With gradual contributions, one can move up in the chain.
...
...
@@ -33,14 +33,14 @@ The goal of the community is to develop a platform for delivery of the immersive
# Getting started
- Fork the repository on GitLab
- Read the [developer guide](../setup/develop_OpenIMF.md) for build instructions.
- Read the [developer guide](./README.md) for build instructions.
# Your First Contribution
We will help you to contribute in different areas like filing issues, developing features, fixing critical bugs and getting your work reviewed and merged.
If you have questions about the development process, feel free to jump into our [Slack Channel](https://join.slack.com/t/OpenIMF) or join our [mailing list](https://groups.google.com/forum/#!forum/OpenIMF).
If you have questions about the development process, feel free to jump into our [mailing list](https://groups.google.com/forum/#!forum/OpenIMF).
## Find something to work on
...
...
@@ -50,7 +50,7 @@ Here is how you get started.
### Find a good first topic
There is currently only one [repository](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder) within the OpenIMF organization.
There is currently only one [repository](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder) within the OpenV3C organization.
We can help new contributors who wish to work on such issues.
Another good way to contribute is to find a documentation improvement, such as a missing/broken link. Please see [Contributing](#contributing) below for the workflow.
...
...
@@ -63,9 +63,9 @@ then the robot will assign the issue to you and your name will present at `Assig
### File an Issue
While we encourage everyone to contribute code, it is also appreciated when someone reports an issue.
Issues should be filed under the OpenIMF repository.
Issues should be filed under the OpenV3C repository.
*Example:* a OpenIMF issue should be opened to [OpenIMF](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder/issues).
*Example:* a OpenV3C issue should be opened to [OpenV3C](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder/issues).
Please follow the prompted submission guidelines while opening an issue.
...
...
@@ -79,13 +79,13 @@ This is a rough outline of what a contributor's workflow looks like:
- Make commits of logical units.
- Make sure commit messages are in the proper format (see below).
- Push changes in a topic branch to a personal fork of the repository.
- Submit a pull request to [OpenIMF](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder).
- Submit a pull request to [OpenV3C](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder).
- The PR must receive an approval from two maintainers.
## Creating Pull Requests
Pull requests are often called simply "PR".
OpenIMF generally follows the standard [gitlab pull request](https://docs.gitlab.com/ee/topics/gitlab_flow.html) process.
OpenV3C generally follows the standard [gitlab pull request](https://docs.gitlab.com/ee/topics/gitlab_flow.html) process.
In addition to the above process, a bot will begin applying structured labels to your PR.
...
...
@@ -135,4 +135,4 @@ There are multiple types of tests.
The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test:
* Unit: These confirm that a particular function behaves as intended. Unit test source code can be found adjacent to the corresponding source code within a given package. These are easily run locally by any developer.
* Integration: These tests cover interactions of package components or interactions between OpenIMF components and OpenIMF core.
\ No newline at end of file
* Integration: These tests cover interactions of package components or interactions between OpenV3C components and OpenV3C core.
The project Open Immersive Media Framework is a cross platform reference decoder and reconstruction implementation of the ISO/IEC 23090-5 compression standard: MPEG-I part 5 "Video-based Point Cloud Compression"
The project Open V3C, the Immersive Media Framework is a cross platform reference decoder and reconstruction implementation of the ISO/IEC 23090-5 compression standard: MPEG-I part 5 "Video-based Point Cloud Compression"
| [Member](#member) | Sponsor from 2 approvers, active in community, contributed to OpenIMF | Welcome and guide new contributors | OpenIMF GitLab organization Member |
| [Member](#member) | Sponsor from 2 approvers, active in community, contributed to OpenV3C | Welcome and guide new contributors | OpenV3C GitLab organization Member |
| [Approver](#approver) | Sponsor from 2 maintainers, has good experience and knowledge of domain, actively contributed to code and review | Review and approve contributions from community members | Write access to specific packagies in relevant repository |
| [Maintainer](#maintainer) | Sponsor from 2 owners, shown good technical judgement in feature design/development and PR review | Participate in release planning and feature development/maintenance | Top level write access to relevant repository. Name entry in Maintainers file of the repository |
| [Owner](#owner) | Sponsor from 3 owners, helps drive the overall OpenIMF project | Drive the overall technical roadmap of the project and set priorities of activities in release planning | OpenImf GitLab organization Admin access |
| [Owner](#owner) | Sponsor from 3 owners, helps drive the overall OpenV3C project | Drive the overall technical roadmap of the project and set priorities of activities in release planning | OpenV3C GitLab organization Admin access |
**Note :** It is mandatory for all OpenIMF community members to follow OpenIMF [Code of Conduct].
**Note :** It is mandatory for all OpenV3C community members to follow OpenV3C [Code of Conduct].
## Member
...
...
@@ -28,17 +28,17 @@ reviewing issues/PRs or participate in community discussions on slack/mailing li
- Authoring PRs
- Reviewing issues/PRs authored by other community members
- Participating in community discussions on slack/mailing list
- Participate in OpenIMF community meetings
- Participate in OpenV3C community meetings
### Responsibilities and privileges
- Member of the OpenIMF GitLab organization
- Member of the OpenV3C GitLab organization
- Can be assigned to issues and PRs and community members can also request their review
- Participate in assigned issues and PRs
- Welcome new contributors
- Guide new contributors to relevant docs/files
- Help/Motivate new members in contributing to OpenIMF
- Help/Motivate new members in contributing to OpenV3C
## Approver
...
...
@@ -61,7 +61,7 @@ They have actively participated in the issue/PR reviews and have identified rele
- Acknowledge and work on review requests from community members
- May approve code contributions for acceptance related to relevant expertise
- Have 'write access' to specific packages inside a repo, enforced via bot
- Continue to contribute and guide other community members to contribute in OpenIMF project
- Continue to contribute and guide other community members to contribute in OpenV3C project
## Maintainer
...
...
@@ -80,7 +80,7 @@ Has overall knowledge of the project and features in the project.
- Participate in release planning
- Maintain project code quality
- Ensure API compatibility with forward/backward versions based on feature graduation criteria
- Analyze and propose new features/enhancements in OpenIMF project
- Analyze and propose new features/enhancements in OpenV3C project
- Demonstrate sound technical judgement
- Mentor contributors and approvers
- Have top level write access to relevant repository (able click Merge PR button when manual check-in is necessary)
...
...
@@ -90,7 +90,7 @@ Has overall knowledge of the project and features in the project.
## Owner
Owners are maintainers who have helped drive the overall project direction.
Has deep understanding of OpenIMF and related domain and facilitates major agreement in release planning
Has deep understanding of OpenV3C and related domain and facilitates major agreement in release planning
### Requirements
...
...
@@ -112,8 +112,8 @@ Has deep understanding of OpenIMF and related domain and facilitates major agree
- Participate & Drive design/development of multiple features
**Note :** These roles are applicable only for OpenIMF GitLab organization and repositories. Currently OpenIMF doesn't have a formal process for review and acceptance into these roles. We will come-up with a process soon.
**Note :** These roles are applicable only for OpenV3C GitLab organization and repositories. Currently OpenV3C doesn't have a formal process for review and acceptance into these roles. We will come-up with a process soon.
[Code of Conduct]:https://GitLab.com/OpenIMF/CODE_OF_CONDUCT.md
-[Before you get started](#before-you-get-started)
-[Code of Conduct](#code-of-conduct)
...
...
@@ -24,7 +24,7 @@ Please make sure to read and observe our [Code of Conduct](http://mpegx.int-evry
## Community Expectations
OpenIMF is a community project driven by its community which strives to promote a healthy, friendly and productive environment.
OpenV3C is a community project driven by its community which strives to promote a healthy, friendly and productive environment.
The goal of the community is to develop a platform for delivery of the immersive media over the network. To build a platform at such scale requires the support of a community with similar aspirations.
- See [Community Membership](./community_membership.md) for a list of various community roles. With gradual contributions, one can move up in the chain.
...
...
@@ -33,14 +33,14 @@ The goal of the community is to develop a platform for delivery of the immersive
# Getting started
- Fork the repository on GitLab
- Read the [developer guide](../setup/develop_OpenIMF.md) for build instructions.
- Read the [developer guide](../setup/develop_OpenV3C.md) for build instructions.
# Your First Contribution
We will help you to contribute in different areas like filing issues, developing features, fixing critical bugs and getting your work reviewed and merged.
If you have questions about the development process, feel free to jump into our [Slack Channel](https://join.slack.com/t/OpenIMF) or join our [mailing list](https://groups.google.com/forum/#!forum/OpenIMF).
If you have questions about the development process, feel free to jump into our [Slack Channel](https://join.slack.com/t/OpenV3C) or join our [mailing list](https://groups.google.com/forum/#!forum/OpenV3C).
## Find something to work on
...
...
@@ -50,7 +50,7 @@ Here is how you get started.
### Find a good first topic
There is currently only one [repository](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder) within the OpenIMF organization.
There is currently only one [repository](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder) within the OpenV3C organization.
We can help new contributors who wish to work on such issues.
Another good way to contribute is to find a documentation improvement, such as a missing/broken link. Please see [Contributing](#contributing) below for the workflow.
...
...
@@ -63,9 +63,9 @@ then the robot will assign the issue to you and your name will present at `Assig
### File an Issue
While we encourage everyone to contribute code, it is also appreciated when someone reports an issue.
Issues should be filed under the OpenIMF repository.
Issues should be filed under the OpenV3C repository.
*Example:* a OpenIMF issue should be opened to [OpenIMF](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder/issues).
*Example:* a OpenV3C issue should be opened to [OpenV3C](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder/issues).
Please follow the prompted submission guidelines while opening an issue.
...
...
@@ -79,13 +79,13 @@ This is a rough outline of what a contributor's workflow looks like:
- Make commits of logical units.
- Make sure commit messages are in the proper format (see below).
- Push changes in a topic branch to a personal fork of the repository.
- Submit a pull request to [OpenIMF](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder).
- Submit a pull request to [OpenV3C](http://mpegx.int-evry.fr/software/MPEG-Public/PCC/V-PCC_decoder).
- The PR must receive an approval from two maintainers.
## Creating Pull Requests
Pull requests are often called simply "PR".
OpenIMF generally follows the standard [gitlab pull request](https://docs.gitlab.com/ee/topics/gitlab_flow.html) process.
OpenV3C generally follows the standard [gitlab pull request](https://docs.gitlab.com/ee/topics/gitlab_flow.html) process.
In addition to the above process, a bot will begin applying structured labels to your PR.
...
...
@@ -135,4 +135,4 @@ There are multiple types of tests.
The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test:
* Unit: These confirm that a particular function behaves as intended. Unit test source code can be found adjacent to the corresponding source code within a given package. These are easily run locally by any developer.
* Integration: These tests cover interactions of package components or interactions between OpenIMF components and OpenIMF core.
\ No newline at end of file
* Integration: These tests cover interactions of package components or interactions between OpenV3C components and OpenV3C core.
If any part of the OpenIMF project has bugs or documentation mistakes, please let us know by opening an issue. We treat bugs and mistakes very seriously and believe no issue is too small. Before creating a bug report, please check that an issue reporting the same problem does not already exist.
If any part of the OpenV3C project has bugs or documentation mistakes, please let us know by opening an issue. We treat bugs and mistakes very seriously and believe no issue is too small. Before creating a bug report, please check that an issue reporting the same problem does not already exist.
To make the bug report accurate and easy to understand, please try to create bug reports that are:
@@ -4,10 +4,6 @@ If you need support, start with the [troubleshooting guide](../troubleshooting/t
## Community
**Slack channel:**
We use Slack for public discussions. To chat with us or the rest of the community, join us in the [OpenIMF Slack](https://openimf.slack.com) team channel #general. To sign up, use our Slack inviter link [here](https://join.slack.com/t/openimf/shared_invite/TBU).
**Mailing List**
Please sign up on our [mailing list](https://groups.google.com/forum/#!forum/openimf)