Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A2CC8200BCF for ; Mon, 5 Dec 2016 19:39:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A166D160B18; Mon, 5 Dec 2016 18:39:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 72979160B09 for ; Mon, 5 Dec 2016 19:39:06 +0100 (CET) Received: (qmail 51338 invoked by uid 500); 5 Dec 2016 18:39:05 -0000 Mailing-List: contact commits-help@metron.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@metron.incubator.apache.org Delivered-To: mailing list commits@metron.incubator.apache.org Received: (qmail 51329 invoked by uid 99); 5 Dec 2016 18:39:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2016 18:39:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2932F1AB0F7 for ; Mon, 5 Dec 2016 18:39:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.019 X-Spam-Level: X-Spam-Status: No, score=-5.019 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, KAM_LINEPADDING=1.2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id pmK77mWpi8ul for ; Mon, 5 Dec 2016 18:38:55 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id F3DFE5F19D for ; Mon, 5 Dec 2016 18:38:52 +0000 (UTC) Received: (qmail 50651 invoked by uid 99); 5 Dec 2016 18:38:52 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2016 18:38:52 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 14AEBE076F; Mon, 5 Dec 2016 18:38:52 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: cestella@apache.org To: commits@metron.incubator.apache.org Message-Id: <7111a9dc5e5e4b428a3d8fcf9f1f1506@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: incubator-metron git commit: METRON-591: Make the website in compliance with ASF standards Date: Mon, 5 Dec 2016 18:38:52 +0000 (UTC) archived-at: Mon, 05 Dec 2016 18:39:08 -0000 Repository: incubator-metron Updated Branches: refs/heads/asf-site 4bb606ec6 -> 5106e8df8 METRON-591: Make the website in compliance with ASF standards Project: http://git-wip-us.apache.org/repos/asf/incubator-metron/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-metron/commit/5106e8df Tree: http://git-wip-us.apache.org/repos/asf/incubator-metron/tree/5106e8df Diff: http://git-wip-us.apache.org/repos/asf/incubator-metron/diff/5106e8df Branch: refs/heads/asf-site Commit: 5106e8df814475b539eb5c014d5466814153f57f Parents: 4bb606e Author: cstella Authored: Mon Dec 5 13:38:34 2016 -0500 Committer: cstella Committed: Mon Dec 5 13:38:34 2016 -0500 ---------------------------------------------------------------------- about/index.html | 4 +- community/index.html | 8 +- develop/bylaws.html | 514 +++++++++++++++++++++++++ develop/coding.html | 249 ++++++++++++ develop/index.html | 8 +- docs/hive-ddl.html | 142 +++---- docs/index.html | 142 +++---- docs/sensor.html | 144 +++---- documentation/index.html | 4 +- feed.xml | 10 +- help/index.html | 6 +- index.html | 8 +- news/2015/12/12/new-logo/index.html | 40 +- news/2016/01/08/debo-committer/index.html | 2 +- news/index.html | 2 +- 15 files changed, 1030 insertions(+), 253 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-metron/blob/5106e8df/about/index.html ---------------------------------------------------------------------- diff --git a/about/index.html b/about/index.html index 6c3f097..34f37ee 100644 --- a/about/index.html +++ b/about/index.html @@ -4,7 +4,7 @@ - Apache Metron About + Apache Metron (Incubating) About + + + + Apache Metron (Incubating) Bylaws + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+ + +
+
+ +
+
+

Apache Metron (Incubating) Bylaws

+

Introduction

+ +

This document defines the bylaws under which the Apache Metron (Incubating) project +operates. It defines the roles and responsibilities of the project, +who may vote, how voting works, how conflicts are resolved, etc.

+ +

Metron is a project of the Apache Software Foundation (ASF) and the foundation +holds the trademark on the name “Metron” and copyright on the combined +code base. The Apache Foundation +FAQ and +How-It-Works +explain the operation and background of the foundation.

+ +

Apache has a code of +conduct that +it expects its members to follow. In particular:

