Settling governance matters

PPPDUD commented

2026-03-26 13:22:49 -05:00

(Migrated from github.com)

In recent days, me and @codingisfun2831t have had several disagreements on the path forward for Sparkle. I don't think that it's productive for us to constantly play tug-of-war over the only surviving fork of the abandoned Crackle codebase, so here's my proposal going forward.

Governance of Sparkle

Sparkle shall be governed by me, @e016, and any other maintainers who I add later on. We shall each try our best to work together peacefully and make compromises where needed. The build.sh script shall not be edited by anybody other than me except via a pull request, unless I specifically request otherwise.

Sparkle shall not require the installation of Node.js on the building party's machine in order to be built and packaged.

Target browsers

Sparkle shall not have releases for Firefox or its derivatives.

Governance of the new Crackle

@codingisfun2831t and any other maintainers who they appoint shall be permitted to work on a fork of Sparkle, named Crackle, which shall have releases for Firefox targets, but not Chromium ones. We shall not compete with one another when collaboration is possible, and any significant, useful changes made in Crackle shall be proposed in an upstream PR so that Sparkle can consider its merits and have equal capabilities.

@codingisfun2831t @e016 Would you all be willing to follow this policy from now on if I do so as well?

In recent days, me and @codingisfun2831t have had several disagreements on the path forward for Sparkle. I don't think that it's productive for us to constantly play tug-of-war over the only surviving fork of the abandoned Crackle codebase, so here's my proposal going forward. ## Governance of Sparkle Sparkle shall be governed by me, @e016, and any other maintainers who I add later on. We shall each try our best to work together peacefully and make compromises where needed. The `build.sh` script shall not be edited by anybody other than me except via a pull request, unless I specifically request otherwise. Sparkle shall not require the installation of Node.js on the building party's machine in order to be built and packaged. ### Target browsers Sparkle shall not have releases for Firefox or its derivatives. ## Governance of the new Crackle @codingisfun2831t and any other maintainers who they appoint shall be permitted to work on a fork of Sparkle, named _Crackle_, which shall have releases for Firefox targets, but not Chromium ones. We shall not compete with one another when collaboration is possible, and any significant, useful changes made in Crackle shall be proposed in an upstream PR so that Sparkle can consider its merits and have equal capabilities. @codingisfun2831t @e016 Would you all be willing to follow this policy from now on if I do so as well?

e016 commented

2026-03-26 13:25:55 -05:00

(Migrated from github.com)

I kind of get having separate versions of Sparkle, but why can't these be branches of the main Sparkle repo?

PPPDUD commented

2026-03-26 13:29:04 -05:00

(Migrated from github.com)

I kind of get having separate versions of Sparkle, but why can't these be branches of the main Sparkle repo?

@codingisfun2831t wants a seperate branding and organization.

> I kind of get having separate versions of Sparkle, but why can't these be branches of the main Sparkle repo? @codingisfun2831t wants a seperate branding and organization.

e016 commented

2026-03-26 13:40:01 -05:00

(Migrated from github.com)

I don't think that it's productive for us to constantly play tug-of-war

@codingisfun2831t only made a couple of requests to you; that was it.

> I don't think that it's productive for us to constantly play tug-of-war @codingisfun2831t only made a couple of requests to you; that was it.

PPPDUD commented

2026-03-26 13:41:34 -05:00

(Migrated from github.com)

I don't think that it's productive for us to constantly play tug-of-war

@codingisfun2831t only made a couple of requests to you; and after those suggestions, now we're splitting up.

How was he supposed to know that you don't want more organisations? He has said about the Crackle/Sparkle brand, although not recently.

I didn't really express my opinions because I was afraid of starting a flame war. I want to split up now and not later, because otherwise we're bound to enter a worse conflict at some point in the future, and I don't want it to come to that.

