Community Composer Plugin is still in IPZilla [1]. We are after some
questions so I hope that we receive +1 this week.
After approve and piggy back libs from orbit, can be merged.
Patch is ready to integrate with PDT build system. Things to do:
1. Add as maven module for PDT parent pom
2. Modify site.xml

What is state of community Composer plugin? Patch is ready to merge or
we have additional things to do? If we want first version ready for
Neon.1 we need to start integration. It's how I imagine process:

1. Merge community plugin to master (can be still in incubation directory)

2. Add community plugin to build system, mark it as
experimental/incubation (if you don't have time I can do this)

3. If we (Zend) will notice something useful in Zend plugin what is
missing we will merge it with community plugin

4. Later we can think what we should do with issues reported on github
for community plugin

In general I believe that community plugin will be that main plugin
and we just move/integrate some features from Zend version of plugin.

Yes, I was thinking about place in our gitroot where we can push
source code, even without making it visible to the world with update
site. Pushed code will be after IP review and it will be easier to
manage it. When initial product (like Composer support) will be ready
we can add it to category.xml with Incubator/Experimental label. For
example I can start and commit Zend Composer plugins.

Regarding existing pdt.incubator I also think that we should
terminate it.

Your plan looks good From our side (Zend) we have green light to
contribute our Composer support to PDT. Maybe we can reopen
Incubator and push code there to have full image. We can think about
things that can be taken from both implementations. For example we
integrated TM Terminal[1] in Console view for colored and
interactive output. Also if there will be problem with IP I can help
reimplement some parts.