+ +
    +
  • +

    Be open and welcoming. It is important that we grow and +encourage the community of users and developers for our project.

    +
    • +
  • +

    Be collaborative. Working together on the open mailing lists and +bug database to make decisions helps the project grow.

    +
    • +
  • +

    Be respectful of others. Everyone is volunteering their time and +efforts to work on this project. Please be respectful of everyone +and their views.

    +
    • +
+ +

Metron is typical of Apache projects in that it operates under a set of +principles, known collectively as the “Apache Way”. If you are new to +Apache development, please refer to the Incubator +project for more +information on how Apache projects operate.

+ +

Roles and Responsibilities

+ +

Apache projects define a set of roles with associated rights and +responsibilities. These roles govern what tasks an individual may +perform within the project. The roles are defined in the following +sections.

+ +

Users

+ +

The most important participants in the project are people who use our +software. The majority of our developers start out as users and guide +their development efforts from the user’s perspective. Users +contribute to the Apache projects by providing feedback to developers +in the form of bug reports and feature suggestions. As well, users +participate in the Apache community by helping other users on mailing +lists and user support forums.

+ +

Contributors

+ +

Contributors include all of the volunteers who donate time, code, +documentation, +or resources to the Metron Project. A contributor that makes sustained, +welcome contributions to the project may be invited to become a +committer, though the exact timing of such invitations depends on many +factors.

+ +

Committers

+ +

The project’s committers are responsible for the project’s technical +management. Committers have the right to commit to the project’s git +repository. Committers may cast binding votes on any technical +discussion.

+ +

Committer access is by invitation only and must be approved by +consensus approval of the active Project Management Committee (PMC) +members.

+ +

If a committer wishes to leave the project or does not contribute to +the project in any form for six months, the PMC may make them emeritus. +Emeritus committers lose their ability to commit code or cast binding +votes. An emeritus committer may +request reinstatement of commit access from the PMC. Such +reinstatement is subject to consensus approval of active PMC members.

+ +

All Apache committers are required to have a signed Individual +Contributor License +Agreement (ICLA) on file +with the Apache Software Foundation. There is a Committer +FAQ which provides more +details on the requirements for Committers.

+ +

A committer who makes a +sustained contribution to the project may be invited to become a +member of the PMC. The form of contribution +is not limited to code. It can also include code review, helping out +users on the mailing lists, documentation, testing, etc.

+ +

Release Manager

+ +

A Release Manager (RM) is a committer who volunteers to produce a +Release Candidate. The RM shall publish a Release Plan on the +dev mailing list stating the branch from which they intend to +make a Release Candidate.

+ +

Project Management Committee

+ +

The Project Management Committee (PMC) for Apache Metron was created by +the Apache Board in December 2015 when Metron moved out of Cisco’s OpenSOC
+project and became an incubated project at Apache. +The PMC is responsible to the board and +the ASF for the management and oversight of the Apache Metron +codebase. The responsibilities of the PMC include

+ +
    +
  • +

    Deciding what is distributed as products of the Apache Metron +project. In particular all releases must be approved by the PMC.

    +
    • +
  • +

    Maintaining the project’s shared resources, including the codebase +repository, mailing lists, and websites.

    +
    • +
  • +

    Speaking on behalf of the project.

    +
    • +
  • +

    Resolving license disputes regarding products of the project

    +
    • +
  • +

    Nominating new PMC members and committers

    +
    • +
  • +

    Maintaining these bylaws and other guidelines of the project

    +
    • +
+ +

Membership of the PMC is by invitation only and must be approved by a +consensus approval of active PMC members.

+ +

A PMC member is considered +emeritus by their own declaration or by not contributing in any form +to the project for over six months. An emeritus member may request +reinstatement to the PMC. Such reinstatement is subject to consensus +approval of the active PMC members.

+ +

The chair of the PMC is appointed by the ASF board. The chair is an +office holder of the Apache Software Foundation (Vice President, +Apache Metron) and has primary responsibility to the board for the +management of the project within the scope of the Metron PMC. The +chair reports to the board quarterly on developments within the Metron +project.

+ +

When the project desires a new PMC chair, the PMC votes to recommend a +new chair using Single Transferable +Vote voting. The decision +must be ratified by the Apache board.

