Gergana Petrova and the Work of Making Internet Institutions Legible

Summary

• Gergana Petrova matters because the public record places her in the practical middle layer between RIPE NCC as a Regional Internet Registry and the regional communities that need to understand, question, and use its institutions.
• Official RIPE sources identify Petrova as Specialist Community Development Officer at the RIPE NCC, responsible for engagement with members, the RIPE community, operators, academia, government, law enforcement, and other Internet stakeholders.
• Her RIPE Labs writing documents the mechanisms behind that role: regional events, Network Operator Group support, academic engagement, fellowships, newcomer support, diversity work, local hubs, community funding, and Internet governance participation.
• The strongest article is not a personal-celebrity profile. It is an infrastructure profile about legibility: how institutions become understandable enough for smaller and regional operators to participate in them before crisis or policy pressure arrives.
• The evidence supports role, authorship, program detail, and institutional context. It does not support quantified claims that Petrova personally changed regional resilience outcomes, so the article keeps impact claims bounded.

The Quiet Layer Between Registry and Community

Internet infrastructure institutions often look clean from a distance. A Regional Internet Registry allocates and registers number resources. A meeting has an agenda. A working group has a mailing list. A policy process has steps. A fellowship has a form. A Network Operator Group has a date, a venue, and a room full of people comparing notes about routing, IPv6, measurement, abuse handling, or regulation. On paper, this is legible. In practice, it can be opaque to the people who most need to use it.

That gap is where Gergana Petrova's public record sits. RIPE NCC's official speaker profile identifies her as Specialist Community Development Officer at the RIPE NCC. It says she works with the RIPE NCC membership, the RIPE community, network operators, academia, government, law enforcement, and other Internet stakeholders.

It also says her team organises regional events across Europe, the Middle East, and Central Asia, sponsors and presents at technical Internet community events, and helps develop national and regional Network Operator Groups, Internet Exchange Points, national Internet Governance Forums, Internet governance schools, and other projects that benefit the Internet in the RIPE NCC service region.

That is a wide remit, but the important word is not "wide." It is "between." Petrova's role is not the same as operating a registry database, chairing a technical working group, running an Internet exchange, or writing a national telecommunications law. The work described in her public profiles and RIPE Labs articles lives between those functions. It translates needs from regional communities back into the institution. It takes institutional activity back out to people who may not already know how to participate. It turns meetings into pathways rather than ceremonies.

It treats community development not as soft outreach around hard infrastructure, but as one of the mechanisms that lets hard infrastructure remain accountable, understandable, and useful.

That distinction matters because infrastructure resilience is not only a property of routers, registries, and policies. It is also a property of comprehension. Operators need to know where to ask for help, which forum handles which question, how a proposal becomes policy, what tools exist, who else is facing the same local constraint, and how to be heard without already being part of the inner circle. When those pathways are obscure, the institution can be technically correct and socially brittle at the same time.

Petrova's record is useful because it makes that maintenance layer visible. Her RIPE Labs pieces do not read like a grand theory of Internet governance. They are programmatic, practical, and sometimes almost administrative. They list regions, meetings, support mechanisms, student tickets, NOG contacts, local hubs, academic sessions, sponsorship amounts, open houses, data gaps, and participation barriers. That is exactly why they matter. The documents show how an infrastructure community tries to see itself, find its missing entities, and build enough institutional memory to respond to different local conditions.

For BTW readers, the most interesting subject is not simply Petrova as a named staff member. It is the operating surface she represents: the human and institutional work that makes a registry-adjacent community more legible to the people who depend on it.

What the Record Establishes

The identity evidence is clear and bounded. RIPE NCC's speaker profile names Gergana Petrova and identifies her as Specialist Community Development Officer. RIPE Labs' author profile repeats the same role and places her in a body of published work. A 2026 RIPE Labs article on RIPE 92 local hubs carries the same author identity and byline context. The fixed record therefore supports a public people article.

The record also supports restraint. Petrova's RIPE profile says she has spent more than ten years at the RIPE NCC and has worked in the Communications and External Relations departments. It says she is originally from Bulgaria, studied for her bachelor's degree in Germany, and obtained a master's degree in Business Research in the Netherlands. Those details help locate a career, but they do not give enough for an intimate biography. There are no sourced childhood scenes, private motivations, or independent character sketches in the evidence used for this article.

