Identify the canonical location & maintainer of Feature Server

This project has been sleeping for literally ages. Nobody stepped up, there are no actions, of any "core-maintainers", no further development and no statements at all.

At some point we have to stop waiting and actually for me, thats now.

Phase2 can join the work here and we can join efforts.

And out of my experience with Features, Spaces and other great devseed projects, they stand still for a while and i cant see phase2 taken up all this projects. Iam not sure they even tend to, i mean that means binding a lot of man-power to the projects which have quiet some complexity and code-base.

To the "apps" thing:
Thats more a replacement for Features then for the fsever. The fserver shouldnt even be called "feature server". It more a replacement for the "project" project and has not really anything directly todo with features themself. It can and does host any kind of drupal project.

I have already implemented support for new style git tags and for proper sorting once you reach beyond alpha/beta/rc9. Feel free to cherry pick and integrate the changes from over at http://github.com/phase2/FeatureServer. I dont have any problem contributing to FeatureServer work here, makes sense to be central. Add me as a maintainer if you'd like.

You are correct though that Apps is more an extension of Features, but that said there are extensions of Feature Servers that are coming into the mix too, used to support Apps hosted on Feature Servers. It is just another module though so there is no reason that they cannot all coexist, they are doing different things right now, and if they need to be merged in the future it should not be that difficult.

hi Febbraro

i have implemented the "new git tags" also, and thats one of those points we need a central "fserver project" - so we dont double effort over and over again :). I will def. look at your patch, my implementation was more an upgrade-like thing.

If you work on the fserver activily iam very happy to add you as a maintainer. Overall, i have started this projects to centralize the effort, so iam happy for every single person helping making the fserver project a cool one.

We are using the fserver together with aegir and:
- http://drupal.org/project/update_feed_api
- http://drupal.org/project/update_feed_cck
- http://drupal.org/project/drush_make_ui

The first one can handle and unlimitted ammount of fserver on different locations and also drupal.org. so you kind of have a system like a "apt repo" and you can configure were to fetch those modules from.

Later on, using update_feed_cck, you can first chose which server you want to chose the module of ( so there can be several version of modules from different server), and then select the module / version ( all autocompletition ).

And thats were i actually see the Feature-Server in the future. A "sharing room" for those features, apps or whatever you like. This should help drupal sharing-ecosystem and esp. those "ready to use features".

Everybody running a feature server can run a translation server also, as the they integration OOTB. Overall we have a perfect way to manage and release internal projects and share them to others.

Features / Apps:
Its great having an alternative, eventhough i those projects need a lot of effort and integration. And will most like make no sense, with the current drupal architecture, having 2 of those projects ( eventhough ctools exportables can be seen as an general integration for both ), when thinking about the effort of all the contribus integration with apps / features. But i guess that is a different topic.

for my taste, that one is cleared out. Febarro as you the main person to ask in this regards, i would be hoping you to comment on this. If you think its fine working here on d.o ( you are added as a maintainer ), centralized the effort here to get the fserver project up to speed, then just close this issue or comment what ever you think about.

Just wanted to say thanks for stepping up on this, Eugen. I didn't even know of Febarro's version on github and it's great to have a centralized place for combining efforts!
I am using this module for one of my feature servers now and looking forward to future versions! :)

Waiting for over 2 weeks here now, closing this issue.

thank @ bforchhammer

I'm also glad that someone finally stepped up and brought some attention to this... I was afraid Feature Server was a dead project. So if we are using 6.x-1.0-beta1 from the DevSeed server, what would you recommend we do in order to ensure we have the latest and greatest version, and continue to receive updates? Should we upgrade to the 6.x-1.1 version here?

Yes you can upgrade. 1.1 is stable, we are using it in production, daily based with ~1000 releases and 100 projects of every type ( libs, themes, core, modules)