Novu is a comprehensive notification infrastructure platform designed for multi-channel delivery (Email, SMS, Push, Chat, In-App) and workflow orchestration. It functions as both a SaaS product and a self-hosted solution, providing a unified API to manage subscribers, triggers, and notification templates. The system integrates deeply with AI agents, supporting Model Context Protocol (MCP) and managed runtimes (e.g., Anthropic) for conversational notifications. The architecture is a TypeScript monorepo managed by Nx and pnpm, featuring a NestJS backend (API, Worker, WebSocket), React/Next.js frontend (Dashboard, Playground), and MongoDB/Redis/ClickHouse data stores. It emphasizes extensibility through a provider factory pattern and a programmatic workflow DSL.
Zulip Desktop is an Electron-based desktop client for the Zulip team chat platform. It wraps the Zulip web application in a native window, providing multi-organization support via tabbed webviews, desktop notifications, tray/dock integration, spellcheck, and automatic updates. The architecture follows a standard Electron pattern with a main process (app/main/index.ts) managing windows, IPC, and system integrations, and a renderer process (app/renderer/js/main.ts) handling the UI, tab management, and settings pages. Communication between processes is facilitated by a strongly typed IPC system (typed-ipc.ts) that defines all channels and ensures type safety. The application persists user preferences and server configurations via JSON files (settings.json, domain.json) with Zod schema validation, and supports enterprise deployment through a global configuration file. External dependencies include Electron, electron-builder for packaging, electron-updater for auto-updates, Sentry for error reporting, and i18next for internationalization. The codebase is well-structured with clear separation of concerns, reusable component patterns, and comprehensive build pipelines for Windows, macOS, and Linux.
Operately is an open-source company operating system for coordinating goals, projects, and teams. It provides a full collaboration suite including spaces (groups), goals with OKRs, project management with milestones and tasks, check-in cadence, retrospectives, discussions, document and file management (Resource Hubs), KPI tracking, and people management. The system is built as a monolith with a Phoenix (Elixir) backend serving a custom TurboConnect API (mutation/query protocol) and a React/TypeScript single-page application frontend with a reusable component library (turboui). It also offers a CLI tool, Model Context Protocol (MCP) integration for AI agents, and extensive background job processing via Oban for notifications, email delivery, search indexing, and billing operations. The architecture follows a clean domain-driven design with operations (Ecto.Multi transactions), activity logging (event sourcing with embedded schemas), an access control system with hierarchical groups and bindings, and a rich content editor with link enrichment and blob storage. The codebase is well-tested with both backend (ExUnit, Wallaby) and frontend (Jest, React Testing Library) tests, and includes a demo data builder for development. The enterprise edition (ee/) extends the core with SaaS admin capabilities, billing management via Polar, site messages, and feature flags. The system has evolved significantly with over 115 data migrations, indicating active development. While the core architecture is solid and many patterns are reusable, there are some incomplete features (e.g., stubbed notification handlers, missing email templates) and occasional code duplication between internal API and MCP tool layers. Overall, it demonstrates strong engineering craftsmanship with practical trade-offs for an open-source SaaS application.
This repository provides the ROS 2 Middleware (RMW) implementation for eProsima Fast DDS, a high-performance DDS (Data Distribution Service) implementation. It translates the standard ROS 2 RMW API (publish, subscribe, services, clients, events) into Fast DDS operations, enabling ROS 2 nodes to communicate over DDS. The codebase is structured into three packages: `rmw_fastrtps_cpp` (static typesupport using compile-time code generation), `rmw_fastrtps_dynamic_cpp` (runtime introspection-based typesupport), and `rmw_fastrtps_shared_cpp` (shared logic for both variants). It supports advanced features such as content-filtered subscriptions, loaned messages, zero-copy data sharing via buffer backends (including GPU offloading), DDS security (PKI-DH, AES-GCM, access control), and comprehensive QoS mapping. The architecture follows a layered design where the shared package contains the core RMW implementations, and the two variant packages provide thin wrappers that differ only in how type support is resolved. This is a foundational infrastructure package for ROS 2, not an end-user application; it is selected at runtime via the `RMW_IMPLEMENTATION` environment variable.
This repository is a TypeScript monorepo implementing the Waku v2 protocol stack for decentralized, peer-to-peer messaging. It provides a comprehensive SDK (`@waku/sdk`) for building light nodes that support relay, filter, light push, and store protocols, along with advanced features like rate-limiting nullifiers (RLN) for spam protection, structured data synchronization (SDS) for reliable ordered delivery, and message encryption (ECIES/symmetric). The architecture is modular, with separate packages for core protocol logic, peer discovery (DNS, peer exchange, local cache), Ethereum Node Records (ENR), protobuf definitions, React hooks, and a local development environment via Docker Compose. The codebase targets both Node.js and browser environments, with extensive unit and integration tests using Mocha, Karma, and Playwright. While the core protocols are mature, some packages (SDS, RLN) are experimental and show signs of rapid iteration, with skipped tests and generated code that may drift from upstream specifications.
This repository is a Chinese translation and adaptation of the 'CCNA in 60 Days' study guide, organized as an mdBook static site with a companion Tauri desktop application. The primary content consists of 60 daily lessons covering Cisco CCNA exam topics (routing, switching, security, WAN, etc.), each with theory, configuration examples, review questions, and hands-on labs. The desktop app (src-tauri/) provides offline reading, bookmarking, reading progress tracking, and an LLM assistant (Anthropic Claude) for answering questions about the material. The project is hybrid: the vast majority of the repository is documentation, but it also includes a functional application wrapper with CI/CD. While the educational content is thorough and well-structured, the application components are minimal and tightly coupled to the mdBook ecosystem. The repository appears to have been abandoned (last commit with a future date indicates likely clock skew or repository corruption; no recent activity).
SimART is an open-source simulation platform for wireless communication and sensing research, integrating ray-tracing (Sionna RT), 3D visualization (VTK/Qt), drone simulation (AirSim/Unreal Engine), and ROS1 for data streaming. The system provides a desktop GUI (C++/Qt5) that loads 3D scenes from files, OpenStreetMap, or AirSim, and orchestrates real-time or offline radio propagation simulations. It generates channel knowledge maps (CKMs), beam codebooks, and system-level metrics (SINR, BLER, MCS), and supports machine learning-based beam selection via a DeepSense predictor. The platform is designed for researchers prototyping algorithms for UAV communications, beamforming, and link adaptation. While the codebase is functionally rich and modular in parts (scene providers, transform manager, socket workers), it suffers from significant technical drift: it depends on ROS1 (end-of-life), Unreal Engine 4.27 (discontinued), Qt5, and legacy VTK APIs. The C++ code contains large monolithic files (e.g., OsmSceneProvider.cpp ~1100 lines) and duplication between C++ and Python transform logic. There are no automated tests, and many configuration files lack schema validation. Despite these issues, several components (blender scripts, beam codebook utilities, scene provider interface) are well-isolated and could be reused in other projects with minimal adaptation.