RFC for Tilde Center specification #4
Loading…
Reference in New Issue
No description provided.
Delete Branch "center/rfcs:tilde-center"
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?
Defines the ideologies and components of the Tilde Center project, its network, and its
peer servers.
aka ~aewens
should be(better known in the community as aewens)
(parenthetical with different wording)dthe user accounts"bedirect decisions"{#blah}
not#{blah}
Other than these issues, this LGTM! Finally having somebody actually write an RFC who isn't me revealed that I forgot to say
must
in RFC 0 when I was talking about the procedural.Maybe we didn't configure it here, but the markdown parser can be set to automatically add an id to the header.
For compatibility with RFC 0, the automatic ID can't really be used.
See changes made in
2acd257a26
anda6e868ad1a
.What configuration considerations are required for the tildeverse as a whole? If you add a sentence about it to the config consideration section, then I think this draft can be accepted on its merits and on your merits as a member-in-good-standing of the tildeverse.
Does the latest commit include what you had in mind?
As this RFC meets standards, it is hereby ordained Accepted, on the merits of aewens as a member in good standing of the tildeverse, as well as on its own merits as a document.
It is hereby assigned the number RFC 3.
Draft has been renamed to RFC 3, along with assigning the number and status properties to the correct values.
You forgot to change the number and status properties.
Whoops! Did a
git mv
withoutgit add
for the file changes. The new commit is added.In that case, this RFC is hereby added to the collection.
In that case, this RFC is hereby added to the collection.