Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2018-08-17 02:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Traffic Control

15 Aug 2018 [David Neuman / Rich]

Report was filed, but display is awaiting the approval of the Board minutes.

18 Jul 2018 [David Neuman / Brett]

## Description:
 - Apache Traffic Control can be used to build, monitor, configure, and
   provision a large-scale content delivery network (CDN).

## Issues:
- How can we fix our committee health score?
  [https://reporter.apache.org/chi.py#trafficcontrol]
- No other issues requiring board attention at this time

## Activity:

- Announced the 2.2 release of Traffic Control
- Started working on finalizing scope and a Release Manager for 3.0
- There has been some discussion around PMC vs Committer and how to best allow
  our committers to perform releases without being PMC. As a new TLP this is
  something that we need to work out.

## Health report:
 - The project is healthy.

## PMC changes:

 - Currently 13 PMC members.
 - No new PMC members added in the last 3 months

## Committer base changes:

 - Currently 18 committers.
 - No changes (the PMC was established in the last 3 months)

## Releases:

 - apache-trafficcontrol-2.2.0 was released on Mon Jun 25 2018

## Mailing list activity:

 - Overall mailing list activity seems to be pretty consistent over the last
   month.  We tend to use dev@ more heavily than other lists, maybe we should
   consider using users@ a little more.

 - users@trafficcontrol.apache.org:
    - 95 subscribers (up 7 in the last 3 months)
    - only 1 email sent over the last month (compared to 7 in the current
      month prior)
    - most of our communication happens on dev@, perhaps we can get better at
      using the users list.

 - dev@trafficcontrol.apache.org:
    - 93 subscribers (up 4 in the last 3 months)
    - 77 emails sent to the list (up about 5% from the last month)

 - issues@trafficcontrol.apache.org:
    - 29 subscribers (up 0 in the last 3 months)
    - > 1000 emails over the last month (actually a 1% decrease)
    - This list is primarily automated emails from github so statistics are
      not too interesting

 - summits@trafficcontrol.apache.org:
    - 6 subscribers (up 0 in the last 3 months)
    - this list is meant for users to submit CFPs for summits, therefore it is
      hardly used.


## GitHub activity:
 - 93 Pull requests submitted in the last 30 days
 - 85 Pull Requests merged in the last 30 days
 - 27 issues created in the last 30 days
 - 23 issues closed in the last 30 days
 - 205 stars on the Traffic Control repo

## Commit activity:
 - >8,500 lines of code changed
 - 235 commits in the last 30 days
 - 16 authors in the last 30 days

20 Jun 2018 [David Neuman / Mark]

## Description:
 - Apache Traffic Control can be used to build, monitor, configure, and
   provision a large-scale content delivery network (CDN).

## Issues:
 - Waiting on Infra to complete Graduation ticket:
   https://issues.apache.org/jira/browse/INFRA-16631
 - We have a release ready to be announced but PMC members can't upload
   binaries to dist.apache.org until the infra ticket is complete and we get
   the proper permissions.

## Activity:
 - Worked on a press release announcing our graduation.
 - Worked on figuring out what the next steps are for becoming a TLP
 - Opened INFRA ticket to take care of incubator -> TLP migration
 - Called the vote on the Traffic Control 2.2 release (waiting for Infra
   ticket before announcing - see issues above)
 - Agreed on versioning for next release, currently working on naming a
   release manager and defining scope.

## Health report:
 - Just became a TLP
 - The entire community is very excited to graduate from the Incubator and
   become a TLP
 - The project is healthy.

## PMC changes:

 - Currently 13 PMC members.
 - No new PMC members added in the last 3 months

## Committer base changes:

 - Currently 18 committers.
 - No changes (the PMC was established in the last 3 months)

## Releases:

 - Traffic Control 2.1 was released on 1/22/2018
 - The vote for Traffic Control 2.2 was called as passed on 6/7/2018
 - Traffic Control 3.0 is currently being defined.

16 May 2018

Establish the Apache Traffic Control Project

 WHEREAS, the Board of Directors deems it to be in the best interests
 of the Foundation and consistent with the Foundation's purpose to
 establish a Project Management Committee charged with the creation and
 maintenance of open-source software, for distribution at no charge to
 the public, related to building, monitoring, configuring, and
 provisioning a large scale content delivery network (CDN).

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
 (PMC), to be known as the "Apache Traffic Control Project", be and
  hereby is established pursuant to Bylaws of the Foundation; and be it
  further

 RESOLVED, that the Apache Traffic Control Project be and hereby is
 responsible for the creation and maintenance of software related to
 building, monitoring, configuring, and provisioning a large scale
 content delivery network (CDN); and be it further

 RESOLVED, that the office of "Vice President, Apache Traffic Control"
 be and hereby is created, the person holding such office to serve at
 the direction of the Board of Directors as the chair of the Apache
 Traffic Control Project, and to have primary responsibility for
 management of the projects within the scope of responsibility of the
 Apache Traffic Control Project; and be it further

 RESOLVED, that the persons listed immediately below be and hereby are
 appointed to serve as the initial members of the Apache Traffic
 Control Project:

 * Dan Kirkwood       <dangogh@apache.org>
 * David Neuman       <neuman@apache.org>
 * Dewayne Richardson <dewrich@apache.org>
 * Eric Covener       <covener@apache.org>
 * Eric Friedrich     <friede@apache.org>
 * Hank Beatty        <hbeatty@apache.org>
 * Jan van Doorn      <jvd@apache.org>
 * Jeff Elsloo        <elsloo@apache.org>
 * Jeremy Mitchell    <mitchell852@apache.org>
 * Leif Hedstrom      <zwoop@apache.org>
 * Mark Torluemke     <mtorluemke@apache.org>
 * Phil Sorber        <sorber@apache.org>
 * Steve Malenfant    <smalenfant@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
 to the office of Vice President, Apache Traffic Control, to serve in
 accordance with and subject to the direction of the Board of Directors
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed; and be
 it further

 RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
 tasked with the creation of a set of bylaws intended to encourage open
 development and increased participation in the Apache Traffic Control
 Project; and be it further

 RESOLVED, that the Apache Traffic Control Project be and hereby is
 tasked with the migration and rationalization of the Apache Incubator
 Traffic Control podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache Incubator
 Traffic Control podling encumbered upon the Apache Incubator PMC are
 hereafter discharged.

 Special Order 7D, Establish the Apache Traffic Control
 Project, was approved by Unanimous Vote of the directors
 present.

18 Oct 2017

Traffic Control is a set of components that can be used to build, monitor, configure, and provision a large scale content delivery network (CDN).

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

1. Enhance automation to make it easier to build, install, and configure each component.
2. Improve documentation to ease ramp-up time for new community members and make it easier for existing community members to find what they are looking for.
3. Grow the community.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None.

How has the community developed since the last report?

The community took a vote and decided to move to full GitHub for source code management and to use github for issue tracking instead of Jira.

Traffic Control will be holding its fall summit on October 17th and 18th in Atlanta, GA.  There are currently over 20 participants from 5 different companies registered to join.

How has the project developed since the last report?

 Since the last report (July 2017), we have

 * Merged 93 Pull Requests with 609 commits from 21 contributors
 * Opened 284 Github/Jira issues
 * Closed 83 Github/Jira issues
 * 284 emails sent by 39 people on the dev@ list
 * 5 emails sent by 2 people on the users@ list

How would you assess the podling's maturity?
Please feel free to add your own commentary.

At our next summit (Oct 2017), we will be discussing what steps we need to take to get to graduation.  We still have some hurdles to clear, but it’s good that we have recognized we need to start the discussion.

 [ ] Initial setup
 [ ] Working towards first release (wip)
 [x] Community building (wip)
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 Traffic Control 2.0 was released on July 7th, 2017.

When were the last committers or PPMC members elected?

In August, Traffic Control added 3 new committers from 2 different companies: Derek Gelinas (Comcast), Rob Butts (Comcast) , and Peter Ryder (Cisco)

Signed-off-by:

 [X](trafficcontrol) Phil Sorber
    Comments:
 [](trafficcontrol) Eric Covener
    Comments:
 [X](trafficcontrol) Leif Hedstrom
    Comments:

IPMC/Shepherd notes:

 johndament: It's great to see a community driven in person event being scheduled.  However, the podling should be cautious and ensure that all information discussed in person is brought back to the list when complete.

19 Jul 2017

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

  1. Enhance automation to facilitate committer voting on new releases.
  2. Enhance documentation to ease ramp-up time for new community members.
  3. Grow the community.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?

Traffic Control held a summit with Traffic Server during ApacheCon North
America.  This helped bring more attention to our project and encouraged
cross-pollination between the two projects.  In total there were 45 confirmed
attendees with 23 signing up as having interest in Traffic Control.

Traffic Control added 5 new contributors (went from 65 to 70 total unique
                contributors).

How has the project developed since the last report?

  Since the last report (April 2017), we have

  * Merged 225 Pull Requests with 714 commits from 27 contributors
  * Opened 189 JIRA issues
  * Closed 97 JIRA issues
  * 393 emails sent by 44 people on the dev@ list
  * 15 emails sent by 9 people on the users@ list

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release (wip)
  [x] Community building (wip)
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  Traffic Control 1.8.1 was released on 6/13/2017.
  Traffic Control 2.0 has passed the project team and IPMC vote and a release
  announcement should be sent out this week.

When were the last committers or PPMC members elected?

  No new committers or PPMC members yet.

Signed-off-by:

  [X](trafficcontrol) Phil Sorber
     Comments:
  [X](trafficcontrol) Eric Covener
     Comments:
  [ ](trafficcontrol) Daniel Gruno
     Comments:
  [ ](trafficcontrol) J. Aaron Farr
     Comments:

IPMC/Shepherd notes:

  johndament: The podling has grown quite a bit, once they start growing
  outside of their initial committer set they should think about graduation.

--------------------
Weex is a framework for building Mobile cross-platform high performance UI.
Weex has been incubating since 2016-11-30.

Three most important issues to address in the move towards graduation:
  1. Move the whole workflow and infra into Apache (not the codebase only).
  2. Develop more contributors and committers.
  3. First Release while in Incubator.
  4. Improve the developer's activity in JIRA.

 How has the community developed since the last report?

   - We voted a new committer: Jianfeng Li
   - Our Github has growth contributors (110), forks (517), watchers (222) and
     stars (3858)
   - We have encouraged people to discuss more in the JIRA and dev mail list.
     Up to now, 21 issues are reported on JIRA and 15 of them are resovled.
   - WebSite Trends Month Active , PV(295160) , UV(39778) , IP(36988), New
     Unique Visitor(20700) , Session(68747)

 How has the project developed since the last report?

   - Excluding merges, 19 authors have pushed 33 commits to master and 240
     commits to all branches.
   - This month we have successfully released the 0.12 version.

 How would you assess the podling's maturity?
 Please feel free to add your own commentary.

  [  ] Initial setup
  [  ] Working towards first release
  [x ] Community building
  [  ] Nearing graduation
  [  ] Other:

Date of last release:
  2017-06-08

When were the last committers or PPMC members elected?
  Jianfeng Li, 16 June 2017

Signed-off-by:

  [ ](weex) Luke Han
     Comments:
  [ ](weex) Willem Jiang
     Comments:
  [ ](weex) Stephan Ewen
     Comments:
  [x](weex) Raphael Bircher
     Comments:
     I started during the first release, and at this time there was nearly no
     communication on the list. We increased the list traffic last month over 100%
     but there is still a load of work to do.

IPMC/Shepherd notes:

  David Fisher: I want to note that Raphael is stepping up efforts as Mentor
  to really help the Weex community. Seems to be effective.

  jda: manual reminder sent.  report drafted on dev list

19 Apr 2017

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

 1. Enhance automation to facilitate committer voting on new releases.
 2. Enhance documentation to ease ramp-up time for new community members.
 3. Grow the community.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?

 Several new people have become active on the project. A 2 week hackathon
 was organized to on-board some new contributors from Qwilt.

How has the project developed since the last report?

 Traffic Control 1.8 was released on 3/7/2017 after a lot of cleanup of
 licenses and dependencies! Traffic Control 2.0 is converging on the first
 release candidate.

 Since the last report (January 2017), we have

 * Merged 232 Pull Requests with 441 commits from 16 contributors
 * Opened 135 JIRA issues
 * Closed 68 JIRA issues
 * Seen 105 messages on the dev@ list.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release (wip)
 [ ] Community building (wip)
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 Traffic Control 1.8 was released on 3/7/2017.

When were the last committers or PPMC members elected?

 No new committers or PPMC members yet.

Signed-off-by:

 [X](trafficcontrol) Phil Sorber
    Comments:
 [ ](trafficcontrol) Eric Covener
    Comments:
 [ ](trafficcontrol) Daniel Gruno
    Comments:
 [ ](trafficcontrol) J. Aaron Farr
    Comments:

18 Jan 2017

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

 1. Licenses and legal details. Traffic Control is a project made up of
    several different components, and includes or depends on an extensive
    list of software. We are working on making sure all source files have
    the right headers, all the licenses of included software are compatible
    and the LICENSE and NOTICE are correct.
 2. Enhance automation to facilitate committer voting on new releases.
 3. Enhance documentation to ease ramp-up time for new community members.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?

 We hosted a 2 day user / dev meetup in the Bay Area in October that was
 attended by 16 people representing 5 companies.

How has the project developed since the last report?

 All code has been move to Apache git. All new issues are being opened
 in Apache JIRA. All email communications have been moved to to Apache
 email lists. Our website has been moved to
 http://trafficcontrol.incubator.apache.org/ .

 Since the last report (October 2016), we have

 * Merged 145 Pull Requests with 314 commits from 19 contributors
 * Opened 83 JIRA issues
 * Closed 45 JIRA issues
 * Seen 81 messages on the dev@ list in December (before December we
   had commit messages going to dev@ as well, so those numbers are not
   indicative of dev communications)

Date of last release:

 None yet. We are addressing issues with release 1.8-incubating RC5.

When were the last committers or PPMC members elected?

 No new committers or PPMC members yet.

Signed-off-by:

 [X](trafficcontrol) Phil Sorber
 [x](trafficcontrol) Eric Covener
 [ ](trafficcontrol) Daniel Gruno
 [ ](trafficcontrol) J. Aaron Farr

Shepherd/Mentor notes:

 Drew Farris (shepherd):

   Healthy activity on mailing lists, one mentor active.

19 Oct 2016

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

 1. Move code, issues, email lists and release process to ASF

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?


How has the community developed since the last report?

 All CCLAs and ICLAs have been signed, and we are clear to proceed with
 moving the source from github.com to Apache. We are cleaning up the
 issues and open PRs at this time, and should be able to move the code
 before mid October.

How has the project developed since the last report?

 - All legal hurdles for software grant have been cleared.

Date of last release:

 We are trying to release 1.7 using the old process and git before the move
 in to Apache git.

When were the last committers or PMC members elected?

 2016-07-12 - initial committer list.

Signed-off-by:

 [x](trafficcontrol) Phil Sorber
 [ ](trafficcontrol) Eric Covener
 [ ](trafficcontrol) Daniel Gruno
 [ ](trafficcontrol) J. Aaron Farr

Shepherd/Mentor notes:

   Drew Farris (shepherd): Still getting off the ground, mailing lists are
     new. No observable mentor activity.

   Phil Sorber (mentor): There were some struggles getting all the legal ducks
     in a row but that's all complete now so expect decent uptick in activity.

21 Sep 2016

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

 1. Software grant from Comcast and others active in the current
    github.com/Comcast project to ASF. Discussion between Comcast and ASF
    legal on-going, this is blocking all other progress.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 See above issue 1.

How has the community developed since the last report?

 Established apache.org accounts for all of the initial committers.

How has the project developed since the last report?

 - Setup git repo and mailing lists.
 - Started Software Grant process.

Date of last release:

 We released 1.6.0 on 2016-07-29 under the old process, because the release
 process (candidates and votes) had already started before our official
 entry in the incubator. We have started release 1.7.0 under the old process
 as well, since we don't have the necessary ASF infrastructure in place, and
 this is pending the SGA.

When were the last committers or PMC members elected?

 2016-07-12 - initial committer list.

Signed-off-by:

 [X](trafficcontrol) Phil Sorber
 [X](trafficcontrol) Eric Covener
 [ ](trafficcontrol) Daniel Gruno
 [ ](trafficcontrol) J. Aaron Farr

17 Aug 2016

Traffic Control allows you to build a large scale content delivery network
using open source.

Traffic Control has been incubating since 2016-07-12.

Three most important issues to address in the move towards graduation:

 1. Get set up with all resources (git / mailing lists / JIRA / irc / etc)
 2. Name search / name sign off
 3. Prepare for next release under apache process

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 No.

How has the community developed since the last report?

 This is the first report, we are just getting started.

How has the project developed since the last report?

 This is the first report, we are just getting started. ICLAs are done.

Date of last release:

 We released 1.6.0 on 2016-07-29 under the old process, because the release
 process (candidates and votes) had already started before our official
 entry in the incubator. Our next release will be the first release where
 we will follow the Apache incubator process.

When were the last committers or PMC members elected?

 2016-07-12 - initial committer list.

Signed-off-by:

 [x](trafficcontrol) Phil Sorber
 [x](trafficcontrol) Eric Covener
 [ ](trafficcontrol) Daniel Gruno
 [ ](trafficcontrol) J. Aaron Farr