Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Sichere ProgrammierungFirst-touch attribution on a cookieless static Nuxt site(21.09.2026 um 02:51 Uhr)
Sichere ProgrammierungWho Is the Customer? It Might Not Be Who Uses the Product(21.09.2026 um 02:57 Uhr)
Sichere ProgrammierungOn My Japanese Team, We Greet Each Other by Saying "You Must Be Tired"(21.09.2026 um 03:06 Uhr)
Sichere ProgrammierungRedis vs Memcached: Complete Comparison(21.09.2026 um 03:16 Uhr)
Sichere ProgrammierungHow Databricks Serverless Compute Cost My Team $14k in One Weekend(21.09.2026 um 03:20 Uhr)
Sichere ProgrammierungStop trying to make Airflow work for Medallion pipelines(21.09.2026 um 03:21 Uhr)
Sichere ProgrammierungI built an app that turns workout videos into actual workouts(21.09.2026 um 03:39 Uhr)
Sichere ProgrammierungFirst-touch attribution on a cookieless static Nuxt site(21.09.2026 um 02:51 Uhr)
Sichere ProgrammierungWho Is the Customer? It Might Not Be Who Uses the Product(21.09.2026 um 02:57 Uhr)
Sichere ProgrammierungOn My Japanese Team, We Greet Each Other by Saying "You Must Be Tired"(21.09.2026 um 03:06 Uhr)
Sichere ProgrammierungRedis vs Memcached: Complete Comparison(21.09.2026 um 03:16 Uhr)
Sichere ProgrammierungHow Databricks Serverless Compute Cost My Team $14k in One Weekend(21.09.2026 um 03:20 Uhr)
Sichere ProgrammierungStop trying to make Airflow work for Medallion pipelines(21.09.2026 um 03:21 Uhr)
Sichere ProgrammierungI built an app that turns workout videos into actual workouts(21.09.2026 um 03:39 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

FOSS.IN organization team critique

Reagiere als Erste:r — dein Feedback zählt!
Back in June I submitted a talk to FOSS.IN 2012 conference in Bangalore, India. Unfortunately my talk was not included in the list of accepted proposals, in other words, it was rejected. But that's not the reason why I'm writing, or why I am most disappointed in how things were handled by FOSS.IN's organizing team. 

The program's call for participation stated that the list of accepted proposals would be published by August 6th. This, however, did not occur until two months later, in early October. Working in academia, I am well aware that conference dates and deadlines can be changed, and one gets used to this, and takes it with a grain of salt. What I cannot understand, or accept, is the fact that FOSS.IN did not bother to inform anyone (specially those of us who took the time to submit a talk) that the deadlines were not going to be kept. A delay of two months is already incredible, not to mention the total lack of information as to when the accepted talks would be published. I had never seen such a thing from a conference, and hope to never see it again.

Furthermore, I was not even informed that my talk had been rejected. FOSS.IN already has an automated system to send people emails, I got one confirming my submission. So why wasn't I notified? Automatic emails are easy, fast and free.

Submitting a good talk to a conference takes time and careful preparation. I would expect a minimal amount of courtesy and professionalism by FOSS.IN. People make plans around deadlines and it's extremely rude to keep them in the dark.

This kind of behavior is simply unacceptable and makes the entire conference look bad. Yes, it's quite a big and well known event within the free software community, but that's not a justification. I am aware of Atul Chitnis' condition and wish him all the best and hope he can overcome the illness. I was very sorry to learn about it. But FOSS.IN is not a one man job.

I am writing this as a constructive criticism, hoping that these unpleasant things do not reoccur in future events. Since this year was the first time I proposed a presentation I don't know if these issues were a one time thing or is what people have come to expect from the FOSS.IN teams. Still I wish the best of luck to you folks and hope that you have another great conference this year.
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten FOSS.IN organization team critique

Thematisch verwandte Begriffe: FOSSIN, organization, team, critique · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-93968 | A vulnerability was determined in aiyiyi121 SxDevOps 1.0/1.1. This affec…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick