The October 2016 board report has been submitted.

On Tue, Oct 4, 2016 at 11:16 AM, Dylan Millikin <dylan.milli...@gmail.com>
wrote:

> Yeah looking great!
>
> On Tue, Oct 4, 2016 at 10:39 AM, Marko Rodriguez <okramma...@gmail.com>
> wrote:
>
> > Diiiiiamn — that is one solid report.
> >
> > Marko.
> >
> > http://markorodriguez.com
> >
> >
> >
> > > On Oct 4, 2016, at 8:36 AM, Stephen Mallette <spmalle...@gmail.com>
> > wrote:
> > >
> > > A lot of stuff seems to have happened since our last report - did I
> miss
> > > anything?
> > >
> > > ------------------------------------------------------------
> > ------------------
> > >
> > > ## Description:
> > > Apache TinkerPop is a graph computing framework for both graph
> databases
> > > (OLTP) and graph analytic systems (OLAP).
> > >
> > > ## Activity:
> > > TinkerPop has added a new member to the PMC in Jason Plurad and a new
> > > committer in David Brown.
> > >
> > > TinkerPop released 3.1.4 and 3.2.2. 3.2.2 contains gremlin-python[1],
> > > which
> > > officially opens TinkerPop up to the Python community. We tend to think
> > > of Python as the most used language for TinkerPop outside of the JVM so
> > > having native support for it should help expand usage. October will see
> > > releases 3.1.5 and 3.2.3. These two releases are mostly bug fixes and
> > > minor
> > > usability improvements. We expect to continue to maintain both of these
> > > lines of code (bug fixes for 3.1.4 and ongoing development of 3.2.2),
> but
> > > intend to begin work on a new major line in 3.3.0 in the coming weeks.
> > >
> > > In an effort to share the technical knowledge of "releasing TinkerPop",
> > > we've
> > > started to share the work of that process. While we've always had our
> > > release
> > > process documented[2] and a single release manager can handle releases,
> > > we've determined it better (when possible) to have one release manager
> > per
> > > release line. Our initial trial with one release manager per version,
> on
> > > the
> > > previous release, worked well. We hope to continue with this approach
> for
> > > future releases.
> > >
> > > Promotionally speaking, there have been a number of talks at
> conferences
> > > on,
> > > or related, to TinkerPop. As a sample, here are the talks given by PMC
> > > members:
> > >
> > > Graph Computing with Apache TinkerPop - Dr. Marko Rodriguez [3]
> > > Graph Processing with Titan and Scylla - Jason Plurad [4]
> > >
> > > On the brand management front, it was noted by a PMC member (Jason
> Plurad
> > > had just been voted in almost to the day he made the report) that there
> > > was
> > > an individual selling products (baby clothes, mugs, t-shirts, etc.) on
> > > Amazon
> > > with TinkerPop graphics on them. Soon after, a second company was also
> > > noted
> > > selling similar products on an independent site. Neither, had
> permission
> > > from
> > > Apache to do that. After some discussion with Trademarks, the PMC chair
> > > sent
> > > notice to both sites requesting that they acknowledge the marks in
> their
> > > product description. No response was received from the seller on
> Amazon,
> > > but
> > > all products were quickly removed. No response was received from the
> > second
> > > seller, but on greater inspection of the site, it doesn't really appear
> > to
> > > be
> > > terribly active or maintained. Next steps with respect to this seller
> > have
> > > yet to be discussed.
> > >
> > > ## Issues:
> > > There are no issues requiring board attention at this time.
> > >
> > > ## Releases:
> > > - 3.1.4 (September 6, 2016)
> > > - 3.2.2 (September 6, 2016)
> > >
> > > ## PMC/Committer:
> > >
> > > - Last PMC addition was Jason Plurad - August 2016
> > > - Last committer addition was David Brown - August 2016
> > >
> > > ## Links
> > >
> > > [1] http://tinkerpop.apache.org/docs/current/reference/#gremlin-python
> > > [2] http://tinkerpop.apache.org/docs/current/dev/developer/#_
> > release_process
> > > [3] https://www.youtube.com/watch?v=tLR-I53Gl9g
> > > [4] https://www.youtube.com/watch?v=RllAy9OjzIo
> >
> >
>

Reply via email to