You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by sblackmon <sb...@apache.org> on 2016/09/28 20:00:00 UTC
[DISCUSS] Setting priorities for our next few releases
All,
Joey brought this up over the weekend and I think a discussion is overdue on the topic.
Encouraging community growth and performing regular releases are on our list of graduation criteria.
A few easy behaviors we can adopt to take to make progress on these goals:
- planning release versions around one or two significant improvements
- setting target dates to kick off upcoming releases
- prioritizing our backlog after each release
- discussing project and community milestones openly on the list
- organizing JIRA so that all contributors (especially new) can decide where it’s most important to focus their efforts
I think to get things moving again and demonstrate we are capable of consistent progress, we should aim to perform a release once per month around the end of the month.
As for what to focus on, I think it’s time to discuss adopting Activity Streams 2.0, figure out what form that transition would take, and get started down that path. Working implementations demonstrate the suitability of the standard and drive it’s adoption, and the prospects of this project are closely tied to those of the standard. Separate DISCUSS coming on this topic.
Also important for the ‘reboot’ theme, we should delete any modules we aren’t going to maintain, and bring all modules we are going to maintain up to acceptable standards - exactly what that means is an open question but broadly they should have documentation, code comments, and tests at the level of a typical module in a typical TLP.
Expanding the examples to demonstrate how to use streams providers and processors within various execution engines and fixing any bugs that have been reported is desirable as well. Adding at least one new example per release is a good target for now.
I have created some future versions with target release dates in JIRA and invite all committers to associate existing or new issues with those releases, or anyone who can’t modify JIRA to summarize their thoughts and share with the list and I will incorporate those ideas into JIRA. This should be the default reference for anyone looking for a way to help - look at issues associated with the next few releases and the top of the backlog and pick something that appeals and is in line with your experience.
Anything else that should be a top priority for the rest of the year? Or other ideas on improving planning and coordination?
Steve
On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
- This has already come up, but maybe ActivityStreams 2.0 support would broaden the community and motivate more work. It's also a concrete
goal to work toward so people would know where they can start.
- Steve and I did a little work here a few months ago, but the JIRA could reflect the priorities better and I think keep the community working in a common direction.
Re: [DISCUSS] Setting priorities for 0.4-incubating
Posted by Suneel Marthi <su...@gmail.com>.
please add me to the list of 'contributors' in Jira.
On Tue, Oct 4, 2016 at 12:56 PM, sblackmon <sb...@apache.org> wrote:
> With 0.3-incubating in the books, it’s time to take a look at what is most
> important for the next release.
>
> Here are a few concrete things I propose we tackle in October. They are
> tagged in JIRA with fixVersion=0.4
>
> https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
>
> I saw some new issues being created the last few days. Please keep it up,
> no matter how small!
>
> Major themes:
> * Reboot and Clean-up
> * Provider and Configuration consistency
> * Prep for the AS 2.0 switch
> Also:
> * POC persist integration tests with docker
> * POC provider integration tests that perform collection
> * Fix lingering and simple bugs / documentation
> * Flink example code
>
> If we target early week of October 24 for code freeze and cut rc1 that
> should give us time to get the release passed (hopefully with unanimous
> support from three active IPMC members on PPMC) by our November report.
>
> Feedback welcome! And feel free to assign yourself or let us someone with
> permissions know if you want to have something assigned to you.
>
> Steve
> On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org)
> wrote:
>
> All,
>
> Joey brought this up over the weekend and I think a discussion is overdue
> on the topic.
>
> Encouraging community growth and performing regular releases are on our
> list of graduation criteria.
>
> A few easy behaviors we can adopt to take to make progress on these goals:
> - planning release versions around one or two significant improvements
> - setting target dates to kick off upcoming releases
> - prioritizing our backlog after each release
> - discussing project and community milestones openly on the list
> - organizing JIRA so that all contributors (especially new) can decide
> where it’s most important to focus their efforts
>
> I think to get things moving again and demonstrate we are capable of
> consistent progress, we should aim to perform a release once per month
> around the end of the month.
>
> As for what to focus on, I think it’s time to discuss adopting Activity
> Streams 2.0, figure out what form that transition would take, and get
> started down that path. Working implementations demonstrate the
> suitability of the standard and drive it’s adoption, and the prospects of
> this project are closely tied to those of the standard. Separate DISCUSS
> coming on this topic.
>
> Also important for the ‘reboot’ theme, we should delete any modules we
> aren’t going to maintain, and bring all modules we are going to maintain up
> to acceptable standards - exactly what that means is an open question but
> broadly they should have documentation, code comments, and tests at the
> level of a typical module in a typical TLP.
>
> Expanding the examples to demonstrate how to use streams providers and
> processors within various execution engines and fixing any bugs that have
> been reported is desirable as well. Adding at least one new example per
> release is a good target for now.
>
> I have created some future versions with target release dates in JIRA and
> invite all committers to associate existing or new issues with those
> releases, or anyone who can’t modify JIRA to summarize their thoughts and
> share with the list and I will incorporate those ideas into JIRA. This
> should be the default reference for anyone looking for a way to help - look
> at issues associated with the next few releases and the top of the backlog
> and pick something that appeals and is in line with your experience.
>
> Anything else that should be a top priority for the rest of the year? Or
> other ideas on improving planning and coordination?
>
> Steve
>
> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
> - This has already come up, but maybe ActivityStreams 2.0 support would
> broaden the community and motivate more work. It's also a concrete
> goal to work toward so people would know where they can start.
> - Steve and I did a little work here a few months ago, but the JIRA
> could reflect the priorities better and I think keep the community working
> in a common direction.
Re: provider refactoring/improvement exemplar
Posted by Steve Blackmon <st...@blackmon.org>.
Update on provider refactoring for this release:
Twitter improvements for the issues mentioned in this thread have merged.
PRs for Facebook, instagram, google+, YouTube are open.
The commit logs and JIRA comments cover which issues have been tackled for
which providers.
These PRs don't cover every provider class or complete the refactoring we
need before adding AS 2 but does at least add real integration tests anyone
can run to get current profiles and posts from upstream.
RSS provider already has real testing.
Most remaining provider modules are commercial services and can't be used
or tested this easily.
Feedback on these changes welcome - sometime next week will finish merging
these and whatever other fixes are ready and start the release process.
On Oct 11, 2016 1:57 PM, "Steve Blackmon" <st...@blackmon.org> wrote:
> STREAMS-403 : run embedded, outside of a streams runtime
> STREAMS-411 : run from console via main method
>
>
> On Tue, Oct 11, 2016 at 1:43 PM, Matt Franklin <m....@gmail.com>
> wrote:
> > On Thu, Oct 6, 2016 at 10:32 AM Steve Blackmon <st...@blackmon.org>
> wrote:
> >
> >> This issue order makes sense to me, based on simplicity and complexity
> >>
> >> of improvement:
> >>
> >>
> >>
> >> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
> >>
> >> > > Ensure all providers function stand-alone
> >>
> >
> > Just so I am following, what is the purpose of this? Run standalone
> from a
> > console or run standalone outside of a streams runtime.
> >
> >
> >>
> >> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
> >>
> >> > > ability (and instructions on how) to run providers directly from
> >> console
> >>
> >> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
> >>
> >> > > SNS providers should emit appropriately typed documents by default
> >>
> >> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
> >>
> >> > > Proof of concept integration test that pulls actual data from
> generator
> >>
> >>
> >>
> >> In terms of which providers to target in what order, I’d suggest:
> >>
> >>
> >>
> >> twitter
> >>
> >> instagram
> >>
> >> rss
> >>
> >> youtube
> >>
> >> facebook
> >>
> >> gplus
> >>
> >> sysomos
> >>
> >> moreover
> >>
> >>
> >>
> >> Further down the list: more uncertainly about what exactly to do, how
> >>
> >> to do it, how to live test it, higher likelihood of encountering
> >>
> >> technical debt.
> >>
> >>
> >>
> >> If anyone wants to take a shot at any piece of this, go for it. No
> >>
> >> need for omni-bus PRs covering a full story or a full provider, every
> >>
> >> incremental improvement helps. I’ll happily code review any PR that’s
> >>
> >> opened and help get it finished.
> >>
> >>
> >>
> >> Steve
> >>
> >>
> >>
> >>
> >>
> >> On October 6, 2016 at 7:52:42 AM, Suneel Marthi
> >>
> >> (smarthi@apache.org(mailto:smarthi@apache.org)) wrote:
> >>
> >>
> >>
> >> > On Tue, Oct 4, 2016 at 9:58 PM, sblackmon wrote:
> >>
> >> >
> >>
> >> > >
> >>
> >> > > All,
> >>
> >> > >
> >>
> >> > > I’ve pushed a branch that depicts the sort of provider upgrades
> that I
> >>
> >> > > envision making across all providers this quarter.
> >>
> >> > >
> >>
> >> > > https://github.com/apache/incubator-streams/compare/
> >>
> >> > > master...steveblackmon:STREAMS-415?expand=1
> >>
> >> > >
> >>
> >> > > It solves for all of the following clean-up and improvement issues,
> >>
> >> > > specifically for the TwitterTimelineProvider
> >>
> >> > >
> >>
> >> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
> >>
> >> > > Ensure all providers function stand-alone
> >>
> >> > >
> >>
> >> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
> >>
> >> > > SNS providers should emit appropriately typed documents by default
> >>
> >> > >
> >>
> >> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
> >>
> >> > > ability (and instructions on how) to run providers directly from
> >> console
> >>
> >> > >
> >>
> >> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
> >>
> >> > > Proof of concept integration test that pulls actual data from
> generator
> >>
> >> > >
> >>
> >> > > Rather than tackle these stories one at a time laterally across all
> >>
> >> > > providers, we could consider divide-and-conquer by module or by
> class
> >> to
> >>
> >> > > reduce the number of commits and committers hitting each provider.
> >>
> >> > >
> >>
> >> > > Curious what others want to try. Would you rather take on one
> provider
> >> at
> >>
> >> > > a time and improve it’s quality across several dimensions, or
> improve
> >> many
> >>
> >> > > at once in a single dimension?
> >>
> >> > >
> >>
> >> >
> >>
> >> > I think we should do one at a time given the available and committed
> >>
> >> > resources. Which one would u like to tackle fist from the list above?
> >>
> >> >
> >>
> >> > >
> >>
> >> > > Steve
> >>
> >> > >
> >>
> >> > > On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org
> >> (mailto:
> >>
> >> > > sblackmon@apache.org)) wrote:
> >>
> >> > >
> >>
> >> > > > With 0.3-incubating in the books, it’s time to take a look at
> what is
> >>
> >> > > most important for the next release.
> >>
> >> > > >
> >>
> >> > > > Here are a few concrete things I propose we tackle in October.
> They
> >> are
> >>
> >> > > tagged in JIRA with fixVersion=0.4
> >>
> >> > > >
> >>
> >> > > > https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
> >>
> >> > > >
> >>
> >> > > > I saw some new issues being created the last few days. Please
> keep it
> >>
> >> > > up, no matter how small!
> >>
> >> > > >
> >>
> >> > > > Major themes:
> >>
> >> > > > * Reboot and Clean-up
> >>
> >> > > > * Provider and Configuration consistency
> >>
> >> > > > * Prep for the AS 2.0 switch
> >>
> >> > > > Also:
> >>
> >> > > > * POC persist integration tests with docker
> >>
> >> > > > * POC provider integration tests that perform collection
> >>
> >> > > > * Fix lingering and simple bugs / documentation
> >>
> >> > > > * Flink example code
> >>
> >> > > >
> >>
> >> > > > If we target early week of October 24 for code freeze and cut rc1
> >> that
> >>
> >> > > should give us time to get the release passed (hopefully with
> unanimous
> >>
> >> > > support from three active IPMC members on PPMC) by our November
> report.
> >>
> >> > > >
> >>
> >> > > > Feedback welcome! And feel free to assign yourself or let us
> someone
> >>
> >> > > with permissions know if you want to have something assigned to you.
> >>
> >> > > >
> >>
> >> > > > Steve
> >>
> >> > > >
> >>
> >> > > > On September 28, 2016 at 3:00:01 PM, sblackmon (
> sblackmon@apache.org
> >>
> >> > > (mailto:sblackmon@apache.org)) wrote:
> >>
> >> > > >
> >>
> >> > > > > All,
> >>
> >> > > > >
> >>
> >> > > > > Joey brought this up over the weekend and I think a discussion
> is
> >>
> >> > > overdue on the topic.
> >>
> >> > > > >
> >>
> >> > > > > Encouraging community growth and performing regular releases
> are on
> >>
> >> > > our list of graduation criteria.
> >>
> >> > > > >
> >>
> >> > > > > A few easy behaviors we can adopt to take to make progress on
> these
> >>
> >> > > goals:
> >>
> >> > > > > - planning release versions around one or two significant
> >> improvements
> >>
> >> > > > > - setting target dates to kick off upcoming releases
> >>
> >> > > > > - prioritizing our backlog after each release
> >>
> >> > > > > - discussing project and community milestones openly on the list
> >>
> >> > > > > - organizing JIRA so that all contributors (especially new) can
> >> decide
> >>
> >> > > where it’s most important to focus their efforts
> >>
> >> > > > >
> >>
> >> > > > > I think to get things moving again and demonstrate we are
> capable
> >> of
> >>
> >> > > consistent progress, we should aim to perform a release once per
> month
> >>
> >> > > around the end of the month.
> >>
> >> > > > >
> >>
> >> > > > > As for what to focus on, I think it’s time to discuss adopting
> >>
> >> > > Activity Streams 2.0, figure out what form that transition would
> take,
> >> and
> >>
> >> > > get started down that path. Working implementations demonstrate the
> >>
> >> > > suitability of the standard and drive it’s adoption, and the
> prospects
> >> of
> >>
> >> > > this project are closely tied to those of the standard. Separate
> >> DISCUSS
> >>
> >> > > coming on this topic.
> >>
> >> > > > >
> >>
> >> > > > > Also important for the ‘reboot’ theme, we should delete any
> >> modules we
> >>
> >> > > aren’t going to maintain, and bring all modules we are going to
> >> maintain up
> >>
> >> > > to acceptable standards - exactly what that means is an open
> question
> >> but
> >>
> >> > > broadly they should have documentation, code comments, and tests at
> the
> >>
> >> > > level of a typical module in a typical TLP.
> >>
> >> > > > >
> >>
> >> > > > > Expanding the examples to demonstrate how to use streams
> providers
> >> and
> >>
> >> > > processors within various execution engines and fixing any bugs that
> >> have
> >>
> >> > > been reported is desirable as well. Adding at least one new example
> per
> >>
> >> > > release is a good target for now.
> >>
> >> > > > >
> >>
> >> > > > > I have created some future versions with target release dates in
> >> JIRA
> >>
> >> > > and invite all committers to associate existing or new issues with
> >> those
> >>
> >> > > releases, or anyone who can’t modify JIRA to summarize their
> thoughts
> >> and
> >>
> >> > > share with the list and I will incorporate those ideas into JIRA.
> This
> >>
> >> > > should be the default reference for anyone looking for a way to
> help -
> >> look
> >>
> >> > > at issues associated with the next few releases and the top of the
> >> backlog
> >>
> >> > > and pick something that appeals and is in line with your experience.
> >>
> >> > > > >
> >>
> >> > > > > Anything else that should be a top priority for the rest of the
> >> year?
> >>
> >> > > Or other ideas on improving planning and coordination?
> >>
> >> > > > >
> >>
> >> > > > > Steve
> >>
> >> > > > >
> >>
> >> > > > > On September 24, 2016 at 1:01:02 PM, apache (
> sblackmon@apache.org
> >>
> >> > > (mailto:sblackmon@apache.org)) wrote:
> >>
> >> > > > > > - This has already come up, but maybe ActivityStreams 2.0
> support
> >>
> >> > > would broaden the community and motivate more work. It's also a
> >> concrete
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > > > goal to work toward so people would know where they can start.
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > > > - Steve and I did a little work here a few months ago, but the
> >> JIRA
> >>
> >> > > could reflect the priorities better and I think keep the community
> >> working
> >>
> >> > > in a common direction.
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > > >
> >>
> >> > > >
> >>
> >> > > >
> >>
> >> > > >
> >>
> >> > > >
> >>
> >> > >
> >>
> >> > >
> >>
> >> > >
> >>
> >> > >
> >>
> >> > >
> >>
> >>
>
Re: provider refactoring/improvement exemplar
Posted by Steve Blackmon <st...@blackmon.org>.
STREAMS-403 : run embedded, outside of a streams runtime
STREAMS-411 : run from console via main method
On Tue, Oct 11, 2016 at 1:43 PM, Matt Franklin <m....@gmail.com> wrote:
> On Thu, Oct 6, 2016 at 10:32 AM Steve Blackmon <st...@blackmon.org> wrote:
>
>> This issue order makes sense to me, based on simplicity and complexity
>>
>> of improvement:
>>
>>
>>
>> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
>>
>> > > Ensure all providers function stand-alone
>>
>
> Just so I am following, what is the purpose of this? Run standalone from a
> console or run standalone outside of a streams runtime.
>
>
>>
>> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
>>
>> > > ability (and instructions on how) to run providers directly from
>> console
>>
>> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
>>
>> > > SNS providers should emit appropriately typed documents by default
>>
>> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
>>
>> > > Proof of concept integration test that pulls actual data from generator
>>
>>
>>
>> In terms of which providers to target in what order, I’d suggest:
>>
>>
>>
>> twitter
>>
>> instagram
>>
>> rss
>>
>> youtube
>>
>> facebook
>>
>> gplus
>>
>> sysomos
>>
>> moreover
>>
>>
>>
>> Further down the list: more uncertainly about what exactly to do, how
>>
>> to do it, how to live test it, higher likelihood of encountering
>>
>> technical debt.
>>
>>
>>
>> If anyone wants to take a shot at any piece of this, go for it. No
>>
>> need for omni-bus PRs covering a full story or a full provider, every
>>
>> incremental improvement helps. I’ll happily code review any PR that’s
>>
>> opened and help get it finished.
>>
>>
>>
>> Steve
>>
>>
>>
>>
>>
>> On October 6, 2016 at 7:52:42 AM, Suneel Marthi
>>
>> (smarthi@apache.org(mailto:smarthi@apache.org)) wrote:
>>
>>
>>
>> > On Tue, Oct 4, 2016 at 9:58 PM, sblackmon wrote:
>>
>> >
>>
>> > >
>>
>> > > All,
>>
>> > >
>>
>> > > I’ve pushed a branch that depicts the sort of provider upgrades that I
>>
>> > > envision making across all providers this quarter.
>>
>> > >
>>
>> > > https://github.com/apache/incubator-streams/compare/
>>
>> > > master...steveblackmon:STREAMS-415?expand=1
>>
>> > >
>>
>> > > It solves for all of the following clean-up and improvement issues,
>>
>> > > specifically for the TwitterTimelineProvider
>>
>> > >
>>
>> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
>>
>> > > Ensure all providers function stand-alone
>>
>> > >
>>
>> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
>>
>> > > SNS providers should emit appropriately typed documents by default
>>
>> > >
>>
>> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
>>
>> > > ability (and instructions on how) to run providers directly from
>> console
>>
>> > >
>>
>> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
>>
>> > > Proof of concept integration test that pulls actual data from generator
>>
>> > >
>>
>> > > Rather than tackle these stories one at a time laterally across all
>>
>> > > providers, we could consider divide-and-conquer by module or by class
>> to
>>
>> > > reduce the number of commits and committers hitting each provider.
>>
>> > >
>>
>> > > Curious what others want to try. Would you rather take on one provider
>> at
>>
>> > > a time and improve it’s quality across several dimensions, or improve
>> many
>>
>> > > at once in a single dimension?
>>
>> > >
>>
>> >
>>
>> > I think we should do one at a time given the available and committed
>>
>> > resources. Which one would u like to tackle fist from the list above?
>>
>> >
>>
>> > >
>>
>> > > Steve
>>
>> > >
>>
>> > > On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org
>> (mailto:
>>
>> > > sblackmon@apache.org)) wrote:
>>
>> > >
>>
>> > > > With 0.3-incubating in the books, it’s time to take a look at what is
>>
>> > > most important for the next release.
>>
>> > > >
>>
>> > > > Here are a few concrete things I propose we tackle in October. They
>> are
>>
>> > > tagged in JIRA with fixVersion=0.4
>>
>> > > >
>>
>> > > > https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
>>
>> > > >
>>
>> > > > I saw some new issues being created the last few days. Please keep it
>>
>> > > up, no matter how small!
>>
>> > > >
>>
>> > > > Major themes:
>>
>> > > > * Reboot and Clean-up
>>
>> > > > * Provider and Configuration consistency
>>
>> > > > * Prep for the AS 2.0 switch
>>
>> > > > Also:
>>
>> > > > * POC persist integration tests with docker
>>
>> > > > * POC provider integration tests that perform collection
>>
>> > > > * Fix lingering and simple bugs / documentation
>>
>> > > > * Flink example code
>>
>> > > >
>>
>> > > > If we target early week of October 24 for code freeze and cut rc1
>> that
>>
>> > > should give us time to get the release passed (hopefully with unanimous
>>
>> > > support from three active IPMC members on PPMC) by our November report.
>>
>> > > >
>>
>> > > > Feedback welcome! And feel free to assign yourself or let us someone
>>
>> > > with permissions know if you want to have something assigned to you.
>>
>> > > >
>>
>> > > > Steve
>>
>> > > >
>>
>> > > > On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org
>>
>> > > (mailto:sblackmon@apache.org)) wrote:
>>
>> > > >
>>
>> > > > > All,
>>
>> > > > >
>>
>> > > > > Joey brought this up over the weekend and I think a discussion is
>>
>> > > overdue on the topic.
>>
>> > > > >
>>
>> > > > > Encouraging community growth and performing regular releases are on
>>
>> > > our list of graduation criteria.
>>
>> > > > >
>>
>> > > > > A few easy behaviors we can adopt to take to make progress on these
>>
>> > > goals:
>>
>> > > > > - planning release versions around one or two significant
>> improvements
>>
>> > > > > - setting target dates to kick off upcoming releases
>>
>> > > > > - prioritizing our backlog after each release
>>
>> > > > > - discussing project and community milestones openly on the list
>>
>> > > > > - organizing JIRA so that all contributors (especially new) can
>> decide
>>
>> > > where it’s most important to focus their efforts
>>
>> > > > >
>>
>> > > > > I think to get things moving again and demonstrate we are capable
>> of
>>
>> > > consistent progress, we should aim to perform a release once per month
>>
>> > > around the end of the month.
>>
>> > > > >
>>
>> > > > > As for what to focus on, I think it’s time to discuss adopting
>>
>> > > Activity Streams 2.0, figure out what form that transition would take,
>> and
>>
>> > > get started down that path. Working implementations demonstrate the
>>
>> > > suitability of the standard and drive it’s adoption, and the prospects
>> of
>>
>> > > this project are closely tied to those of the standard. Separate
>> DISCUSS
>>
>> > > coming on this topic.
>>
>> > > > >
>>
>> > > > > Also important for the ‘reboot’ theme, we should delete any
>> modules we
>>
>> > > aren’t going to maintain, and bring all modules we are going to
>> maintain up
>>
>> > > to acceptable standards - exactly what that means is an open question
>> but
>>
>> > > broadly they should have documentation, code comments, and tests at the
>>
>> > > level of a typical module in a typical TLP.
>>
>> > > > >
>>
>> > > > > Expanding the examples to demonstrate how to use streams providers
>> and
>>
>> > > processors within various execution engines and fixing any bugs that
>> have
>>
>> > > been reported is desirable as well. Adding at least one new example per
>>
>> > > release is a good target for now.
>>
>> > > > >
>>
>> > > > > I have created some future versions with target release dates in
>> JIRA
>>
>> > > and invite all committers to associate existing or new issues with
>> those
>>
>> > > releases, or anyone who can’t modify JIRA to summarize their thoughts
>> and
>>
>> > > share with the list and I will incorporate those ideas into JIRA. This
>>
>> > > should be the default reference for anyone looking for a way to help -
>> look
>>
>> > > at issues associated with the next few releases and the top of the
>> backlog
>>
>> > > and pick something that appeals and is in line with your experience.
>>
>> > > > >
>>
>> > > > > Anything else that should be a top priority for the rest of the
>> year?
>>
>> > > Or other ideas on improving planning and coordination?
>>
>> > > > >
>>
>> > > > > Steve
>>
>> > > > >
>>
>> > > > > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org
>>
>> > > (mailto:sblackmon@apache.org)) wrote:
>>
>> > > > > > - This has already come up, but maybe ActivityStreams 2.0 support
>>
>> > > would broaden the community and motivate more work. It's also a
>> concrete
>>
>> > > > >
>>
>> > > > >
>>
>> > > > > > goal to work toward so people would know where they can start.
>>
>> > > > >
>>
>> > > > >
>>
>> > > > >
>>
>> > > > >
>>
>> > > > > > - Steve and I did a little work here a few months ago, but the
>> JIRA
>>
>> > > could reflect the priorities better and I think keep the community
>> working
>>
>> > > in a common direction.
>>
>> > > > >
>>
>> > > > >
>>
>> > > > >
>>
>> > > > >
>>
>> > > > >
>>
>> > > >
>>
>> > > >
>>
>> > > >
>>
>> > > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>>
Re: provider refactoring/improvement exemplar
Posted by Matt Franklin <m....@gmail.com>.
On Thu, Oct 6, 2016 at 10:32 AM Steve Blackmon <st...@blackmon.org> wrote:
> This issue order makes sense to me, based on simplicity and complexity
>
> of improvement:
>
>
>
> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
>
> > > Ensure all providers function stand-alone
>
Just so I am following, what is the purpose of this? Run standalone from a
console or run standalone outside of a streams runtime.
>
> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
>
> > > ability (and instructions on how) to run providers directly from
> console
>
> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
>
> > > SNS providers should emit appropriately typed documents by default
>
> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
>
> > > Proof of concept integration test that pulls actual data from generator
>
>
>
> In terms of which providers to target in what order, I’d suggest:
>
>
>
> twitter
>
> instagram
>
> rss
>
> youtube
>
> facebook
>
> gplus
>
> sysomos
>
> moreover
>
>
>
> Further down the list: more uncertainly about what exactly to do, how
>
> to do it, how to live test it, higher likelihood of encountering
>
> technical debt.
>
>
>
> If anyone wants to take a shot at any piece of this, go for it. No
>
> need for omni-bus PRs covering a full story or a full provider, every
>
> incremental improvement helps. I’ll happily code review any PR that’s
>
> opened and help get it finished.
>
>
>
> Steve
>
>
>
>
>
> On October 6, 2016 at 7:52:42 AM, Suneel Marthi
>
> (smarthi@apache.org(mailto:smarthi@apache.org)) wrote:
>
>
>
> > On Tue, Oct 4, 2016 at 9:58 PM, sblackmon wrote:
>
> >
>
> > >
>
> > > All,
>
> > >
>
> > > I’ve pushed a branch that depicts the sort of provider upgrades that I
>
> > > envision making across all providers this quarter.
>
> > >
>
> > > https://github.com/apache/incubator-streams/compare/
>
> > > master...steveblackmon:STREAMS-415?expand=1
>
> > >
>
> > > It solves for all of the following clean-up and improvement issues,
>
> > > specifically for the TwitterTimelineProvider
>
> > >
>
> > > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
>
> > > Ensure all providers function stand-alone
>
> > >
>
> > > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
>
> > > SNS providers should emit appropriately typed documents by default
>
> > >
>
> > > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
>
> > > ability (and instructions on how) to run providers directly from
> console
>
> > >
>
> > > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
>
> > > Proof of concept integration test that pulls actual data from generator
>
> > >
>
> > > Rather than tackle these stories one at a time laterally across all
>
> > > providers, we could consider divide-and-conquer by module or by class
> to
>
> > > reduce the number of commits and committers hitting each provider.
>
> > >
>
> > > Curious what others want to try. Would you rather take on one provider
> at
>
> > > a time and improve it’s quality across several dimensions, or improve
> many
>
> > > at once in a single dimension?
>
> > >
>
> >
>
> > I think we should do one at a time given the available and committed
>
> > resources. Which one would u like to tackle fist from the list above?
>
> >
>
> > >
>
> > > Steve
>
> > >
>
> > > On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org
> (mailto:
>
> > > sblackmon@apache.org)) wrote:
>
> > >
>
> > > > With 0.3-incubating in the books, it’s time to take a look at what is
>
> > > most important for the next release.
>
> > > >
>
> > > > Here are a few concrete things I propose we tackle in October. They
> are
>
> > > tagged in JIRA with fixVersion=0.4
>
> > > >
>
> > > > https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
>
> > > >
>
> > > > I saw some new issues being created the last few days. Please keep it
>
> > > up, no matter how small!
>
> > > >
>
> > > > Major themes:
>
> > > > * Reboot and Clean-up
>
> > > > * Provider and Configuration consistency
>
> > > > * Prep for the AS 2.0 switch
>
> > > > Also:
>
> > > > * POC persist integration tests with docker
>
> > > > * POC provider integration tests that perform collection
>
> > > > * Fix lingering and simple bugs / documentation
>
> > > > * Flink example code
>
> > > >
>
> > > > If we target early week of October 24 for code freeze and cut rc1
> that
>
> > > should give us time to get the release passed (hopefully with unanimous
>
> > > support from three active IPMC members on PPMC) by our November report.
>
> > > >
>
> > > > Feedback welcome! And feel free to assign yourself or let us someone
>
> > > with permissions know if you want to have something assigned to you.
>
> > > >
>
> > > > Steve
>
> > > >
>
> > > > On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org
>
> > > (mailto:sblackmon@apache.org)) wrote:
>
> > > >
>
> > > > > All,
>
> > > > >
>
> > > > > Joey brought this up over the weekend and I think a discussion is
>
> > > overdue on the topic.
>
> > > > >
>
> > > > > Encouraging community growth and performing regular releases are on
>
> > > our list of graduation criteria.
>
> > > > >
>
> > > > > A few easy behaviors we can adopt to take to make progress on these
>
> > > goals:
>
> > > > > - planning release versions around one or two significant
> improvements
>
> > > > > - setting target dates to kick off upcoming releases
>
> > > > > - prioritizing our backlog after each release
>
> > > > > - discussing project and community milestones openly on the list
>
> > > > > - organizing JIRA so that all contributors (especially new) can
> decide
>
> > > where it’s most important to focus their efforts
>
> > > > >
>
> > > > > I think to get things moving again and demonstrate we are capable
> of
>
> > > consistent progress, we should aim to perform a release once per month
>
> > > around the end of the month.
>
> > > > >
>
> > > > > As for what to focus on, I think it’s time to discuss adopting
>
> > > Activity Streams 2.0, figure out what form that transition would take,
> and
>
> > > get started down that path. Working implementations demonstrate the
>
> > > suitability of the standard and drive it’s adoption, and the prospects
> of
>
> > > this project are closely tied to those of the standard. Separate
> DISCUSS
>
> > > coming on this topic.
>
> > > > >
>
> > > > > Also important for the ‘reboot’ theme, we should delete any
> modules we
>
> > > aren’t going to maintain, and bring all modules we are going to
> maintain up
>
> > > to acceptable standards - exactly what that means is an open question
> but
>
> > > broadly they should have documentation, code comments, and tests at the
>
> > > level of a typical module in a typical TLP.
>
> > > > >
>
> > > > > Expanding the examples to demonstrate how to use streams providers
> and
>
> > > processors within various execution engines and fixing any bugs that
> have
>
> > > been reported is desirable as well. Adding at least one new example per
>
> > > release is a good target for now.
>
> > > > >
>
> > > > > I have created some future versions with target release dates in
> JIRA
>
> > > and invite all committers to associate existing or new issues with
> those
>
> > > releases, or anyone who can’t modify JIRA to summarize their thoughts
> and
>
> > > share with the list and I will incorporate those ideas into JIRA. This
>
> > > should be the default reference for anyone looking for a way to help -
> look
>
> > > at issues associated with the next few releases and the top of the
> backlog
>
> > > and pick something that appeals and is in line with your experience.
>
> > > > >
>
> > > > > Anything else that should be a top priority for the rest of the
> year?
>
> > > Or other ideas on improving planning and coordination?
>
> > > > >
>
> > > > > Steve
>
> > > > >
>
> > > > > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org
>
> > > (mailto:sblackmon@apache.org)) wrote:
>
> > > > > > - This has already come up, but maybe ActivityStreams 2.0 support
>
> > > would broaden the community and motivate more work. It's also a
> concrete
>
> > > > >
>
> > > > >
>
> > > > > > goal to work toward so people would know where they can start.
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > > > - Steve and I did a little work here a few months ago, but the
> JIRA
>
> > > could reflect the priorities better and I think keep the community
> working
>
> > > in a common direction.
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
>
Re: provider refactoring/improvement exemplar
Posted by Steve Blackmon <st...@blackmon.org>.
This issue order makes sense to me, based on simplicity and complexity
of improvement:
> > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
> > Ensure all providers function stand-alone
> > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
> > ability (and instructions on how) to run providers directly from console
> > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
> > SNS providers should emit appropriately typed documents by default
> > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
> > Proof of concept integration test that pulls actual data from generator
In terms of which providers to target in what order, I’d suggest:
twitter
instagram
rss
youtube
facebook
gplus
sysomos
moreover
Further down the list: more uncertainly about what exactly to do, how
to do it, how to live test it, higher likelihood of encountering
technical debt.
If anyone wants to take a shot at any piece of this, go for it. No
need for omni-bus PRs covering a full story or a full provider, every
incremental improvement helps. I’ll happily code review any PR that’s
opened and help get it finished.
Steve
On October 6, 2016 at 7:52:42 AM, Suneel Marthi
(smarthi@apache.org(mailto:smarthi@apache.org)) wrote:
> On Tue, Oct 4, 2016 at 9:58 PM, sblackmon wrote:
>
> >
> > All,
> >
> > I’ve pushed a branch that depicts the sort of provider upgrades that I
> > envision making across all providers this quarter.
> >
> > https://github.com/apache/incubator-streams/compare/
> > master...steveblackmon:STREAMS-415?expand=1
> >
> > It solves for all of the following clean-up and improvement issues,
> > specifically for the TwitterTimelineProvider
> >
> > STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
> > Ensure all providers function stand-alone
> >
> > STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
> > SNS providers should emit appropriately typed documents by default
> >
> > STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
> > ability (and instructions on how) to run providers directly from console
> >
> > STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
> > Proof of concept integration test that pulls actual data from generator
> >
> > Rather than tackle these stories one at a time laterally across all
> > providers, we could consider divide-and-conquer by module or by class to
> > reduce the number of commits and committers hitting each provider.
> >
> > Curious what others want to try. Would you rather take on one provider at
> > a time and improve it’s quality across several dimensions, or improve many
> > at once in a single dimension?
> >
>
> I think we should do one at a time given the available and committed
> resources. Which one would u like to tackle fist from the list above?
>
> >
> > Steve
> >
> > On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org(mailto:
> > sblackmon@apache.org)) wrote:
> >
> > > With 0.3-incubating in the books, it’s time to take a look at what is
> > most important for the next release.
> > >
> > > Here are a few concrete things I propose we tackle in October. They are
> > tagged in JIRA with fixVersion=0.4
> > >
> > > https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
> > >
> > > I saw some new issues being created the last few days. Please keep it
> > up, no matter how small!
> > >
> > > Major themes:
> > > * Reboot and Clean-up
> > > * Provider and Configuration consistency
> > > * Prep for the AS 2.0 switch
> > > Also:
> > > * POC persist integration tests with docker
> > > * POC provider integration tests that perform collection
> > > * Fix lingering and simple bugs / documentation
> > > * Flink example code
> > >
> > > If we target early week of October 24 for code freeze and cut rc1 that
> > should give us time to get the release passed (hopefully with unanimous
> > support from three active IPMC members on PPMC) by our November report.
> > >
> > > Feedback welcome! And feel free to assign yourself or let us someone
> > with permissions know if you want to have something assigned to you.
> > >
> > > Steve
> > >
> > > On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org
> > (mailto:sblackmon@apache.org)) wrote:
> > >
> > > > All,
> > > >
> > > > Joey brought this up over the weekend and I think a discussion is
> > overdue on the topic.
> > > >
> > > > Encouraging community growth and performing regular releases are on
> > our list of graduation criteria.
> > > >
> > > > A few easy behaviors we can adopt to take to make progress on these
> > goals:
> > > > - planning release versions around one or two significant improvements
> > > > - setting target dates to kick off upcoming releases
> > > > - prioritizing our backlog after each release
> > > > - discussing project and community milestones openly on the list
> > > > - organizing JIRA so that all contributors (especially new) can decide
> > where it’s most important to focus their efforts
> > > >
> > > > I think to get things moving again and demonstrate we are capable of
> > consistent progress, we should aim to perform a release once per month
> > around the end of the month.
> > > >
> > > > As for what to focus on, I think it’s time to discuss adopting
> > Activity Streams 2.0, figure out what form that transition would take, and
> > get started down that path. Working implementations demonstrate the
> > suitability of the standard and drive it’s adoption, and the prospects of
> > this project are closely tied to those of the standard. Separate DISCUSS
> > coming on this topic.
> > > >
> > > > Also important for the ‘reboot’ theme, we should delete any modules we
> > aren’t going to maintain, and bring all modules we are going to maintain up
> > to acceptable standards - exactly what that means is an open question but
> > broadly they should have documentation, code comments, and tests at the
> > level of a typical module in a typical TLP.
> > > >
> > > > Expanding the examples to demonstrate how to use streams providers and
> > processors within various execution engines and fixing any bugs that have
> > been reported is desirable as well. Adding at least one new example per
> > release is a good target for now.
> > > >
> > > > I have created some future versions with target release dates in JIRA
> > and invite all committers to associate existing or new issues with those
> > releases, or anyone who can’t modify JIRA to summarize their thoughts and
> > share with the list and I will incorporate those ideas into JIRA. This
> > should be the default reference for anyone looking for a way to help - look
> > at issues associated with the next few releases and the top of the backlog
> > and pick something that appeals and is in line with your experience.
> > > >
> > > > Anything else that should be a top priority for the rest of the year?
> > Or other ideas on improving planning and coordination?
> > > >
> > > > Steve
> > > >
> > > > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org
> > (mailto:sblackmon@apache.org)) wrote:
> > > > > - This has already come up, but maybe ActivityStreams 2.0 support
> > would broaden the community and motivate more work. It's also a concrete
> > > >
> > > >
> > > > > goal to work toward so people would know where they can start.
> > > >
> > > >
> > > >
> > > >
> > > > > - Steve and I did a little work here a few months ago, but the JIRA
> > could reflect the priorities better and I think keep the community working
> > in a common direction.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
Re: provider refactoring/improvement exemplar
Posted by Suneel Marthi <sm...@apache.org>.
On Tue, Oct 4, 2016 at 9:58 PM, sblackmon <sb...@apache.org> wrote:
>
> All,
>
> I’ve pushed a branch that depicts the sort of provider upgrades that I
> envision making across all providers this quarter.
>
> https://github.com/apache/incubator-streams/compare/
> master...steveblackmon:STREAMS-415?expand=1
>
> It solves for all of the following clean-up and improvement issues,
> specifically for the TwitterTimelineProvider
>
> STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
> Ensure all providers function stand-alone
>
> STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
> SNS providers should emit appropriately typed documents by default
>
> STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
> ability (and instructions on how) to run providers directly from console
>
> STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
> Proof of concept integration test that pulls actual data from generator
>
> Rather than tackle these stories one at a time laterally across all
> providers, we could consider divide-and-conquer by module or by class to
> reduce the number of commits and committers hitting each provider.
>
> Curious what others want to try. Would you rather take on one provider at
> a time and improve it’s quality across several dimensions, or improve many
> at once in a single dimension?
>
I think we should do one at a time given the available and committed
resources. Which one would u like to tackle fist from the list above?
>
> Steve
>
> On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org(mailto:
> sblackmon@apache.org)) wrote:
>
> > With 0.3-incubating in the books, it’s time to take a look at what is
> most important for the next release.
> >
> > Here are a few concrete things I propose we tackle in October. They are
> tagged in JIRA with fixVersion=0.4
> >
> > https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
> >
> > I saw some new issues being created the last few days. Please keep it
> up, no matter how small!
> >
> > Major themes:
> > * Reboot and Clean-up
> > * Provider and Configuration consistency
> > * Prep for the AS 2.0 switch
> > Also:
> > * POC persist integration tests with docker
> > * POC provider integration tests that perform collection
> > * Fix lingering and simple bugs / documentation
> > * Flink example code
> >
> > If we target early week of October 24 for code freeze and cut rc1 that
> should give us time to get the release passed (hopefully with unanimous
> support from three active IPMC members on PPMC) by our November report.
> >
> > Feedback welcome! And feel free to assign yourself or let us someone
> with permissions know if you want to have something assigned to you.
> >
> > Steve
> >
> > On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org
> (mailto:sblackmon@apache.org)) wrote:
> >
> > > All,
> > >
> > > Joey brought this up over the weekend and I think a discussion is
> overdue on the topic.
> > >
> > > Encouraging community growth and performing regular releases are on
> our list of graduation criteria.
> > >
> > > A few easy behaviors we can adopt to take to make progress on these
> goals:
> > > - planning release versions around one or two significant improvements
> > > - setting target dates to kick off upcoming releases
> > > - prioritizing our backlog after each release
> > > - discussing project and community milestones openly on the list
> > > - organizing JIRA so that all contributors (especially new) can decide
> where it’s most important to focus their efforts
> > >
> > > I think to get things moving again and demonstrate we are capable of
> consistent progress, we should aim to perform a release once per month
> around the end of the month.
> > >
> > > As for what to focus on, I think it’s time to discuss adopting
> Activity Streams 2.0, figure out what form that transition would take, and
> get started down that path. Working implementations demonstrate the
> suitability of the standard and drive it’s adoption, and the prospects of
> this project are closely tied to those of the standard. Separate DISCUSS
> coming on this topic.
> > >
> > > Also important for the ‘reboot’ theme, we should delete any modules we
> aren’t going to maintain, and bring all modules we are going to maintain up
> to acceptable standards - exactly what that means is an open question but
> broadly they should have documentation, code comments, and tests at the
> level of a typical module in a typical TLP.
> > >
> > > Expanding the examples to demonstrate how to use streams providers and
> processors within various execution engines and fixing any bugs that have
> been reported is desirable as well. Adding at least one new example per
> release is a good target for now.
> > >
> > > I have created some future versions with target release dates in JIRA
> and invite all committers to associate existing or new issues with those
> releases, or anyone who can’t modify JIRA to summarize their thoughts and
> share with the list and I will incorporate those ideas into JIRA. This
> should be the default reference for anyone looking for a way to help - look
> at issues associated with the next few releases and the top of the backlog
> and pick something that appeals and is in line with your experience.
> > >
> > > Anything else that should be a top priority for the rest of the year?
> Or other ideas on improving planning and coordination?
> > >
> > > Steve
> > >
> > > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org
> (mailto:sblackmon@apache.org)) wrote:
> > > > - This has already come up, but maybe ActivityStreams 2.0 support
> would broaden the community and motivate more work. It's also a concrete
> > >
> > >
> > > > goal to work toward so people would know where they can start.
> > >
> > >
> > >
> > >
> > > > - Steve and I did a little work here a few months ago, but the JIRA
> could reflect the priorities better and I think keep the community working
> in a common direction.
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
>
provider refactoring/improvement exemplar
Posted by sblackmon <sb...@apache.org>.
All,
I’ve pushed a branch that depicts the sort of provider upgrades that I envision making across all providers this quarter.
https://github.com/apache/incubator-streams/compare/master...steveblackmon:STREAMS-415?expand=1
It solves for all of the following clean-up and improvement issues, specifically for the TwitterTimelineProvider
STREAMS-403(https://issues.apache.org/jira/browse/STREAMS-403)
Ensure all providers function stand-alone
STREAMS-422(https://issues.apache.org/jira/browse/STREAMS-422)
SNS providers should emit appropriately typed documents by default
STREAMS-411(https://issues.apache.org/jira/browse/STREAMS-411)
ability (and instructions on how) to run providers directly from console
STREAMS-415(https://issues.apache.org/jira/browse/STREAMS-415)
Proof of concept integration test that pulls actual data from generator
Rather than tackle these stories one at a time laterally across all providers, we could consider divide-and-conquer by module or by class to reduce the number of commits and committers hitting each provider.
Curious what others want to try. Would you rather take on one provider at a time and improve it’s quality across several dimensions, or improve many at once in a single dimension?
Steve
On October 4, 2016 at 11:56:18 AM, sblackmon (sblackmon@apache.org(mailto:sblackmon@apache.org)) wrote:
> With 0.3-incubating in the books, it’s time to take a look at what is most important for the next release.
>
> Here are a few concrete things I propose we tackle in October. They are tagged in JIRA with fixVersion=0.4
>
> https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
>
> I saw some new issues being created the last few days. Please keep it up, no matter how small!
>
> Major themes:
> * Reboot and Clean-up
> * Provider and Configuration consistency
> * Prep for the AS 2.0 switch
> Also:
> * POC persist integration tests with docker
> * POC provider integration tests that perform collection
> * Fix lingering and simple bugs / documentation
> * Flink example code
>
> If we target early week of October 24 for code freeze and cut rc1 that should give us time to get the release passed (hopefully with unanimous support from three active IPMC members on PPMC) by our November report.
>
> Feedback welcome! And feel free to assign yourself or let us someone with permissions know if you want to have something assigned to you.
>
> Steve
>
> On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org(mailto:sblackmon@apache.org)) wrote:
>
> > All,
> >
> > Joey brought this up over the weekend and I think a discussion is overdue on the topic.
> >
> > Encouraging community growth and performing regular releases are on our list of graduation criteria.
> >
> > A few easy behaviors we can adopt to take to make progress on these goals:
> > - planning release versions around one or two significant improvements
> > - setting target dates to kick off upcoming releases
> > - prioritizing our backlog after each release
> > - discussing project and community milestones openly on the list
> > - organizing JIRA so that all contributors (especially new) can decide where it’s most important to focus their efforts
> >
> > I think to get things moving again and demonstrate we are capable of consistent progress, we should aim to perform a release once per month around the end of the month.
> >
> > As for what to focus on, I think it’s time to discuss adopting Activity Streams 2.0, figure out what form that transition would take, and get started down that path. Working implementations demonstrate the suitability of the standard and drive it’s adoption, and the prospects of this project are closely tied to those of the standard. Separate DISCUSS coming on this topic.
> >
> > Also important for the ‘reboot’ theme, we should delete any modules we aren’t going to maintain, and bring all modules we are going to maintain up to acceptable standards - exactly what that means is an open question but broadly they should have documentation, code comments, and tests at the level of a typical module in a typical TLP.
> >
> > Expanding the examples to demonstrate how to use streams providers and processors within various execution engines and fixing any bugs that have been reported is desirable as well. Adding at least one new example per release is a good target for now.
> >
> > I have created some future versions with target release dates in JIRA and invite all committers to associate existing or new issues with those releases, or anyone who can’t modify JIRA to summarize their thoughts and share with the list and I will incorporate those ideas into JIRA. This should be the default reference for anyone looking for a way to help - look at issues associated with the next few releases and the top of the backlog and pick something that appeals and is in line with your experience.
> >
> > Anything else that should be a top priority for the rest of the year? Or other ideas on improving planning and coordination?
> >
> > Steve
> >
> > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org(mailto:sblackmon@apache.org)) wrote:
> > > - This has already come up, but maybe ActivityStreams 2.0 support would broaden the community and motivate more work. It's also a concrete
> >
> >
> > > goal to work toward so people would know where they can start.
> >
> >
> >
> >
> > > - Steve and I did a little work here a few months ago, but the JIRA could reflect the priorities better and I think keep the community working in a common direction.
> >
> >
> >
> >
> >
>
>
>
>
[DISCUSS] Setting priorities for 0.4-incubating
Posted by sblackmon <sb...@apache.org>.
With 0.3-incubating in the books, it’s time to take a look at what is most important for the next release.
Here are a few concrete things I propose we tackle in October. They are tagged in JIRA with fixVersion=0.4
https://issues.apache.org/jira/browse/STREAMS-418?filter=12338530
I saw some new issues being created the last few days. Please keep it up, no matter how small!
Major themes:
* Reboot and Clean-up
* Provider and Configuration consistency
* Prep for the AS 2.0 switch
Also:
* POC persist integration tests with docker
* POC provider integration tests that perform collection
* Fix lingering and simple bugs / documentation
* Flink example code
If we target early week of October 24 for code freeze and cut rc1 that should give us time to get the release passed (hopefully with unanimous support from three active IPMC members on PPMC) by our November report.
Feedback welcome! And feel free to assign yourself or let us someone with permissions know if you want to have something assigned to you.
Steve
On September 28, 2016 at 3:00:01 PM, sblackmon (sblackmon@apache.org) wrote:
All,
Joey brought this up over the weekend and I think a discussion is overdue on the topic.
Encouraging community growth and performing regular releases are on our list of graduation criteria.
A few easy behaviors we can adopt to take to make progress on these goals:
- planning release versions around one or two significant improvements
- setting target dates to kick off upcoming releases
- prioritizing our backlog after each release
- discussing project and community milestones openly on the list
- organizing JIRA so that all contributors (especially new) can decide where it’s most important to focus their efforts
I think to get things moving again and demonstrate we are capable of consistent progress, we should aim to perform a release once per month around the end of the month.
As for what to focus on, I think it’s time to discuss adopting Activity Streams 2.0, figure out what form that transition would take, and get started down that path. Working implementations demonstrate the suitability of the standard and drive it’s adoption, and the prospects of this project are closely tied to those of the standard. Separate DISCUSS coming on this topic.
Also important for the ‘reboot’ theme, we should delete any modules we aren’t going to maintain, and bring all modules we are going to maintain up to acceptable standards - exactly what that means is an open question but broadly they should have documentation, code comments, and tests at the level of a typical module in a typical TLP.
Expanding the examples to demonstrate how to use streams providers and processors within various execution engines and fixing any bugs that have been reported is desirable as well. Adding at least one new example per release is a good target for now.
I have created some future versions with target release dates in JIRA and invite all committers to associate existing or new issues with those releases, or anyone who can’t modify JIRA to summarize their thoughts and share with the list and I will incorporate those ideas into JIRA. This should be the default reference for anyone looking for a way to help - look at issues associated with the next few releases and the top of the backlog and pick something that appeals and is in line with your experience.
Anything else that should be a top priority for the rest of the year? Or other ideas on improving planning and coordination?
Steve
On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
- This has already come up, but maybe ActivityStreams 2.0 support would broaden the community and motivate more work. It's also a concrete
goal to work toward so people would know where they can start.
- Steve and I did a little work here a few months ago, but the JIRA could reflect the priorities better and I think keep the community working in a common direction.
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Suneel Marthi <sm...@apache.org>.
Will definitely do over this weekend.
On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org> wrote:
> Thanks Suneel!
>
> One key point from the original thread was the need to have a shared
> vision of what improvements would position the project well for community
> and user growth over the short and medium term.
>
> I’ve begun adding issues in line with the themes I mentioned and
> associating them to the releases labelled 0.4 - 0.6 and intend to come back
> to the list with some proposals shortly.
>
> One thing you could help with immediately is to validate our
> 0.3-incubating release and contribute an IPMC vote over on general.
>
>
> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org)
> wrote:
>
> Hi Ate and Steve,
>
> I will be glad to contribute code too and be more involved in keeping the
> project moving. If u could point me to jiras I could tackle I'll get
> started on that.
>
> Suneel
>
> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>
> > Hi Steve, community, silent followers,
> >
> > In general the proposal and suggestions from Steve are all good steps
> > forward.
> >
> > But I'm for now top posting and forking that discussion to try address
> > everyone
> > in the community directly, because I think there are other and more
> > critical
> > actions needed to make clear to the Incubator PMC that cancelling of
> this
> > project retirement will not end up to be just a temporary pause.
> >
> > The first and highest priority action should be getting more and diverse
> > involvement and active participation from the community.
> > The steps suggested by Steve are definitely helpful and needed as well.
> > But it just as well might end up remaining a one man's task list...
> >
> > Instead, we need to get more active input and suggestions/questions from
> > others
> > in the community, like Joey, our new mentor Suneel, and hopefully as
> well
> > from
> > the W3C ActivityStream 2.0 working group people, like Benjamin Young.
> >
> > And we need not just 'talk' feedback, but actual interest and
> participation
> > with concrete contributions.
> > (Suneel: I know you signed up just to mentor, which of course also is
> > needed)
> >
> > We need to see and show serious promise for growth of the project
> > community to
> > the IPMC, and in a reasonable short time frame (a few months at most).
> > Without that I think the changes of getting this project back on its
> feet
> > will
> > remain unrealistic, and then better be stopped.
> >
> > This also was indicated by the request from John Ament (the Incubator
> > Chair), to
> > switch back to monthly reporting for the coming 3 months, so the IPMC
> can
> > monitor the progress and chances for success. And if not, probably will
> > decide
> > (or at least vote) for a final retirement after all.
> > I agree with John this make perfectly sense, and I'll update the
> reporting
> > schedule for Streams shortly to make it so.
> >
> > Meaning: a next Incubator board report will need to be delivered monthly
> > for
> > at least the coming 3 months.
> > We better make sure there is positive news to report :-)
> >
> > I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
> > to see what ideas he has and what concrete actions can take in getting
> the
> > W3C
> > ActivityStreams 2.0 people involved as well.
> >
> > And I'm explicitly calling out to the mostly silent community, including
> > the
> > other committers, to speak up and let us know what you might be able to
> do
> > for
> > the project *now*: ideas, feedback, testing, maybe even code
> contributions?
> >
> > Kind regards, Ate
> >
> > On 2016-09-28 22:00, sblackmon wrote:
> >
> >> All,
> >>
> >> Joey brought this up over the weekend and I think a discussion is
> overdue
> >> on the topic.
> >>
> >> Encouraging community growth and performing regular releases are on our
> >> list of graduation criteria.
> >>
> >> A few easy behaviors we can adopt to take to make progress on these
> goals:
> >> - planning release versions around one or two significant improvements
> >> - setting target dates to kick off upcoming releases
> >> - prioritizing our backlog after each release
> >> - discussing project and community milestones openly on the list
> >> - organizing JIRA so that all contributors (especially new) can decide
> >> where it’s most important to focus their efforts
> >>
> >> I think to get things moving again and demonstrate we are capable of
> >> consistent progress, we should aim to perform a release once per month
> >> around the end of the month.
> >>
> >> As for what to focus on, I think it’s time to discuss adopting Activity
> >> Streams 2.0, figure out what form that transition would take, and get
> >> started down that path. Working implementations demonstrate the
> >> suitability of the standard and drive it’s adoption, and the prospects
> of
> >> this project are closely tied to those of the standard. Separate
> DISCUSS
> >> coming on this topic.
> >>
> >> Also important for the ‘reboot’ theme, we should delete any modules we
> >> aren’t going to maintain, and bring all modules we are going to
> maintain up
> >> to acceptable standards - exactly what that means is an open question
> but
> >> broadly they should have documentation, code comments, and tests at the
> >> level of a typical module in a typical TLP.
> >>
> >> Expanding the examples to demonstrate how to use streams providers and
> >> processors within various execution engines and fixing any bugs that
> have
> >> been reported is desirable as well. Adding at least one new example per
> >> release is a good target for now.
> >>
> >> I have created some future versions with target release dates in JIRA
> and
> >> invite all committers to associate existing or new issues with those
> >> releases, or anyone who can’t modify JIRA to summarize their thoughts
> and
> >> share with the list and I will incorporate those ideas into JIRA. This
> >> should be the default reference for anyone looking for a way to help -
> look
> >> at issues associated with the next few releases and the top of the
> backlog
> >> and pick something that appeals and is in line with your experience.
> >>
> >> Anything else that should be a top priority for the rest of the year?
> Or
> >> other ideas on improving planning and coordination?
> >>
> >> Steve
> >>
> >> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org)
> wrote:
> >> - This has already come up, but maybe ActivityStreams 2.0 support would
> >> broaden the community and motivate more work. It's also a concrete
> >> goal to work toward so people would know where they can start.
> >> - Steve and I did a little work here a few months ago, but the JIRA
> could
> >> reflect the priorities better and I think keep the community working in
> a
> >> common direction.
> >>
> >>
> >
> >
>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Suneel Marthi <su...@gmail.com>.
On Sun, Oct 2, 2016 at 3:16 PM, Ate Douma <at...@douma.nu> wrote:
> On 2016-10-01 03:36, Suneel Marthi wrote:
>
>> It's optional, u need 3 +1 binding votes for a release to pass; so u r
>> good to close the vote and finalize the release
>>
>
> The 72h minimum is not optional and there was no reason to rush the vote.
> For sure 4 +1 binding votes are enough.
> But a later -1 vote concerning for example legal issues should still be
> considered blocking until resolved.
> However in this case I don't think there was anything to worry, certainly
> not
> after the +1 from Justin. So no harm done.
Hence, I took the liberty to close the Vote, since we had a +1 from Justin.
:)
Next time, definitely will honor the 72 hr deadline.
>
However for next time we should again honour the 72h minimum time.
>
> Thanks, Ate
>
>
>
>> Sent from my iPhone
>>
>> On Sep 30, 2016, at 9:31 PM, Steve Blackmon <sb...@apache.org> wrote:
>>>
>>> Will do. I was leaving vote open for the full 72 hour duration. Is that
>>> optional once a quorum to release is reached?
>>>
>>>
>>> On Sep 30, 2016 6:20 PM, "Suneel Marthi" <sm...@apache.org> wrote:
>>>> @Steve I see 3 +1 binding iPMC votes for 0.3-incubating release, u may
>>>> want to close the vote and finalize the release.
>>>>
>>>> On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org>
>>>>> wrote:
>>>>> Thanks Suneel!
>>>>>
>>>>> One key point from the original thread was the need to have a shared
>>>>> vision of what improvements would position the project well for community
>>>>> and user growth over the short and medium term.
>>>>>
>>>>> I’ve begun adding issues in line with the themes I mentioned and
>>>>> associating them to the releases labelled 0.4 - 0.6 and intend to come back
>>>>> to the list with some proposals shortly.
>>>>>
>>>>> One thing you could help with immediately is to validate our
>>>>> 0.3-incubating release and contribute an IPMC vote over on general.
>>>>>
>>>>>
>>>>> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org)
>>>>>> wrote:
>>>>>>
>>>>>> Hi Ate and Steve,
>>>>>>
>>>>>> I will be glad to contribute code too and be more involved in keeping
>>>>>> the
>>>>>> project moving. If u could point me to jiras I could tackle I'll get
>>>>>> started on that.
>>>>>>
>>>>>> Suneel
>>>>>>
>>>>>> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>>>>>>
>>>>>> Hi Steve, community, silent followers,
>>>>>>>
>>>>>>> In general the proposal and suggestions from Steve are all good steps
>>>>>>> forward.
>>>>>>>
>>>>>>> But I'm for now top posting and forking that discussion to try
>>>>>>> address
>>>>>>> everyone
>>>>>>> in the community directly, because I think there are other and more
>>>>>>> critical
>>>>>>> actions needed to make clear to the Incubator PMC that cancelling of
>>>>>>> this
>>>>>>> project retirement will not end up to be just a temporary pause.
>>>>>>>
>>>>>>> The first and highest priority action should be getting more and
>>>>>>> diverse
>>>>>>> involvement and active participation from the community.
>>>>>>> The steps suggested by Steve are definitely helpful and needed as
>>>>>>> well.
>>>>>>> But it just as well might end up remaining a one man's task list...
>>>>>>>
>>>>>>> Instead, we need to get more active input and suggestions/questions
>>>>>>> from
>>>>>>> others
>>>>>>> in the community, like Joey, our new mentor Suneel, and hopefully as
>>>>>>> well
>>>>>>> from
>>>>>>> the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>>>>>>>
>>>>>>> And we need not just 'talk' feedback, but actual interest and
>>>>>>> participation
>>>>>>> with concrete contributions.
>>>>>>> (Suneel: I know you signed up just to mentor, which of course also is
>>>>>>> needed)
>>>>>>>
>>>>>>> We need to see and show serious promise for growth of the project
>>>>>>> community to
>>>>>>> the IPMC, and in a reasonable short time frame (a few months at
>>>>>>> most).
>>>>>>> Without that I think the changes of getting this project back on its
>>>>>>> feet
>>>>>>> will
>>>>>>> remain unrealistic, and then better be stopped.
>>>>>>>
>>>>>>> This also was indicated by the request from John Ament (the Incubator
>>>>>>> Chair), to
>>>>>>> switch back to monthly reporting for the coming 3 months, so the
>>>>>>> IPMC can
>>>>>>> monitor the progress and chances for success. And if not, probably
>>>>>>> will
>>>>>>> decide
>>>>>>> (or at least vote) for a final retirement after all.
>>>>>>> I agree with John this make perfectly sense, and I'll update the
>>>>>>> reporting
>>>>>>> schedule for Streams shortly to make it so.
>>>>>>>
>>>>>>> Meaning: a next Incubator board report will need to be delivered
>>>>>>> monthly
>>>>>>> for
>>>>>>> at least the coming 3 months.
>>>>>>> We better make sure there is positive news to report :-)
>>>>>>>
>>>>>>> I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this
>>>>>>> list)
>>>>>>> to see what ideas he has and what concrete actions can take in
>>>>>>> getting the
>>>>>>> W3C
>>>>>>> ActivityStreams 2.0 people involved as well.
>>>>>>>
>>>>>>> And I'm explicitly calling out to the mostly silent community,
>>>>>>> including
>>>>>>> the
>>>>>>> other committers, to speak up and let us know what you might be able
>>>>>>> to do
>>>>>>> for
>>>>>>> the project *now*: ideas, feedback, testing, maybe even code
>>>>>>> contributions?
>>>>>>>
>>>>>>> Kind regards, Ate
>>>>>>>
>>>>>>> On 2016-09-28 22:00, sblackmon wrote:
>>>>>>>
>>>>>>> All,
>>>>>>>>
>>>>>>>> Joey brought this up over the weekend and I think a discussion is
>>>>>>>> overdue
>>>>>>>> on the topic.
>>>>>>>>
>>>>>>>> Encouraging community growth and performing regular releases are on
>>>>>>>> our
>>>>>>>> list of graduation criteria.
>>>>>>>>
>>>>>>>> A few easy behaviors we can adopt to take to make progress on these
>>>>>>>> goals:
>>>>>>>> - planning release versions around one or two significant
>>>>>>>> improvements
>>>>>>>> - setting target dates to kick off upcoming releases
>>>>>>>> - prioritizing our backlog after each release
>>>>>>>> - discussing project and community milestones openly on the list
>>>>>>>> - organizing JIRA so that all contributors (especially new) can
>>>>>>>> decide
>>>>>>>> where it’s most important to focus their efforts
>>>>>>>>
>>>>>>>> I think to get things moving again and demonstrate we are capable of
>>>>>>>> consistent progress, we should aim to perform a release once per
>>>>>>>> month
>>>>>>>> around the end of the month.
>>>>>>>>
>>>>>>>> As for what to focus on, I think it’s time to discuss adopting
>>>>>>>> Activity
>>>>>>>> Streams 2.0, figure out what form that transition would take, and
>>>>>>>> get
>>>>>>>> started down that path. Working implementations demonstrate the
>>>>>>>> suitability of the standard and drive it’s adoption, and the
>>>>>>>> prospects of
>>>>>>>> this project are closely tied to those of the standard. Separate
>>>>>>>> DISCUSS
>>>>>>>> coming on this topic.
>>>>>>>>
>>>>>>>> Also important for the ‘reboot’ theme, we should delete any modules
>>>>>>>> we
>>>>>>>> aren’t going to maintain, and bring all modules we are going to
>>>>>>>> maintain up
>>>>>>>> to acceptable standards - exactly what that means is an open
>>>>>>>> question but
>>>>>>>> broadly they should have documentation, code comments, and tests at
>>>>>>>> the
>>>>>>>> level of a typical module in a typical TLP.
>>>>>>>>
>>>>>>>> Expanding the examples to demonstrate how to use streams providers
>>>>>>>> and
>>>>>>>> processors within various execution engines and fixing any bugs
>>>>>>>> that have
>>>>>>>> been reported is desirable as well. Adding at least one new example
>>>>>>>> per
>>>>>>>> release is a good target for now.
>>>>>>>>
>>>>>>>> I have created some future versions with target release dates in
>>>>>>>> JIRA and
>>>>>>>> invite all committers to associate existing or new issues with those
>>>>>>>> releases, or anyone who can’t modify JIRA to summarize their
>>>>>>>> thoughts and
>>>>>>>> share with the list and I will incorporate those ideas into JIRA.
>>>>>>>> This
>>>>>>>> should be the default reference for anyone looking for a way to
>>>>>>>> help - look
>>>>>>>> at issues associated with the next few releases and the top of the
>>>>>>>> backlog
>>>>>>>> and pick something that appeals and is in line with your experience.
>>>>>>>>
>>>>>>>> Anything else that should be a top priority for the rest of the
>>>>>>>> year? Or
>>>>>>>> other ideas on improving planning and coordination?
>>>>>>>>
>>>>>>>> Steve
>>>>>>>>
>>>>>>>> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org)
>>>>>>>> wrote:
>>>>>>>> - This has already come up, but maybe ActivityStreams 2.0 support
>>>>>>>> would
>>>>>>>> broaden the community and motivate more work. It's also a concrete
>>>>>>>> goal to work toward so people would know where they can start.
>>>>>>>> - Steve and I did a little work here a few months ago, but the JIRA
>>>>>>>> could
>>>>>>>> reflect the priorities better and I think keep the community
>>>>>>>> working in a
>>>>>>>> common direction.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Ate Douma <at...@douma.nu>.
On 2016-10-01 03:36, Suneel Marthi wrote:
> It's optional, u need 3 +1 binding votes for a release to pass; so u r good to close the vote and finalize the release
The 72h minimum is not optional and there was no reason to rush the vote.
For sure 4 +1 binding votes are enough.
But a later -1 vote concerning for example legal issues should still be
considered blocking until resolved.
However in this case I don't think there was anything to worry, certainly not
after the +1 from Justin. So no harm done.
However for next time we should again honour the 72h minimum time.
Thanks, Ate
>
> Sent from my iPhone
>
>> On Sep 30, 2016, at 9:31 PM, Steve Blackmon <sb...@apache.org> wrote:
>>
>> Will do. I was leaving vote open for the full 72 hour duration. Is that optional once a quorum to release is reached?
>>
>>
>>> On Sep 30, 2016 6:20 PM, "Suneel Marthi" <sm...@apache.org> wrote:
>>> @Steve I see 3 +1 binding iPMC votes for 0.3-incubating release, u may want to close the vote and finalize the release.
>>>
>>>> On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org> wrote:
>>>> Thanks Suneel!
>>>>
>>>> One key point from the original thread was the need to have a shared vision of what improvements would position the project well for community and user growth over the short and medium term.
>>>>
>>>> I’ve begun adding issues in line with the themes I mentioned and associating them to the releases labelled 0.4 - 0.6 and intend to come back to the list with some proposals shortly.
>>>>
>>>> One thing you could help with immediately is to validate our 0.3-incubating release and contribute an IPMC vote over on general.
>>>>
>>>>
>>>>> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org) wrote:
>>>>>
>>>>> Hi Ate and Steve,
>>>>>
>>>>> I will be glad to contribute code too and be more involved in keeping the
>>>>> project moving. If u could point me to jiras I could tackle I'll get
>>>>> started on that.
>>>>>
>>>>> Suneel
>>>>>
>>>>> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>>>>>
>>>>>> Hi Steve, community, silent followers,
>>>>>>
>>>>>> In general the proposal and suggestions from Steve are all good steps
>>>>>> forward.
>>>>>>
>>>>>> But I'm for now top posting and forking that discussion to try address
>>>>>> everyone
>>>>>> in the community directly, because I think there are other and more
>>>>>> critical
>>>>>> actions needed to make clear to the Incubator PMC that cancelling of this
>>>>>> project retirement will not end up to be just a temporary pause.
>>>>>>
>>>>>> The first and highest priority action should be getting more and diverse
>>>>>> involvement and active participation from the community.
>>>>>> The steps suggested by Steve are definitely helpful and needed as well.
>>>>>> But it just as well might end up remaining a one man's task list...
>>>>>>
>>>>>> Instead, we need to get more active input and suggestions/questions from
>>>>>> others
>>>>>> in the community, like Joey, our new mentor Suneel, and hopefully as well
>>>>>> from
>>>>>> the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>>>>>>
>>>>>> And we need not just 'talk' feedback, but actual interest and participation
>>>>>> with concrete contributions.
>>>>>> (Suneel: I know you signed up just to mentor, which of course also is
>>>>>> needed)
>>>>>>
>>>>>> We need to see and show serious promise for growth of the project
>>>>>> community to
>>>>>> the IPMC, and in a reasonable short time frame (a few months at most).
>>>>>> Without that I think the changes of getting this project back on its feet
>>>>>> will
>>>>>> remain unrealistic, and then better be stopped.
>>>>>>
>>>>>> This also was indicated by the request from John Ament (the Incubator
>>>>>> Chair), to
>>>>>> switch back to monthly reporting for the coming 3 months, so the IPMC can
>>>>>> monitor the progress and chances for success. And if not, probably will
>>>>>> decide
>>>>>> (or at least vote) for a final retirement after all.
>>>>>> I agree with John this make perfectly sense, and I'll update the reporting
>>>>>> schedule for Streams shortly to make it so.
>>>>>>
>>>>>> Meaning: a next Incubator board report will need to be delivered monthly
>>>>>> for
>>>>>> at least the coming 3 months.
>>>>>> We better make sure there is positive news to report :-)
>>>>>>
>>>>>> I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
>>>>>> to see what ideas he has and what concrete actions can take in getting the
>>>>>> W3C
>>>>>> ActivityStreams 2.0 people involved as well.
>>>>>>
>>>>>> And I'm explicitly calling out to the mostly silent community, including
>>>>>> the
>>>>>> other committers, to speak up and let us know what you might be able to do
>>>>>> for
>>>>>> the project *now*: ideas, feedback, testing, maybe even code contributions?
>>>>>>
>>>>>> Kind regards, Ate
>>>>>>
>>>>>> On 2016-09-28 22:00, sblackmon wrote:
>>>>>>
>>>>>>> All,
>>>>>>>
>>>>>>> Joey brought this up over the weekend and I think a discussion is overdue
>>>>>>> on the topic.
>>>>>>>
>>>>>>> Encouraging community growth and performing regular releases are on our
>>>>>>> list of graduation criteria.
>>>>>>>
>>>>>>> A few easy behaviors we can adopt to take to make progress on these goals:
>>>>>>> - planning release versions around one or two significant improvements
>>>>>>> - setting target dates to kick off upcoming releases
>>>>>>> - prioritizing our backlog after each release
>>>>>>> - discussing project and community milestones openly on the list
>>>>>>> - organizing JIRA so that all contributors (especially new) can decide
>>>>>>> where it’s most important to focus their efforts
>>>>>>>
>>>>>>> I think to get things moving again and demonstrate we are capable of
>>>>>>> consistent progress, we should aim to perform a release once per month
>>>>>>> around the end of the month.
>>>>>>>
>>>>>>> As for what to focus on, I think it’s time to discuss adopting Activity
>>>>>>> Streams 2.0, figure out what form that transition would take, and get
>>>>>>> started down that path. Working implementations demonstrate the
>>>>>>> suitability of the standard and drive it’s adoption, and the prospects of
>>>>>>> this project are closely tied to those of the standard. Separate DISCUSS
>>>>>>> coming on this topic.
>>>>>>>
>>>>>>> Also important for the ‘reboot’ theme, we should delete any modules we
>>>>>>> aren’t going to maintain, and bring all modules we are going to maintain up
>>>>>>> to acceptable standards - exactly what that means is an open question but
>>>>>>> broadly they should have documentation, code comments, and tests at the
>>>>>>> level of a typical module in a typical TLP.
>>>>>>>
>>>>>>> Expanding the examples to demonstrate how to use streams providers and
>>>>>>> processors within various execution engines and fixing any bugs that have
>>>>>>> been reported is desirable as well. Adding at least one new example per
>>>>>>> release is a good target for now.
>>>>>>>
>>>>>>> I have created some future versions with target release dates in JIRA and
>>>>>>> invite all committers to associate existing or new issues with those
>>>>>>> releases, or anyone who can’t modify JIRA to summarize their thoughts and
>>>>>>> share with the list and I will incorporate those ideas into JIRA. This
>>>>>>> should be the default reference for anyone looking for a way to help - look
>>>>>>> at issues associated with the next few releases and the top of the backlog
>>>>>>> and pick something that appeals and is in line with your experience.
>>>>>>>
>>>>>>> Anything else that should be a top priority for the rest of the year? Or
>>>>>>> other ideas on improving planning and coordination?
>>>>>>>
>>>>>>> Steve
>>>>>>>
>>>>>>> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
>>>>>>> - This has already come up, but maybe ActivityStreams 2.0 support would
>>>>>>> broaden the community and motivate more work. It's also a concrete
>>>>>>> goal to work toward so people would know where they can start.
>>>>>>> - Steve and I did a little work here a few months ago, but the JIRA could
>>>>>>> reflect the priorities better and I think keep the community working in a
>>>>>>> common direction.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for our next few releases]
Posted by Suneel Marthi <su...@gmail.com>.
It's optional, u need 3 +1 binding votes for a release to pass; so u r good to close the vote and finalize the release
Sent from my iPhone
> On Sep 30, 2016, at 9:31 PM, Steve Blackmon <sb...@apache.org> wrote:
>
> Will do. I was leaving vote open for the full 72 hour duration. Is that optional once a quorum to release is reached?
>
>
>> On Sep 30, 2016 6:20 PM, "Suneel Marthi" <sm...@apache.org> wrote:
>> @Steve I see 3 +1 binding iPMC votes for 0.3-incubating release, u may want to close the vote and finalize the release.
>>
>>> On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org> wrote:
>>> Thanks Suneel!
>>>
>>> One key point from the original thread was the need to have a shared vision of what improvements would position the project well for community and user growth over the short and medium term.
>>>
>>> I’ve begun adding issues in line with the themes I mentioned and associating them to the releases labelled 0.4 - 0.6 and intend to come back to the list with some proposals shortly.
>>>
>>> One thing you could help with immediately is to validate our 0.3-incubating release and contribute an IPMC vote over on general.
>>>
>>>
>>>> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org) wrote:
>>>>
>>>> Hi Ate and Steve,
>>>>
>>>> I will be glad to contribute code too and be more involved in keeping the
>>>> project moving. If u could point me to jiras I could tackle I'll get
>>>> started on that.
>>>>
>>>> Suneel
>>>>
>>>> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>>>>
>>>> > Hi Steve, community, silent followers,
>>>> >
>>>> > In general the proposal and suggestions from Steve are all good steps
>>>> > forward.
>>>> >
>>>> > But I'm for now top posting and forking that discussion to try address
>>>> > everyone
>>>> > in the community directly, because I think there are other and more
>>>> > critical
>>>> > actions needed to make clear to the Incubator PMC that cancelling of this
>>>> > project retirement will not end up to be just a temporary pause.
>>>> >
>>>> > The first and highest priority action should be getting more and diverse
>>>> > involvement and active participation from the community.
>>>> > The steps suggested by Steve are definitely helpful and needed as well.
>>>> > But it just as well might end up remaining a one man's task list...
>>>> >
>>>> > Instead, we need to get more active input and suggestions/questions from
>>>> > others
>>>> > in the community, like Joey, our new mentor Suneel, and hopefully as well
>>>> > from
>>>> > the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>>>> >
>>>> > And we need not just 'talk' feedback, but actual interest and participation
>>>> > with concrete contributions.
>>>> > (Suneel: I know you signed up just to mentor, which of course also is
>>>> > needed)
>>>> >
>>>> > We need to see and show serious promise for growth of the project
>>>> > community to
>>>> > the IPMC, and in a reasonable short time frame (a few months at most).
>>>> > Without that I think the changes of getting this project back on its feet
>>>> > will
>>>> > remain unrealistic, and then better be stopped.
>>>> >
>>>> > This also was indicated by the request from John Ament (the Incubator
>>>> > Chair), to
>>>> > switch back to monthly reporting for the coming 3 months, so the IPMC can
>>>> > monitor the progress and chances for success. And if not, probably will
>>>> > decide
>>>> > (or at least vote) for a final retirement after all.
>>>> > I agree with John this make perfectly sense, and I'll update the reporting
>>>> > schedule for Streams shortly to make it so.
>>>> >
>>>> > Meaning: a next Incubator board report will need to be delivered monthly
>>>> > for
>>>> > at least the coming 3 months.
>>>> > We better make sure there is positive news to report :-)
>>>> >
>>>> > I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
>>>> > to see what ideas he has and what concrete actions can take in getting the
>>>> > W3C
>>>> > ActivityStreams 2.0 people involved as well.
>>>> >
>>>> > And I'm explicitly calling out to the mostly silent community, including
>>>> > the
>>>> > other committers, to speak up and let us know what you might be able to do
>>>> > for
>>>> > the project *now*: ideas, feedback, testing, maybe even code contributions?
>>>> >
>>>> > Kind regards, Ate
>>>> >
>>>> > On 2016-09-28 22:00, sblackmon wrote:
>>>> >
>>>> >> All,
>>>> >>
>>>> >> Joey brought this up over the weekend and I think a discussion is overdue
>>>> >> on the topic.
>>>> >>
>>>> >> Encouraging community growth and performing regular releases are on our
>>>> >> list of graduation criteria.
>>>> >>
>>>> >> A few easy behaviors we can adopt to take to make progress on these goals:
>>>> >> - planning release versions around one or two significant improvements
>>>> >> - setting target dates to kick off upcoming releases
>>>> >> - prioritizing our backlog after each release
>>>> >> - discussing project and community milestones openly on the list
>>>> >> - organizing JIRA so that all contributors (especially new) can decide
>>>> >> where it’s most important to focus their efforts
>>>> >>
>>>> >> I think to get things moving again and demonstrate we are capable of
>>>> >> consistent progress, we should aim to perform a release once per month
>>>> >> around the end of the month.
>>>> >>
>>>> >> As for what to focus on, I think it’s time to discuss adopting Activity
>>>> >> Streams 2.0, figure out what form that transition would take, and get
>>>> >> started down that path. Working implementations demonstrate the
>>>> >> suitability of the standard and drive it’s adoption, and the prospects of
>>>> >> this project are closely tied to those of the standard. Separate DISCUSS
>>>> >> coming on this topic.
>>>> >>
>>>> >> Also important for the ‘reboot’ theme, we should delete any modules we
>>>> >> aren’t going to maintain, and bring all modules we are going to maintain up
>>>> >> to acceptable standards - exactly what that means is an open question but
>>>> >> broadly they should have documentation, code comments, and tests at the
>>>> >> level of a typical module in a typical TLP.
>>>> >>
>>>> >> Expanding the examples to demonstrate how to use streams providers and
>>>> >> processors within various execution engines and fixing any bugs that have
>>>> >> been reported is desirable as well. Adding at least one new example per
>>>> >> release is a good target for now.
>>>> >>
>>>> >> I have created some future versions with target release dates in JIRA and
>>>> >> invite all committers to associate existing or new issues with those
>>>> >> releases, or anyone who can’t modify JIRA to summarize their thoughts and
>>>> >> share with the list and I will incorporate those ideas into JIRA. This
>>>> >> should be the default reference for anyone looking for a way to help - look
>>>> >> at issues associated with the next few releases and the top of the backlog
>>>> >> and pick something that appeals and is in line with your experience.
>>>> >>
>>>> >> Anything else that should be a top priority for the rest of the year? Or
>>>> >> other ideas on improving planning and coordination?
>>>> >>
>>>> >> Steve
>>>> >>
>>>> >> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
>>>> >> - This has already come up, but maybe ActivityStreams 2.0 support would
>>>> >> broaden the community and motivate more work. It's also a concrete
>>>> >> goal to work toward so people would know where they can start.
>>>> >> - Steve and I did a little work here a few months ago, but the JIRA could
>>>> >> reflect the priorities better and I think keep the community working in a
>>>> >> common direction.
>>>> >>
>>>> >>
>>>> >
>>>> >
>>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Steve Blackmon <sb...@apache.org>.
Will do. I was leaving vote open for the full 72 hour duration. Is that
optional once a quorum to release is reached?
On Sep 30, 2016 6:20 PM, "Suneel Marthi" <sm...@apache.org> wrote:
> @Steve I see 3 +1 binding iPMC votes for 0.3-incubating release, u may
> want to close the vote and finalize the release.
>
> On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org> wrote:
>
>> Thanks Suneel!
>>
>> One key point from the original thread was the need to have a shared
>> vision of what improvements would position the project well for community
>> and user growth over the short and medium term.
>>
>> I’ve begun adding issues in line with the themes I mentioned and
>> associating them to the releases labelled 0.4 - 0.6 and intend to come back
>> to the list with some proposals shortly.
>>
>> One thing you could help with immediately is to validate our
>> 0.3-incubating release and contribute an IPMC vote over on general.
>>
>>
>> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org)
>> wrote:
>>
>> Hi Ate and Steve,
>>
>> I will be glad to contribute code too and be more involved in keeping the
>> project moving. If u could point me to jiras I could tackle I'll get
>> started on that.
>>
>> Suneel
>>
>> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>>
>> > Hi Steve, community, silent followers,
>> >
>> > In general the proposal and suggestions from Steve are all good steps
>> > forward.
>> >
>> > But I'm for now top posting and forking that discussion to try address
>> > everyone
>> > in the community directly, because I think there are other and more
>> > critical
>> > actions needed to make clear to the Incubator PMC that cancelling of
>> this
>> > project retirement will not end up to be just a temporary pause.
>> >
>> > The first and highest priority action should be getting more and
>> diverse
>> > involvement and active participation from the community.
>> > The steps suggested by Steve are definitely helpful and needed as well.
>> > But it just as well might end up remaining a one man's task list...
>> >
>> > Instead, we need to get more active input and suggestions/questions
>> from
>> > others
>> > in the community, like Joey, our new mentor Suneel, and hopefully as
>> well
>> > from
>> > the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>> >
>> > And we need not just 'talk' feedback, but actual interest and
>> participation
>> > with concrete contributions.
>> > (Suneel: I know you signed up just to mentor, which of course also is
>> > needed)
>> >
>> > We need to see and show serious promise for growth of the project
>> > community to
>> > the IPMC, and in a reasonable short time frame (a few months at most).
>> > Without that I think the changes of getting this project back on its
>> feet
>> > will
>> > remain unrealistic, and then better be stopped.
>> >
>> > This also was indicated by the request from John Ament (the Incubator
>> > Chair), to
>> > switch back to monthly reporting for the coming 3 months, so the IPMC
>> can
>> > monitor the progress and chances for success. And if not, probably will
>> > decide
>> > (or at least vote) for a final retirement after all.
>> > I agree with John this make perfectly sense, and I'll update the
>> reporting
>> > schedule for Streams shortly to make it so.
>> >
>> > Meaning: a next Incubator board report will need to be delivered
>> monthly
>> > for
>> > at least the coming 3 months.
>> > We better make sure there is positive news to report :-)
>> >
>> > I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
>> > to see what ideas he has and what concrete actions can take in getting
>> the
>> > W3C
>> > ActivityStreams 2.0 people involved as well.
>> >
>> > And I'm explicitly calling out to the mostly silent community,
>> including
>> > the
>> > other committers, to speak up and let us know what you might be able to
>> do
>> > for
>> > the project *now*: ideas, feedback, testing, maybe even code
>> contributions?
>> >
>> > Kind regards, Ate
>> >
>> > On 2016-09-28 22:00, sblackmon wrote:
>> >
>> >> All,
>> >>
>> >> Joey brought this up over the weekend and I think a discussion is
>> overdue
>> >> on the topic.
>> >>
>> >> Encouraging community growth and performing regular releases are on
>> our
>> >> list of graduation criteria.
>> >>
>> >> A few easy behaviors we can adopt to take to make progress on these
>> goals:
>> >> - planning release versions around one or two significant improvements
>> >> - setting target dates to kick off upcoming releases
>> >> - prioritizing our backlog after each release
>> >> - discussing project and community milestones openly on the list
>> >> - organizing JIRA so that all contributors (especially new) can decide
>> >> where it’s most important to focus their efforts
>> >>
>> >> I think to get things moving again and demonstrate we are capable of
>> >> consistent progress, we should aim to perform a release once per month
>> >> around the end of the month.
>> >>
>> >> As for what to focus on, I think it’s time to discuss adopting
>> Activity
>> >> Streams 2.0, figure out what form that transition would take, and get
>> >> started down that path. Working implementations demonstrate the
>> >> suitability of the standard and drive it’s adoption, and the prospects
>> of
>> >> this project are closely tied to those of the standard. Separate
>> DISCUSS
>> >> coming on this topic.
>> >>
>> >> Also important for the ‘reboot’ theme, we should delete any modules we
>> >> aren’t going to maintain, and bring all modules we are going to
>> maintain up
>> >> to acceptable standards - exactly what that means is an open question
>> but
>> >> broadly they should have documentation, code comments, and tests at
>> the
>> >> level of a typical module in a typical TLP.
>> >>
>> >> Expanding the examples to demonstrate how to use streams providers and
>> >> processors within various execution engines and fixing any bugs that
>> have
>> >> been reported is desirable as well. Adding at least one new example
>> per
>> >> release is a good target for now.
>> >>
>> >> I have created some future versions with target release dates in JIRA
>> and
>> >> invite all committers to associate existing or new issues with those
>> >> releases, or anyone who can’t modify JIRA to summarize their thoughts
>> and
>> >> share with the list and I will incorporate those ideas into JIRA. This
>> >> should be the default reference for anyone looking for a way to help -
>> look
>> >> at issues associated with the next few releases and the top of the
>> backlog
>> >> and pick something that appeals and is in line with your experience.
>> >>
>> >> Anything else that should be a top priority for the rest of the year?
>> Or
>> >> other ideas on improving planning and coordination?
>> >>
>> >> Steve
>> >>
>> >> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org)
>> wrote:
>> >> - This has already come up, but maybe ActivityStreams 2.0 support
>> would
>> >> broaden the community and motivate more work. It's also a concrete
>> >> goal to work toward so people would know where they can start.
>> >> - Steve and I did a little work here a few months ago, but the JIRA
>> could
>> >> reflect the priorities better and I think keep the community working
>> in a
>> >> common direction.
>> >>
>> >>
>> >
>> >
>>
>>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Suneel Marthi <sm...@apache.org>.
@Steve I see 3 +1 binding iPMC votes for 0.3-incubating release, u may want
to close the vote and finalize the release.
On Thu, Sep 29, 2016 at 9:30 PM, sblackmon <sb...@apache.org> wrote:
> Thanks Suneel!
>
> One key point from the original thread was the need to have a shared
> vision of what improvements would position the project well for community
> and user growth over the short and medium term.
>
> I’ve begun adding issues in line with the themes I mentioned and
> associating them to the releases labelled 0.4 - 0.6 and intend to come back
> to the list with some proposals shortly.
>
> One thing you could help with immediately is to validate our
> 0.3-incubating release and contribute an IPMC vote over on general.
>
>
> On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org)
> wrote:
>
> Hi Ate and Steve,
>
> I will be glad to contribute code too and be more involved in keeping the
> project moving. If u could point me to jiras I could tackle I'll get
> started on that.
>
> Suneel
>
> On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
>
> > Hi Steve, community, silent followers,
> >
> > In general the proposal and suggestions from Steve are all good steps
> > forward.
> >
> > But I'm for now top posting and forking that discussion to try address
> > everyone
> > in the community directly, because I think there are other and more
> > critical
> > actions needed to make clear to the Incubator PMC that cancelling of
> this
> > project retirement will not end up to be just a temporary pause.
> >
> > The first and highest priority action should be getting more and diverse
> > involvement and active participation from the community.
> > The steps suggested by Steve are definitely helpful and needed as well.
> > But it just as well might end up remaining a one man's task list...
> >
> > Instead, we need to get more active input and suggestions/questions from
> > others
> > in the community, like Joey, our new mentor Suneel, and hopefully as
> well
> > from
> > the W3C ActivityStream 2.0 working group people, like Benjamin Young.
> >
> > And we need not just 'talk' feedback, but actual interest and
> participation
> > with concrete contributions.
> > (Suneel: I know you signed up just to mentor, which of course also is
> > needed)
> >
> > We need to see and show serious promise for growth of the project
> > community to
> > the IPMC, and in a reasonable short time frame (a few months at most).
> > Without that I think the changes of getting this project back on its
> feet
> > will
> > remain unrealistic, and then better be stopped.
> >
> > This also was indicated by the request from John Ament (the Incubator
> > Chair), to
> > switch back to monthly reporting for the coming 3 months, so the IPMC
> can
> > monitor the progress and chances for success. And if not, probably will
> > decide
> > (or at least vote) for a final retirement after all.
> > I agree with John this make perfectly sense, and I'll update the
> reporting
> > schedule for Streams shortly to make it so.
> >
> > Meaning: a next Incubator board report will need to be delivered monthly
> > for
> > at least the coming 3 months.
> > We better make sure there is positive news to report :-)
> >
> > I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
> > to see what ideas he has and what concrete actions can take in getting
> the
> > W3C
> > ActivityStreams 2.0 people involved as well.
> >
> > And I'm explicitly calling out to the mostly silent community, including
> > the
> > other committers, to speak up and let us know what you might be able to
> do
> > for
> > the project *now*: ideas, feedback, testing, maybe even code
> contributions?
> >
> > Kind regards, Ate
> >
> > On 2016-09-28 22:00, sblackmon wrote:
> >
> >> All,
> >>
> >> Joey brought this up over the weekend and I think a discussion is
> overdue
> >> on the topic.
> >>
> >> Encouraging community growth and performing regular releases are on our
> >> list of graduation criteria.
> >>
> >> A few easy behaviors we can adopt to take to make progress on these
> goals:
> >> - planning release versions around one or two significant improvements
> >> - setting target dates to kick off upcoming releases
> >> - prioritizing our backlog after each release
> >> - discussing project and community milestones openly on the list
> >> - organizing JIRA so that all contributors (especially new) can decide
> >> where it’s most important to focus their efforts
> >>
> >> I think to get things moving again and demonstrate we are capable of
> >> consistent progress, we should aim to perform a release once per month
> >> around the end of the month.
> >>
> >> As for what to focus on, I think it’s time to discuss adopting Activity
> >> Streams 2.0, figure out what form that transition would take, and get
> >> started down that path. Working implementations demonstrate the
> >> suitability of the standard and drive it’s adoption, and the prospects
> of
> >> this project are closely tied to those of the standard. Separate
> DISCUSS
> >> coming on this topic.
> >>
> >> Also important for the ‘reboot’ theme, we should delete any modules we
> >> aren’t going to maintain, and bring all modules we are going to
> maintain up
> >> to acceptable standards - exactly what that means is an open question
> but
> >> broadly they should have documentation, code comments, and tests at the
> >> level of a typical module in a typical TLP.
> >>
> >> Expanding the examples to demonstrate how to use streams providers and
> >> processors within various execution engines and fixing any bugs that
> have
> >> been reported is desirable as well. Adding at least one new example per
> >> release is a good target for now.
> >>
> >> I have created some future versions with target release dates in JIRA
> and
> >> invite all committers to associate existing or new issues with those
> >> releases, or anyone who can’t modify JIRA to summarize their thoughts
> and
> >> share with the list and I will incorporate those ideas into JIRA. This
> >> should be the default reference for anyone looking for a way to help -
> look
> >> at issues associated with the next few releases and the top of the
> backlog
> >> and pick something that appeals and is in line with your experience.
> >>
> >> Anything else that should be a top priority for the rest of the year?
> Or
> >> other ideas on improving planning and coordination?
> >>
> >> Steve
> >>
> >> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org)
> wrote:
> >> - This has already come up, but maybe ActivityStreams 2.0 support would
> >> broaden the community and motivate more work. It's also a concrete
> >> goal to work toward so people would know where they can start.
> >> - Steve and I did a little work here a few months ago, but the JIRA
> could
> >> reflect the priorities better and I think keep the community working in
> a
> >> common direction.
> >>
> >>
> >
> >
>
>
Re: [DISCUSS] Community - call for help [Was: Setting
priorities for our next few releases]
Posted by sblackmon <sb...@apache.org>.
Thanks Suneel!
One key point from the original thread was the need to have a shared vision of what improvements would position the project well for community and user growth over the short and medium term.
I’ve begun adding issues in line with the themes I mentioned and associating them to the releases labelled 0.4 - 0.6 and intend to come back to the list with some proposals shortly.
One thing you could help with immediately is to validate our 0.3-incubating release and contribute an IPMC vote over on general.
On September 29, 2016 at 5:46:43 PM, Suneel Marthi (smarthi@apache.org) wrote:
Hi Ate and Steve,
I will be glad to contribute code too and be more involved in keeping the
project moving. If u could point me to jiras I could tackle I'll get
started on that.
Suneel
On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
> Hi Steve, community, silent followers,
>
> In general the proposal and suggestions from Steve are all good steps
> forward.
>
> But I'm for now top posting and forking that discussion to try address
> everyone
> in the community directly, because I think there are other and more
> critical
> actions needed to make clear to the Incubator PMC that cancelling of this
> project retirement will not end up to be just a temporary pause.
>
> The first and highest priority action should be getting more and diverse
> involvement and active participation from the community.
> The steps suggested by Steve are definitely helpful and needed as well.
> But it just as well might end up remaining a one man's task list...
>
> Instead, we need to get more active input and suggestions/questions from
> others
> in the community, like Joey, our new mentor Suneel, and hopefully as well
> from
> the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>
> And we need not just 'talk' feedback, but actual interest and participation
> with concrete contributions.
> (Suneel: I know you signed up just to mentor, which of course also is
> needed)
>
> We need to see and show serious promise for growth of the project
> community to
> the IPMC, and in a reasonable short time frame (a few months at most).
> Without that I think the changes of getting this project back on its feet
> will
> remain unrealistic, and then better be stopped.
>
> This also was indicated by the request from John Ament (the Incubator
> Chair), to
> switch back to monthly reporting for the coming 3 months, so the IPMC can
> monitor the progress and chances for success. And if not, probably will
> decide
> (or at least vote) for a final retirement after all.
> I agree with John this make perfectly sense, and I'll update the reporting
> schedule for Streams shortly to make it so.
>
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
> to see what ideas he has and what concrete actions can take in getting the
> W3C
> ActivityStreams 2.0 people involved as well.
>
> And I'm explicitly calling out to the mostly silent community, including
> the
> other committers, to speak up and let us know what you might be able to do
> for
> the project *now*: ideas, feedback, testing, maybe even code contributions?
>
> Kind regards, Ate
>
> On 2016-09-28 22:00, sblackmon wrote:
>
>> All,
>>
>> Joey brought this up over the weekend and I think a discussion is overdue
>> on the topic.
>>
>> Encouraging community growth and performing regular releases are on our
>> list of graduation criteria.
>>
>> A few easy behaviors we can adopt to take to make progress on these goals:
>> - planning release versions around one or two significant improvements
>> - setting target dates to kick off upcoming releases
>> - prioritizing our backlog after each release
>> - discussing project and community milestones openly on the list
>> - organizing JIRA so that all contributors (especially new) can decide
>> where it’s most important to focus their efforts
>>
>> I think to get things moving again and demonstrate we are capable of
>> consistent progress, we should aim to perform a release once per month
>> around the end of the month.
>>
>> As for what to focus on, I think it’s time to discuss adopting Activity
>> Streams 2.0, figure out what form that transition would take, and get
>> started down that path. Working implementations demonstrate the
>> suitability of the standard and drive it’s adoption, and the prospects of
>> this project are closely tied to those of the standard. Separate DISCUSS
>> coming on this topic.
>>
>> Also important for the ‘reboot’ theme, we should delete any modules we
>> aren’t going to maintain, and bring all modules we are going to maintain up
>> to acceptable standards - exactly what that means is an open question but
>> broadly they should have documentation, code comments, and tests at the
>> level of a typical module in a typical TLP.
>>
>> Expanding the examples to demonstrate how to use streams providers and
>> processors within various execution engines and fixing any bugs that have
>> been reported is desirable as well. Adding at least one new example per
>> release is a good target for now.
>>
>> I have created some future versions with target release dates in JIRA and
>> invite all committers to associate existing or new issues with those
>> releases, or anyone who can’t modify JIRA to summarize their thoughts and
>> share with the list and I will incorporate those ideas into JIRA. This
>> should be the default reference for anyone looking for a way to help - look
>> at issues associated with the next few releases and the top of the backlog
>> and pick something that appeals and is in line with your experience.
>>
>> Anything else that should be a top priority for the rest of the year? Or
>> other ideas on improving planning and coordination?
>>
>> Steve
>>
>> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
>> - This has already come up, but maybe ActivityStreams 2.0 support would
>> broaden the community and motivate more work. It's also a concrete
>> goal to work toward so people would know where they can start.
>> - Steve and I did a little work here a few months ago, but the JIRA could
>> reflect the priorities better and I think keep the community working in a
>> common direction.
>>
>>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Suneel Marthi <sm...@apache.org>.
Hi Ate and Steve,
I will be glad to contribute code too and be more involved in keeping the
project moving. If u could point me to jiras I could tackle I'll get
started on that.
Suneel
On Thu, Sep 29, 2016 at 2:26 AM, Ate Douma <at...@douma.nu> wrote:
> Hi Steve, community, silent followers,
>
> In general the proposal and suggestions from Steve are all good steps
> forward.
>
> But I'm for now top posting and forking that discussion to try address
> everyone
> in the community directly, because I think there are other and more
> critical
> actions needed to make clear to the Incubator PMC that cancelling of this
> project retirement will not end up to be just a temporary pause.
>
> The first and highest priority action should be getting more and diverse
> involvement and active participation from the community.
> The steps suggested by Steve are definitely helpful and needed as well.
> But it just as well might end up remaining a one man's task list...
>
> Instead, we need to get more active input and suggestions/questions from
> others
> in the community, like Joey, our new mentor Suneel, and hopefully as well
> from
> the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>
> And we need not just 'talk' feedback, but actual interest and participation
> with concrete contributions.
> (Suneel: I know you signed up just to mentor, which of course also is
> needed)
>
> We need to see and show serious promise for growth of the project
> community to
> the IPMC, and in a reasonable short time frame (a few months at most).
> Without that I think the changes of getting this project back on its feet
> will
> remain unrealistic, and then better be stopped.
>
> This also was indicated by the request from John Ament (the Incubator
> Chair), to
> switch back to monthly reporting for the coming 3 months, so the IPMC can
> monitor the progress and chances for success. And if not, probably will
> decide
> (or at least vote) for a final retirement after all.
> I agree with John this make perfectly sense, and I'll update the reporting
> schedule for Streams shortly to make it so.
>
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
> to see what ideas he has and what concrete actions can take in getting the
> W3C
> ActivityStreams 2.0 people involved as well.
>
> And I'm explicitly calling out to the mostly silent community, including
> the
> other committers, to speak up and let us know what you might be able to do
> for
> the project *now*: ideas, feedback, testing, maybe even code contributions?
>
> Kind regards, Ate
>
> On 2016-09-28 22:00, sblackmon wrote:
>
>> All,
>>
>> Joey brought this up over the weekend and I think a discussion is overdue
>> on the topic.
>>
>> Encouraging community growth and performing regular releases are on our
>> list of graduation criteria.
>>
>> A few easy behaviors we can adopt to take to make progress on these goals:
>> - planning release versions around one or two significant improvements
>> - setting target dates to kick off upcoming releases
>> - prioritizing our backlog after each release
>> - discussing project and community milestones openly on the list
>> - organizing JIRA so that all contributors (especially new) can decide
>> where it’s most important to focus their efforts
>>
>> I think to get things moving again and demonstrate we are capable of
>> consistent progress, we should aim to perform a release once per month
>> around the end of the month.
>>
>> As for what to focus on, I think it’s time to discuss adopting Activity
>> Streams 2.0, figure out what form that transition would take, and get
>> started down that path. Working implementations demonstrate the
>> suitability of the standard and drive it’s adoption, and the prospects of
>> this project are closely tied to those of the standard. Separate DISCUSS
>> coming on this topic.
>>
>> Also important for the ‘reboot’ theme, we should delete any modules we
>> aren’t going to maintain, and bring all modules we are going to maintain up
>> to acceptable standards - exactly what that means is an open question but
>> broadly they should have documentation, code comments, and tests at the
>> level of a typical module in a typical TLP.
>>
>> Expanding the examples to demonstrate how to use streams providers and
>> processors within various execution engines and fixing any bugs that have
>> been reported is desirable as well. Adding at least one new example per
>> release is a good target for now.
>>
>> I have created some future versions with target release dates in JIRA and
>> invite all committers to associate existing or new issues with those
>> releases, or anyone who can’t modify JIRA to summarize their thoughts and
>> share with the list and I will incorporate those ideas into JIRA. This
>> should be the default reference for anyone looking for a way to help - look
>> at issues associated with the next few releases and the top of the backlog
>> and pick something that appeals and is in line with your experience.
>>
>> Anything else that should be a top priority for the rest of the year? Or
>> other ideas on improving planning and coordination?
>>
>> Steve
>>
>> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
>> - This has already come up, but maybe ActivityStreams 2.0 support would
>> broaden the community and motivate more work. It's also a concrete
>> goal to work toward so people would know where they can start.
>> - Steve and I did a little work here a few months ago, but the JIRA could
>> reflect the priorities better and I think keep the community working in a
>> common direction.
>>
>>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Ate Douma <at...@douma.nu>.
On 2016-10-04 23:55, Ate Douma wrote:
> Draft report looks good to me.
> But I suggest to add one extra line to the "issues the IPMC/Board wish/need to
> be aware of" section, see inline comment below.
>
> If there is no objection, I can add the report to the wiki tomorrow morning,
> unless someone else beats me to it :-)
I've added the Streams report to the wiki:
https://wiki.apache.org/incubator/October2016
>
> Ate
>
> On 2016-10-04 17:52, sblackmon wrote:
>> Year on latest release date should be 2016 not 2015
>>
>>
>> On October 4, 2016 at 10:51:23 AM, sblackmon (sblackmon@apache.org) wrote:
>>
>> I haven’t been able to get into the wiki this morning, but here’s the draft
>> report I’ve come up with.
>>
>> --------------------
>> Streams
>>
>> Apache Streams (incubating) unifies a diverse world of digital profiles
>> and online activities into common formats and vocabularies, and makes
>> these datasets accessible across a variety of databases, devices, and
>> platforms for streaming, browsing, search, sharing, and analytics use-cases.
>>
>> Streams has been incubating since 2012-11-20.
>>
>> Three most important issues to address in the move towards graduation:
>>
>> 1. Community growth and PMC maturity.
>> 2. Demonstrate a consistent release schedule.
>> 3. Participation of project community within related standards-bodies and
>> Apache projects.
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>> A vote to retire the project was initiated but cancelled after several
>> individuals on the IPMC list expressed new interest in helping the project
>> continue to grow and eventually graduate. The project is now on a monthly
>> reporting schedule.
>
> I suggest adding:
> "[...] to monitor effective progress in growing the community and active
> participation."
>
>>
>> How has the community developed since the last report?
>>
>> dev@streams.incubator.apache.org
>> 46 emails sent by 15 people, divided into 9 topics.
>>
>> http://streams.incubator.apache.org
>> 196 Sessions, 170 Users, 512 Pageviews
>>
>> How has the project developed since the last report?
>>
>> https://github.com/apache/incubator-streams-master
>> Excluding merges, 1 author has pushed 9 commits to master and 9 commits to all
>> branches. On master, 8 files have changed and there have been 114 additions
>> and 193 deletions.
>>
>> https://github.com/apache/incubator-streams
>> Excluding merges, 1 author has pushed 6 commits to master and 6 commits to all
>> branches. On master, 61 files have changed and there have been 85 additions
>> and 66 deletions.
>>
>> https://github.com/apache/incubator-streams-examples
>> Excluding merges, 1 author has pushed 12 commits to master and 15 commits to
>> all branches. On master, 67 files have changed and there have been 549
>> additions and 761 deletions.
>>
>> 92 Issues closed with release of 0.3-incubating
>> 7 new Issues opened
>>
>> Date of last release:
>>
>> 2015-10-03 : 03-incubating release
>>
>> When were the last committers or PMC members elected?
>>
>> 2016-09-28: Suneel Marthi elected as mentor / PMC member
>>
>> Signed-off-by:
>>
>> [ ](streams) Ate Douma
>> [ ](streams) Matt Franklin
>> [ ](streams) Suneel Marthi
>>
>>
>> On October 3, 2016 at 12:26:48 PM, Suneel Marthi (suneel.marthi@gmail.com) wrote:
>>
>> ...the report for Oct 2016 is due on Oct 5, we have one +ve news to report
>> with the recent release.
>>
>> On Mon, Oct 3, 2016 at 1:11 PM, sblackmon <sb...@apache.org> wrote:
>>
>>> Meaning: a next Incubator board report will need to be delivered monthly
>>> for
>>> at least the coming 3 months.
>>> We better make sure there is positive news to report :-)
>>>
>>> I’ll get started on September 2016 and circulate a draft. Completing the
>>> 0.3-incubating release is positive.
>>> On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
>>>
>>
>>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Ate Douma <at...@douma.nu>.
Draft report looks good to me.
But I suggest to add one extra line to the "issues the IPMC/Board wish/need to
be aware of" section, see inline comment below.
If there is no objection, I can add the report to the wiki tomorrow morning,
unless someone else beats me to it :-)
Ate
On 2016-10-04 17:52, sblackmon wrote:
> Year on latest release date should be 2016 not 2015
>
>
> On October 4, 2016 at 10:51:23 AM, sblackmon (sblackmon@apache.org) wrote:
>
> I haven’t been able to get into the wiki this morning, but here’s the draft report I’ve come up with.
>
> --------------------
> Streams
>
> Apache Streams (incubating) unifies a diverse world of digital profiles
> and online activities into common formats and vocabularies, and makes
> these datasets accessible across a variety of databases, devices, and
> platforms for streaming, browsing, search, sharing, and analytics use-cases.
>
> Streams has been incubating since 2012-11-20.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Community growth and PMC maturity.
> 2. Demonstrate a consistent release schedule.
> 3. Participation of project community within related standards-bodies and
> Apache projects.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> A vote to retire the project was initiated but cancelled after several
> individuals on the IPMC list expressed new interest in helping the project
> continue to grow and eventually graduate. The project is now on a monthly
> reporting schedule.
I suggest adding:
"[...] to monitor effective progress in growing the community and active
participation."
>
> How has the community developed since the last report?
>
> dev@streams.incubator.apache.org
> 46 emails sent by 15 people, divided into 9 topics.
>
> http://streams.incubator.apache.org
> 196 Sessions, 170 Users, 512 Pageviews
>
> How has the project developed since the last report?
>
> https://github.com/apache/incubator-streams-master
> Excluding merges, 1 author has pushed 9 commits to master and 9 commits to all branches. On master, 8 files have changed and there have been 114 additions and 193 deletions.
>
> https://github.com/apache/incubator-streams
> Excluding merges, 1 author has pushed 6 commits to master and 6 commits to all branches. On master, 61 files have changed and there have been 85 additions and 66 deletions.
>
> https://github.com/apache/incubator-streams-examples
> Excluding merges, 1 author has pushed 12 commits to master and 15 commits to all branches. On master, 67 files have changed and there have been 549 additions and 761 deletions.
>
> 92 Issues closed with release of 0.3-incubating
> 7 new Issues opened
>
> Date of last release:
>
> 2015-10-03 : 03-incubating release
>
> When were the last committers or PMC members elected?
>
> 2016-09-28: Suneel Marthi elected as mentor / PMC member
>
> Signed-off-by:
>
> [ ](streams) Ate Douma
> [ ](streams) Matt Franklin
> [ ](streams) Suneel Marthi
>
>
> On October 3, 2016 at 12:26:48 PM, Suneel Marthi (suneel.marthi@gmail.com) wrote:
>
> ...the report for Oct 2016 is due on Oct 5, we have one +ve news to report
> with the recent release.
>
> On Mon, Oct 3, 2016 at 1:11 PM, sblackmon <sb...@apache.org> wrote:
>
>> Meaning: a next Incubator board report will need to be delivered monthly
>> for
>> at least the coming 3 months.
>> We better make sure there is positive news to report :-)
>>
>> I’ll get started on September 2016 and circulate a draft. Completing the
>> 0.3-incubating release is positive.
>> On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
>>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting
priorities for our next few releases]
Posted by sblackmon <sb...@apache.org>.
Year on latest release date should be 2016 not 2015
On October 4, 2016 at 10:51:23 AM, sblackmon (sblackmon@apache.org) wrote:
I haven’t been able to get into the wiki this morning, but here’s the draft report I’ve come up with.
--------------------
Streams
Apache Streams (incubating) unifies a diverse world of digital profiles
and online activities into common formats and vocabularies, and makes
these datasets accessible across a variety of databases, devices, and
platforms for streaming, browsing, search, sharing, and analytics use-cases.
Streams has been incubating since 2012-11-20.
Three most important issues to address in the move towards graduation:
1. Community growth and PMC maturity.
2. Demonstrate a consistent release schedule.
3. Participation of project community within related standards-bodies and
Apache projects.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
A vote to retire the project was initiated but cancelled after several
individuals on the IPMC list expressed new interest in helping the project
continue to grow and eventually graduate. The project is now on a monthly
reporting schedule.
How has the community developed since the last report?
dev@streams.incubator.apache.org
46 emails sent by 15 people, divided into 9 topics.
http://streams.incubator.apache.org
196 Sessions, 170 Users, 512 Pageviews
How has the project developed since the last report?
https://github.com/apache/incubator-streams-master
Excluding merges, 1 author has pushed 9 commits to master and 9 commits to all branches. On master, 8 files have changed and there have been 114 additions and 193 deletions.
https://github.com/apache/incubator-streams
Excluding merges, 1 author has pushed 6 commits to master and 6 commits to all branches. On master, 61 files have changed and there have been 85 additions and 66 deletions.
https://github.com/apache/incubator-streams-examples
Excluding merges, 1 author has pushed 12 commits to master and 15 commits to all branches. On master, 67 files have changed and there have been 549 additions and 761 deletions.
92 Issues closed with release of 0.3-incubating
7 new Issues opened
Date of last release:
2015-10-03 : 03-incubating release
When were the last committers or PMC members elected?
2016-09-28: Suneel Marthi elected as mentor / PMC member
Signed-off-by:
[ ](streams) Ate Douma
[ ](streams) Matt Franklin
[ ](streams) Suneel Marthi
On October 3, 2016 at 12:26:48 PM, Suneel Marthi (suneel.marthi@gmail.com) wrote:
...the report for Oct 2016 is due on Oct 5, we have one +ve news to report
with the recent release.
On Mon, Oct 3, 2016 at 1:11 PM, sblackmon <sb...@apache.org> wrote:
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I’ll get started on September 2016 and circulate a draft. Completing the
> 0.3-incubating release is positive.
> On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
>
Re: [DISCUSS] Community - call for help [Was: Setting
priorities for our next few releases]
Posted by sblackmon <sb...@apache.org>.
I haven’t been able to get into the wiki this morning, but here’s the draft report I’ve come up with.
--------------------
Streams
Apache Streams (incubating) unifies a diverse world of digital profiles
and online activities into common formats and vocabularies, and makes
these datasets accessible across a variety of databases, devices, and
platforms for streaming, browsing, search, sharing, and analytics use-cases.
Streams has been incubating since 2012-11-20.
Three most important issues to address in the move towards graduation:
1. Community growth and PMC maturity.
2. Demonstrate a consistent release schedule.
3. Participation of project community within related standards-bodies and
Apache projects.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
A vote to retire the project was initiated but cancelled after several
individuals on the IPMC list expressed new interest in helping the project
continue to grow and eventually graduate. The project is now on a monthly
reporting schedule.
How has the community developed since the last report?
dev@streams.incubator.apache.org
46 emails sent by 15 people, divided into 9 topics.
http://streams.incubator.apache.org
196 Sessions, 170 Users, 512 Pageviews
How has the project developed since the last report?
https://github.com/apache/incubator-streams-master
Excluding merges, 1 author has pushed 9 commits to master and 9 commits to all branches. On master, 8 files have changed and there have been 114 additions and 193 deletions.
https://github.com/apache/incubator-streams
Excluding merges, 1 author has pushed 6 commits to master and 6 commits to all branches. On master, 61 files have changed and there have been 85 additions and 66 deletions.
https://github.com/apache/incubator-streams-examples
Excluding merges, 1 author has pushed 12 commits to master and 15 commits to all branches. On master, 67 files have changed and there have been 549 additions and 761 deletions.
92 Issues closed with release of 0.3-incubating
7 new Issues opened
Date of last release:
2015-10-03 : 03-incubating release
When were the last committers or PMC members elected?
2016-09-28: Suneel Marthi elected as mentor / PMC member
Signed-off-by:
[ ](streams) Ate Douma
[ ](streams) Matt Franklin
[ ](streams) Suneel Marthi
On October 3, 2016 at 12:26:48 PM, Suneel Marthi (suneel.marthi@gmail.com) wrote:
...the report for Oct 2016 is due on Oct 5, we have one +ve news to report
with the recent release.
On Mon, Oct 3, 2016 at 1:11 PM, sblackmon <sb...@apache.org> wrote:
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I’ll get started on September 2016 and circulate a draft. Completing the
> 0.3-incubating release is positive.
> On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Suneel Marthi <su...@gmail.com>.
...the report for Oct 2016 is due on Oct 5, we have one +ve news to report
with the recent release.
On Mon, Oct 3, 2016 at 1:11 PM, sblackmon <sb...@apache.org> wrote:
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I’ll get started on September 2016 and circulate a draft. Completing the
> 0.3-incubating release is positive.
> On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
>
> Hi Steve, community, silent followers,
>
> In general the proposal and suggestions from Steve are all good steps
> forward.
>
> But I'm for now top posting and forking that discussion to try address
> everyone
> in the community directly, because I think there are other and more
> critical
> actions needed to make clear to the Incubator PMC that cancelling of this
> project retirement will not end up to be just a temporary pause.
>
> The first and highest priority action should be getting more and diverse
> involvement and active participation from the community.
> The steps suggested by Steve are definitely helpful and needed as well.
> But it just as well might end up remaining a one man's task list...
>
> Instead, we need to get more active input and suggestions/questions from
> others
> in the community, like Joey, our new mentor Suneel, and hopefully as well
> from
> the W3C ActivityStream 2.0 working group people, like Benjamin Young.
>
> And we need not just 'talk' feedback, but actual interest and participation
> with concrete contributions.
> (Suneel: I know you signed up just to mentor, which of course also is
> needed)
>
> We need to see and show serious promise for growth of the project
> community to
> the IPMC, and in a reasonable short time frame (a few months at most).
> Without that I think the changes of getting this project back on its feet
> will
> remain unrealistic, and then better be stopped.
>
> This also was indicated by the request from John Ament (the Incubator
> Chair), to
> switch back to monthly reporting for the coming 3 months, so the IPMC can
> monitor the progress and chances for success. And if not, probably will
> decide
> (or at least vote) for a final retirement after all.
> I agree with John this make perfectly sense, and I'll update the reporting
> schedule for Streams shortly to make it so.
>
> Meaning: a next Incubator board report will need to be delivered monthly
> for
> at least the coming 3 months.
> We better make sure there is positive news to report :-)
>
> I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
> to see what ideas he has and what concrete actions can take in getting the
> W3C
> ActivityStreams 2.0 people involved as well.
>
> And I'm explicitly calling out to the mostly silent community, including
> the
> other committers, to speak up and let us know what you might be able to do
> for
> the project *now*: ideas, feedback, testing, maybe even code contributions?
>
> Kind regards, Ate
>
> On 2016-09-28 22:00, sblackmon wrote:
> > All,
> >
> > Joey brought this up over the weekend and I think a discussion is
> overdue on the topic.
> >
> > Encouraging community growth and performing regular releases are on our
> list of graduation criteria.
> >
> > A few easy behaviors we can adopt to take to make progress on these
> goals:
> > - planning release versions around one or two significant improvements
> > - setting target dates to kick off upcoming releases
> > - prioritizing our backlog after each release
> > - discussing project and community milestones openly on the list
> > - organizing JIRA so that all contributors (especially new) can decide
> where it’s most important to focus their efforts
> >
> > I think to get things moving again and demonstrate we are capable of
> consistent progress, we should aim to perform a release once per month
> around the end of the month.
> >
> > As for what to focus on, I think it’s time to discuss adopting Activity
> Streams 2.0, figure out what form that transition would take, and get
> started down that path. Working implementations demonstrate the suitability
> of the standard and drive it’s adoption, and the prospects of this project
> are closely tied to those of the standard. Separate DISCUSS coming on this
> topic.
> >
> > Also important for the ‘reboot’ theme, we should delete any modules we
> aren’t going to maintain, and bring all modules we are going to maintain up
> to acceptable standards - exactly what that means is an open question but
> broadly they should have documentation, code comments, and tests at the
> level of a typical module in a typical TLP.
> >
> > Expanding the examples to demonstrate how to use streams providers and
> processors within various execution engines and fixing any bugs that have
> been reported is desirable as well. Adding at least one new example per
> release is a good target for now.
> >
> > I have created some future versions with target release dates in JIRA
> and invite all committers to associate existing or new issues with those
> releases, or anyone who can’t modify JIRA to summarize their thoughts and
> share with the list and I will incorporate those ideas into JIRA. This
> should be the default reference for anyone looking for a way to help - look
> at issues associated with the next few releases and the top of the backlog
> and pick something that appeals and is in line with your experience.
> >
> > Anything else that should be a top priority for the rest of the year? Or
> other ideas on improving planning and coordination?
> >
> > Steve
> >
> > On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org)
> wrote:
> > - This has already come up, but maybe ActivityStreams 2.0 support would
> broaden the community and motivate more work. It's also a concrete
> > goal to work toward so people would know where they can start.
> > - Steve and I did a little work here a few months ago, but the JIRA
> could reflect the priorities better and I think keep the community working
> in a common direction.
> >
>
>
>
Re: [DISCUSS] Community - call for help [Was: Setting
priorities for our next few releases]
Posted by sblackmon <sb...@apache.org>.
Meaning: a next Incubator board report will need to be delivered monthly for
at least the coming 3 months.
We better make sure there is positive news to report :-)
I’ll get started on September 2016 and circulate a draft. Completing the 0.3-incubating release is positive.
On September 29, 2016 at 1:26:28 AM, Ate Douma (ate@douma.nu) wrote:
Hi Steve, community, silent followers,
In general the proposal and suggestions from Steve are all good steps forward.
But I'm for now top posting and forking that discussion to try address everyone
in the community directly, because I think there are other and more critical
actions needed to make clear to the Incubator PMC that cancelling of this
project retirement will not end up to be just a temporary pause.
The first and highest priority action should be getting more and diverse
involvement and active participation from the community.
The steps suggested by Steve are definitely helpful and needed as well.
But it just as well might end up remaining a one man's task list...
Instead, we need to get more active input and suggestions/questions from others
in the community, like Joey, our new mentor Suneel, and hopefully as well from
the W3C ActivityStream 2.0 working group people, like Benjamin Young.
And we need not just 'talk' feedback, but actual interest and participation
with concrete contributions.
(Suneel: I know you signed up just to mentor, which of course also is needed)
We need to see and show serious promise for growth of the project community to
the IPMC, and in a reasonable short time frame (a few months at most).
Without that I think the changes of getting this project back on its feet will
remain unrealistic, and then better be stopped.
This also was indicated by the request from John Ament (the Incubator Chair), to
switch back to monthly reporting for the coming 3 months, so the IPMC can
monitor the progress and chances for success. And if not, probably will decide
(or at least vote) for a final retirement after all.
I agree with John this make perfectly sense, and I'll update the reporting
schedule for Streams shortly to make it so.
Meaning: a next Incubator board report will need to be delivered monthly for
at least the coming 3 months.
We better make sure there is positive news to report :-)
I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
to see what ideas he has and what concrete actions can take in getting the W3C
ActivityStreams 2.0 people involved as well.
And I'm explicitly calling out to the mostly silent community, including the
other committers, to speak up and let us know what you might be able to do for
the project *now*: ideas, feedback, testing, maybe even code contributions?
Kind regards, Ate
On 2016-09-28 22:00, sblackmon wrote:
> All,
>
> Joey brought this up over the weekend and I think a discussion is overdue on the topic.
>
> Encouraging community growth and performing regular releases are on our list of graduation criteria.
>
> A few easy behaviors we can adopt to take to make progress on these goals:
> - planning release versions around one or two significant improvements
> - setting target dates to kick off upcoming releases
> - prioritizing our backlog after each release
> - discussing project and community milestones openly on the list
> - organizing JIRA so that all contributors (especially new) can decide where it’s most important to focus their efforts
>
> I think to get things moving again and demonstrate we are capable of consistent progress, we should aim to perform a release once per month around the end of the month.
>
> As for what to focus on, I think it’s time to discuss adopting Activity Streams 2.0, figure out what form that transition would take, and get started down that path. Working implementations demonstrate the suitability of the standard and drive it’s adoption, and the prospects of this project are closely tied to those of the standard. Separate DISCUSS coming on this topic.
>
> Also important for the ‘reboot’ theme, we should delete any modules we aren’t going to maintain, and bring all modules we are going to maintain up to acceptable standards - exactly what that means is an open question but broadly they should have documentation, code comments, and tests at the level of a typical module in a typical TLP.
>
> Expanding the examples to demonstrate how to use streams providers and processors within various execution engines and fixing any bugs that have been reported is desirable as well. Adding at least one new example per release is a good target for now.
>
> I have created some future versions with target release dates in JIRA and invite all committers to associate existing or new issues with those releases, or anyone who can’t modify JIRA to summarize their thoughts and share with the list and I will incorporate those ideas into JIRA. This should be the default reference for anyone looking for a way to help - look at issues associated with the next few releases and the top of the backlog and pick something that appeals and is in line with your experience.
>
> Anything else that should be a top priority for the rest of the year? Or other ideas on improving planning and coordination?
>
> Steve
>
> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
> - This has already come up, but maybe ActivityStreams 2.0 support would broaden the community and motivate more work. It's also a concrete
> goal to work toward so people would know where they can start.
> - Steve and I did a little work here a few months ago, but the JIRA could reflect the priorities better and I think keep the community working in a common direction.
>
Re: [DISCUSS] Community - call for help [Was: Setting priorities for
our next few releases]
Posted by Ate Douma <at...@douma.nu>.
Hi Steve, community, silent followers,
In general the proposal and suggestions from Steve are all good steps forward.
But I'm for now top posting and forking that discussion to try address everyone
in the community directly, because I think there are other and more critical
actions needed to make clear to the Incubator PMC that cancelling of this
project retirement will not end up to be just a temporary pause.
The first and highest priority action should be getting more and diverse
involvement and active participation from the community.
The steps suggested by Steve are definitely helpful and needed as well.
But it just as well might end up remaining a one man's task list...
Instead, we need to get more active input and suggestions/questions from others
in the community, like Joey, our new mentor Suneel, and hopefully as well from
the W3C ActivityStream 2.0 working group people, like Benjamin Young.
And we need not just 'talk' feedback, but actual interest and participation
with concrete contributions.
(Suneel: I know you signed up just to mentor, which of course also is needed)
We need to see and show serious promise for growth of the project community to
the IPMC, and in a reasonable short time frame (a few months at most).
Without that I think the changes of getting this project back on its feet will
remain unrealistic, and then better be stopped.
This also was indicated by the request from John Ament (the Incubator Chair), to
switch back to monthly reporting for the coming 3 months, so the IPMC can
monitor the progress and chances for success. And if not, probably will decide
(or at least vote) for a final retirement after all.
I agree with John this make perfectly sense, and I'll update the reporting
schedule for Streams shortly to make it so.
Meaning: a next Incubator board report will need to be delivered monthly for
at least the coming 3 months.
We better make sure there is positive news to report :-)
I also cc'ed Benjamin Young (who AFAIK hasn't subscribed to this list)
to see what ideas he has and what concrete actions can take in getting the W3C
ActivityStreams 2.0 people involved as well.
And I'm explicitly calling out to the mostly silent community, including the
other committers, to speak up and let us know what you might be able to do for
the project *now*: ideas, feedback, testing, maybe even code contributions?
Kind regards, Ate
On 2016-09-28 22:00, sblackmon wrote:
> All,
>
> Joey brought this up over the weekend and I think a discussion is overdue on the topic.
>
> Encouraging community growth and performing regular releases are on our list of graduation criteria.
>
> A few easy behaviors we can adopt to take to make progress on these goals:
> - planning release versions around one or two significant improvements
> - setting target dates to kick off upcoming releases
> - prioritizing our backlog after each release
> - discussing project and community milestones openly on the list
> - organizing JIRA so that all contributors (especially new) can decide where it’s most important to focus their efforts
>
> I think to get things moving again and demonstrate we are capable of consistent progress, we should aim to perform a release once per month around the end of the month.
>
> As for what to focus on, I think it’s time to discuss adopting Activity Streams 2.0, figure out what form that transition would take, and get started down that path. Working implementations demonstrate the suitability of the standard and drive it’s adoption, and the prospects of this project are closely tied to those of the standard. Separate DISCUSS coming on this topic.
>
> Also important for the ‘reboot’ theme, we should delete any modules we aren’t going to maintain, and bring all modules we are going to maintain up to acceptable standards - exactly what that means is an open question but broadly they should have documentation, code comments, and tests at the level of a typical module in a typical TLP.
>
> Expanding the examples to demonstrate how to use streams providers and processors within various execution engines and fixing any bugs that have been reported is desirable as well. Adding at least one new example per release is a good target for now.
>
> I have created some future versions with target release dates in JIRA and invite all committers to associate existing or new issues with those releases, or anyone who can’t modify JIRA to summarize their thoughts and share with the list and I will incorporate those ideas into JIRA. This should be the default reference for anyone looking for a way to help - look at issues associated with the next few releases and the top of the backlog and pick something that appeals and is in line with your experience.
>
> Anything else that should be a top priority for the rest of the year? Or other ideas on improving planning and coordination?
>
> Steve
>
> On September 24, 2016 at 1:01:02 PM, apache (sblackmon@apache.org) wrote:
> - This has already come up, but maybe ActivityStreams 2.0 support would broaden the community and motivate more work. It's also a concrete
> goal to work toward so people would know where they can start.
> - Steve and I did a little work here a few months ago, but the JIRA could reflect the priorities better and I think keep the community working in a common direction.
>