Just wondering on the status of this project

Hey Jef-vratny,

Sorry about the delay on progress. Updates on Wave are picking up again :) I had some work to finish up for the DevDojo site. I would be open to adding some contributors to the github repo if you are interested.

Open Source projects can be a full-time gig to manage at times, so I don't think I'll open source it. I also wanted to let you know some of my focuses for Wave moving forward. (not set in stone, but I want to let you know where I'm coming from) I want to be cautious not to add too many features because I don't want Wave to be overly opinionated. One perfect example of this would be Spark. Spark is great; however, it is tightly coupled to VueJS and creating your own features and building on top of the functionality is kind of a pain.

So, my goals for version 1.0 is bug fixes, cleanliness, simplicity, and keeping functionality lean in order for the developer to eventually take the platform and grow their SAAS outside the boundaries of Wave.

When someone asks the SAAS creator what their application is built on. I don't want the developer to only have to say "It's built with Wave", I want them to be able to say, "It is built with Laravel (and voyager admin). We leveraged the features of Wave and built out the app to what it is today". Not sure if my point is getting across, but I hope it is (again, this is not set in stone, and this response could be a result of one-to-many cups of coffee)

Ok, let me know if you would like to be added to the repo and let me know in your opinion how you would like to see this project grow.

Thanks! Talk to you soon.

i'm with @tnylea the wave project is a great starting point for your own SAAS project.

And adding a bunch of features will clutter the source but it could ba a idea to create some hooks for Wave @larapack.io ore somewhere else

So we can add features without touching the existing code.

Thanks @andrewo0,

I'm definitely going to add a more robust hook, plugin feature so that way expansions can be created for Wave :)

Glad to hear you'll continue to work on the project.

I'm actually not wanting features, but a more robust build, packaging and update process seems pretty critical to success. Until it can be isolated as a dependency in a package, we're stuck forking it into our own repos and manually installing, which isn't really sustainable or scalable for my needs. If it were open source, that'd be a no brainer contrib, not sure how the IP dynamic works in this scenario.

Great! Totally. Couldn't agree with you more.

I'll look into ways that I can distribute a private package, and turn it into more of a package :)

@tnylea, Any update on this?

I'm beginning to feel frustrated with Wave.

Composer 2.0 won't install composer dependencies when it comes out.

Deprecation warning: require.voyager-themes is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "a-z0-9/a-z0-9". Make sure you fix this as Composer 2.0 will error.

There are 14 security related issues with dependencies and managing these manually is unworkable for production projects.

There are problems with the UI in either Bootstrap or UIKit in Safari, which are also a pain to fix in production as new releases will just overwrite patches.

I was excited with Tony's vision for Wave and his work on Voyager, however now progress on both projects has slowed to a point where I am re-considering whether to deploy either in production environments.

Spark may be a pain to extend, however it's an regularly bugfixed and updated pain. At the moment both Wave & Voyager feel like abandonware.

Sorry to be so frank, but this is my opinion as things stand now.

Hey @rjkmelb,

I want to say that I'm sorry about not releasing these updates earlier. I'm currently working with Mark Topper who was one of the original creators of the Hooks that were built with Voyager. We are going to have to restructure the way a few things are done with Voyager and Hooks, but should have a solution soon.

These dependencies that you are talking about. Are these all front-end dependencies? If so, this shouldn't be too much of an issue. Can you share a screenshot of that.

I will work on these UI fixes, can you send me a more detailed list of these bugs and I will work on them this week.

I appreciate your patience on this and feel free to send me over your Github username and I can make you a collaborator on this project if you would like :)

Thanks! Talk to you soon.

Hey @tnylea, Please add team option like add user with role feature for each customer. its very important to a SAAS.

This is the list of dependencies with issues. I disagree that these aren't much of an issue if they are on the front end. They are security risks in and of themselves and should be addressed.

For example in the Bootstrap dependencies there are issues that could be exploited from the front end to arbitarily execute code.

CVE-2018-13797 macaddress

From a repo point of view, addressing these is quite straight forward, however when we're dealing with a downloadable zip file that has all the code bundled, unless we create a new repository and manually address the issue we're kind of stuck with what we're given. Then when addressing changes on our own local repo when a new version comes out then refactoring changes becomes messy.

I did note the new Voyager release but even that has left a number of issues unaddressed, 39 open pull requests of which probably 12 should have been included in 1.2.0 and there are some serious issues open that have been there since last year and unaddressed.

I appreciate Voyager is an open source volunteer effort, however when people submit important PRs to solve obviously problematic issues and these get relegated to a later release then that's disheartening to see.

Hi tnylea, thanks for creating Wave. You mentioned that you would publish an update on Wave last week - Or did I misunderstand? Anyway - Would be great to know when the next update will be (and what it includes).

Hey guys,

Yes I am currently resolving an issue with the Voyager hooks where they need to have a vendor folder to work with Composer 2.0. I will also be addressing these security risks. @rjkmelb Voyager is currently being maintained by a few people but you are more than welcome to join in on some of the issues you think need to be resolved.

I am additionally working on an integration with https://paddle.com/ this way users can choose between 3 billing options. I have currently put this branch on hold and started resolving the voyager hooks issue and will be fixing the security risks as well.

Anyone here want to join the github repo as a collaborator, let me know :) Thanks!

Hey @tnylea, What is the progress of this little project?