Gitea is so much better than this. MIT licensed as well.
this post was submitted on 13 Nov 2023
22 points (95.8% liked)
Programming
17412 readers
76 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
Thats why they don't compare themselved against it
Gitea is so much better than this.
Is it, though?
Also, Apache Allura supports revision control services other than Git, which apparently Gitea does not.
MIT licensed as well.
Why do you think that is relevant, specially given Apache Allura is released under the Apache license?
Also, Apache Allura supports revision control services other than Git, which apparently Gitea does not.
Well, do you think its relevant to support anything else other than Git nowadays? Allura might do a bit more on that but Gitea has way more features and the UI is actually decent.
Well, do you think its relevant to support anything else other than Git nowadays?
Yes. There are people who prefer Mercurial than Git, and there are quite a lot of projects out there which still use Subversion.
I really don't understand the mindset that leads to a belief that a monoculture is good or desirable.
Allura might do a bit more on that (...)
Yes, it does.
(...) but Gitea has way more features and the UI is actually decent.
That's debatable, but to each its own.
Perhaps this could shine some light on the "do you think it's relevant to suport anything else other than ".
Oh well, we value different things it seems.
Not OP, but personally yes. Every code forge supporting only git just further enforces git's monopoly on the VCS space. Git isn't perfect, nor should be treated as perfect.
The above is probably the reason why so many alternative VCS's have to cludge themselves onto git's file format despite likely being better served with their own.
Interesting new VCS's, all supporting their own native format as well for various reasons:
- pijul
- sapling
- jujutsu
Sapling is developed by meta, jujutsu by an engineer at Google. Pijul is not tied to any company and was developed by an academic iirc. If you're okay with not new:
- mercurial
- fossil
- darcs
VCS's are still being itterated on and tooling being super git centric hurts that.
Every code forge supporting only git just further enforces git’s monopoly on the VCS space
So what? You speak about git as if it were some half-proprietary solution aimed at maximizing corporate profit. Git isn't Chrome.
Git isn’t perfect, nor should be treated as perfect.
Yes, and because of that fact it has been evolving over the years.
VCS’s are still being itterated on and tooling being super git centric hurts that.
What I see is some resentful people about git - in the same way that happened with SVN and oh well git is objectively better than that.
It being objectively better then SVN or CVS doesn't mean that it's the best we can do. Git has all sorts of non-ideal behaviors that other VCS's don't. Pijul's data structure for instance is inherently different from git and it can't be retrofitted on top. Making tooling only support git effectively kills off any potential competitors that could be superior to git.
One example is pijul specifically let's you get away from the idea that moving commits between branches changes their identity, because pijul builds a tree of diffs. If two subtrees of diffs are distinct, they can always be applied without changing identity of those diffs. This means "cherry picking" a commit and then merging a commit doesn't effectively merge that commit twice resulting in a merge conflict.
That's one example how one VCS can be better.
That’s one example how one VCS can be better.
What if we just upgrade git to have those features instead of reinventing the wheel?
The data model there is fundamentally different. That would break how git would work because operations that worked one way before would now no longer work that way. You'd functionally have rewritten and mapped all the old functionality to new functionality with subtle differences, but at that point is it even git? You have a wrapper with similar but subtly different commands and that's it. It's like saying "instead of reinventing functionality by building both ext4 and btrfs, why don't we just improve ext4"?
The two are practically entirely different.
Woah, the landing page looks like some unfinished Wordpress template and the forge itself looks 15years old. Nothing wrong, with the former, I just don't like the style.
Here are some possibly related communities in the instance:
Feel free to crosspost into them or post future content on this topic there if they are relevant.
I am a bot and this was performed automatically 🤖 For any issues contact Ategon.
Here are some possibly related communities in the instance:
Instead of deploying annoying bots, if you care about traffic then you should post some discussions from now and then.
@Ategon , [email protected] is basically dead and you haven't posted a single message there. If you care about content, shouldn't your effort be focused on creating posts instead of deploying annoying bots?
I have two accounts, a mod account and a non mod account which I use to post called mac
I've been posting a ton of content on various communities (and am the most active poster) but this bot is just to help guide people from things like the programming community to the more specific topic communities to help get those active since c/programming tends to have content that would fit in those and its supposed to be a collector community to filter people towards other communities due to lemmy having bad community discovery out of the instance
I'll be tweaking the triggers and making it fire less based on what I see happening over time
- that also didn't ping me btw, you need to include the @programming.dev at the end
I have two accounts,
The last post to [email protected] was 6 days ago.
During the past week, the community received two posts. Only two.
In the past two weeks, it received 8 posts.
Again, if you care about content, all you need to do is post content. Please don't ruin everyone's experience by deploying spambots that add no value at all. Be smart about where to invest some effort.
I really fail to see your problem here. "There is no activity in that community" maybe that is because everyone posts to c/programming instead, causing a negative feedback loop. Crossposting doesn't cost you any engagement.
It's also peak entitlement to berate the guy doing the most amount of work on this instance to keep it active and going for not posting enough content just because you didn't like what the bot told you. A single bot informing people that there are other, more suitable, communities that would benefit from a crosspost isn't spam.
It does add value, I just said what the value is. The bot isn't just something that points out the opensource community, it's for all communities and it just noticed here youre posting about open source which you are
But yeah open-source is one of the communities I've posted less to recently cause I tend to not get things I can post to it from what I normally browse but I can add some more activity there. Been mainly focusing on building up the language communities and communities that don't even get posts in a week normally