Agenda Tech Brasil: a community-maintained calendar of Brazilian tech events

The problem: Brazilian tech events are scattered across many sites

The README opens with the question the project is built around: knowing an event exists but not knowing where to find it, or having to visit several places to search. Agenda Tech Brasil answers that by keeping dates and information about technology events happening in Brazil in one repository. The intended audience is anyone in the Brazilian tech community who plans attendance: developers looking for a meetup, DevRel people tracking where their community is active, and organisers who want their event visible next to others. The project also offers a weekly newsletter, linked from the README through a LinkedIn newsletter page, for people who would rather receive the list than check the repository.

The scope is deliberately geographic and thematic. Entries carry a city and state (Manaus/AM, João Pessoa/PB, Porto Alegre/RS), and some are marked as online or hybrid rather than in person. That mix matters: a list of only in-person events would miss the online workshops and webinars that appear alongside the meetups. The README is organised by year and then by month, with navigation links at the top jumping to Janeiro through Dezembro, so the reading model is a calendar rather than a feed.

How the repository is structured: a README, month markers, and a Python test setup

The top level of the repository contains .github/, .gitignore, README.md, arquivo/, assets/, pyproject.toml and src/. The event data itself lives in README.md, not in a database or a JSON file. Each month sits between HTML comment markers, for example ANO2026:START, JANEIRO:START and JANEIRO:END. Those markers are the mechanism that makes the file machine-readable enough to be validated: a tool can find the block for a given month and check what is inside it.

Each entry follows a line format visible throughout the README: a day or day range, a bracketed event title that is also the link, an optional location in italics, and a tag such as presencial, online or híbrido rendered as an image. Some months in the README jump from Março to Maio, and the July block lists dates out of order (22, 23 and 24 before 31 before 08, 09, 10 and 11). That is a maintenance artefact rather than a feature, and it is the kind of thing a contributor should expect to fix rather than copy.

The Python side is thin but explicit. pyproject.toml configures pytest with testpaths set to src/tests, quiet output, coverage measured over src, terminal-missing and XML reports, and a coverage failure threshold of 85 percent. Coverage omits src/tests/* and tests/*. So the project treats the README and the code around it as something to be checked, not just edited by hand. The README does not describe what the tests assert, so the exact validation rules are not documented.

Installing Agenda Tech Brasil and adding your first event

There is no package to install. The README points contributors to .github/CONTRIBUTING.md for how to include new events, and the deliverable is a pull request against README.md. The practical setup is cloning the repository and installing the test dependencies so you can run the same checks the project runs. The pyproject.toml shows pytest and coverage are the tools involved, but it does not pin versions, so the commands below assume you have a Python environment and install pytest with its coverage plugin.

git clone https://github.com/agenda-tech-brasil/agenda-tech-brasil.git
cd agenda-tech-brasil
python -m pip install pytest pytest-cov

After installing, run the test suite the way pyproject.toml defines it. Because addopts already carries the coverage flags and the 85 percent threshold, a bare pytest invocation is enough, and a run that drops below the threshold will fail rather than warn.

python -m pytest

The expected result is a quiet run over src/tests with a terminal coverage report and an XML report written for the src tree. Then edit README.md inside the correct month block. An entry follows the pattern the README already uses: day, linked title, location, and a presence tag.

- 28: [SQL Saturday Belo Horizonte 2026](https://sqlsaturday.com/2026-02-28-sqlsaturday1132/) - _Belo Horizonte/MG_ ![presencial]

Keep the line inside the JANEIRO:START and JANEIRO:END style markers for the month you are editing. If you put it outside the markers, the block-based tooling has no reason to see it. The README does not document what happens to entries for past months; the arquivo/ directory exists at the top level, which suggests an archiving convention, but the README does not explain it.

What the list cannot promise: accuracy, structure and coverage

The first limitation is that this is a hand-maintained list. Nothing in the repository shows an automated import from event platforms, so a date change on an event page will not propagate here until someone edits the README. The February block contains only four entries while January has six and May has seven, which is consistent with uneven coverage rather than with February being a quiet month in Brazil.

The second limitation is the data format. A README is readable by people and awkward for programs. There is no documented API, feed, CSV export or schema, so a downstream tool that wants to filter by state or by online versus in-person has to parse the markdown and the image tags. The month markers help, but the fields inside a line are positional and depend on contributors following the convention.

Third, the project is a listing, not a ticketing or registration system. It links out to even3, Sympla, Doity, thedevconf and others. If a link rots or an event sells out, the README still shows the entry. Anyone treating this as the authoritative source for whether an event is happening is using it for something it does not claim to do. The README also does not state a licence, which matters if you plan to reuse the compiled list in another product rather than just read it.

Alternatives: platform-hosted event pages and community calendars

The obvious alternative is to rely on the platforms the entries already link to, such as Sympla, even3 or Doity. Those give you registration, capacity and cancellation status directly from the organiser, which Agenda Tech Brasil cannot. The difference in approach is aggregation versus authority: the platforms each know their own events well and know nothing about the others, while Agenda Tech Brasil knows a little about many and depends on contributors to keep each line true. If your question is "is this specific event still on", go to the platform. If your question is "what is happening in Brazil in May", the aggregated README answers it faster.

A second alternative is a general community calendar or a local meetup group's own page, for example the tech.floripa.br event pages that already appear as entries in the list. Those are narrower and usually more current for one city. The trade-off is the same one the README describes at the top: you go back to checking several places. Agenda Tech Brasil is the middle ground, and it is only as good as the pull requests it receives.

Maintenance, contributions and licence status

The last push to the repository was on 2026-09-22, and the repository is not archived. The README names its maintainers: the project was created by @pachicodes and is maintained by her in collaboration with @stephan-lopes, with the web version credited to fabiobrasileiroo. Contribution instructions live in .github/CONTRIBUTING.md, and the README explicitly invites people to add events they think belong. That is the upgrade path: there are no releases to track and no version to pin, so staying current means pulling the README.

The cost of that model is editor time. Every new event is a pull request, every correction is another, and the pytest configuration with its 85 percent coverage floor means changes to the Python side have to keep the suite green. For a data file, that is a reasonable guard; for a busy month, the bottleneck is human review, not tooling.

On licensing, the repository metadata does not include a licence, and the README does not state one either. Without a licence, the default position is that no reuse rights are granted, so anyone planning to republish the list, embed it in a product, or build a derivative dataset should treat the terms as unresolved and ask the maintainers directly. This is a description of what the repository shows, not legal advice.

Editorial conclusion

Adopt Agenda Tech Brasil if you want a single, editable list of Brazilian tech events and are willing to open a pull request when something is missing or wrong. Do not adopt it if you need guaranteed accuracy, structured data, or an API: the project is a README plus a small Python test setup, and the README does not document any feed or endpoint. Before relying on it, check the month section you care about, confirm the linked event page still resolves, and read .github/CONTRIBUTING.md to see the format your entry has to follow.

Frequently asked questions

Official sources

1. agenda-tech-brasil/agenda-tech-brasil on GitHub
2. Issues
3. Project website
4. README