Skip to content

Scriptura last piece: second maintainer resolved,solo-maintaining risk avoided - #99

Closed
jason1015-coder wants to merge 4 commits into
Nano-Collective:mainfrom
jason1015-coder:main
Closed

jason1015-coder wants to merge 4 commits into
Nano-Collective:mainfrom
jason1015-coder:main

Conversation

@jason1015-coder

@jason1015-coder jason1015-coder commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Updated the maintainer status and clarified the need for a second maintainer in the project documentation.

@will-lamerton one question--

Will I be able to in charge of the repo after transfer? Like using my repo management tools etc in the remote repo
Thx:))))))
😄

Updated the maintainer status and clarified the need for a second maintainer in the project documentation.
Added MKCL as a contributor for various services.
@jason1015-coder

Copy link
Copy Markdown
Contributor Author

@will-lamerton
what is meant by "p0 not meet apparently in second review"? as the plan explicitly says the plan will be executed AFTER transfer of repo, p0 is apparently not planned to change in scriptura repo before repo is transferred to the Nano-collective
Would that be a mistake? thx and pls answer ASAP so I have enough time to edit/ do change before deadline of finalising

@jason1015-coder jason1015-coder changed the title Scriptura whitepaper: second maintainer resolved, solo-maintaining risk avoided Scriptura whitepaper: second maintainer resolved,solo-maintaining risk avoided Sep 14, 2026
@jason1015-coder jason1015-coder changed the title Scriptura whitepaper: second maintainer resolved,solo-maintaining risk avoided Scriptura last piece: second maintainer resolved,solo-maintaining risk avoided Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant