You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iota.apache.org by Tony Faustini <to...@litbit.com> on 2017/05/04 03:15:15 UTC

Draft iota report for April

Hi all, sorry for the late notice. I will be submitting an iota report by the end of today. Below is a draft - input welcome. 
-Tony


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 had a few more people get engaged in the process. In particular 
Gunnar Tapper from Trafodian is helping us get a release done. 
Omkar Prabhu and Rutvij Clerk have made commitments to help with performers and 
the release process. Barbara Gomes and Tony Faustini will be giving a 
presentation and demo on how to develop performers 
(components for iota at ApacheCon). Hoping this will get more folks engaged
in development and use of iota.

How has the project developed since the last report?

We have stated the process of a release. We have some cleanup to do in 
the code base. We also need to get Rutvij Clerk's GPG key signed by an 
Apache committer who is in the "Apache circle of trust". Tried to get this done 
locally
but not been successful. Perhaps at the upcoming ApacheCon in Miami. We were 
hoping to have this done by ApacheCon. 

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:

  None yet

When were the last committers or PPMC members elected?


Re: Draft iota report for April

Posted by Tony Faustini <to...@litbit.com>.
Hi Justin,

1) https://issues.apache.org/jira/browse/IOTA-40 <https://issues.apache.org/jira/browse/IOTA-40> this is the cleanup ticket.

2) Barbara Gomes can have her key signed as she will be at ApacheCon and she can then sign Rutvij’s key

3) If we can move forward without a key we will do so immediately

Thanks
-Tony


> On May 3, 2017, at 8:33 PM, Justin Mclean <ju...@classsoftware.com> wrote:
> 
> Hi,
> 
> I still don't see any meaningful progress towards making a release.
> 
> It’s seems to me that again development and conversations may be happening off list.
> 
> At this time it may be an idea to start discussing if Apache is actually a good fit for this project or if it would be better off on GitHub? Perhaps once the project has got used to development in the open and built a community on GitHub then possibly consider coming back to Apache? Do you or any other mentors have any thoughts on this?
> 
>> We have stated the process of a release. We have some cleanup to do in 
>> the code base.
> 
> Can you point me to the clean up you mentioned in git? I see a couple of checkin in the last month, the previous ones several months before that.
> 
>> We also need to get Rutvij Clerk's GPG key signed by an 
>> Apache committer who is in the "Apache circle of trust". Tried to get this done 
>> locally but not been successful.
> 
> As has been discussed have the key signing this is NOT a requirement for a release.
> 
> Please just make a release. It doesn’t have to be perfect. The longer you delay this the more likely the project will is likely to move to the attic.
> 
>> Perhaps at the upcoming ApacheCon in Miami. We were 
>> hoping to have this done by ApacheCon. 
> 
> There is likely to be a key signing party at ApacehCon but Rutvij will need to be physically present to get his key signed.
> 
> Thanks,
> Justin


Re: Draft iota report for April

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

I still don't see any meaningful progress towards making a release.

It’s seems to me that again development and conversations may be happening off list.

At this time it may be an idea to start discussing if Apache is actually a good fit for this project or if it would be better off on GitHub? Perhaps once the project has got used to development in the open and built a community on GitHub then possibly consider coming back to Apache? Do you or any other mentors have any thoughts on this?

> We have stated the process of a release. We have some cleanup to do in 
> the code base.

Can you point me to the clean up you mentioned in git? I see a couple of checkin in the last month, the previous ones several months before that.

> We also need to get Rutvij Clerk's GPG key signed by an 
> Apache committer who is in the "Apache circle of trust". Tried to get this done 
> locally but not been successful.

As has been discussed have the key signing this is NOT a requirement for a release.

Please just make a release. It doesn’t have to be perfect. The longer you delay this the more likely the project will is likely to move to the attic.

> Perhaps at the upcoming ApacheCon in Miami. We were 
> hoping to have this done by ApacheCon. 

There is likely to be a key signing party at ApacehCon but Rutvij will need to be physically present to get his key signed.

Thanks,
Justin