I'll suggest you guys move on with the release without Spring
integration... We're taking this one back to the drawing board.

On Wed, Aug 2, 2017 at 5:38 PM, Tony Faustini <[email protected]> wrote:

> iota
>
> Open source system that enables the orchestration of IoT devices.
>
> iota has been incubating since 2016-01-20.
>
> Three most important issues to address in the move towards graduation:
>
> 1. An initial release of iota
> 2. Building a more active community
> 3. Consistency in the discussions on mailing lists/ steady flow of source
> code
> contributions
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> We have @crostofolini and @rafaelweingartner working on integrating the
> Spring framework into iota (pull request 35)
>
> We are waiting on a jar file to be removed from the test suite so that
> an initial release of the software can be produced. (The jar file is
> related to
> iota tests - need committer to publish the source code - enabling us to
> remove the
> jar artifact enabling the initial release of the software).
>
> The initial release will include the Spring integration if the needed
> fixes are
> in place otherwise the initial release will proceed without the Spring
> Framework
> Integration.
>
> Ticket's are in place for the initial release.
>
> How has the project developed since the last report?
>
> Interest in using iota (including the Spring Framework) outside the
> committer group
>
> The email reflectors for dev and users have become more active.
>
> New functionality was added to iota - global performers.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>  [ ] Initial setup
>  [X] Working towards first release
>  [X] Community building
>  [ ] Nearing graduation
>  [ ] Other:
>
> Date of last release:
>
>  XXXX-XX-XX
>
> When were the last committers or PPMC members elected?
>
> Yes - Barbara Gomes was added as a committer on 12/02/2016

Reply via email to