Meeting minutes

Campaign strategies; how and where.

• The total fund collected will be to fill the existing negative balance and two year service expenses.

• There will be option to fund individual services or FSCI as whole.

• The fund collected for FSCI will be split and shared to individual services or for un attended renewals for domains. A formula for splitting has to be derived.

• The priority will be to get funding for next year and recover already negative amount.

• Domains funding will be seperate from general funding campaign.

• Unless there are no other platforms available, there will be a seperate funding web page for contributor to enter transaction ID and to where their fund goes.

• The possibility of using Open collective with the support of navodaya as host for collecting fund has to be explored.

• Following platforms can be used for campaigns

  • Advertising on our services

  • Peertube videos

  • Other free software groups

  • Asking people perosnally

  • Colleges and schools

• What to do with services that aren't funded enough has to be discussed.

Campaign targets; amount and time.

The campaign will run all through the year, where it restarts on next year

Targets for individual services (All amounts are in Rupees)

poddery.com

Negative balance: 28962

Average yearly expense (rounded off): 30000

Two year expenses (+ contingency + inflation): 75000

Total: 103962

lists.fsci.in

Negative balance: -

Average yearly expense (rounded off): 4000

Two year expenses (+ contingency + inflation): 9500

Total: -

codema.in

Negative balance: -

Average yearly expense (rounded off): 4000

Two year expenses (+ contingency + inflation): 9500

Total: -

video.fsci.in

Negative balance: -

Average yearly expense (rounded off): 5500

Two year expenses (+ contingency + inflation): 12500

Total: -

meet.fsci.in

Negative balance: -

Average yearly expense (rounded off): 5500

Two year expenses (+ contingency + inflation): 12500

Total: -

FSCI

Total: -

Account handling and distribution for FSCI services.

• The possibility for working with Navodaya will have to be communicated.

• Till then personal account(s) can be used.

• Kannan and Snehal volunteered to handle funding

Requirement for an organization for account handling.

• This can be filled by coordinating with Navodaya

Domains management

• Manu is handling 9 domains

• 7 .in domains (Rs. 640) and 2 .org.in domains (Rs. 460)

Todo

• Praveen will communicate with Navodaya team

• Migration and maintenance

  • 2 vps handles backup should be migrated to a new instance

  • codema.in migration to Hetzner

  • poddery.com audit and scaledown if necessary

  • monitor.fsci.in migration to meet.fsci.in server

  • saakhi loomio instance disposal

• Update current funding status on website

• Look at possibility for scaleway open source credits - https://www.scaleway.com/en/about-us/open-source-program/

• Setup funding website for fsci

Meeting minutes of 16/01/2022 

Agenda - Discuss resource usages and scaling down for services. 

attendees - Bady, Kannan, Pirate Praveen, Ravi, sahilister

Pointers

• Resources users for all the services discussed.

• Scale down meet.fsci.in to CPX21 from earlier CPX31. @sahilister to install jitsi.

• Merge codema.in into meet.fsci.in after scaledown. @Pirate Bady to do it. 

• Migrate camp websites to meet.fsci.in server

• @Kannan V M to contact scaleway opensource program

• @Kannan V M and @Pirate Bady to talk to Kiran for scaledown

• Moniter to be disposed.

we haven't shut down monitor service yet. in a recent discussion with @suman, he said he is happy to volunteer to maintain the service and also suggested the idea of enabling notifications for resource throttling. but if we're continuing the service, i think we'll have to migrate it to hetzner to reduce expenses.

Not sure this is the right place to report this, but: I was looking around and saw that https://wiki.fsci.org.in is someone's personal site. That doesn't look right.

This happened while the server was migrated. We are aware about it, but we could not fix it yet. In general, we don't have enough volunteers to take care of all the services we manage. We will have to on board more volunteers or shut down some of the services.

Specifically, the DNS seems to be misconfigured and multiple IP addresses are resolved for this domain making let's encrypt certificate process to fail. Volunteers to fix this welcome.

I can take a look, but I am new here (which means I am yet to establish trust with everyone here and I am very unfamiliar with the processes) and someone will have to onboard me. Presumably that someone who will onboard me should be able to fix the problems quickly on their own, no?

If an additional pair of hands is welcome regardless, I'm available. :-)

It seems that https://git.fosscommunity.in also is broken, with 500 errors. Both wiki and git sites are prominently linked from https://fsci.org.in, so this is less than ideal. If they are unused and unmaintained, perhaps it might be better to retire them both?

git.fosscommunity.in issue is new (I will check). And about expertise, it not only about if one person can fix, but availability of time is an issue too. So more hands is always welcome.

Not running any service is the 100% guaranteed way of not having problems :) Only when things don't work people come up and volunteer so having things not working for some time is unfortunately required for us to get new volunteers :( but yes, we should think, plan and shut down services when we don't have enough volunteers.

For git.fosscommunity.in, the disk was full. It should be back soon.