Board meeting December 2025
fugata proposed this in Prav public group:
Ravi mentioned that there's help needed with writing and designing content for Prāv, and I said I'd like to help with it, but since I have no day job to fall back on, I can't be working for free. I proposed that I can dedicate up to 2 hours/week on writing and/or designing for Prāv, for ₹1000/week.
We need to consider this proposal and if we agree raise funds for it.
Detailed proposal ,https://codema.in/d/5BFEZcLU/offering-to-dedicate-regular-effort-to-pr-v
Update: He revised it to 4 hours a week for 1000 rupees
perry Sat 29 Nov 2025 4:01PM
Creating accounts on proprietary social media (X, LinkedIn and others) was discussed multiple times in the Publicity and Outreach group, but it's not clear if a consensus was formed on this. Please add this to the meeting agenda.
perry Sat 29 Nov 2025 4:05PM
Also, follow up on data handling and retention of member's ID cards. From the previous meeting minutes (https://codema.in/d/b2eFqs4m):
Prav cooperative member data collection needs a data retention and and data handling policy. Prav should also display who will have access to personal private data of members and how they will be stored at the data collection form.
A final structure for data retention policy and data handling can be derived after confirming the data handling requirements for cooperative. @kannanvm will be collecting info about it.
Kannan V M Wed 3 Dec 2025 3:01PM
@perry This is yet to be done from my side. Will do it by this week.
Prav Board Meeting for December 2025
opt-in by Athul Closed Tue 2 Dec 2025 7:00PM
Prav Board meeting for November 2025 on Wednesday, 03 December 2025 8.30 pm.
Meeting Link: https://meet.fsci.in/PravBoardMeeting25
What is the team, working group or event you are inviting people to?
Scheduling the Prav Board meeting for December 2025 on Wednesday 3 December 2025, 8.30 p.m.
More details and Agenda at https://codema.in/d/8LZSU62K/board-meeting-nov-dec
Why is this important?
What are you asking people to do?
Select 'Accept' to participate!
Results
| Results | Option | Voters | |||
|---|---|---|---|---|---|
|
|
Accept | 3 |
|
||
| Decline | 0 | ||||
|
|
Undecided | 8 |
|
3 of 11 votes cast (27% participation)
Pirate Praveen Sun 30 Nov 2025 5:47PM
We also need to discuss about DoT's sim binding directions https://scroll.in/article/1088890/why-indias-telecom-department-has-mandated-sim-binding-for-whatsapp-some-other-app-services
On the one hand, the new definition of TIUE (Telecommunication Identifier User Entity) is too broad and we are likely to be one, on the other hand, the notification seems to identify only specific big players (WhatsApp, Telegram, Signal, Arattai, Snapchat, ShareChat, JioChat, and Josh) as TIUE and only sent them this notification. We will have to consult with SFLC.IN or IFF about our options. I have asked Kiran (hacksk) to check with Prashant Sugathan.
Pirate Praveen Wed 3 Dec 2025 2:26PM
SFLC.in confirmed we have to comply https://codema.in/d/pzc15FDt/dot-notification-for-sim-binding
Our options,
Just implement it
Challenge it in court if SFLC.in can take it up - argument being, a. excessive - other options to prevent unauthorized use can be implemented that don't need sim binding b. at least make it optional if we have other acceptable options like periodic device reverification, notification of new device sign in etc
-
See if custom username can skip this requirement. Since they are worried about people using an Indian number as identified to legitimize, it might be fine. Need to confirm with Prashant.
Prashant can join us for a call tomorrow - Kiran to coordinate/inform us time.
Pirate Praveen · Sat 22 Nov 2025 1:45PM
We should also set a deadline for id collection.