+ +

Decision Making

+ +

Within the Metron project, different types of decisions require +different forms of approval. For example, the previous section +describes several decisions which require “consensus approval.” +This section defines how voting is performed, the types of +approvals, and which types of decision require which type of approval.

+ +

Voting

+ +

Decisions regarding the project are made by votes on the primary +project development mailing list (dev@Metron.apache.org). Where +necessary, PMC voting may take place on the private Metron PMC mailing +list. Votes are clearly indicated by subject line starting with +[VOTE]. Votes may contain multiple items for approval and these should +be clearly separated. Voting is carried out by replying to the vote +mail. Voting may take five flavors:

+ +
    +
  • +

    +1 – “Yes,” “Agree,” or “the action should be performed.” In general, +this vote also indicates a willingness on the behalf of the voter in +“making it happen.”

    +
    • +
  • +

    +0 – This vote indicates a willingness for the action under +consideration to go ahead. The voter, however, will not be able to +help.

    +
    • +
  • +

    0 – The voter is neutral on the topic under discussion.

    +
    • +
  • +

    -0 – This vote indicates that the voter does not, in general, agree + with the proposed action but is not concerned enough to prevent the + action going ahead.

    +
    • +
  • +

    -1 – This is a negative vote. On issues where consensus is required, + this vote counts as a veto. All vetoes must contain an explanation + of why the veto is appropriate. Vetoes with no explanation are + void. It may also be appropriate for a -1 vote to include an + alternative course of action.

    +
    • +
+ +

All participants in the Metron project are encouraged to show their +agreement for or against a particular action by voting, regardless of +whether their vote is binding. Nonbinding votes are useful for +encouraging discussion and understanding the scope of opinions within +the project.

+ +

Approvals

+ +

These are the types of approvals that can be sought. Different actions +require different types of approvals.

+ +
    +
  • +

    Consensus Approval – Consensus approval requires 3 binding +1 +votes and no binding vetoes.

    +
    • +
  • +

    Lazy Consensus – Lazy consensus requires at least one +1 vote and +no -1 votes (‘silence gives assent’).

    +
    • +
  • +

    Lazy Majority – A lazy majority vote requires 3 binding +1 votes + and more binding +1 votes than -1 votes.

    +
    • +
  • +

    Lazy 2/3 Majority – Lazy 2/3 majority votes requires at least 3 +votes and twice as many +1 votes as -1 votes.

    +
    • +
+ +

Vetoes

+ +

A valid, binding veto cannot be overruled. If a veto is cast, it must +be accompanied by a valid reason explaining the reasons for the +veto. The validity of a veto, if challenged, can be confirmed by +anyone who has a binding vote. This does not necessarily signify +agreement with the veto - merely that the veto is valid. If you +disagree with a valid veto, you must lobby the person casting the veto +to withdraw their veto. If a veto is not withdrawn, any action that +has already been taken must be reversed in a timely manner.

+ +

Actions

+ +

This section describes the various actions which are undertaken within +the project, the corresponding approval required for that action and +those who have binding votes over the action.

+ +

Code Change

+ +

A change made to a codebase of the project requires lazy consensus +of active committers other than the author of the patch. The code can +be committed after the first +1.

+ +

Product Release

+ +

To make a release, the release manager creates a release candidate and +a vote requiring a lazy majority of the active PMC members is +required. Once the vote passes, the release candidate becomes an +official release.

+ +

Adoption of New Codebase

+ +

When the codebase for an existing, released product is to be replaced +with an alternative codebase, it requires a lazy 2/3 majority of PMC +members. This also covers the creation of new sub-projects and +submodules within the project.

+ +

New Committer

+ +

When a new committer is proposed for the project, consensus approval +of the active PMC members is required.

+ +

New PMC Member

+ +

To promote a committer to a PMC member requires consensus approval +of active PMC members.

+ +

If the vote passes, the Apache Board must be notified to make the change +official.

+ +

Committer Removal

+ +

Removal of commit privileges requires a lazy 2/3 majority of active +PMC members.

+ +

PMC Member Removal

+ +