The better use of the record is to stay with what it actually shows: a community-development professional whose public output documents how RIPE NCC's service-region engagement is made operational.

The institutional setting is also established. RIPE NCC's Regional Internet Registry page says that, as an RIR, the organisation allocates and registers blocks of Internet number resources to Internet service providers and other organisations in its geographical service region. It identifies those resources as IPv4 address space, IPv6 address space, and Autonomous System Numbers. It says organisations become members to receive allocations, that RIPE NCC maintains a registry of allocated resources in the RIPE Database, and that it is one of five RIRs serving the global Internet community.

That background matters because community development around a Regional Internet Registry is not ordinary event marketing. Number-resource institutions are control surfaces for the Internet. They touch routing, resource stewardship, database accuracy, membership accountability, sanctions pressure, transfer markets, policy development, and technical trust. People who run local networks, exchange points, research groups, or national forums may experience those issues through very different local constraints.

A large carrier in Western Europe, a small operator in South East Europe, an academic researcher using measurement data, and a policy official trying to understand RPKI or IPv6 are all interacting with the same institutional universe from different angles.

The RIPE NCC speaker profile makes this breadth explicit. It does not describe Petrova as working with a narrow audience. It names members, the RIPE community, operators, academia, government, law enforcement, and other stakeholders. It also names national and regional NOGs, IXPs, national IGFs, and Internet governance schools. That is the profile's strongest fact pattern. It says the work is not a single outreach lane. It is a map of interfaces.

The article therefore treats Petrova as a lens on institutional legibility. The evidence supports that she is one of the people doing and explaining the work by which RIPE NCC listens, convenes, teaches, funds, and translates between communities. It does not support turning her into the sole author of regional outcomes. Community development is team work, and her own RIPE Labs writing repeatedly speaks in the first-person plural. The profile should preserve that.

Community Development as Infrastructure Work

Petrova's 2022 RIPE Labs article is the best starting point for the mechanics. In that piece, she explains that the Community Development department tries to learn what the RIPE community and other regional and national communities want and need from the RIPE NCC, then deliver it directly or through colleagues. Where a need cannot yet be met, the department passes the information internally. It also keeps the community updated on RIPE NCC activities and raises topics that may be useful or interesting.

That definition is modest and revealing. It frames community development as a feedback system. The work starts with listening, but not as a symbolic exercise. The point is to identify what different communities need from the institution, route that information to the relevant departments, and create enough public discussion for the community to understand what is happening. In infrastructure terms, this is not decoration. It is a control loop between a regional technical institution and the people affected by its services, tools, meetings, policies, and legitimacy.

The 2022 priorities make the control loop more concrete: regional community outreach, NOG support, academic engagement, administration and metrics. Petrova describes RIPE NCC's service region as large and diverse, with different levels of local activity, different connectivity realities, and different needs. South East Europe, Central Asia and the Caucasus, Eastern Europe, the Middle East, and West/Central Europe are not treated as interchangeable markets. They are described as different engagement problems.

That matters because the Internet is global only after it is local. Network operators buy local access, solve local power and transport constraints, deal with national regulators, hire from local talent pools, and often learn from nearby peers before they can participate confidently in broader forums. A community-development approach that begins with local needs is therefore more than courtesy. It is how an RIR-adjacent institution avoids mistaking the loudest and most connected entities for the whole community.

Petrova's 2023 update sharpens the point. She writes that the Community Development work moves in two directions: understanding diverse needs and expectations from RIPE NCC, passing feedback internally and following up on progress, while also keeping the community up to date and creating space to discuss useful topics. Again, the operating model is bidirectional. It is not simply broadcast from Amsterdam outward, and it is not simply a complaint channel inward. It is translation across distance, language, institutional familiarity, and technical maturity.

This kind of translation is easy to undervalue because it rarely produces a headline. A country Open House, a NOG organisers' meeting, a student session, a fellowship, a local hub, or a RIPE Labs summary may look small compared with a new registry policy or a routing-security incident. But those smaller forms determine who can show up before the next policy or incident.

