rfc, future-work: rename section to 'Future possibilities' + consequence edits.

Author: Centril

text/0000-future-work.md

@@ -1,13 +1,13 @@
-- Feature Name: `future_work`
+- Feature Name: `future_possibilities`
 - Start Date: 2018-10-11
 - RFC PR: _
 - Rust Issue: N/A. The RFC is self-executing.
 
 # Summary
 [summary]: #summary
 
-Adds a *"Future work"* section to the `0000-template.md` RFC template that
-asks authors to elaborate on what natural extensions there might to their
+Adds a *"Future possibilities"* section to the `0000-template.md` RFC template
+that asks authors to elaborate on what natural extensions there might to their
 RFC and what future directions this may take the project into.
 This section asks authors to think *holistically*.
 
@@ -19,9 +19,9 @@ This section asks authors to think *holistically*.
 Often times, when an RFC is written, the only thing an author considers
 may be the feature or change proposal itself but not the larger picture
 and context in which the RFC operates in. By asking the author to reflect
-on future work, a larger degree of introspection within the author themselves
-may ensue. The hope is then that they may consider what larger effects
-their proposal may have and what subsequent proposals may be.
+on future possibilities, a larger degree of introspection within the author
+themselves may ensue. The hope is then that they may consider what larger
+effects their proposal may have and what subsequent proposals may be.
 
 [#2532]: https://github.com/Centril/rfcs/blob/rfc/assoc-default-groups/text/0000-assoc-default-groups.md#future-work
 [#2529]: https://github.com/Centril/rfcs/blob/rfc/hidden-impls/text/0000-hidden-impls.md#future-work-1
@@ -33,17 +33,17 @@ their proposal may have and what subsequent proposals may be.
 [#2385]: https://github.com/Centril/rfcs/blob/rfc/implied-derive/text/0000-implied-derive.md#future-work
 [#2306]: https://github.com/rust-lang/rfcs/blob/master/text/2306-convert-id.md#possible-future-work
 
-The author of this RFC has benefitted personally from writing future-work
+The author of this RFC has benefitted personally from writing future-possibilities
 sections ([#2532], [#2529], [#2524], [#2523], [#2522], [#2401], [#2421],
 [#2385], and [#2306]). Said written sections have also caused the current
 author to think more clearly about interactions in each of the written RFCs.
-If for no other reason, these sections offer a permantent space to idea-dump
+If for no other reason, these sections offer a permanent space to idea-dump
 while writing an RFC.
 
 ## For the team
 
-The holistic perspective that a future work section can offer may also
-help the relevant subteam to understand:
+The holistic perspective that a future-possibilities section can offer may also
+help the relevant sub-team to understand:
 
 1. why something is proposed,
 2. what the long term effects of said proposal is,
@@ -54,17 +54,17 @@ help the relevant subteam to understand:
 
 More generally, the benefits for the teams described above also hold for
 all readers. In particular, a reader can better infer what sort of language
-Rust is turning into given the information in a future-work section.
+Rust is turning into given the information in a future-possibilities section.
 Having such a section may also help generate interest in subsequent proposals
 which a different author may then write.
 
 # Guide-level explanation
 [guide-level-explanation]: #guide-level-explanation
 
-This Meta-RFC modifies the RFC template by adding a *"Future work"* section
-after the *"Unresolved questions"*. The newly introduced section is intended
-to help the authors, teams and readers in general reflect holistically on
-the big picture effects that a specific RFC proposal has.
+This Meta-RFC modifies the RFC template by adding a *"Future possibilities"*
+section after the *"Unresolved questions"*. The newly introduced section is
+intended to help the authors, teams and readers in general reflect holistically
+on the big picture effects that a specific RFC proposal has.
 
 Please read the [reference-level-explanation] for exact details of what an
 RFC author will see in the changed template.
@@ -75,24 +75,24 @@ RFC author will see in the changed template.
 The implementation of this RFC consists of inserting the following text to the
 RFC template *after* the section *Unresolved questions*:
 
-> # Future work
+> # Future possibilities
 >
 > Think about what the natural extension and evolution of your proposal would
 > be and how it would affect the language and project as a whole in a holistic
 > way. Try to use this section as a tool to more fully consider all possible
 > interactions with the project and language in your proposal.
 > Also consider how the this all fits into the roadmap for the project
-> and of the relevant subteam.
+> and of the relevant sub-team.
 >
 > This is also a good place to "dump ideas", if they are out of scope for the
 > RFC you are writing but otherwise related.
 >
-> If you have tried and cannot think of any future work, you may simply state
-> that you cannot think of anything.
+> If you have tried and cannot think of any future possibilities,
+> you may simply state that you cannot think of anything.
 >
-> Note that having something written down in the future-work section is not
-> a reason to accept the current or a future RFC; such notes should be in the
-> section on motivation or rationale in this or subsequent RFCs.
+> Note that having something written down in the future-possibilities section
+> is not a reason to accept the current or a future RFC; such notes should be
+> in the section on motivation or rationale in this or subsequent RFCs.
 > The section merely provides additional information.
 
 # Drawbacks
@@ -106,11 +106,11 @@ There's some risk that the section will simply be left empty and unused.
 However, in the recent RFCs written by the author as noted in the [motivation],
 this has not been a problem. On the contrary, the very idea behind adding
 this section has come as a result of the experience gained by writing
-such future-work sections in the aforementioned RFCs.
+such future-possibilities sections in the aforementioned RFCs.
 
 However, some of the RFCs written by the this RFC's author have not had such
 sections. Therefore, if an RFC leaves the newly introduced section empty,
-it is not the end of the world. The section is inteded as encouragement and
+it is not the end of the world. The section is intended as encouragement and
 recommendation; it is not mandatory as no section in an RFC has ever really been. 
 
 ## Higher barrier to entry
@@ -123,10 +123,10 @@ This can raise the barrier to entry somewhat.
 However, we argue that it is worth the minor raise in the bar since
 it is OK for RFCs to leave the section empty.
 
-## Readers reacting negatively on the future work
+## Readers reacting negatively on the future possibilities
 
 Another potential drawback is that readers of the RFC will focus too much
-on what is written in the future-work section and not the actual proposal
+on what is written in the future-possibilities section and not the actual proposal
 that is made in the RFC. This has not been the case in the RFCs mentioned
 in the [motivation].
 
@@ -136,7 +136,10 @@ in the [motivation].
 1. We could rephrase the section in various ways.
    It is possible to do such tweaking in the future.
 
-2. We could rename it but the proposed name is customary.
+2. We could rename it to "possible future work" or "future work" where the latter
+   is more customary, but we have opted to use a section title that makes it more
+   clear that the contents of the section are not what is accepted but only
+   *possibilities*.
 
 3. We could move the section up and down and around.
 
@@ -150,17 +153,17 @@ in the [motivation].
 
 None of the languages enumerated in [RFC 2333] have such a section proposed
 in this RFC. However, there are plenty of academic papers published which
-do contain sections pertaining to future work. It is customary for such
-sections to be at the end of papers so as to not bore readers and keep
+do contain sections pertaining to future possibilities. It is customary for
+such sections to be at the end of papers so as to not bore readers and keep
 them reading.
 
 # Unresolved questions
 [unresolved-questions]: #unresolved-questions
 
 None as of yet.
 
-# Future work
-[future-work]: #future-work
+# Future possibilities
+[future-possibilities]: #future-possibilities
 
 [staged]: http://smallcultfollowing.com/babysteps/blog/2018/06/20/proposal-for-a-staged-rfc-process/