> > I don't think that it's productive for us to constantly play tug-of-war > > [@codingisfun2831t](https://github.com/codingisfun2831t) only made a couple of requests to you; and after those suggestions, now we're splitting up. > > How was he supposed to know that you don't want more organisations? He has said about the Crackle/Sparkle brand, although not recently. I didn't really express my opinions because I was afraid of starting a flame war. I want to split up now and not later, because otherwise we're bound to enter a worse conflict at some point in the future, and I don't want it to come to that.

codingisfun2831t commented

2026-03-26 13:43:55 -05:00

(Migrated from github.com)

I really do not think having a fork would be productive. And to be honest, I am fine with the Sparkle naming, but there SHOULD be a seperate organization! It'll allow a good logo, and provide seperation! I don't want any wars, no, I just wanna see a modding platform flourish!

You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise. And suddenly now you're trying to fully seperate Crackle! We should've just waited for @Tethrarxixet to come back on...

I really do not think having a fork would be productive. And to be honest, I am fine with the Sparkle naming, but there SHOULD be a seperate organization! It'll allow a good logo, and provide seperation! I don't want any wars, no, I just wanna see a modding platform flourish! You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise. And suddenly now you're trying to fully seperate Crackle! We should've just waited for @Tethrarxixet to come back on...

codingisfun2831t commented

2026-03-26 13:44:40 -05:00

(Migrated from github.com)

And express your opinions! Its better to express them then have Crackle/Sparkle be stuck in a everlasting war over ownership.

PPPDUD commented

2026-03-26 13:48:03 -05:00

(Migrated from github.com)

I really do not think having a fork would be productive.

Fair. I can understand why it might be a bad idea.

And to be honest, I am fine with the Sparkle naming, but there SHOULD be a seperate organization! It'll allow a good logo, and provide seperation! I don't want any wars, no, I just wanna see a modding platform flourish!

I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase.

You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise. And suddenly now you're trying to fully seperate Crackle! We should've just waited for @Tethrarxixet to come back on...

If @Tethrarxixet comes back and manages to unify us under a new Crackle leadership that can move forward at a reasonable pace in the areas where they're involved, I'd be happy to join, but right now they don't seem to be very active on GitHub.

And express your opinions! Its better to express them then have Crackle/Sparkle be stuck in a everlasting war over ownership.

Understood. Neither of us want a civil war.

> I really do not think having a fork would be productive. Fair. I can understand why it might be a bad idea. > And to be honest, I am fine with the Sparkle naming, but there SHOULD be a seperate organization! It'll allow a good logo, and provide seperation! I don't want any wars, no, I just wanna see a modding platform flourish! > I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase. > You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise. And suddenly now you're trying to fully seperate Crackle! We should've just waited for @Tethrarxixet to come back on... If @Tethrarxixet comes back and manages to unify us under a new Crackle leadership that can move forward at a reasonable pace in the areas where they're involved, I'd be happy to join, but right now they don't seem to be very active on GitHub. > And express your opinions! Its better to express them then have Crackle/Sparkle be stuck in a everlasting war over ownership. Understood. Neither of us want a civil war.

codingisfun2831t commented

2026-03-26 13:49:34 -05:00

(Migrated from github.com)

I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase.

Sure, I have actually changed my opinion on it and its fine.

> I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase. Sure, I have actually changed my opinion on it and its fine.

PPPDUD commented

2026-03-26 13:52:52 -05:00

(Migrated from github.com)

I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase.

Sure, I have actually changed my opinion on it and its fine.

You're alright with being a part of the Mojavesoft organization?

> > I don't want to crusade over whether or not Sparkle deserves an organization, but my viewpoint here is unlikely to change in the near future: Sparkle does not warrant independence until it has a considerably-larger userbase. > > Sure, I have actually changed my opinion on it and its fine. You're alright with being a part of the Mojavesoft organization?

codingisfun2831t commented

2026-03-26 13:59:02 -05:00

(Migrated from github.com)

Yes, just when Sparkle actually (hopefully!) grows and is usable, we should at that point switch to a seperate organization. But for now, its fine.

PPPDUD commented

2026-03-26 14:02:31 -05:00

(Migrated from github.com)

Yes, just when Sparkle actually (hopefully!) grows and is usable, we should at that point switch to a seperate organization. But for now, its fine.

Awesome! Thanks for working that out with me. I really appreciate that we got to share our opinions and reach a compromise.

> Yes, just when Sparkle actually (hopefully!) grows and is usable, we should at that point switch to a seperate organization. But for now, its fine. Awesome! Thanks for working that out with me. I really appreciate that we got to share our opinions and reach a compromise.

PPPDUD commented

2026-03-26 14:05:20 -05:00

(Migrated from github.com)

I still think that we need a more formalized system of governance though, because I don't like the fact that we keep ending up in little disputes over the same repository (which is why I proposed forking).

e016 commented

2026-03-26 16:31:53 -05:00

(Migrated from github.com)

So, are we still going to fork? I ask as I'd like an update for the OP, just to keep things clear and organised

PPPDUD commented

2026-03-26 17:56:25 -05:00

(Migrated from github.com)

So, are we still going to fork? I ask as I'd like an update for the OP, just to keep things clear and organised

Most likely not.

> So, are we still going to fork? I ask as I'd like an update for the OP, just to keep things clear and organised Most likely not.

e016 commented

2026-03-26 18:00:57 -05:00

(Migrated from github.com)

Oh, thanks!

I just wanted the original top post to be updated to reflect the new decisions.

Oh, thanks! I just wanted the original top post to be updated to reflect the new decisions.

PPPDUD commented

2026-03-26 18:11:43 -05:00

(Migrated from github.com)

Closing issue as no longer relevant.

PPPDUD commented

2026-04-02 15:28:20 -05:00

(Migrated from github.com)

You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise.

Sorry to dwell in the past here, but for the record, Jameson is the only Snap! fork that I know of that supports:

JS-style promises
UUID generation
Google Translate functionality
etc.
by default.

Jameson, though it may appear to be small and uninteresting, is actually very fascinating if you dig deep enough.

> You started from litterally just randomly wanting to use random stuff for your little Jameson fork or otherwise. Sorry to dwell in the past here, but for the record, Jameson is the only Snap! fork that I know of that supports: * JS-style promises * UUID generation * Google Translate functionality * etc. by default. Jameson, though it may appear to be small and uninteresting, is actually very fascinating if you dig deep enough.

Rows
Columns

Settling governance matters #10

Governance of Sparkle

Target browsers

Governance of the new Crackle