A client for the fediverse that is fast, modern, and intuitive.
This community is a place to ask questions, report bugs, check on the latest updates, or share your experiences with Photon!
You can contact me at @Xylight@lemdro.id.
You can support development at Buy me a coffee
Rules
[solved] if it's been fixed.
I mean, i'ts your project. It's your baby. You do what you think it's best for it.
I don't think GitHub userbase number is going to drop dramatically any time soon (same thing with shady-associated services like Reddit, WhatsApp, you name it) but I'd bet everyone who would think about contributing to Photon already has an account in Codeberg (me!) or has the means do collaborate in Forgejo.
Both is fine, but in the short term Codeberg is probably the better option. Once Forgejo adds AP federation, a selfhosted instance is probably the best.
It's a tough question. Lots of people use GitHub because they want "stars". They want their project to trend so that it gets more attention, and thus more users, and thus more contributors, thereby making it a better product.
That being said, if Photon had zero improvements moving forward, I'd still be very happy, so my vote is yes, abso-fuckin-lutely.
Whether you self-host or use codeberg is your own decision, but I think the best solution is to move from GitHub this is a project for lemmy and piefed anyway most of us support FOSS and are against big tech, so I don't think there would be less amount of contributions if you moved away if that does happen tho you can keep the GitHub page and use it for issue tracking I have seen many projects linking their issue tracker on GitHub to their source code on codeberg.
codeberg is great and the sooner we all get off microsoft github the better...
I don't feel too strongly about it either way, but I do think codeberg would be a better idea than a self-hosted forgejo.
The magic of git is that if something happens it's trivial to switch. Honestly, I would just stick on GitHub until there's an actual reason to change. You can just do git remote set-url origin NEW_SERVER, do a git push and bam, your repo is restored with all of its history.
It's so easy to move, it's not worth worrying about imo
Only difficult part is moving pull requests and issues.
It would be kinda funny as an excuse to run away from the issues tab though
it's not so hard. you can just link previous PRs for comments, and re-home them. you can make a PR cross-platform it just won't necessarily render right in the web UI.
git is stupid powerful. reject web UI return to email list (Linux kernel vibes)