@Athul @Hari Govind S @Aji Ahamed @sudo_medark @Badri Sunderarajan thanks for volunteering. Lets plan a meeting soon? How about 23 or 24 June? 7pm or 8pm?

@Pirate Praveen maybe you should add a few more timeslot options for people to state their preferences

I would also like to join the initial meeting

We are waiting at https://meet.fsci.in/git_fsci

I have given ssh access to @Badri Sunderarajan to the server and I will share access with Vishal later. Vishal will also make a proposal to migrate all repos to the forgejo instance that he maintains.

Sorry I couldn't join but FbIN (Vishal) informed me that my server could be used as a backup and this was discussed in the call. If you could provide the specifications I could create a fresh one on Azure, I am not sure if the hosting provider is acceptable or not. Currently I just use the server for personal purposes (it's from my student credits on azure), so the specs are as follows,

```
System RAM: total: 974 MiB available: 846.9 MiB used: 488.6 MiB (57.7%)
           CPU:
             Info: model: AMD EPYC 7763 bits: 64 type: MT arch: Zen 3 gen: 4 level: v3 note: check
               built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 1 stepping: 1
               microcode: 0xFFFFFFFF
             Topology: cpus: 1x cores: 1 tpc: 2 threads: 2 smt: enabled cache: L1: 64 KiB
               desc: d-1x32 KiB; i-1x32 KiB L2: 512 KiB desc: 1x512 KiB L3: 32 MiB desc: 1x32 MiB
             Speed (MHz): avg: 2928 high: 3261 min/max: N/A cores: 1: 3261 2: 2596 bogomips: 9781

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        61G   12G   50G  19% /
```

Thanks @pun for updating your details. @Pirate Praveen OOC, I see git currently as 20GB space, and 5GB used till now (including any spam, where applicable). @Badri Sunderarajan since you have admin account, can you see and delete/kill the spam stuff to release further and tone down?

Meanwhile, here is what I was suggesting on the call yesterday.

I have 2 domains. fbin.in - runs yunohost which already has forgejo, gogs & gitea packages.

The other one is flossboxin.org.in - where I already run forgejo git.flossboxin.org.in, open to public. However, I believe the best proposal I can give is, to help run and migrate the fsci git to either of the 2 places.

@Akshay whether we migrate the existing projects is part of the question. In case we decide to move the projects, this continue to be maintained by these volunteers under a new identity. We could also have a redirect at domain level to not break at least project level links. Full backward compatibility for all links would be more complex, but could be done if needed.

@Badri Sunderarajan we don't have many domain name options - the domain name has to be available too. If you find any other available and simple domains, then you can suggest it.

@Derpitron yes, I think that is the plan: to reach out to the owners once the decision is finalised.

For the domain, I was thinking we should collect suggestions and have a separate vote. A subdomain sounds good to me, though if people strongly prefer a separate domain I am open to that too. Depending on the concrete suggestions!

@Derpitron I don't think the focus should be on fsci. It should have its on independent identity for people to consider it in the same line of codeberg.org, gitlab.com or github.com Think from the point of view of people who want to host a git repo.

I think the current choice of sub domain is a factor in people not preferring it. When I choose an address, I always prefer a simpler and top level domain to a sub domain. When you chose a mastodon account, did you prefer a sub domain? A subdomain works only for people who already know/like the main domain. We are expecting people who don't know fsci also to be using our git hosting.

@FbIN (VB) and @Pirate Praveen, I think there is confusion about what exactly is being agreed to in this proposal and what is to be discussed in a future proposal.

Since most of the comments are about domain, I think it would be better to make a fresh proposal about the server/management only, and let the community decide on a domain after the poll is concluded. Otherwise, it ends up becoming a distraction from the main point which is about using @FbIN (VB)'s existing instance and server.

Further, the original proposal was initially not clear and only edited after @Akshay pointed it out, so people may have skipped voting or abstained on the older version and not seen the newer edited version. Now, they will get a chance to see the proper version from the beginning itself.

Here is an edited version that we could vote on. If needed, we can even leave out those points related to domain entirely and discuss that later, as the main point is about adopting @FbIN (VB)'s server.

