rename codebase #527
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#288 external developers empowered to contribute
fediversity/fediversity
Reference
fediversity/fediversity#527
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
one feedback point from our reporting call with the EC was to look for a name perhaps more descriptive of our positioning.
in case we end up splitting up our code into multiple repos, we may end up having to pick multiple names - but then we may need to figure out how to split things:
nix-module-formnix-tf-schemamodule-schema: conversion of Nix modules to JSON-Schemanpins-update-actionnix-docs-libpanel/)api/)core/setups/,nixosConfigurations)core/applications/)core/resources/)core/lib/)core/effects/)extraTestScript#770@michiel had suggested nixpanel here (prior to the frontend split between demo vs product), tho that might invoke an analytics firm more so than the intended meaning