They decide whether an operator in a less-visible region knows where the conversation is happening, whether a student can afford a meeting, whether a newcomer is introduced to experienced community members, and whether academics know how to bring useful measurement research into the technical community.

The available public record shows Petrova working in precisely this terrain. It supports an article about the community-development layer as infrastructure work: not because it configures routers, but because it configures participation.

Regional Communities Are Not a Side Audience

The RIPE NCC service region covers very different operating environments. Petrova's 2023 article gives the most vivid examples. South East Europe, she writes, is geographically small but difficult to connect as a community because mountains, country borders, and poor transport links can make travel between neighbouring countries indirect and expensive. That detail is not incidental. If the people who need to build regional trust cannot easily meet, the regional institution has to design around that constraint.

The same article describes SEE 10 in Ljubljana in April 2022 as the first post-COVID event, with 294 entities split between onsite and online attendance. It points to RIPE 85 in Belgrade, SEE 11 in Split, and RIPE NCC Days in Sofia as part of the same South East Europe engagement. It also mentions Open Houses around country reports for Bulgaria, Moldova, and Romania. This is what legibility looks like at regional scale: not one giant meeting, but repeated formats that let local operators, researchers, and stakeholders see themselves inside the larger RIPE system.

Central Asia and the Caucasus appear differently in the same source. Petrova describes the region as a newer engagement area with a lot of work to do, but also with local enthusiasm. The article mentions Internet Measurement Days, RIPE NCC Days in Tashkent, an action plan to boost IPv6 in Uzbekistan, intensive IPv6 trainings, and CAPIF, the Central Asia Peering and Interconnection Forum, as a way to promote peering and IXPs and identify opportunities to improve regional and international connectivity. The point is not that each activity has already produced a measured result.

The point is that RIPE NCC's community-development view connects regional convening with concrete infrastructure themes: IPv6 deployment, IXPs, peering, measurement, and connectivity.

The Middle East section offers another angle. The 2023 update says the first post-pandemic MENOG and Peering Forum took place in Manama and attracted 184 entities. It describes routing-security sessions, a ROA signing party, IPv6 presentations, local IXP introductions, and dedicated time for peering bilaterals. That mix is telling. It shows how a regional meeting can combine education, operational coordination, security practice, and relationship-building in the same container. In a decentralised network, that container matters.

NOGs are the most direct expression of this regional logic. In the 2022 article, Petrova describes significant overlap between NOGs, the RIPE NCC membership, and the RIPE community.

She says NOGs are strong platforms for RIPE NCC engagement, and describes efforts to build institutional knowledge of NOGs, establish RIPE NCC staff native contacts for most NOGs, improve coordination among organisers, support Open Houses, deliver relevant technical and informational content, promote learning and certification programs, update communities on legislative developments, make funding available, and keep the wider RIPE community informed about local NOG meetings.

The 2023 article reports that RIPE NCC attended 19 NOGs in 2022 and sponsored many of them, with plans to send staff to most NOGs in the service region, continue NOG organisers' Open Houses, and increase annual sponsorship in countries organising multiple events. Again, the interesting fact is not the number alone. It is the model. NOGs are not treated as peripheral social clubs. They are the local fabric through which operators share technical practice and institutional awareness.

This is where Petrova's profile becomes more than a profile. It shows a philosophy of infrastructure institutions: regional operator communities are not a side audience to be informed after decisions are made. They are part of the institution's ability to understand itself.

Meetings as Tools, Not Rituals

RIPE Meetings can look, from the outside, like ordinary technical conferences. Petrova's writing treats them as something more operational. They are where newcomers learn the shape of the RIPE community, academics find a place to present research, working-group entities test ideas, and operators translate local experience into shared knowledge. The public record around Petrova shows sustained attention to who can attend, who feels able to participate, and what kinds of support make participation real.

Her 2024 article on diversity at RIPE Meetings is especially important because it uses data to examine participation rather than assuming that an open meeting automatically creates an open community. Petrova focuses on academics, newcomers, and women across the last 22 RIPE Meetings. She reports that students average about 12 attendees per meeting, or 2 percent of total attendees. She notes reduced student tickets, outreach to universities in the meeting host country, online introductory sessions before the meeting, and up to 15 free local student tickets approved by the RIPE Chair team after the pandemic.

