This was extracted (@ 2025-02-19 17: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.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (eg, documentation,
framework)
### Are there any issues that the IPMC or ASF Board need to be aware of?
No notification was sent about our upcoming March 2022 report and as result
we missed submitting our report.
### How has the community developed since the last report?
We're continuing to solidify a short term and long term on a roadmap with
the community that will allow more contributors to focus and work on
different levels of the project (i.e. data modeling and schema design,
use-cases, ingestion, ml, ui, dev ops, docs, etc). We're working to
prioritize these discussions, onboarding new committers, and getting
schedules aligned relative to everyone's other workloads.
### How has the project developed since the last report?
The master branch of Apache Spot was largely developed for commercial but
freely available Hadoop software (i.e. Cloudera, Hortonworks) are now in an
end of life (eol) state. In the next several quarters there should be some
priority to shift and add more native implementations on cloud providers
(i.e. AWS, Azure, GCP).
In the short-term it may be feasible to get things working in AWS EMR, and
specifically focus on fixing any issues related to getting the existing
Spot software installed and working. We anticipate lots of compatibility
issues such as working with newer versions of Spark with the existing code
base, as well as updating python code to be compatible with Python 3.9 or
later. Once we get this working we can also release a Cloudformation
template to the public community so that getting Spot setup is much less
labor intesnive than in the past.
In the long term we will want to support several cloud providers and
on-premise options depending on the interest of the community.
Investigate and exploring a replacement for the Spot UI is also still a
high priority. In the short-term, exploring Apache Supersets might be the
best approach. Apache Supersets would give us a basic authentication and
visualization layer into the data landed and processed by Spot.
In the long-term we will need to develop a more comprehensive security and
use-case roadmap for the UI and determine if it makes sense to develop
something from scratch. This will require more involvement and feedback in
the community before we can start designing and planning.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2019-09-02
### Have your mentors been helpful and responsive?
Our mentor has been helpful. However, the board and our mentor have
suggested we request an additional mentor to help us keep on top of things.
We would like make this a high priority during the next quarter.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (spot) Uma Maheswara Rao G
Comments:
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (eg, documentation,
framework)
### Are there any issues that the IPMC or ASF Board need to be aware of?
We last reported on June 2021. Our ordinarily scheduled quarterly report
was due in October 2021. The ASF board meeting notes for October 2021
noted that the report reminders did not go out, and so we did not report as
expected. We were expected to report for November 2021. On November 6,
2021, we were informed that our quarterly report was due to be completed on
November 3, 2021. Therefore, this report is being done quickly, to do as
much as possible to comply with ASF expectations. Regrettably this means
this is being done with minimum community discussion.
### How has the community developed since the last report?
We're continuing to solidify a short term and long term on a roadmap with
the community that will allow more contributors to focus and work on
different levels of the project (i.e. data modeling and schema design,
use-cases, ingestion, ml, ui, dev ops, docs, etc). These discussions have
been delayed this quarter due to COVID and getting schedules aligned
relative to other workloads.
### How has the project developed since the last report?
The master branch of Apache Spot was largely developed for commercial but
freely available Hadoop software (i.e. Cloudera, Hortonworks) that now have
been either End of Life’d (or will be in 2022) in favor of the newer
Cloudera Data Platform (CDP), or have been put behind a paywall to get
updates. The cloud provider landscape has also changed drastically in the
last few years and it's time that we start looking at better support for
Quickstart options in each major cloud providers so we can further develop
the project for the community with wider platform support, and give
committers better options for creating development environments to more
efficiently contribute to the project.
The following topics are planned for the next set of discussions with the
community to determine what we focus on for the next several quarters:
Add more native support on cloud infrastructure and software (i.e. AWS,
Azure, GCP)
In the short-term we can focus on AWS EMR on standing up Spot and fixing
any issues related to getting the software installed and working.
In the long term we will want to support several cloud providers and
on-premise options depending on the interest of the community.
Add an infrastructure module to Spot to automate creating clusters in
each providers we plan to support.
Initially we can focus on Cloudformation support with AWS EMR.
Our goal will be to generalize further in the long term with Terraform
across each provider.
Investigate and explore alternative replacement for Spot UI (i.e. Apache
Supersets)
In the short-term Apache Supersets may give us a basic authentication and
visualization layer into the data landed and processed by Spot.
In the long-term we will need to develop a more comprehensive security
and use-case roadmap for the UI and determine if it makes sense to develop
something from scratch.
The next step will be to create Jira Epic’s and tasks for these items so
we can start to distribute the work across the community.
### 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-09-08
### When were the last committers or PPMC members elected?
2019-09-02
### Have your mentors been helpful and responsive?
Our mentor has been helpful. However, we notice the board has suggested
we request an additional mentor to help us keep on top of things. We will
undertake this for the next quarter.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: I don't think this project is anywhere near to graduation.
And I don't see any noticeable activities in mailing lists. This project
needs additional mentors.
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
There is confusing communication with the organization. We submitted our
quarterly
report last month. The final report from last month noted that our
report was not
accepted because it was not signed off. However, we read the minutes
from the Board
that said all submitted reports were accepted, so we assumed we didn't
need to worry
about a report for another quarter. Last night at midnight we were
notified for the
first time that our report was due the same day. With less than 24 hours
notice, it
seems unlikely we'll be able to get sign-off from our mentor.
### How has the community developed since the last report?
We're continuing to solidify a short term and long term on a roadmap with
the community
that will allow more contributors to focus and work on different levels
of the project
(i.e. data modeling and schema design, use-cases, ingestion, ml, ui, dev
ops, docs, etc).
These discussions have been delayed this quarter due to COVID and getting
schedules aligned
relative to other workloads.
### How has the project developed since the last report?
The master branch of Apache Spot was largely developed for commercial but
freely
available Hadoop software (i.e. Cloudera, Hortonworks) that now have been
either
End of Life’d (or will be in 2022) in favor of the newer Cloudera Data
Platform
(CDP), or have been put behind a paywall to get updates. The cloud
provider
landscape has also changed drastically in the last few years and it's
time that
we start looking at better support for Quickstart options in each major
cloud
providers so we can further develop the project for the community with
wider
platform support, and give committers better options for creating
development
environments to more efficiently contribute to the project.
The following topics are planned for the next set of discussions with the
community
to determine what we focus on for the next several quarters:
* Add more native support on cloud infrastructure and software (i.e. AWS,
Azure, GCP)
* In the short-term we can focus on AWS EMR on standing up Spot and
fixing any issues
related to getting the software installed and working.
* In the long term we will want to support several cloud providers and
on-premise
options depending on the interest of the community.
* Add an infrastructure module to Spot to automate creating clusters in
each providers
we plan to support.
* Initially we can focus on Cloudformation support with AWS EMR.
* Our goal will be to generalize further in the long term with
Terraform across each provider.
* Investigate and explore alternative replacement for Spot UI (i.e.
Apache Supersets)
* In the short-term Apache Supersets may give us a basic authentication
and visualization
layer into the data landed and processed by Spot.
* In the long-term we will need to develop a more comprehensive
security and use-case
roadmap for the UI and determine if it makes sense to develop
something from scratch.
The next step will be to create Jira Epic’s and tasks for these items so
we can start to distribute the work across the community.
### 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-09-08
### When were the last committers or PPMC members elected?
2019-09-02
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
Yes our mentors have been helpful. We will be engaging them more soon for
guidance
on on-boarding new committers, as well as a few other items related to
the Whimsy
and Clutch reports and also updating the Apache Spot Podling website as
this is missing a number of updates.
### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
Yes.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments:
### IPMC/Shepherd notes:
Justin Mclean: The board signed off the incubator report but it can still
have reportsnot signed off by mentor. In your case it looks liked the
sign off come in late after the Incubator report was submitted, so sorry
for asking you to report again. Best to try and submit the report and have
it signed off by the due date if possible. Reminders are sent
to the incubator general list and you mentor(s) should be watching for
those. I would suggest you ask for another mentor so that you are not
dependant on just one person.
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
Not at this time
### How has the community developed since the last report?
We're continuing to solidify a short term and long term on a roadmap with
the community that will allow more contributors to focus and work on
different levels of the project (i.e. data modeling and schema design,
use-cases, ingestion, ml, ui, dev ops, docs, etc). These discussions have
been delayed this quarter due to COVID and getting schedules aligned
relative to other workloads.
### How has the project developed since the last report?
The master branch of Apache Spot was largely developed on commercial but
freely available Hadoop software (i.e. Cloudera, Hortonworks) that now have
been either End of Life’d (or will be in 2022) in favor of the newer
Cloudera Data Platform (CDP), or have been put behind a paywall to get
updates. The cloud provider landscape has also changed drastically in the
last few years and it's time that we start looking at better support for
Quickstart options in each major cloud providers so we can further develop
the project for the community with wider platform support, and give
committers better options for creating development environments to more
efficiently contribute to the project.
The following topics are planned for the next set of discussions with the
community to determine what we focus on for the next several quarters:
- Add more native support on cloud infrastructure and software (i.e. AWS,
Azure, GCP)
- In the short-term we can focus on AWS EMR on standing up Spot and
fixing any issues related to getting the software installed and
working.
- In the long term we will want to support several cloud providers and
on-premise options depending on the interest of the community.
- Add an infrastructure module to Spot to automate creating clusters in each
providers we plan to support.
- Initially we can focus on Cloudformation support with AWS EMR.
- Our goal will be to generalize further in the long term with Terraform
across each provider.
- Investigate and explore alternative replacement for Spot UI
(i.e. Apache Supersets)
- In the short-term Apache Supersets may give us a basic authentication
and visualization layer into the data landed and processed by Spot.
- In the long-term we will need to develop a more comprehensive security
and use-case roadmap for the UI and determine if it makes sense to
develop something from scratch.
The next step will be to create Jira Epic’s and tasks for these items so we
can start to distribute the work across the community.
### 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-09-08
### When were the last committers or PPMC members elected?
2019-09-02
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues
that need to be addressed.
Yes our mentors have been helpful. We will be engaging them more soon for
guidance on on-boarding new committers, as well as a few other items related
to the Whimsy and Clutch reports and also updating the Apache Spot Podling
website as this is missing a number of updates.
### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand?
If not what actions has the PPMC taken to correct this? Has the VP, Brand
approved the project name?
Yes.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G Comments: Need few more mentors. Very less
IPMC involvement currently. Need more efforts from IPMC in building
community. IPMC roll call was going on.
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Increase community activity in mailing list and commits
2. Make the product more approachable for new contributors and users
3. Develop a roadmap that focuses on delivering one use case effectively
### Are there any issues that the IPMC or ASF Board need to be aware of?
Not at this time.
### How has the community developed since the last report?
We're continuing to work on a roadmap with the community that will allow
more contributors to focus and work on different levels of the project
(i.e. data modeling and schema design, use-cases, ingestion, ml, ui, dev
ops, docs, etc).
### How has the project developed since the last report?
We've started regular weekly discussions around several topics, including
configuration management, authentication, and authorization models within
Spot so that we have a better backbone for adding more features and can
also backport existing functionality to a stronger foundation. These
discussions were delayed this quarter due to COVID and getting schedules
aligned relative to other workloads so we don't have any proposals
documented yet, but that is our next step.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2020-08-24 - We removed PPMC members who were not subscribed to the
private mailing list and who did not respond to an email asking them to
subscribe
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
Our mentors have been helpful in onboarding new contributors, and in
getting us the Whimsy and Clutch reports and updating the website so we
more completely conform to ASF policy requirements for podlings.
### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
We have no knowledge of any issues with the brand or trademark.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: This community needs few more mentors.
### IPMC/Shepherd notes:
Justin Mclean: Where are these weekly discussion taking place? Is what is
discussed in them brought back to the mailing list?
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Increase community activity in mailing list and commits
2. Make the product more approachable for new contributors and users
3. Develop a roadmap that focuses on delivering one use case effectively
### Are there any issues that the IPMC or ASF Board need to be aware of?
Not at this time.
### How has the community developed since the last report?
Our new contributors have helped us increase our capacity to fix and
resolve issues. Our goal in the near future is to work with the
community on a roadmap that will allow more contributors to focus
and work on different levels of the project (i.e. data modeling and
schema design, use-cases, ingestion, ml, ui, dev ops, docs, etc).
### How has the project developed since the last report?
We have increased our conformance with ASF podling policies by removing
from the PPMC all who are not on the private mailing list. This has
been the longest-standing caution against us.
We have significantly revamped the project website with the object of
making it more approachable for new contributors. We have used whimsy
to ensure that all ASF requirements are complied with.
We have captured all of the sample data used by the project and are now
hosting them using ASF resources, instead of a third party AWS S3 link,
which was hosted by unknown persons.
We have cleared away a large development effort that was initiated by
a large company but not completed, and no contributors appear to be
ready to resume work on it. Discussions have been started to take
this feature in a direction fulfilling different use cases.
### 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-09-08
### When were the last committers or PPMC members elected?
2020-08-24 - We removed PPMC members who were not subscribed
to the private mailing list and who did not respond to
an email asking them to subscribe
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
Our mentors have been helpful in onboarding new contributors,
and in getting us the Whimsy and Clutch reports and updating
the website so we more completely conform to ASF policy
requirements for podlings.
### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
We have no knowledge of any issues with the brand or trademark.
### Signed-off-by:
- [ ] (spot) Uma Maheswara Rao G
Comments:
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Increase community activity in mailing list and commits
2. Make the product more approachable for new contributors and users
3. Develop a roadmap that focuses on delivering one use case effectively
### Are there any issues that the IPMC or ASF Board need to be aware of?
Not at this time.
### How has the community developed since the last report?
We have on-boarded new contributors in the past quarter, who are very
excited to help us increase our capacity to address issues and move
us to a new level of maturity. One of the new contributors has adopted
the responsibility of secretary and ensuring process compliance and
improvement for the project facing Apache leadership.
We have continued to make further strides towards compliance with all
Apache Software Foundation requirements for incubating projects,
particularly ensuring that all contributors are on the private list.
### How has the project developed since the last report?
As the project has a large backlog of issues inherited from before its
contribution, we continue to emphasize finding issues that are still
relevant and blocking progress, and addressing them. We have engaged
with a dozen issues and resolved quite a few of them. There is work
that is ongoing to remove a third party dependency which is a major
impediment to installing the product.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2020-05-14 - Jeremy Nelson
### Have your mentors been helpful and responsive?
Our mentors have been helpful in on-boarding new contributors, and
in getting us the Whimsy and Clutch reports and updating the website
so we more completely conform to ASF policy requirements for podlings.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: Recently project improved on mailing list activities and
project needs few more mentors.
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
- Revive community activity (Discussion in mailing lists, increase
frequency of commits)
- Create a new roadmap and release plan that will improve adoption.
- Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
The number of active committers has increased over the past quarter, and
we also have several new potential community members looking to become
committers. We will work with our mentors to go through the process to
onboard them.
Much of the activity from the community has been focused on stabilizing
the codebase and fixing known issues in the documentation and Spot website.
This will greatly benefit new users and reduce confusion when standing up
the Spot different modules.
### How has the project developed since the last report?
Several projects have been proposed, discussed, and completed during the
past quarter. We're also working to close the remaining open PRs as soon
once the community finishes its review. Additionally there were some
Podling Website check failures in the Whimsy report that we began to look
into and resolve. These should be mostly resolved by the next Podling
report update.
We've also begun discussions on the second version of the Open Data Model
(ODM v2). There were several problems seen in the implementation with ODM
v1 that need to be resolved before substantial adoption of Apache Spot
can take place. Its our goal to come to a decision on the design of ODM
v2 this next quarter. Once a data model redesign is agreed upon this will
serve as a catalyst to modernizing other Spot modules so everything is
properly integrated.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
- 2017-09-08
### When were the last committers or PPMC members elected?
- 2019-09-02 - Mark Schoeni
### Have your mentors been helpful and responsive?
Yes our mentors have been helpful. We will be engaging them more soon for
guidance on on-boarding new committers, as well as a few other items
related to the Whimsy and Clutch reports and also updating the Apache
Spot Podling website as this is missing a number of updates.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: There is some improvement on mailing lists recently.
IMO, Still needs improvement in community development.
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption.
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
There are community members that have reached out and are interested in
contributing, but there are only a couple of active committers at this
time. Currently the main hurdle for new contributors is the amount of
effort required today to deploy Spot and build development environments.
### How has the project developed since the last report?
Open PRs with sufficient votes against the master branch and SPOT-181
epic have been merged. There's also been a substantial amount of work
to categorize all of the open JIRAs into a Project board on Github to
help the community more easily triage high priority issues, organize
feature enhancements into future epics, clean-up closed tickets, and
also group issues that require more information from the community
before taking action. Additionally there's been some work to clean-up
the asf-site branch, and minor updates (PRs are being pushed soon).
There's a larger project to re-organize the asf-site to make it easier
for the community to update and add new pages, but that hasn't started
yet.
The project with the most priority going forward is to make Spot easier
to deploy. There's a large learning curve for deploying Spot today, which
makes it difficult for both users and committers to be successful when
standing up Spot, using certain features, testing, and making
contributions back into the project. Using Cloudbreak to stand-up an
environment and deploying Spot as an Ambari package will help lower the
barriers to entry for new and existing users and contributors alike.
We expect during this project that we'll also uncover a number of deployment
issues and incompatibilities along the way and by resolving these will also
help bring confidence to users that this new deployment pattern will be
better tested and reliable.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2018-01-18
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: Community is not active in mailing lists. I have not seen
any discussions on release plans etc. I don't see committers/PPMC
responding to queries on dev list. I am concerned on community
building as well. With this pace, I don't think project can apply
for graduation in near future time.
### IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption.
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
Unfortunately there has not been much more community activity. However,
we are need of more committers as there are only a couple of active
committers at this time. This creates a bottleneck which makes it hard
for the community to grow in interest.
### How has the project developed since the last report?
There are a series of PRs that have been evaluated for the SPOT-181 epic,
and Spot website branch (asf-site) that are in the process of being
merged. We have enough votes to merge, and have put out a request to
committers to review so they can be auto-merged if possible, otherwise we
will just manually merge them via cli.
Once those are merged, we will work on the plan to merge SPOT-181 into
master so that the Open Data Model is consolidated into the main branch
of our code.
We're also working on re-focusing the project release roadmap. Our first
step will be to re-engage with the community to better understand
how/where Spot is being used today, what features/enhancements would benefit
the community best, and which committers (existing and potential) are
interested in contributing to the roadmap and releases moving forward.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2019-09-05
### Have your mentors been helpful and responsive?
Yes, but we would welcome more mentors and further guidance on
positioning the project for future graduation.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: Low/no activities on the lists. Raised the same concern on spot dev lists. PPMC is planning to address this concern.
### IPMC/Shepherd notes:
Justin Mclean: Please ask on the incubator general@ list for more mentors.
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Make it easier for Devs to contribute to the project (e.g.
documentation, framework).
3. Developing a workflow in Spot that allows for intuitive analytics.
### 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?
Unfortunately there has not been much more community activity. However,
we are need of more committers as there are only a couple of active
committers at this time. This creates a bottleneck which makes it hard
for the community to grow in interest.
### How has the project developed since the last report?
There's been discussions on the dev list to merge the existing SPOT-181
ODM branch into the master branch so that its easier to use the Open Data
Model within the existing architecture. This should avoid a lot of
confusion among new community members in the future as most of the recent
work as been done in the SPOT-181 branch. A series of PRs have also been
evaluated and we're waiting for more votes before starting the merge
process on those PR, and also the PR for moving SPOT-181 into master.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2018-01-18
### Have your mentors been helpful?
Yes our single mentor is responsive, however we only have one and may
need 1 more to help.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: I don't see much progress in community building. Very low
activities on mailing lists. Also this project needs additional mentors.
### IPMC/Shepherd notes:
Justin Mclean: Please ask for more mentors the incubators general@ list.
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Make it easier for Devs to contribute to the project (e.g.
documentation, framework).
3. Developing a workflow in Spot that allows for intuitive analytics.
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?
Unfortunately there has not been much more community activity. However, we
are need of more committers as there are only a couple of active committers
at this time. This creates a bottleneck which makes it hard for the
community to grow in interest.
How has the project developed since the last report?
A few members have been looking into merging one of the major branches that
the community has been waiting on into master. This should avoid a lot of
confusion among new community members in the future.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[x] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-08
When were the last committers or PPMC members elected?
2018-01-18
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes our single mentor is responsive, however we only have one and may need
1 more to help.
Signed-off-by:
[X](spot) Uma Maheswara Rao G
Comments:
Very low activity on mailing lists. Some times we don't even get replies
for questions in private lists ( May be all PPMC busy with other activities).
I don't see any steps or thoughts being discussed on Graduation.
Considering the community activity, I don't think its ready yet though.
Hope to see better responses in mailing lists and community growth.
IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Make it easier for Devs to contribute to the project (e.g.
documentation, framework).
3. Developing a workflow in Spot that allows for intuitive analytics.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We are currently down to 1 mentor. Although we put a request for an
additional mentor, we are not going to push the request until we wrap up
what we need to do for the next release. Once we have finished up work
and are ready to set up a vote we will push harder to invite another
mentor to help us with the process. We anticipate having a lot of
questions around the release process.
How has the community developed since the last report?
Since having pushed through some stagnant pull requests we have noticed a
little more activity. We are trying out different ways to make it easier
for developers to contribute. We are talking to users to understand what
pieces of Spot are important to them.
How has the project developed since the last report?
We have identified issues we think would block our release; mainly around
the ease of installation and use. We are doing some documentation
write-ups and code updates to make the Install process easier. We’re also
testing out setup on a VM with the aim to make it easier for developers to
contribute.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[x] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-08
When were the last committers or PPMC members elected?
2018-01-18
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Holding off on pushing for more mentors until we are ready to start the
official release process.
Signed-off-by:
[X](spot) Uma Maheswara Rao G
Comments: Project is seeking for additional mentors.
IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits).
2. Make it easier for Devs to create plug-ins for ingest of data.
3. Developing a workflow in Spot that allows intuitive analytics without
the need of licensed software.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
N/A
Have your mentors been helpful and responsive or are things falling through
the cracks?
Due to the community’s irregular activity level over the past months we
have had trouble aligning with our mentors.
The project is in the process of establishing a cadence to our activities
and we welcome help and advice from mentors.
How has the community developed since the last report?
Project wide meetings are continuing every 2 weeks. We are starting to see
more Pull Requests come in. Hoping that the end of summer (end of
vacations) will bring further participation from the community. We are
working on updating the Spot website and confluence pages to reflect
changes in the project.
How has the project developed since the last report?
A roadmap draft has been constructed. Our next focus is creating a new
release. Therefore, work is underway on closing some long running Pull
Requests and important bug fixes.
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-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments:
IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. More activity in the User and Dev mail lists
2. Revive Community activity (Discussion, commits)
3. Develop a better release process
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Lack of community discussion and activity is being addressed.
How has the community developed since the last report?
Started Bi-weekly (2 weeks) project wide community live meetings to try to
revive development on the project.
How has the project developed since the last report?
Community revival is underway. Bi-weekly meetings are taking place in order
to achieve momentum in the project. Goals are to prioritize Pull Requests
and promote the creation of new features in the community.
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-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments: Recently there was some improvement in discussions and
conducting community meetings etc.
IPMC/Shepherd notes:
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. More activity in the User and Dev mail lists
2. Integrate Open Data Model on top of Spot modules
3. Develop a better release process
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?
A. more interaction from partners
B. Seeing more interest and usage of Spot leading to more contributions in on the way
How has the project developed since the last report?
A. More development around Open Data Model
B. New data sources being integrated with ODM is maturing the structure
C. Adding Kerberos support to the project
D. Ingest Redesign
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-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments: Dev list discussions are low and community should give more attention to this point.
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Develop a better release process
2. Handle additional data types for ingestion and enrichment into ODM shema
3. Fostering more activity in the user, dev and private mail lists
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
a. Issues providing podling reports during December, January.
This is being addressed moving forward.
How has the community developed since the last report?
a. Seeing more pull requests from new contributors
How has the project developed since the last report?
a. Development on the ODM branch has been moving forward and will continue to push towards adoption into the master branch.
b. Ingest redesign underway
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-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[X](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[ ](spot) Uma Maheswara Rao G
Comments:
IPMC/Shepherd notes:
Dave Fisher: It's not clear to me where this podling has development discussions.
It would be good for the mentors to guide Spot to at least reflect discussions
on the dev@ list from Slack, Github or wherever these are happening.
Apache Spot is a solution stack that provides the capability to ingest IT related telemetry (network flows, domain name service DNS, and proxy server logs) and provide unsupervised machine learning capabilities to identify suspicious activity. The information is organized and presented using operational analytics so that a security analyst can investigate the most suspicious connections. Apache Spot is built on and using Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Build diverse community
2. Continue building a strong and diverse body of PPMC members for long term project continuity
3. Demonstrate ability to create releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* Recently Facebook decided to re-license React under MIT license, to enable compatibility with Apache licensed projects and many others. If there are not other indications from Incubator board we’ll call out a vote to keep it for now: https://code.facebook.com/posts/300798627056246/relicensing-react-jest-flow-and-immutable-js/
How has the community developed since the last report?
* Committers that are specialized on Ingest functions are merging branches for Open Data Model (ODM) development.
* Same case for views in order to simplify the process of normalization through the UI.
* Datasets with both benign and malicious traffic have been crafted to allow community to test/evaluate ML executions, and facilitate visualization exercises when doing Threat Hunting .
* Number of issues and discussion have increased with both feedback/RFE and bug fixes, which probes adoption, of course Community growth also consists on continue expanding the Committer baseline.
How has the project developed since the last report?
* The Spot project completed the first official Apache release for Spot v1.0, approved and voted by Incubator PMC.
* Open Data Model, development efforts continue over its branch in both directions specification and code pushes.
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:
Comments:
* Completion of the first Apache release was a significant milestone. The focus now needs to be converting the large number of project observers into project committers to foster a more diverse community, creating project awareness through technology blog posts, and Meetups is a significant effort that needs to happen for project evangelization
Date of last release:
2017-09-08
When were the last committers or PPMC members elected?
2017-06-02
Signed-off-by:
[X](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments:
IPMC/Shepherd notes:
Project is active and moving forward well. They do use ReactJS and will need to upgrade and release as soon as the relicensed version is available.
Dave Fisher
IPMC/Shepherd notes: - Drew Farris (shepherd): No mentor activity apparent from the mailing lists, ongoing project activity observed. - John D. Ament: Podling needed some reminding about the board report, I suspect next report will be in and of high quality.
Apache Spot is a solution stack that provides the capability to ingest IT
related telemetry (network flows, domain name service DNS, and proxy server
logs) and provide unsupervised machine learning capabilities to identify
suspicious activity. The information is organized and presented using
operational analytics so that a security analyst can investigate the most
suspicious connections. Apache Spot is built on an open data model using
Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Move infrastructure and development to ASF (code, issues, mailing list,
...)
2. Build diverse community
3. Demonstrate ability to create releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of? Two out of the four mentors are the ones showing the most active
participation and involvement on the project so we need to discuss with IPMC
our options to get the other two replaced.
How has the community developed since the last report? By remaking the
Community section on the Project webpage and driving users on Slack to limit
the usage of the same tool just for quick interactions, the traffic over Mail
Lists has increased, we still need to continue driving usage questions to USER
list. A group of Developers from Brazil is coming with a proposal for UX and
UI, based on the merits of the proposal, and the potential that the same has
we have invited them to become Committers on the projects.
The initial purpose of the Project on Network & Security needs to expand the
scope to IT Analytics to cover other uses cases and/or enrich content with
User and Endpoint data. While a normalization framework has been drafted to
what we call Open Data Model we still need more work and contributions on
technical delivery to make it a reality. Contributions to improve the concept
of Ingestion Pipeline & Data Lake are delivered with more cadence, there is a
recognition from Community to normalize data to open the space for other
sources of Ingestion
How has the project developed since the last report? The team has created the
epic on ASF JIRA towards the first Apache release, we’re working now including
the user stories that will be part of release, and doing checks to what can be
delivered before we do the the formal announcement on DEV for the code freeze.
Integrations for context enrichment are critical, however also the need of
bringing a plugin manager where does can be handled, the Spec was drafted, and
the team now is finalizing the last Pull requests to begin merging
functionality onto project code. Documentation is an area of focus so from May
to July committers we’ll continue improving & detailing more, architecture
definitions, deployment options, and UI usage sections. As the whole delivery
is concluded we’ll vote for a FAQ section which can be a point of reference
for common issues/situations. Being part of ASF is important Community
requests that project enables integration/consumption of other Apache
projects, one of our DEVOPS committers, for that reason having an API
framework now will open the door for more smooth integrations.
Date of last release: N/A
When were the last committers or PMC members elected? Last committer was
elected on 06/02
How does the podling rate their own maturity? By know we’re almost ready to do
our first Apache Release which is good, but we still need to mature Community,
the ramping of other Contributors has been slow, we have a strong base of
Consumer positive aspect as it probed consumption, however more Commits from
other interested parties will accelerate functionality delivery.
Signed-off-by:
[X](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments:
Apache Spot is a solution stack that provides the capability to ingest IT
related telemetry (network flows, domain name service information and proxy
server logs) and provide unsupervised machine learning capabilities to
identify suspicious activity. The information is organized and presented
using operational analytics so that a security analyst can investigate the
most suspicious connections. Apache Spot is built on an open data model using
Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Move infrastructure and development to ASF (code, issues, mailing
list, ...)
2. Build diverse community
3. Demonstrate ability to create releases
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?
Based on initial feedback, process for issues was updated on the project
website, with primary objective to facilitate the workflow and interaction
with Community, and having diverse ownership of them until resolution.
Slack channel has become very popular, however in order to adhere to ASF
official communications channels, those conversations that involve quick
question will be kept there, any extended discussion on code, pipeline, and
architecture, are being ported to Dev mail list.
There has been a concern to get continuous improvement of the UI on Apache
Spot, committers have been working on process to get UX interviews that
help to understand and address community and compliance needs.
How has the project developed since the last report?
The project got a major architecture change in order to remove CSV’s,
offload storage from the OS file system and instead leverage HDFS (for
distributed architecture).
Per community request through JIRA issue, and in order to facilitate the
installation/adoption of the project for scale deployments, an installation
script consolidating the ones that were built per pipeline component has
been pulled to repository, it will reduce the complexity of porting files
and configuration variables, by having a central point of deployment.
Open Data Models, which serves as a framework for data sources
normalization, initially for ingestion, was ported through its
Specification to the project repository, this will bring more contributions
to facilitate the design of the NoSQL table, and then determine technology
selection through discussion and voting through mailing list.
February Metrics:
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| Active Contributors (incl mentors)| 14 |
| Jira New Issues | 6 |
| Resolved Issues | 1 |
| Pull Requests merged | 3 |
| Pull Requests proposed | 3 |
+---------------------------------------------+
Date of last release:
N/A
When were the last committers or PMC members elected?
Last committer was elected on 2/24
How does the podling rate their own maturity?
There was a strong focus on code delivery over the last quarter, towards
Apache release, community adoption keeps growing, now by adding a layer of
process for opening issues and commits, plus interaction over channels
we're bringing contributions from others, towards Apache release.
Signed-off-by:
[x](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[x](spot) Uma Maheswara Rao G
Comments:
Apache Spot is a solution stack that provides the capability to ingest IT
related telemetry (network flows, domain name service information and proxy
server logs) and provide unsupervised machine learning capabilities to
identify suspicious activity. The information is organized and presented
using operational analytics so that a security analyst can investigate the
most suspicious connections. Apache Spot is built on an open data model
using Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Move infrastructure and development to ASF (code, issues, mailing
list, ...)
2. Build diverse community
3. Demonstrate ability to create releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
IPMC this point has been posted on the last two report, we have not
received any feedback in terms of how it goes, please comment.
Please elaborate on the process for code scanning and IP reviews. On the
last report this was brought to attention but no communication was
received.
How has the community developed since the last report?
Community is pushing more aggressively on project interaction which is
good, by opening issues on ASF JIRA, some of them have been closed with
their respective PR for bug fixing. Also developers in Brazil are
proposing a new UI schema by their own, which once is voted will
incorporate as contribution/new functionality towards our first Apache
release.
Adoption rate and popularity of the project has been recognized by
Industry receiving an award from Infoworld as Technology of the year and
also finalist on Edison Awards.
How has the project developed since the last report?
The Spot team launched a new project webpage version which incorporate
the long term vision and objectives of Apache Spot, and also includes a
new documentation package which is similar in structure to other ASF
projects.
Two new processes were published to explain on commits and how to open
issues, providing a structured frame that Community in general can follow
up in order to facilitate follow-up in combination of technology tools,
that can facilitate the life cycle continuity.
During this period 14 pull request were merged over different pipeline
components , as committers work also on the new design for data storage
through non-relational database technologies.
Also facilitating a quick demo of the project, we have updated our
container demo, and added automation in order to reflect those changes as
commits to UI are pulled to ASF Git repository.
Date of last release:
N/A
When were the last committers or PMC members elected?
Last committer was elected on 1/24
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
[ ](spot) Brock Noland
[ ](spot) Andrei Savu
[X](spot) Uma Maheswara Rao G
Apache Spot is a solution stack that provides the capability to ingest network related telemetry (network flows, domain name service information and proxy server logs) and provide unsupervised machine learning capabilities to identify suspicious activity. The information is organized and presented using operational analytics so that a security analyst can investigate the most suspicious connections. Apache Spot is built on an open data model using Apache Spark and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important issues to address in the move towards graduation: 1. Move infrastructure and development to ASF (code, issues, mailing list, ...) 2. Build diverse community 3. Demonstrate ability to create releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Please elaborate on the process for code scanning and IP reviews. How has the community developed since the last report? Community interaction has ramped velocity, as new adopters of the project have been posting questions through Twitter and Slack. We have added approximately 20% to our Slack channel and added several contributors through the ICLA. How has the project developed since the last report? We have moved our repo to ASF as of December 8, 2016. We have removed our LDA-C dependencies by switching to Spark LDA, eliminating licensing issues on this particular branch. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [ ](spot) Jarek Jarcec Cecho [ ](spot) Brock Noland [X](spot) Andrei Savu [X](spot) Uma Maheswara Rao G
Apache Spot is a solution stack that provides the capability to ingest network related telemetry (network flows, domain name service information and proxy server logs) and provide unsupervised machine learning capabilities to identify suspicious activity. The information is organized and presented using operational analytics so that a security analyst can investigate the most suspicious connections. Apache Spot is built on an open data model using Apache Spark and Apache Hadoop. Spot has been incubating since 2016-09-23. Three most important issues to address in the move towards graduation: - Move infrastructure and development to ASF (code, issues, mailing list, …) - Build diverse community - Demonstrate ability to create releases Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We currently have a hard dependency via our LDA implementation that requires a GPL license. A rewrite is in progress to move the code from LDA-C to Spark LDA. How has the community developed since the last report? This is first report after accepting Apache Spot to incubator and we still have not transitioned everything to ASF. We do however see increased interest in the project, primarily on our Slack channel. How has the project developed since the last report? This is first report. Date of last release: N/A When were the last committers or PMC members elected? N/A Signed-off-by: [x](spot) Jarek Jarcec Cecho [ ](spot) Brock Noland [ ](spot) Andrei Savu [X](spot) Uma Maheswara Rao G