> You need to specify at least one release in the
project metadata [4]; note that project plans are
version specific and that you should include a link to
the version-specific plan with the release information.
Done. Release 0.8 has been set in the portal,
pointing to a version-specific project plan url.
> I'd like to see increased project diversity,
but that's something that comes with time. Having the
project on the release train will help in that regard.
What sorts of things is the project doing to increase
diversity and grow community?
Increasing diversity is actually one of the main reasons
we are requesting to join the train.
We are actively communicating about the project
in the Lua community, and the feedback so far is very
positive ; see [6], for example. This recent blog post
[7] also had a huge impact on project adoption. We are
reaching to other projects (Corona SDK, VLC, and even
the World of Warcraft add-on developers community ;-))
via forums, blogs, twitter, … to work more closely with
them to provide tooling appropriate to their needs.
In terms of contributions, we already had several
feature requests, bug reports, and a couple of patches
already.
Last but not least, Koneki is not solely composed
of LDT –even though this is the most mature component–,
and the M2M tools that are being developed, or will be,
are discussed in the context of the M2M Industry Working
Group which gathers many different parties.
> The code base looks pretty mature. When do
you intend to graduate?
As you said, we need more diversity first. I am
pretty confident that we should have a couple new
committers on LDT pretty soon though. Also, there are
some features that in our opinion are pretty mandatory
to leave incubation (e.g. support for Lua interpreters).
The idea would be either to graduate whenever LDT will
be sort of feature-complete and the other
M2M tools are stable enough ; or –and that may actually
be my preference– whenever we have a working end-to-end
M2M toolchain, leveraging the M2M metamodel defined
together with the IWG. In this case that would be a
graduation combined with a 1.0 release.
> Are members from the project
participating in the cross-project mailing list?
Yes, I am already. I will ask another committer
to join as well.
I hope you don't feel too bored at the end of what
looks like a pretty verbose e-mail :)