For academics, the same article reports an average of 53 attendees per meeting, or 8.46 percent, while noting post-pandemic decline relative to earlier levels. It describes RACI, the RIPE Academic Cooperation Initiative, as covering travel, accommodation, and meeting fees for academics with useful research to present. It also describes academic and NREN sessions, university presentations, conference sponsorship, and support for researchers using RIPE NCC data and tools.

For newcomers, Petrova reports an average of 179 people per RIPE Meeting, or 26.35 percent of total attendees. The support mechanisms are practical: mentorship, Meet and Greet lunches, a Meet and Greet desk, newcomer sessions before and at the meeting, and a newcomer reception. These are small structures, but they change the meeting from a room where new people are technically allowed to enter into a community where new people can decode what is going on.

The article's gender analysis is cautious and unsentimental. Petrova reports that women average 99 attendees per meeting, or 15.12 percent, and that women among newcomers average 14.79 percent. She also reports higher representation among speakers than attendees, with averages of 20.57 percent for Plenary speakers and 18.81 percent for Working Group speakers. The point is not that the problem is solved. It is the opposite: the data makes the institution's participation gap visible enough to discuss. Childcare and fellowships appear as tools, not as public-relations slogans.

This is central to institutional legitimacy. A community cannot claim openness only because its processes are public. It has to examine who can find, afford, understand, and use those processes. Petrova's public writing makes that examination part of the record. It treats the meeting as a piece of infrastructure in its own right: a recurring machine for turning individual experience into shared operational knowledge.

That perspective also appears in her 2026 article on local hubs at RIPE 92. She describes RIPE Meetings as places where the community gathers to exchange experience, discuss challenges, and build connections. Because not everyone can travel to every meeting, local hubs let people gather in person while participating remotely. For RIPE 92 in Edinburgh, hubs were organised in Sofia, Istanbul, and Jaroslaw. Petrova reports almost 700 onsite and more than 300 online RIPE 92 entities, and frames the hubs as an engagement layer for people who might otherwise not take part.

Local hubs are a deceptively simple idea. They accept that remote access alone is not the same as community participation, and that travel access alone is not equally distributed. A local hub turns remote participation back into local social contact. It lets people hear the same plenary or working-group content while also meeting peers in the same city or region. It is a hybrid answer to a hybrid problem: how to make a transnational infrastructure community accessible without pretending physical presence no longer matters.

In Petrova's record, meetings are not rituals to be defended. They are tools to be improved.

Governance Needs Translators

Petrova's work also sits close to Internet governance, but not in a way that should be reduced to conference attendance. Her official RIPE profile lists Internet governance among her areas of expertise and says she helps develop national IGFs and Internet governance schools. Her RIPE Labs liveblogs from EuroDIG 2023 and IGF 2023 show the same public-policy interface in practice.

EuroDIG 2023, as framed in RIPE Labs coverage, addressed Internet fragmentation, the impact of the war in Ukraine, digital-platform regulation, youth engagement, digital inclusion, and other policy issues. The liveblog includes discussion of technical-community voice, Ukraine's infrastructure resilience, interconnection and IXPs, multistakeholder processes, and the risk that policy choices at the application or content layer can have consequences for the technical layer. Some entries are authored by Petrova; others are by colleagues. As a source for this profile, the value is not that every paragraph belongs to her individually.

It is that her byline and participation sit in a RIPE NCC practice of translating governance debates for the technical community and translating technical-community concerns back into governance spaces.

The IGF 2023 liveblog makes the point even more directly. It frames the IGF as a global forum for public-policy issues related to the Internet and describes themes including fragmentation, cybersecurity, data governance, digital divides, global digital governance, human rights, sustainability, and the technical community's role. It includes Petrova-authored entries on vulnerability governance, rural connectivity, Internet and environment, IGF leadership, WSIS/IGF review questions, and research on institutional legitimacy around RIRs.

It also records a RIPE NCC workshop on routing security and RPKI with speakers from the Netherlands Standardisation Forum, JPNAP, and the OECD.