Removing a PMC member requires a lazy 2/3 majority of active PMC +members, excluding the member in question.

+ +

If the vote passes, the Apache Board must be notified to make the change +official.

+ +

Modifying Bylaws

+ +

Modifying this document requires a lazy majority of active PMC members.

+ +

Voting Timeframes

+ +

Votes are open for a minimum period of 72 hours to allow all active +voters time to consider the vote. For holiday weekends or conferences, +consider using a longer vote window. Votes relating to code changes are +not subject to a strict timetable but should be made as timely as +possible.

+ +
+
+ +
+ +
+
+ + + +
+
+ Apache +
+
+
+ Disclaimer: Apache Metron is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Hortonworks. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. +
+ The contents of this website are © 2016 Apache Software Foundation under the terms of the Apache License v2. Apache Metron and its logo are trademarks of the Apache Software Foundation. +
+
+ + + + + + http://git-wip-us.apache.org/repos/asf/incubator-metron/blob/5106e8df/develop/coding.html ---------------------------------------------------------------------- diff --git a/develop/coding.html b/develop/coding.html new file mode 100644 index 0000000..d2441d3 --- /dev/null +++ b/develop/coding.html @@ -0,0 +1,249 @@ + + + + + + + Coding Guidelines + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+ + +
+
+ +
+
+

Coding Guidelines

+

General rules

+ +
    +
  • All files must have an Apache copyright header at the top of the file.
    • +
  • Code should be removed rather than commented out.
    • +
  • All public functions should have javadoc comments.
    • +
  • Always use braces to surround branches.
    • +
  • try-finally should be avoided.
    • +
+ +

Formatting

+ +
    +
  • All files must have an 80 character maximum line length.
    • +
  • Indentation should be 2 spaces.
    • +
  • Files should use spaces instead of tabs.
    • +
  • Wrapping lines +
      +
    • Break after a comma.
      • +
    • Break before an operator.
      • +
    • Prefer higher-level breaks to lower-level breaks.
      • +
    • Align the new line with beginning of the expression at the same level +on the previous line.
      • +
    • If the above rules lead to confusing code, just indent 8 spaces.
      • +
    +
    • +
  • One variable declaration per a line.
    • +
+ +

Naming

+ +
    +
  • Packages should be all lowercase. +
      +
    • Java code should be in org.apache.,metron, except for compatibility classes
      • +
    +
    • +
  • Classes should be in mixed case.
    • +
  • Variables should be in camel case.
    • +
  • Constants should be in upper case.
    • +
+ +
+
+ +
+ +
+
+ + + +
+
+ Apache +
+
+
+ Disclaimer: Apache Metron is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Hortonworks. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. +
+ The contents of this website are © 2016 Apache Software Foundation under the terms of the Apache License v2. Apache Metron and its logo are trademarks of the Apache Software Foundation. +
+
+ + + + + + http://git-wip-us.apache.org/repos/asf/incubator-metron/blob/5106e8df/develop/index.html ---------------------------------------------------------------------- diff --git a/develop/index.html b/develop/index.html index 6628065..58fd7de 100644 --- a/develop/index.html +++ b/develop/index.html @@ -234,11 +234,11 @@ developers working on the project. The project has created

There are several development mailing lists for Metron

@@ -250,7 +250,7 @@ with archive % git clone https://git-wip-us.apache.org/repos/asf/incubator-metron.git

+

% git clone https://git-wip-us.apache.org/repos/asf/incubator-metron.git

The important branches are:

http://git-wip-us.apache.org/repos/asf/incubator-metron/blob/5106e8df/docs/hive-ddl.html ---------------------------------------------------------------------- diff --git a/docs/hive-ddl.html b/docs/hive-ddl.html index e62b19f..fcfa13e 100644 --- a/docs/hive-ddl.html +++ b/docs/hive-ddl.html @@ -1,7 +1,7 @@ - + Arch @@ -60,12 +60,12 @@ - + - + - + Background @@ -60,12 +60,12 @@ - + - + - + Sensor Ecosystem @@ -60,12 +60,12 @@ - + - + - + Metron adopts new logo @@ -60,12 +60,12 @@ - + - +