• We will adopt the existing Forgejo instance operated by community member @FbIN (VB) as our "official" server, so that we can pool resources instead of trying to run two independent operations

• The server is currently @FbIN (VB)'s personal server, but since the community is adopting it, access will now be provided to other trusted community members (starting with those who volunteered for maintenance in the previous poll)

• @FbIN (VB) is already paying for the server; once it is adopted by the community FSCI will help with fundraising for that server

• We will keep the existing git.fosscommunity.in server running until Infomaniak credits run out, so that people have a chance to migrate. Once the credits run out, we will shut down the current git.fosscommunity.in server.

• The new server is currently running under a flossbox.in subdomain. Since it will now be maintained by FSCI, we will select a new domain (either under FSCI or as its own TLD). This is to be decided once the current poll concludes, but people are welcome to start commenting with suggestions below.

• We will reach out to users of the existing instance informing them of the move. They will have to create an account the new server, but we can help with migrating the repos (see next point)

• Repo migration will happen manually. FSCI specific repos will be moved to this instance by the volunteers. For other repos, the repo owners can request us to do it or perform the migration themselves. Of course, they are also free to migrate to some other server if they so wish

Thanks Badri. I think this version is much clearer.

I do have one concern though. While I'm happy to contribute infrastructure, the current server is still my personal server and it hosts a number of other unrelated public services. Because of that, I'm not sure I'm comfortable giving administrative access to multiple people on the same machine, since it would also mean exposing infrastructure that has nothing to do with the community Forgejo instance.

I wonder if it would make more sense to instead set up a small VPS dedicated to the community Forgejo instance. It wouldn't need to be anything expensive, and it would make it much easier to give admin access to trusted volunteers without having to worry about unrelated services on my personal server. If the community grows or the requirements increase, we can always scale it up or migrate later.

Netcup (where I host), for example, has some very affordable options. Their VPS Lite plans start at under €2 / €3 per month and are intended for smaller workloads, while their regular VPS plans provide more resources and flexibility if we outgrow the initial setup. I think even a small dedicated VPS would be more than enough for Forgejo to begin with.

VPS Lite: https://www.netcup.com/en/server/vps-lite

Regular VPS (x86): https://www.netcup.com/en/server/vps

I think having a dedicated server would also make the separation between personal and community infrastructure much cleaner, while still allowing everyone to collaborate on running and maintaining the service.

We got 500 Euro credits from Infomaniak, so hosting is settled. Now we need to decide on domain.

@praveenarimbrathod Why is subdomain a mistake? Any problems or downside with using a subdomain?

@Buster Keaton with a sub domain, the focus is on us - that is ok for services associated with an organization like source.puri.sm git.gajim.org etc but git.fsci.in is not really hosting fsci's git repos, we are offering it to the public. It is about thinking from the perspective of our users. Do we want to focus on fsci or users. I said mistake because earlier choice of git.fosscommunity.in, I think that sub domain played a part in less adoption.

@Buster Keaton I think name of a service that targets general public should describe that service like codema.in durare.org codeberg.org etc A sub domain shifts the focus (it may be fine for disroot.org or nixnet.services where they provide multiple services). FSCI does that too, but I prefer we shift focus for new domains we use. I think services having independent identity is better for adoption. Also I prefer different teams take ownership of different services we run.

@praveenarimbrathod, do you mean it is not only fsci's repos but other repos too or do fsci hosts their repos somewhere else?

I agree with focus and identity. It is upto fsci to decide on that, and weigh pros and cons of each. And for that there is a need for larger picture as Akshay had pointed out.

At present, FSCI's services are spread across 4 subdomains - git, meet, lists and wiki, and 3 domains - poddery, fsug and codema. Not sure which of them are adopted more or less.

@Buster Keaton it is a public git hosting service, so anyone could host their code on this service, not just fsci's repos (like codeberg.org or gitlab.com).

wiki - this is fine as it's fsci's wiki.

meet - people usually just share links, so it is ok