For an infrastructure institution, this governance layer is not optional. RIRs and technical communities may prefer precise engineering problems, but number resources, routing security, data governance, national regulation, sanctions, law-enforcement access, and digital sovereignty all bring public policy into the operating environment. If technical institutions are not legible to policymakers, policy can damage the technical layer by accident. If governance forums are not legible to operators, operators may be surprised by rules that reshape their work.

The role of a community-development officer in this context is partly educational and partly diplomatic. The reference shows Petrova's work connecting operators, academics, governments, law enforcement, national IGFs, and Internet governance schools. That is not diplomacy in the formal state sense. It is institutional translation. It helps a technical institution speak in venues where non-technical actors are making claims about the Internet, and it helps operators understand why those venues matter.

This is also where "consensus" becomes practical. The RIPE community's working methods depend on people being able to participate, understand arguments, and trust process. Consensus cannot be captured on a mailing list if the people affected by the issue never learned that the list existed, did not understand how to join, could not afford to attend the meeting where the topic was introduced, or assumed the institution was closed to them. Community development is one of the defenses against that kind of quiet exclusion.

The available public record does not prove that Petrova's work prevented bad policy or increased consensus quality across the whole RIPE service region. It does support a narrower claim: her documented work addresses the participation and translation layer on which legitimate consensus depends.

The Institution Becomes Visible Through Its Edges

RIPE NCC's Regional Internet Registry role is technically specific: allocating and registering Internet number resources, maintaining records, and operating within the global RIR system. But most people do not experience an institution through its constitutional description. They experience it through contact points: a meeting, an article, a fellowship, a training session, a NOG organiser, a local hub, a country report, a survey, a mailing list, an open house, a sponsorship, a public-policy session, or a staff member who can explain where to go next.

Petrova's public work is concentrated at those contact points. That is why the article's title uses "legible." Legibility is not simplification. It is the ability to understand enough of a system to act inside it. For a regional ISP, that might mean knowing where to raise a concern about routing security, how to follow an IPv6 training opportunity, why a local IXP discussion matters, or how a NOG can draw support. For a student, it might mean a low-cost ticket, an introductory session, or a local university outreach event. For an academic, it might mean RACI, a meeting slot, or help using RIPE Atlas, RIS, or RIPEstat.

For a policymaker, it might mean understanding why technical-community participation is not industry lobbying but a source of operational reality.

The public sources repeatedly show Petrova and the RIPE NCC Community Development function working through such edges. In 2022, the priorities included local needs, NOGs, academics, metrics, and diversity. In 2023, the update added specific regional activity and continuing country intelligence. In 2024, the diversity article used meeting data to ask who was missing or underrepresented. In 2026, the local hubs article returned to a basic access problem: not everyone can travel, but remote participation alone may not be enough.

This progression is useful because it shows continuity without pretending that the same tactic solves every problem. Some communities need regional meetings. Some need country-specific open houses. Some need support for NOG formation. Some need a fellowship. Some need academic bridges. Some need local hubs. Some need better information about policy debates. Some need training or translated educational materials. The institution becomes visible when these contact points accumulate.

That accumulation is also a resilience mechanism. In a crisis, an institution cannot instantly manufacture trust with communities it has not been serving. The time to know local operators, NOG organisers, academics, governments, and technical experts is before a war, a routing incident, a policy fight, a sanctions question, or a connectivity emergency. Community development may look slow, but slowness is part of its value. It builds the map before the map is needed.

The Ukraine-related passages in EuroDIG and IGF coverage illustrate the stakes without making Petrova responsible for Ukraine's Internet resilience. The sources discuss distributed networks, interconnection, technical-community input, and the need to document operator experience. Those themes align with the broader argument: resilient infrastructure depends on distributed capacity and trusted channels. Community development is one way those channels are found and strengthened.

This is why the profile should not be read as an institution's human-interest sidebar. It is an infrastructure profile about contact surfaces.

What the Sources Do Not Prove

A careful public profile has to say what it cannot say. The record is strong on official role, authorship, program scope, and documented mechanisms. It is weaker on independent evaluation. Most sources are RIPE NCC or RIPE Labs pages. That makes them authoritative for what RIPE NCC says its community-development work is, what Petrova has written, and how specific programs were described. It does not make them neutral audits of whether each program achieved its goals.

