diff --git a/efp/efp010/main.xml b/efp/efp010/main.xml new file mode 100644 index 0000000..14736b6 --- /dev/null +++ b/efp/efp010/main.xml @@ -0,0 +1,164 @@ + + + + + + + + +
+ +

+ As established in the Constitution, Execution Framework Proposals (EFPs) are community-driven, + execution-defining, and immutable once finalized. They provide standards, methods, + and structured execution plans, as well as records of executive procedures in the governance + framework in the Constitution, like this Proposal. +

+

+ An approved EFP may represent the current state of affairs in the Constitution. It includes + when certain procedures are being processed or certain proposals of ideas are created. + An EFP may or may not take effects to change any aspects of affairs in the Constitution depending + on the status of the said EFP. Other than the basic Rules defined in the Constitution, this + Proposal refines further for detailed steps and procedures for EFPs. +

+ +
+
+ +

+ Any natural or artificial person as a participant in the Constitution should be able to initiate + an EFP regardless of their positions and responsibilities, except when those participants are + prohibited from participations in Governing Activities. Primary Roles of people should have been + defined in the Constitution in advance for the participants in the Procedures. +

+

+ Once the identifier is assigned and the Pull Request of the Initiation is merged, the identifier + is no longer free. It is possible that when the related parties have accepted before the creation + of the Pull Request, the identifier is assigned in advance, so before closing the Pull Request, + the identifier should still be reserved. +

+ +
+
+ +

+ The structures for an EFP should not be fixed for the contents, but the metadata. + Besides, while contents other than the Contents are classified as Metadata, References are + classified as Metadata even though they are shown aside the Contents in the Document Body. +

+

+ There should be no special restriction for what to be in the Contents, but probably later + authoring guidelines for the Contents of EFPs may be introduced. This includes the References. +

+

+ The creation date should be the Coordinated Universal Time (UTC) date at the time the Document + being created by the Author, however it is up to the Author's preference whenever the date is + not after the UTC date the Pull Request is being created. +

+

+ Guidelines for how to use References should later be written for the suggestions of using them. + Citation is recommended, but not necessary. +

+ +
+
+ +

+ The directory structure of the Repository should be explained in the words from the root directory. +

+

+ The directory names for the Entries may change if the naming rules of the identifiers change. +

+

+ The reserved idea of having more than one XML file in an Entry was to provide extra information + like appendices, but so far there is no yet a use case, so it is still reserved. +

+ +
+
+ +

+ Having "Provisional" status may be redundant when considering how EFPs are used. + It stands for "Provisionally Adapted", comes from Python Enhancement Proposal (PEP). + In general governance, having a temporarily adapted proposal while plans are mutable could be + problematic in management, and thus fragile. +

+

+ "Deferred" EFPs may mean those EFPs are still incomplete, but not effective or used + at the moment, so this status may be problematic if such EFPs are not properly handled. +

+

+ It is recommended to update the status system of EFPs by the above comments and concerns. +

+ +
+
+ +

+ A guideline for clear boundaries between different contents for different aspects and categories + should be suggested. When certain requirements are met, separate proposals should be made. + Also, when certain standards or specifications could be generalized, such should be firstly made + as Standard Proposals, then adapting proposals are to be made, for potential future reusing + of standards or specifications in similar concepts, simplifying organizations of executions. +

+

+ Certain proposals like proposals of new standards and specifications may include examples, samples, + or other formats of specifications as affiliated files in the Entries. They may be for reference or + basic demonstration purposes. +

+

+ In the future, it is possible that when unified references to or dedicated management of standards are required. + For such, it may be worth to consider whether there is a need to form a new System to govern + all existing standards and specifications. +

+

+ At the moment, this Classification should well encompass all significant and effective proposals + potentially present in the future. However, it is still possible for new Classification to occur; + for such, the Constitution shall also be amended. +

+ +
+
+ +

+ Unlike usual Request For Comments (RFCs) on the Internet, minor changes to EFPs are quite easily + tracked using a public Repository. Thus, it is kind of difficult to draw a line whether + a Pull Request should be enough ready to be merged while being sufficient for public's references. + Therefore, most likely when thematic changes are completed, such a Pull Request may be reviewed + for merging, but the stage may be incomplete while there is no a true draft before official assignments. + Unstable staging may exist due to the aforementioned reasons. +

+ +
+
+ +

+ Unlike usual Request For Comments (RFCs) on the Internet, changes to EFPs may be tracked easily + using a Version Control System (VCS). Thus, errata may be directly made as commits without + having to specifically track them. +

+

+ Errata commits may describe the exact changes in the commit messages, while thematic changes may + also be described in the corresponding Pull Requests. However, for minor changes, commit messages + are more preferred than comments in Pull Requests. +

+ +
+
+ +

+ Amendments to Formatting of Governance Documents may affect all the Document files in all the Entries, + so an EFP should be introduced for the conduction of it. +

+ +
+
+ + +
  • EFP 1 (Constitution)
    • +     +     +
    + +