2025-11-30 - 2025-12-07
Overview
There has not been any commit activity in this period.
7 issues closed from 2 users
Closed
#632 use schemas to validate input
Closed
#104 Have a DNS service running to allow users to tie services to their own domain
Closed
#362 NixOS tests break when CI runs them in parallel
Closed
#561 cache reusable computations
Closed
#102 CI rejects failing deployments
Closed
#26 Set up a secret management scheme
Closed
#326 regression: deployment status template
44 issues created by 1 user
Opened
#598 ensure application resilience
Opened
#599 diagnosing services
Opened
#600 NixOS service version update migration scripts standardized
Opened
#601 applications imported from contract-based implementations
Opened
#602 contracts available in nixpkgs
Opened
#603 contracts useable across nodes
Opened
#604 contracts handle generation of ephemeral state
Opened
#605 contracts provide single sign-on (SSO) integration
Opened
#606 contracts provide LDAP integration
Opened
#607 NixOS service service portability scripts standardized
Opened
#608 web host application implements API
Opened
#609 Install selected applications
Opened
#610 Configure applications
Opened
#611 Update applications
Opened
#612 Switch to a different host
Opened
#613 User management
Opened
#614 catch up on nixpkgs updates
Opened
#615 applications integrated with user management
Opened
#616 operator may manage users
Opened
#617 operator can restart nodes
Opened
#618 rights management streamlined across applications
Opened
#619 kubernetes set up
Opened
#620 generate kubernetes container from portable service
Opened
#621 applications' NixOS modules use portable services
Opened
#622 NixOS modules wrap portable services
Opened
#623 applications use portable services
Opened
#624 application definitions use service-level containers
Opened
#625 contracts coordinated across pods
Opened
#626 nix to json schema coverage
Opened
#627 expose applications' configuration options
Opened
#628 render option forms
Opened
#629 schema updates automated
Opened
#630 nix option modules from TF
Opened
#631 use schemas to generate TF types
Opened
#632 use schemas to validate input
Opened
#633 nodes can identify one another
Opened
#634 resources are versioned
Opened
#635 [D2.8] Technical design [2026-03-01]
Opened
#636 [D2.9] Service portability analysis [2026-04-15]
Opened
#637 [D2.10] Package style guide [2026-05-01]
Opened
#638 [D2.11] API specification [2026-05-15]
Opened
#639 [D2.12] UX prototype [2026-06-01]
Opened
#640 [D2.1] Software release test environment [2026-10-15]
Opened
#641 [D2.4] Nix packages and NixOS Services [2027-11-30]
115 unresolved conversations
Open
#223
resource monitoring for operators
Open
#339
NixOS configuration as a first-class abstraction
Open
#597
WIP: use data model
Open
#341
on migration, allow reconfiguring monolithic vs distributed
Open
#123
enable back-ups of application
Open
#213
visualise schema changes
Open
#214
aid needed actions on schema update
Open
#334
specification published
Open
#494
data model used
Open
#291
code passes security check
Open
#228
[D2.3] brought into production [2027-11-01]
Open
#483
[D2.2] Software release beta version [2027-03-31]
Open
#39
[D2.5] Finalize architecture doc [2025-07-28]
Open
#100
migrating application data between hosting providers
Open
#304
reference front-end is decoupled from version of configuration module
Open
#242
enqueuing deployment syncs
Open
#368
API available
Open
#159
Hosting providers can update their operators' deployments
Open
#366
use dedicated Nix builder
Open
#65
Automated dependency updates
Open
#313
ProxmoX back-end supports multiple users
Open
#184
show indicator of actual deployment progress
Open
#289
key features improving user experience supported
Open
#195
NixOS modules' options exposed
Open
#143
View difference between configured and deployed state
Open
#302
code reviewers can suggest changes
Open
#369
application offering delegated
Open
#493
portable ephemeral state
Open
#584
WIP: add conversion from TF
Open
#331
pydantic enum warning: Expected enum but got str
Open
#24
Disable root SSH authentication altogether
Open
#212
single sign-on (SSO) for services
Open
#110
desired subdomains are assigned to deployed services
Open
#116
Proxmox resources are provisioned to deploy services to
Open
#200
reproduce DNS VM
Open
#99
applications deployed on command
Open
#76
Deployed services are accessible
Open
#433
deployment provisions host infra
Open
#142
Users can configure their desired sub-domains in the online panel, so that the deployed services are assigned the desired sub-domains
Open
#349
exploit our work by enabling reproducible deployments of an initial set of portable applications
Open
#119
ProxmoX deployment allows scaling resources assigned to a VM
Open
#115
Databases are provisioned so that services can use a central storage
Open
#111
Shared file storage is provisioned to ensure persistence of data
Open
#187
provision immutable buckets
Open
#118
Relevant email accounts are provisioned such that the operator may be contacted
Open
#337
operator can delegate user management
Open
#178
admin accounts provisioned for deployed services
Open
#191
Wire up passing credentials from FediPanel to the Peertube configuration
Open
#190
Wire up passing credentials from FediPanel to the Pixelfed configuration
Open
#189
Wire up passing credentials from FediPanel to the Mastodon configuration
Open
#322
pooling instances to shared VMs
Open
#241
user can have multiple deployments
Open
#188
garbage collection of unallocated resources
Open
#180
update or remove VMs
Open
#336
reproducible project infrastructure
Open
#117
SMTP service is provisioned so that applications can send emails
Open
#69
Separate test environments for staging vs. production
Open
#309
port infra to terraform
Open
#332
nix-less bootstrap
Open
#75
Receive a notification when deployment finishes
Open
#138
VMs use central file storage
Open
#158
users can update their deployment configurations
Open
#186
allow disabling service while retaining data
Open
#161
connecting an existing identity management service
Open
#181
update virtualization parameters
Open
#314
ephemeral state is automatically provisioned
Open
#515
orchestrator state persisted
Open
#574
improve developer experience (DX)
Open
#459
can't download repository archives from forgejo
Open
#248
Nix package overlays upstreamed
Open
#542
use upstreamed python packages
Open
#529
avoid referencing parent directories
Open
#518
facilitate use without flakes
Open
#528
retire flake-parts
Open
#527
rename codebase
Open
#517
all tests exposed through flake
Open
#514
data model: migrations
Open
#496
standardize casing conventions
Open
#347
implement a way to run online services emphasising user autonomy and data portability
Open
#342
panel bundled into Fediversity configuration
Open
#333
module upstreamed to nixpkgs
Open
#335
sign-up for external developers
Open
#382
panel nix package allows declaring users
Open
#463
secrets may be scoped to prevent use in PRs
Open
#370
fediversity apps reused in infra
Open
#372
refactor environment variables to typed django settings
Open
#92
Continuous Integration builds available in a public cache
Open
#467
Integration-tested progress reports
Open
#384
CA certificates in NixOS tests generated declaratively
Open
#383
panel allows specifying SSH key
Open
#386
deprecate wiki
Open
#78
Start deployment migration
Open
#126
Operator can make back-ups of applications' mutable file systems
Open
#124
enable back-ups of application database
Open
#125
enable back-ups of applications' immutable storage
Open
#89
Generate documentation on the deployments from the code
Open
#86
Update documentation on services
Open
#185
use immutable buckets from VMs
Open
#155
Address CI friction between security and caching
Open
#87
Replace snakeoil-key with proper secret
Open
#136
panel staging/production configuration
Open
#98
docs: document having to load nix dev shell for pre-commit hook
Open
#199
derive users and their keys from the keys directory
Open
#210
Document the semantics of our various domains
Open
#243
knowledge base
Open
#295
limit security impact of SSH access to service VMs
Open
#272
support password-protected personal SSH keys for deploying services in development
Open
#77
Create a deployment migration string
Open
#68
Describe the hardware infrastructure needed to run Fediversity yourself
Open
#50
[D2.7] Analyze investment on Fediverse
Open
#33
Get the Pixelfed tests to run in CI
Open
#29
Backups for Forgejo
Open
#13
Beefier Forgejo actions machines
Open
#224
automated dev-ops workflows
Open
#288
external developers empowered to contribute