The article therefore avoids several tempting overclaims. It does not say Petrova created all the programs she describes. It does not say she personally caused NOG formation, IPv6 adoption, IXP development, student participation, regional resilience, or diversity gains. It does not claim that the RIPE community is now fully representative or that local hubs solve the travel problem. In fact, her own 2024 diversity article points to gaps and worrying trends, which would make a triumphalist reading inaccurate.

The evidence also does not provide a current independent profile of her day-to-day work. Official pages identify her role and scope; RIPE Labs pieces show public work and program descriptions. They do not show how tasks are divided inside the RIPE NCC team, how decisions are made internally, or how regional stakeholders assess her personally. A stronger independent profile would include operator interviews, NOG organiser perspectives, academic entities, RIPE fellows, and external governance entities. Those are outside this public record.

This limitation does not disqualify the article. It defines the article's form. A responsible profile can be built around public institutional work when the subject is not being used as a proxy for unsupported personal claims. The article can say that Petrova's public record illuminates a specific mechanism. It cannot say that all benefits of that mechanism are attributable to her.

There is also a title caveat. Public role wording can drift in informal summaries, but the official RIPE profile and RIPE Labs author page identify Petrova as Specialist Community Development Officer. This article uses that official wording. In infrastructure reporting, role precision matters. Inflating a title may seem harmless, but it weakens the credibility of every other claim.

The same discipline applies to geography. The article refers to the RIPE NCC service region, Europe, the Middle East, Central Asia, South East Europe, Eastern Europe, West/Central Europe, and the Caucasus because those are the regions and regional frames named in the reference. It does not infer country-level relationships or create durable relationship claims from event mentions. Meetings, trainings, NOGs, and governance forums are evidence of engagement surfaces, not proof of formal institutional relationships beyond what the sources state.

That restraint is not defensive. It is the condition under which the profile becomes useful. It shows how much can be understood from the public record without asking that record to do more than it can.

Why Petrova's Work Matters

The Internet's institutional layer has a readability problem. Experts know where the acronyms live. Long-time entities know which mailing list matters. People who have attended ten meetings understand the room, the hallway, the ritual, the argument styles, and the difference between a policy proposal and an operational complaint. Newcomers do not. Small regional operators may not. Students may not. A policymaker invited into an Internet governance forum may not. A local NOG organiser trying to connect a national community to regional resources may not.

Petrova's public work matters because it addresses that readability problem in practical ways. It identifies regional needs. It supports NOGs. It explains what Community Development is doing. It brings academic research into meeting spaces. It makes newcomer support explicit. It measures participation gaps. It encourages local hubs. It connects RIPE NCC activity to national IGFs, Internet governance schools, EuroDIG, and the IGF. It treats the institution as something that must be continually explained and opened, not merely administered.

That is a form of infrastructure stewardship. It does not look like a route object or a database field. It looks like a student ticket, a country report discussion, a CAPIF session, a ROA signing party at a regional meeting, a NOG organiser Open House, a university presentation, a fellowship, a childcare offer, a local hub in Sofia, an article that tells operators what the team is doing, and a liveblog that makes governance debates visible to the technical community. These are not substitutes for technical work. They are the conditions under which technical work can be shared, debated, trusted, and adopted.

The community-development lens also corrects a common misunderstanding about Internet governance. Governance is often imagined as either formal policy or high-level diplomacy. Petrova's record shows something more grounded. Governance is also the process by which the people affected by infrastructure institutions learn how to participate before decisions harden. It is how a regional operator finds a peer group. It is how an academic brings evidence. It is how a newcomer learns the meeting. It is how the technical community speaks in broader policy spaces.

It is how a registry institution hears that its service region is not one uniform audience.

For the RIPE NCC, this matters because legitimacy cannot be assumed from technical competence alone. A registry can allocate resources accurately and still become distant from parts of its community. A meeting can be open and still be hard to enter. A policy process can be transparent and still be difficult to understand. Community development is one of the ways an institution checks that gap.

Petrova's significance lies in that check. The sources do not support a heroic narrative, and the article does not need one. They support a more durable story about the people who make Internet institutions legible enough to remain shared institutions. In a network built from independent systems, that work is not peripheral. It is part of how the commons keeps finding itself.