I understand forking a project, but why would you wait until its done? Doesn't that defeat the purpose if you still rely on the origin?

Why not just work together?

I'm not worried about pixelfed forks because I have been open to feedback and almost every PR has been merged. Our enemy is not another fediverse developer, its the corporate silo'd social media. Its in everyones best interest to work together.

@dansup If you like what the fork does then you can always just merge back anything they do. If you dont then they can always just merge in future updates from you. Forks help each other thrive.

@freemo A lot of the pixelfed features will be in the form of composer packages. Any one can contribute & use feature packages without having to fork! In a way, this makes forks irrelevant since every feature is optional.

@dansup You'd have to ask them what they hope to gain from a fork. Perhaps its just impatience? I think master on pixelfed is a month stale now, people might just be scared its stalled?

@freemo There is no master branch, or releases. It would be cool if they could contribute some code instead of just rebranding my code!

@dansup I was refering to the dansup/pixelfed repo's master branch.

They will wind up contributing whether its their intention or not. Just merge in any commits they make in their fork that you like.

@freemo That won't be necessary, they can just write their own feature packages that add new functionality or override existing code. It would be nice if they decide to contribute.

Follow

@dansup well that would be in their best interests usually. Lets hope when they see what you can do they will change their minds.

Where is the most recent code for us to contribute to?

Β· Β· 0 Β· 0 Β· 0
Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.