Any plans to open source?

[erquhart]

Hi there - great project! Looks like the actual source is kept offline and only the build files are being added to this repo. If you open source it, the community can help make it better. Any plans to do that?

[rikschennink]

Thanks! The plan is to release the source later this year.

To be able to better facilitate pull requests and new ideas I want to have more unit tests and need to restructure the repository. Without that, it'll cost way too much time to support incoming improvements/suggestions so therefore I've currently only released the build targets.

[paukul]

With full respect for your decision, I gotta say it's quite frustrating to figure out what's happening in the source when something isn't working out as expected right now. Can't you handle the constraints on your time with a disclaimer in the readme? Access to the vanilla code would working with this great library way, way easier ;-)

[rikschennink]

I understand, I’m trying to get this done ASAP but it’s not the only thing on my plate. I’d rather not have pull request than have pull requests I can’t review, judging from the quality of certain issues a simple entry in the readme would not be enough.

[Sopamo]

I'd like to throw in my two cents here. I'm currently implementing filepond into one of our projects. The UI is really nice.
However not being able to look at the source makes things really difficult from time to time and also leaves a bad aftertaste, because it seems like you somehow don't want this to be open source at all. I can understand your decision regarding pull requests, but I'd really like you to reconsider this, I think not having the source available really hinders the progress of this great project.

[rikschennink]

I hear you @Sopamo

because it seems like you somehow don't want this to be open source at all

This is not helping. If I didn't want it to be open source I would've stated that in an earlier comment.

[Sopamo]

After reading my comment again I realized it didn't sound as I meant it. I tried to explain, that without reading your comment on this issue it seems like you don't want this project to be open source. The problem is, that almost no one will ever read your comment here, so people will wonder why the project isn't open source and probably won't come to the correct conclusion. Maybe you could at least link this issue in the readme?

[rikschennink]

@Sopamo Excellent idea I will do that right away.

Thanks for building a Laravel FilePond server!

[Sopamo]

I'm happy to support this great project :) I actually wanted to wait a bit to test the code more before telling you about it and maybe asking if you could link it in the readme, so Laravel people would find it quickly.

[rikschennink]

@Sopamo If you wish I can remove the link (I added it to the README as well, hadn't read your reply).

[Sopamo]

It's fine I guess, the code isn't very complex and works fine for our project.
Sorry guys, I'll stop spamming this issue now with irrelevant comments :)

[rikschennink]

I've started with open sourcing the plugins, they should all be open source in the next few weeks.
https://github.com/pqina/filepond-plugin-file-encode

[rikschennink]

I just published version 4.3.4 of FilePond, with this release all plugins and FilePond itself are now truly open source.

👉 https://twitter.com/rikschennink/status/1110154018758770692