-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define and discuss a hosting strategy for this project #5
Comments
This issue is open for collaboration. We appreciate your support! 🤝 |
As for GitHub that I found interesting to myself:
Here are some Gitea instances which are already hosted and that I trust to exist very long:
|
Hi, vintprox! Thank you for your contribution. I appreciate your support. That is a really good point. As I mentioned partially in the contribution guide, I am all for using a free and opensource solution with as much data ownership as possible and without any vendor or platform lock ins. Gitea seems to be a good option. What we would really need is a solution, to keep everything, including this and any other discussions and all the data of the issues and pull requests under source control. What would mean, to have full control over the whole software development process. I my opinion, we should have a look at Gitea and find such a solution. What do you think? Should we open an issue for the task to evaluate this further? Could become an interesting issue for people who would like to contribute, but who aren't the coding ninjas themselves. |
Adding to the Codeberg suggestion, I'm excited to inform that https://translate.codeberg.org is a thing, the bridge between Codeberg and Weblate (no separate account is needed). Last one is, equally open source, translation platform. I believe your project might benefit from being translated into more than 1-2 languages. They also got Codeberg Pages, service like GitLab/GitHub Pages. As a secure bonus, it supports integration with any Gitea server. |
Thank you, @vintprox. I consider translating this project into as many languages as possible to be important. Right now this whole thing is still a little confused and needs more work, but this is a great hint. I think I will start a small project on Gitea soon, to get familiar with the platform. That will be good option to check the translate tool out. Many thanks for your contribution! 🤛 |
@vintprox Hi again. I just realized, that our discussion in this issue is not at the optimal place. Please don't get me wrong, I highly appreciate your input and I agree with your points. It's just that the topic of an alternative hosting platform for opensource projects is part of my other project called ItIsMine. Would you mind, if I try to find a good way to transfer this to the other project? At this point I only could think of closing this issue and open a new one in here to hold the issue of a security strategy. Please let me know, if you agree. Thank you! |
No problem at all. You can always transfer issues, broaden and clusterised as needed. Whatever works and moves this thing up from point 0 ;) |
@vintprox Hi there. Just wanted to let you know that I transferred this issue to the appropriate project and I renamed it. Thanks again for your input. 🤛 |
What is the topic, opinion, or issue you want to talk about?
Why?
As a community driven project, it needs to be accessible for contribution. We want to have a solid and if suitable also free and opensource solution to host this project. Depending on the outcome of this evaluation, we might still decide to stay on GitHub, if it's the best option.
What?
This is a task for a wide range of possible contributors with experience in hosting opensource projects. We should keep in mind, that we are looking for alternatives to GitHub that are decentralized or even better distributed, but still having the features necessary to keep the maintenance of the project possible at a reasonable effort.
How?
To be discussed. First step is to add the file hosting-strategy.md with a first description of any possible solution. This markdown file should contain the whole discussion, because we want to keep the discussion inside the source control of GIT and not inside a proprietary feature like GitHub discussions or inside GitHub issues or pull requests.
Log outputs, screenshots, questions?
No response
How to contact you
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: