v1.0 roadmap?

I agree that this would help making a choice to move on to Harmony or use another solution.

Hi both, I should be able to bash something out over the next day or so.

@dolu what other solutions were you considering?

Well,

I'm considering - as you say here https://www.drupal.org/node/2237553 and in this discussion also https://www.drupal.org/node/2205349 - either the core forum + advanced_forum drupal modules or a third-party integration (IPB, phpBB...).

The latter doesn't please me while the first seem a quite aged - meaning non-modern - solution.

With a roadmap, I could see if I can implement and work on the Harmony solution for the project I'm working on or if it would be better to wait maybe for a next project.

Do you feel harmony_core is ready to use in production? (or at least that it will be ready in next couple of months?)

Gotcha, always good to know what people see as alternatives!

On the stability of harmony_core, we're in a good place and it's in use on a number of live production sites (one I can vouch for has been live for 4/5 months now. I'm happy for it to sit as dev though in truth I could easily see throwing out an alpha or possibly beta to make things a bit more obvious.

Harmony Core right now is feature complete from my point of view (though always possible for new things to come in) and it's about creating and enhancing the modules around core.

I've recently made a slghtly better harmony site which has a list of significant modules which are in the ecosystem:
http://www.getharmony.io/resources/projects

For future stuff or things happening now...

Harmony Stats
Now that Event Data Store module has its kinks ironed out there's a mountain of stats based information that will be available and provide useful insight into the behaviour of a sites community. Basically Google Analytics in site, available to views based off of events you care about (as long as you've setup cron properly).

Distro
The first few pieces are in place, I need to build this out so we've got a Commerce Kickstart type thing happening, this has it's own requirements which are:
- Admin theme/experience
- Frontend theme (on the radar and mocked up as frontend code here: http://frontend.getharmony.io)

Comstack/Communications Stack
I see notifications & messaging as integral to a proper community solution we can provide:
Facebook style messaging
Thread subscriptions
Notifications (hooked into subscriptions, other events such as @ mentions in content)

That's what's currently in my head that I'm willing to share (got some very cool stuff in mind). As always I work for money (I like to eat) so the above comes about when someone sponsors the work more or less.

I'm happy for it to sit as dev though in truth I could easily see throwing out an alpha or possibly beta to make things a bit more obvious.

This should be a good point to adoption of Harmony, I guess it will make people more confident to use it.
With an alpha/beta version, major rework of the module without automatic upgrade (or at maximum a small easy upgrade path) or regressions shouldn't happen anymore.

Also, with more people using it comes also more issues in the queue.

I would be glad to see a release! :)

The action I'll take from this is to tag an alpha release, expect it before Monday.

Is there anything else that would encourage you to use Harmony over another solution? Or anything else you'd like to know about.

Well,

Personnaly I may (not quite sure at this time) need to set a different vocabulary than the harmony_category.

For now it is hardcoded, as you already said here : #2303153: Select a different taxonomy vocabulary

Please note that this "issue" also exists with core Forum/Advanced forum modules : #1573112: Change forum default vocabulary

I'll continue this request in the dedicated issue.

Do you plan to release an alpha/beta version soon?

I'm including Harmony core into my project and that would help me keeping track of the future updates.

Thanks!

I'll tag an alpha today!

We now have an alpha release! Please read the release notes carefully as I have just made a tweak to two permission names (and with that, that's the last of the breaking changes).

https://www.drupal.org/node/2459047

Great! :)

I'll use tagged releases from now on instead of dev version.

I'm ok to let this issue ride for a bit as people will have the same question I reckon.

On alpha versions, it's sods law that when you tag a release you get a wave of issues come in :) I don't expect this to change or won't worry about this too much. In what may be an odd move compared to other modules I think I'll tag a new alpha every couple of weeks (provided there's reason to). This will result in smaller incremental changes and whilst seem mental, make it easier to report and debug issues.

Hey, I was just curious if you have plans for Drupal 8, but didn't want to make a new issue.

Good question! Right now no. Once we hit a 1.0 release with decent usage I'll start thinking about this but the truth is the (planned) ecosystem is so huge there's plenty of D7 to do :)

I look forward to D8 development but there's the major version transition stuff to happen, Harmony is heavily reliant on the larger contrib community and I remember how long D6 to D7 took and that was without the whole shift we're facing now. We'll be there, but not for some time yet.