afnix/documents
0
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Org dissolution procedure should try to reallocate assets to hosted projects #2

New issue
Open
opened 2025-07-08 14:21:15 +00:00 by delroth · 0 comments
delroth commented 2025-07-08 14:21:15 +00:00 (Migrated from git.lix.systems)
Copy link

For future proofing, I think we should improve the org dissolution procedure written in the bylaws. Specifically, I think some language should be included to try and guarantee that projects hosted by AFNix get their share of the assets back somehow, e.g. if they find a new host that can accept the assets from AFNix. This seems desirable, OTOH also not a blocker for anything right now.

For future proofing, I think we should improve the org dissolution procedure written in the bylaws. Specifically, I think some language should be included to try and guarantee that projects hosted by AFNix get their share of the assets back somehow, e.g. if they find a new host that can accept the assets from AFNix. This seems desirable, OTOH also not a blocker for anything right now.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
rules-current
bylaws-current
rules-2025-07-02
bylaws-2025-07-02
Labels
Clear labels   
bot

Automatic PRs created by bots

No labels
bot
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: afnix/documents#2
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?