From a756bac04633830e3eb8ffa0b5da434f5ccb99d1 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Thu, 11 Apr 2019 21:43:18 +0200 Subject: [PATCH] chg: [PMF] first release as Internet-Draft --- Makefile | 2 +- raw.md | 2 +- raw.md.html | 189 +++++++++++++++++++++++++++------------------------- raw.md.txt | 38 +++++------ raw.md.xml | 8 +-- 5 files changed, 122 insertions(+), 117 deletions(-) diff --git a/Makefile b/Makefile index 210eb88..5998158 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ MMARK:=/home/adulau/git/mmark/mmark/mmark -xml2 -page -docs = $(wildcard *.md) +docs = $(wildcard raw.md) all: $(docs) $(MMARK) $< > $<.xml diff --git a/raw.md b/raw.md index 4aeefb0..1d0c199 100644 --- a/raw.md +++ b/raw.md @@ -6,7 +6,7 @@ % area = "Internet" % keyword = ["software engineering", "engineering", "pmf", "programming"] % -% date = 2017-10-15T00:00:00Z +% date = 2019-04-11T00:00:00Z % % [[author]] % initials="A." diff --git a/raw.md.html b/raw.md.html index 82942f5..a4c5502 100644 --- a/raw.md.html +++ b/raw.md.html @@ -373,24 +373,24 @@ /*]]>*/ - - - - - - - - - - + + + + + + + + + + - + - + @@ -402,20 +402,20 @@ - Network Working Group - A. Dulaunoy +Network Working Group +A. Dulaunoy - Internet-Draft - A. Iklody +Internet-Draft +A. Iklody - Intended status: Informational - CIRCL +Intended status: Informational +CIRCL - Expires: April 18, 2018 - October 15, 2017 +Expires: October 13, 2019 +April 11, 2019 @@ -425,52 +425,57 @@

Programming Methodology Framework aka PMF
draft-dulaunoy-programming-methodology-framework

-

- Abstract -

-

This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw [PROGRAMMING-MF-MANIFESTO] which describes a natural approach to software engineering with a strong focus on the act of programming. The PM methodology uses a soft naming to allow for a non-partisan reference to official engineering or project documents describing one of the most used software engineering methodologies.

-

- Status of This Memo -

+

Abstract

+

This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw [PROGRAMMING-MF-MANIFESTO] which describes a natural approach to software engineering with a strong focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference to official engineering or project documents describing one of the most used software engineering methodologies.

+

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

-

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

+

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

-

This Internet-Draft will expire on April 18, 2018.

-

- Copyright Notice -

-

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

-

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

+

This Internet-Draft will expire on October 13, 2019.

+

Copyright Notice

+

Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.

+

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

-

1. Introduction

+

+1. Introduction +

In 2011, Zed A. Shaw published a blog post which describes:

I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology.

-

The programming methodology was published as a manifesto later [PROGRAMMING-MF-MANIFESTO]. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The [THE-TAO-OF-PROGRAMMING] describes similar methodologies which strongly focus on coding, scripting and programming.

+

The PMF methodology was published as a manifesto later [PROGRAMMING-MF-MANIFESTO]. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The [THE-TAO-OF-PROGRAMMING] describes similar methodologies which strongly focus on coding, scripting and programming.

The overall concept of PMF methodology follows the following process:

-

+

@@ -497,55 +502,55 @@ | | +----------+ -

1.1. Management and PMF methodology

-

A simple management process is a required of the PMF methodology. The management process is meant to be complementary instead of interfering with the programming aspect and solely serves to support the PMF methodology.

-

+

+1.1. Management and PMF methodology +

+

A simple management process is a requirement of the PMF methodology. The management process is meant to be complementary instead of interfering with the programming aspect and solely serves to support the PMF methodology.

+

-

1.2. Conventions and Terminology

-

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

-

2. Security Considerations

-

Secure and defensive programming can only come by practicing programming and this also includes the act of simplifying or removing code to reduce the attack surface.

-

3. Acknowledgements

-

The authors wish to thank all the programmers who program.

-

4. References

-

4.1. Normative References

- - - - - - - -
- [RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
-

4.2. Informative References

- - - - - - - - - - - -
- [PROGRAMMING-MF-MANIFESTO] - Shaw, , "Programming Motherfucker, do you speak it?"
- [THE-TAO-OF-PROGRAMMING] - James, , "The Tao of Programming"
-

- Authors' Addresses +

+1.2. Conventions and Terminology

+

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

+

+2. Security Considerations +

+

Secure and defensive programming can only come by practicing programming and this also includes the act of simplifying or removing code to reduce the attack surface.

+

+3. Acknowledgements +

+

The authors wish to thank all the programmers who program.

+

+4. References

+

+4.1. Normative References

+ + + +
[RFC2119] +Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
+

+4.2. Informative References

+ + + + + + + + + +
[PROGRAMMING-MF-MANIFESTO] +Shaw, "Programming Motherfucker, do you speak it?"
[THE-TAO-OF-PROGRAMMING] +James, "The Tao of Programming"
+

Authors' Addresses

diff --git a/raw.md.txt b/raw.md.txt index 80874e9..3a7af64 100644 --- a/raw.md.txt +++ b/raw.md.txt @@ -5,7 +5,7 @@ Network Working Group A. Dulaunoy Internet-Draft A. Iklody Intended status: Informational CIRCL -Expires: April 18, 2018 October 15, 2017 +Expires: October 13, 2019 April 11, 2019 Programming Methodology Framework aka PMF @@ -17,7 +17,7 @@ Abstract known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw [PROGRAMMING-MF-MANIFESTO] which describes a natural approach to software engineering with a strong - focus on the act of programming. The PM methodology uses a soft + focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference to official engineering or project documents describing one of the most used software engineering methodologies. @@ -30,32 +30,32 @@ Status of This Memo Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- - Drafts is at http://datatracker.ietf.org/drafts/current/. + Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 18, 2018. + This Internet-Draft will expire on October 13, 2019. Copyright Notice - Copyright (c) 2017 IETF Trust and the persons identified as the + Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents - (http://trustee.ietf.org/license-info) in effect on the date of + (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must -Dulaunoy & Iklody Expires April 18, 2018 [Page 1] +Dulaunoy & Iklody Expires October 13, 2019 [Page 1] -Internet-Draft PMF - Programming Methodology Framework October 2017 +Internet-Draft PMF - Programming Methodology Framework April 2019 include Simplified BSD License text as described in Section 4.e of @@ -85,7 +85,7 @@ Table of Contents writing software. It's name even embodies the perfection of this programming methodology. - The programming methodology was published as a manifesto later + The PMF methodology was published as a manifesto later [PROGRAMMING-MF-MANIFESTO]. The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The @@ -109,9 +109,9 @@ Table of Contents -Dulaunoy & Iklody Expires April 18, 2018 [Page 2] +Dulaunoy & Iklody Expires October 13, 2019 [Page 2] -Internet-Draft PMF - Programming Methodology Framework October 2017 +Internet-Draft PMF - Programming Methodology Framework April 2019 +----------+ @@ -136,7 +136,7 @@ Internet-Draft PMF - Programming Methodology Framework October 2017 1.1. Management and PMF methodology - A simple management process is a required of the PMF methodology. + A simple management process is a requirement of the PMF methodology. The management process is meant to be complementary instead of interfering with the programming aspect and solely serves to support the PMF methodology. @@ -165,9 +165,9 @@ Internet-Draft PMF - Programming Methodology Framework October 2017 -Dulaunoy & Iklody Expires April 18, 2018 [Page 3] +Dulaunoy & Iklody Expires October 13, 2019 [Page 3] -Internet-Draft PMF - Programming Methodology Framework October 2017 +Internet-Draft PMF - Programming Methodology Framework April 2019 3. Acknowledgements @@ -180,17 +180,17 @@ Internet-Draft PMF - Programming Methodology Framework October 2017 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, . + DOI 10.17487/RFC2119, March 1997, + . 4.2. Informative References [PROGRAMMING-MF-MANIFESTO] - Shaw, , "Programming Motherfucker, do you speak it?", + Shaw, "Programming Motherfucker, do you speak it?", . [THE-TAO-OF-PROGRAMMING] - James, , "The Tao of Programming", + James, "The Tao of Programming", . Authors' Addresses @@ -221,4 +221,4 @@ Authors' Addresses -Dulaunoy & Iklody Expires April 18, 2018 [Page 4] +Dulaunoy & Iklody Expires October 13, 2019 [Page 4] diff --git a/raw.md.xml b/raw.md.xml index 1382747..f057dca 100644 --- a/raw.md.xml +++ b/raw.md.xml @@ -42,7 +42,7 @@
- + Internet @@ -54,7 +54,7 @@ This document describes the Programming Methodology Framework also known under the PMF methodology. The methodology is based on the manifesto written by Zed A. Shaw which -describes a natural approach to software engineering with a strong focus on the act of programming. The PM methodology uses a soft naming to allow for a non-partisan reference +describes a natural approach to software engineering with a strong focus on the act of programming. The PMF methodology uses a soft naming to allow for a non-partisan reference to official engineering or project documents describing one of the most used software engineering methodologies. @@ -69,7 +69,7 @@ to official engineering or project documents describing one of the most used sof I think I'm going to create the ultimate software development methodology. It'll be revolutionary compared to others because it will focus on the one thing that gets software done. Its entire focus will be this one, glorious, completely useful activity for writing software. It's name even embodies the perfection of this programming methodology. -The programming methodology was published as a manifesto later . The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The describes similar methodologies which strongly focus on coding, scripting and programming. +The PMF methodology was published as a manifesto later . The manifesto clearly describes the focus on programming to avoid the surrounding management overhead and pivot towards the delivery of the software. The describes similar methodologies which strongly focus on coding, scripting and programming. The overall concept of PMF methodology follows the following process: @@ -108,7 +108,7 @@ to official engineering or project documents describing one of the most used sof
-A simple management process is a required of the PMF methodology. +A simple management process is a requirement of the PMF methodology. The management process is meant to be complementary instead of interfering with the programming aspect and solely serves to support the PMF methodology.