Any reason not to just open source it? Personally I'd love to hack on it :-) IANAL, but IMHO AGPL would be a good fit here as it complies with LGPL and also ensures nobody besides you (the copyright holder) can stand it up for profit without contributing back).

▲

netdevphoenix 7 hours ago | parent | next [-]

> Any reason not to just open source it?

Mmmm...potential commercialisation? Always find it curious that people expect to get source code for free in ways that they don't do for other work (ask George Martin to release his drafts and notes).

▲

sroussey 5 hours ago | parent | next [-]

Or the other likely version: prevent commercialization. No source means that someone can’t make a fork, put on a new domain, run ads and charge money for his work.

▲

mbesto 7 hours ago | parent | prev | next [-]

The parent commenter is making that comment because this is precisely the nature of why the GPL license exists. Most of the processing of this application is FFMPEG, so why should someone who has done zero development on that library commercialize it?

▲

afavour 6 hours ago | parent [-]

Most of the processing of the application is FFMPEG yes, but there's a whole lot of application outside of the processing. Video editors UIs that don't make you want to tear your hair out are a valuable commodity and I think OP has the right to commercialize that if they want to. They just need to use FFMPEG in the right way as they do it.

	▲	mbesto 3 hours ago \| parent \| next [-]
		This application doesn't work without FFMPEG. I'm not arguing that the wrapper isn't valuable, I'm saying there is a significant chunk of it that is required for us to work is an open source library.
	▲	jpc0 3 hours ago \| parent \| prev [-]
		From what I understand about this application ffmpeg of only used for export? That is very little of the processing of true, they mentioned the webcodec is used extensively and likely the only real requirement on ffmpeg is muxing into mp4 which to be entirely honest isn't much processing.

▲

mghackerlady 6 hours ago | parent | prev | next [-]

The problem is you can commercialise free software if you're creative about it. RMS made a decent amount of money working on emacs, redhat and SUSE exist, google has managed to commercialise chromium

▲

freedomben 5 hours ago | parent [-]

> The problem is you can commercialise free software if you're creative about it.

Did you mean to say that it is a problem? From the rest of your comment, and in the context of GP's comment, it sounds like commercializing is NOT a problem.

	▲	mghackerlady 5 hours ago \| parent [-]
		prev said that they might not be willing to release the source code so they can commercialise it

▲

freedomben 7 hours ago | parent | prev | next [-]

> Mmmm...potential commercialisation?

Hence why I asked the question... And not everybody does everything for commercial reasons, so it would be dumb to assume that and therefore not ask the question.

> Always find it curious that people expect to get source code for free in ways that they don't do for other work (ask George Martin to release his drafts and notes).

Where in my question did you get that I expect to get source code for free in ways that I don't for other work?

But regardless, you do know that open source is a common thing right? People open source things all the time, especially on HN.

Also OP already says they don't do any uploading of your videos to the cloud, so this thing already runs local-only. It's not like there is a shortage of video editors around (including ... open source ... video editors)

▲

randomtoast 6 hours ago | parent | prev [-]

[dead]

▲

kolx 6 hours ago | parent | prev [-]

I never maintained an open source project and not sure how to even do it properly. I am also not sure how much effort would I have to put to an open source project. I imagine I would need to collaborate with a pretty much anyone who has an interest in the area. Again not that I mind just not sure how much time I have to spare. Right now this is a really slow process and tbh I have to rely on manual testing at least for the editor.

	▲	Mashimo 6 hours ago \| parent \| next [-]
		Nah, besides sharing the code you don't have to do anything. Most people would want you to upload the code to github, then they can star and clone it with ease. But you don't have to have an issue tracker, and you certainly don't have to read any of the issues or pull request. You can ignore or disable that. I think even just having a up to date .zip with all the code would be technically enough.
	▲	qingcharles 4 hours ago \| parent \| prev [-]
		You don't have to collaborate with anyone. Just stick the code up on GitHub and if people file issues or PRs, then you can engage or not as you please. There are plenty of projects that are open source but don't accept any public modifications. You might just find you end up with some folks who genuinely want to help out, though.