You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2021. It is now read-only.
Copy file name to clipboardexpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Apache Apex Incubator Website
1
+
Apache Apex Website
2
2
=============================
3
3
4
4
This is the source code for the Apache Apex website, hosted at [apex.apache.org](http://apex.apache.org/). The following tools are used to build the html pages:
@@ -59,7 +59,7 @@ Contributing
59
59
------------
60
60
If you would like to make a change to the site:
61
61
62
-
1. Fork the [github mirror](https://github.com/apache/incubator-apex-site)
62
+
1. Fork the [github mirror](https://github.com/apache/apex-site)
63
63
2. Create a new branch from `master`
64
64
3. Add commit(s) to your branch
65
65
4. Test your changes locally (see Development section below)
@@ -69,7 +69,7 @@ If you would like to make a change to the site:
69
69
If you are a committer, do the following:
70
70
71
71
1. Update the master branch with your (or a Pull Request's) change.
72
-
2. Push updated master to the asf remote master (https://git-wip-us.apache.org/repos/asf/incubator-apex-site.git)
72
+
2. Push updated master to the asf remote master (https://git-wip-us.apache.org/repos/asf/apex-site.git)
73
73
2. Run `build.sh` from the master branch directory (requires nodejs and npm). This will:
74
74
- ensure the necessary npm and bower dependencies are installed
75
75
- checks out and updates the `asf-site` branch with a new commit of the build from the current branch
Copy file name to clipboardexpand all lines: src/md/community.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,8 @@ The following mailing lists are available for Apex.
20
20
21
21
The Apex Project is made up of two repositories:
22
22
23
-
-[Apex Core](https://github.com/apache/incubator-apex-core) - The core of the Apex platform.
24
-
-[Apex Malhar](https://github.com/apache/incubator-apex-malhar) - Community-driven set of open-source "operators" and utilities for use in your Apex applications.
23
+
-[Apex Core](https://github.com/apache/apex-core) - The core of the Apex platform.
24
+
-[Apex Malhar](https://github.com/apache/apex-malhar) - Community-driven set of open-source "operators" and utilities for use in your Apex applications.
Copy file name to clipboardexpand all lines: src/md/contributing.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -16,36 +16,36 @@ People that help with the project in any of the above categories or other ways a
16
16
17
17
## Becoming a committer
18
18
19
-
Community members that make sustained, welcome contributions to the project may be invited to become a committer. Committers are voted in by the PPMC. A committer has a signed Contributor License Agreement ([CLA](http://www.apache.org/licenses/icla.txt)) on file and an apache.org address.
19
+
Community members that make sustained, welcome contributions to the project may be invited to become a committer. Committers are voted in by the PMC. A committer has a signed Contributor License Agreement ([CLA](http://www.apache.org/licenses/icla.txt)) on file and an apache.org address.
20
20
21
21
We expect committers to subscribe to the [project mailing lists](community.html#mailing-lists).
22
22
23
-
A committer will be considered “emeritus/inactive” by not contributing in any form to the project for over 1 year. An emeritus committer may request reinstatement of commit access from the PPMC. Such reinstatement is subject to lazy consensus of active PPMC members.
23
+
A committer will be considered “emeritus/inactive” by not contributing in any form to the project for over 1 year. An emeritus committer may request reinstatement of commit access from the PMC. Such reinstatement is subject to lazy consensus of active PMC members.
24
24
25
-
The Podling Project Management Committee ([PPMC](http://incubator.apache.org/guides/ppmc.html)) is responsible for the oversight of the project and it also decides who to add as a PPMC member. Existing committers may be invited to become a PPMC member after consistent contribution and activity over a period of time and participation in directional and community building discussions.
25
+
The Project Management Committee ([PMC](http://www.apache.org/dev/pmc.html)) is responsible for the oversight of the project and it also decides who to add as a PMC member. Existing committers may be invited to become a PMC member after consistent contribution and activity over a period of time and participation in directional and community building discussions.
26
26
27
27
## Code Style
28
28
Apache Apex follows coding style that is closest to K & R style and uses [Checkstyle](http://checkstyle.sourceforge.net/) tool to enforce these standards. Travis CI will fail for any pull request that introduces any style violations.
29
29
30
-
The checkstyle configuration that Apache Apex projects use is present here : https://github.com/apache/incubator-apex-core/blob/master/apex_checks.xml
30
+
The checkstyle configuration that Apache Apex projects use is present here : https://github.com/apache/apex-core/blob/master/apex_checks.xml
31
31
32
32
To make it easier for the users to set up their development environment, settings for the following common IDEs are provided in the Apache Apex Core repository with instructions.
The apex-core and apex-malhar repositories both have mirror repositories on github which are used to review pull requests and provide a second remote endpoint for the codebase.
40
40
41
41
1. Create a JIRA ([-core](https://issues.apache.org/jira/browse/APEXCORE/),[-malhar](https://issues.apache.org/jira/browse/APEXMALHAR/)) for the work you plan to do (or assign yourself to an existing JIRA ticket)
42
42
1. Fork the ASF github mirror (one time step):
43
-
https://github.com/apache/incubator-apex-core/
43
+
https://github.com/apache/apex-core/
44
44
1. Clone the **fork** on your local workspace (one time step):
1. Create a new branch from the [master](https://github.com/apache/incubator-apex-core/tree/master) branch. **Name your branch with the JIRA number in it, e.g. `APEXCORE-123.my-feature`.**
1. Create a new branch from the [master](https://github.com/apache/apex-core/tree/master) branch. **Name your branch with the JIRA number in it, e.g. `APEXCORE-123.my-feature`.**
Creating a local branch that tracks a remote makes pull easier (no need to specify the remote branch while pulling). A branch can be made to track a remote branch anytime, not necessarily at its creation by:
51
51
`git branch -u upstream/master`
@@ -113,8 +113,8 @@ Thanks for contributing!
113
113
- Travis CI pull request build needs to pass
114
114
- Ensure tests are added/modified for new features or fixes
115
115
- Ensure appropriate JavaDoc comments have been added
116
-
1. To set up access to the ASF source repository, [follow these steps](https://git-wip-us.apache.org/#committers-getting-started). The ASF master repository is: `https://git-wip-us.apache.org/repos/asf/incubator-apex-core.git`
117
-
1. Use the git command line to pull in the changes from the pull requests. You can refer to the corresponding email that will be automatically sent to the `dev@apex.incubator.apache.org` mailing list to see the exact commands to merge the given pull request.
116
+
1. To set up access to the ASF source repository, [follow these steps](https://git-wip-us.apache.org/#committers-getting-started). The ASF master repository is: `https://git-wip-us.apache.org/repos/asf/apex-core.git`
117
+
1. Use the git command line to pull in the changes from the pull requests. You can refer to the corresponding email that will be automatically sent to the `[email protected]` mailing list to see the exact commands to merge the given pull request.
118
118
1. Once done with verification, push the changes to the ASF repository's `master` branch. Within a few
119
119
seconds, the changes will propagate back to the github mirror and the pull requests be closed and marked merged automatically.
120
120
1. The `Fix version` field on the corresponding JIRA ticket needs to be set and the ticket resolved after pushing the changes.
Copy file name to clipboardexpand all lines: src/md/docs.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ word counting application with Apache Apex starting with setting up your develop
14
14
- <ahref="http://docs.datatorrent.com/tutorials/salesdimensions/"rel="nofollow">Sales Dimensions Application Tutorial</a> Similar to the Top N Words application but covers
15
15
dimensional computations on a simulated sales data stream.
16
16
- <ahref="https://github.com/DataTorrent/examples"rel="nofollow">Example Applications</a> Sample code for specialized tutorials covering a variety of topics such as large key-value state management (HDHT), custom partitioning using stream codecs, etc.
17
-
-[Malhar Demos](https://github.com/apache/incubator-apex-malhar/tree/master/demos) This is part of the source repository for Apache Apex Malhar and contains a number of more substantial sample applications that developers will find especially useful. They include an application that computes some statistics (such as moving averages) from a live stream of stock transactions from *Yahoo! Finance*; one that analyzes a synthetic stream of eruption event data for the *Old Faithful* geyser; a Twitter stream analyzer; and a simulated fraud detector.
17
+
-[Malhar Demos](https://github.com/apache/apex-malhar/tree/master/demos) This is part of the source repository for Apache Apex Malhar and contains a number of more substantial sample applications that developers will find especially useful. They include an application that computes some statistics (such as moving averages) from a live stream of stock transactions from *Yahoo! Finance*; one that analyzes a synthetic stream of eruption event data for the *Old Faithful* geyser; a Twitter stream analyzer; and a simulated fraud detector.
Copy file name to clipboardexpand all lines: src/md/people.md
+13-13
Original file line number
Diff line number
Diff line change
@@ -4,17 +4,17 @@ The community is comprised of the PMC, Committers and Contributors. The PMC (pod
4
4
5
5
## Becoming a committer
6
6
7
-
Community members that make sustained, welcome contributions to the project may be invited to become a committer. Committers are voted in by the PPMC. A committer has a signed Contributor License Agreement (CLA) on file and an apache.org address.
7
+
Community members that make sustained, welcome contributions to the project may be invited to become a committer. Committers are voted in by the PMC. A committer has a signed Contributor License Agreement (CLA) on file and an apache.org address.
8
8
9
9
We expect committers to subscribe to the project mailing lists.
10
10
11
-
A committer will be considered “emeritus/inactive” by not contributing in any form to the project for over 1 year. An emeritus committer may request reinstatement of commit access from the PPMC. Such reinstatement is subject to lazy consensus of active PPMC members.
11
+
A committer will be considered “emeritus/inactive” by not contributing in any form to the project for over 1 year. An emeritus committer may request reinstatement of commit access from the PMC. Such reinstatement is subject to lazy consensus of active PMC members.
12
12
13
-
The Podling Project Management Committee (PPMC) is responsible for the oversight of the project and it also decides who to add as a PPMC member. Existing committers may be invited to become a PPMC member after consistent contribution and activity over a period of time and participation in directional and community building discussions.
13
+
The Project Management Committee (PMC) is responsible for the oversight of the project and it also decides who to add as a PMC member. Existing committers may be invited to become a PMC member after consistent contribution and activity over a period of time and participation in directional and community building discussions.
14
14
15
15
## Committers
16
16
17
-
Following is the list of all Apache Apex committers, PPMC members and mentors. A good place to see all contributors and other project stats is [Open Hub](https://www.openhub.net/p/apache_apex)
17
+
Following is the list of all Apache Apex committers, PMC members and mentors. A good place to see all contributors and other project stats is [Open Hub](https://www.openhub.net/p/apache_apex)
18
18
19
19
| Name | Apache ID | Role |
20
20
| --- | --- | --- |
@@ -28,36 +28,36 @@ Following is the list of all Apache Apex committers, PPMC members and mentors. A
0 commit comments