Public & street art

Open-source cultural infrastructure

Explore art.kubus as open-source cultural infrastructure: GitHub development, community contribution and transparent public archive tooling.

Start with these routes

Open development, practical scope

art.kubus develops parts of its cultural infrastructure in the open so the community can inspect, discuss and improve tooling. Open source is a practical commitment to transparency, not a promise that every service or private system is public.

How to contribute

Community contribution can include code, documentation, issue reports, translations, map markers and editorial corrections. GitHub is the place for published repositories and technical collaboration, while cultural contributions can also happen through the app.

Why openness matters for culture

Open-source cultural infrastructure helps public art records, map tools and archive workflows outlive a single product cycle. It also makes the boundaries of public data, private data and experimental features easier to inspect.

kubus Node for archive availability

kubus Node is the open operator runtime for public art archive replication and verified availability reporting. It supports pending contribution records, not live payouts or investment claims.

Frequently asked questions

Is art.kubus open source?

Parts of the project are open-source. Check the repositories linked on this page to see what is currently published.

Can I contribute without writing code?

Yes. You can submit and verify map markers, report issues, suggest improvements, and help with editorial accuracy and translations.

Do you accept pull requests?

Yes for public repositories. Contributions should be focused, well-documented, and aligned with the platform’s accessibility, SEO, and consent rules.

Is everything in the art.kubus stack public?

Not necessarily. Some services may remain private or depend on third-party infrastructure. The open-source scope is documented via the published repositories.

Editorial and expertise transparency

This page is maintained by the art.kubus editorial team using public-source research, local context, and community-verified map contributions.

Editorial and research team: art.kubus editorial team

Contact and collaboration