lists - it can actually serve any domain, the final address of a mailing list is not dependent on this sub domain - for example contact at prav.app is served by this.

@Akshay Since Infomaniak extended credits and we have volunteers to maintain, git hosting will continue as new service - new name and team.

I can understand there were many options and confusions, I will make another summary of the final plan.

I have added an update to the thread, so

1. We will choose a domain

2. Setup forgejo instance on a new Infomaniak Public Cloud server.

3. Migrate data and shutdown git.fosscommunity.in gitlab instance.

Since sharing with flossboxin.org.in idea was dropped because of being a personal server, git.fosscommunity.in will continue as an fsci service under a new team, server and name.

created another thread/poll with full details https://codema.in/d/tjLu8FQe/new-plan-for-fsci-git-hosting/1 (since one thread can only have one poll).

Just wanted to mansplain that git.disroot.org uses its own account system independent of disroot. Disroot began the code hosting service with Gitea in 2021 (before migrating to forgejo later) and there was no support for SSO or other user authentication then.

@perry so, having it as a subdomain of disroot.org gave me the wrong impression that it was only for Disroot users! 🫠

@perry yeah I remember that actually; I had to reset my password once for some reason and ended up with a different password on that than in other places. I am not sure if it has been rectified yet since I just try both passwords for every Disroot things and didn't bother noting down which it was 😅

@FbIN (VB) this thought process is focused on people running the service and their interest, assuming we don't have to consider users at all. That way, you could argue, these days you can even get tls certificates for ip address itself and don't need domain at all. https://ar.al/2025/06/25/web-numbers/

@untrusem This convinced me why a separate domain would be better.

@fugata codema.in is its own domain, so is poddery.com. The question is would people using one fsci service will also choose our git instance, or are people going to be independently choosing a service. With a sub domain, focus is on FSCI, but with top level domain, the focus is the service. The question is, which is more important?

I liked and support the decision of migrating from gitlab to forgejo.

Talking about domain, we may keep the domain git.fsci.in if that can make people recognize about FSCI or we should choose a domain e.g. librecode.in which is available to get.

@Deep Pandya  librecode.in sounds like a good domain. sourcebox.in is also good.
Anyways it looks like the highest votes were on git.fsci.in.

@Derpitron poll is still open

@Deep Pandya codefree.world is available, but costs 4000 rupees a year!

codefreedom.in is also available

@Akshay I tried adding one more option, but it gave internal server error and the poll seems broken now.

What if we set up a redirect? git.fsci.in is easy to remember for those who already know FSCI, and we can have a standalone domain as the primary one for branding.

Could work for other general-public facing things such as Jitsi as well (no need for more internal things like wiki.fsci.in I guess).

@Badri Sunderarajan this works for just the web part, but oauth will be tied to a single domain, at least with gitlab it was like that. So things like login with codeberg, gitlab.com, github etc will be tied to a single domain.

Jitsi is a very transient service, you have to create/copy-paste a meeting link every time. But if some one wants to find a top level domain and sponsors, that works too.

People can easily pick a different jitsi hosting provider (or bbb) for every meeting. So I think the domain is not as crucial for jitsi meet compared to git hosting. But I'm not opposed to someone pushing for more branding / publicity with a top level domain.

What about codeadda.in? It would give it an Indian flavour. I know "adda" as a word for hanging out/socialising and apparently it means similar things in Hindi and Bengali too, so it is reasonably pan-Indian.

@Badri Sunderarajan we can add it as an option in next poll if tld option wins in this poll. We will have another poll if tld option wins this one.

Since the domain is decided, what are the next steps? Are we going to use the same existing Infomaniak server?

If we are agreed on the software, what we could do is to set up the new repo on the same server and have both running side by side till the migration is complete (unless there's issues with the Debian version or something, in which case let's decide at that point).

Also, can someone direct me to the maintainers' group chat as I am unable to locate it 😅 we should probably discuss there to finalise the software

@Badri Sunderarajan it'd be easier to create a new server instead of trying to fit it into an existing server.

We can start with a smaller server and we can scale up if we need more resources.

xmpp:git.fosscommunity.in@muc.tchncs.de?join