Is this dead?

[phatcher]

The last commit was 3 months ago and there's a bunch of open pull requests - is anyone maintaining this anymore?

[martingbrown]

I was thinking the same thing.

[toobob]

doesn't look like anybody's working on anything anymore. sad

[mguinness]

I think part of the problem is that there is no roadmap for the product. The contributors are all volunteers which means the only time they get to work on it is in their spare time which is in short supply for many.

Most likely someone would need to act as project manager to manage the issues and to corral the devs to work on bugs/enhancements.

Part of the difficulty is that issues have become a dumping ground for problems and aren't getting closed by the OP when issues are resolved which doesn't help. Maybe using Probot: Stale to automatically close stale issues would help.

[SvenVandenbrande]

I talked with @jongalloway about it. It's not dead.

But he is the only one that's working on it for the moment.
He will also answer to some questions and pull requests...

[phatcher]

I think @mguinness idea of a roadmap would be useful as I don't mind contributing but it would be nice to have an overall direction and apply some of the patches such as code highlighting.

[SvenVandenbrande]

I agree, I also don't have a problem to contribute. But we need a direction. :)
But you will see some reactions from Jon in the future. :)

[mguinness]

Glad to hear the news, and from Jon no less. I think an area where people can help is issue triage. Maybe people can handle WordPress related issues, another Blogger etc. where they have knowledge on the platform. Request to become a collaborator so you can help close issues (over 400 open right now).

Also there are seven PR's from 2015. I seriously doubt they'll be merged now so they should be closed and resubmitted if needed. If issues and PR's are being addressed then that will go a long way to dispelling the abandonware label.

The one enhancement that could be worked on is plugins as the gallery is empty. I think if that can be rectified that would be popular.

[kathweaver]

I might be back too. I got discouraged when I couldn't compile the code to fix accessibility issues, and I've been off earning some money.

[phatcher]

@kathweaver if you have any spare let me know ;-)

[jongalloway]

Hey, folks, thanks for all the interest. No, the project isn't dead, the main contributors just have all been pretty busy. I'm planning to get a release out in May or June. I'm really busy until the Build conference (May 7-9), and we'll also want to see if there are any obvious Windows app features that become available at Build.

My current plan is to start by reviewing open pull requests, so the best way for anyone to help is to test open pull requests and comment on the pull request with your results.

If you have more time, two open pull requests that need more input are #596 and #658:

• Allow to add Code Snippets With Syntax Highlighting support (without need for extension) #658 (Allow to add Code Snippets With Syntax Highlighting support) is working but would be great to get some testing and input if it's ready to ship
• Adding the APPX packaging project #596 (Add APPX Packaging Support) would really help us get automated builds going. Right now we have the traditional (MSI/Squirrel) build fully automated, but the APPX build is still manual. Fixing that would allow us to push out more regular builds. If you have expertise on this, or the time to study up on it, let me know. I've got some notes on what needs to happen. Right now we have a pull request, but it doesn't build. Maybe it's as simple as troubleshooting the PR build break?

I'm going to close this issue to encourage people to file separate specific issues on features or problems you're having rather than general project health discussion.