Is there an issue? Send a MessageReason:
None
Changed line(s) 8,9 (click to see context) from:
This can admittedly be a frustrating situation, which sometimes leads some of the more impatient members of our community to start shouting ''"[[TitleDrop Just launch it already]]!"''
to:
This can admittedly be a frustrating situation, which sometimes leads some of the more impatient members of our community to start shouting ''"[[TitleDrop Just ''"Just launch it already]]!"''
already!"''
Is there an issue? Send a MessageReason:
Fixed an error.
Changed line(s) 6,7 (click to see context) from:
Given this kind of timeframe, it's only natural that not everyone who starts a draft will actually ''finish'' it in a timely manner. Some will inevitably forget or lose interest. Others may decide that they don't have what it takes to finish the draft. For others, life will simply get in the way. Others simply can't hit the launch button for fear that that their draft still isn't ready. Whatever the reason, many TLP drafts find themselves floating in limbo, always being worked on (or at least ''contributed to'') but never actually being ''launched''.
to:
Given this kind of timeframe, it's only natural that not everyone who starts a draft will actually ''finish'' it in a timely manner. Some will inevitably forget or lose interest. Others may decide that they don't have what it takes to finish the draft. For others, life will simply get in the way. Others simply can't hit the launch button for fear that that their draft still isn't ready. Whatever the reason, many TLP drafts find themselves floating in limbo, always being worked on (or at least ''contributed to'') but never actually being ''launched''.
Is there an issue? Send a MessageReason:
None
Changed line(s) 4,5 (click to see context) from:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely ''easy'' or ''fast.'' That's just the nature of the TLP process: some drafts can sit for weeks, if not months or even ''years'', before they reach launchworthy status.
to:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely seldom ''easy'' or ''fast.'' That's just the nature of the TLP process: some drafts can sit for weeks, if not months or even ''years'', before they reach launchworthy status.
Is there an issue? Send a MessageReason:
None
Changed line(s) 4,5 (click to see context) from:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely ''easy'' or ''fast.'' That's just the nature of the TLP process: [[DevelopmentHell some drafts can sit for weeks, if not months or even]] ''[[DevelopmentHell years]]'', [[DevelopmentHell before they reach launchworthy status]].
to:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely ''easy'' or ''fast.'' That's just the nature of the TLP process: [[DevelopmentHell some drafts can sit for weeks, if not months or even]] ''[[DevelopmentHell years]]'', [[DevelopmentHell even ''years'', before they reach launchworthy status]].status.
Changed line(s) 10,11 (click to see context) from:
Don't misunderstand: there is nothing inherently wrong with encouraging someone to launch a trope if you think it's ready. Sometimes some friendly encouragement is needed. But [[{{Jerkass}} being nasty or pushy about it]] is not the way to go about it.
to:
Don't misunderstand: there is nothing inherently wrong with encouraging someone to launch a trope if you think it's ready. Sometimes some friendly encouragement is needed. But [[{{Jerkass}} being nasty or pushy about it]] it is not the way to go about it.
Is there an issue? Send a MessageReason:
None
Changed line(s) 4,5 (click to see context) from:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely ''easy'' or ''fast.'' That's just the nature of the TLP process: some drafts can sit for weeks, if not months or even ''years'', before they reach launchworthy status.
to:
The act of proposing, writing, and stewarding a blue-ribbon TLP draft is many things, but it's rarely ''easy'' or ''fast.'' That's just the nature of the TLP process: [[DevelopmentHell some drafts can sit for weeks, if not months or even ''years'', even]] ''[[DevelopmentHell years]]'', [[DevelopmentHell before they reach launchworthy status.status]].
Changed line(s) 10,11 (click to see context) from:
Don't misunderstand: there is nothing inherently wrong with encouraging someone to launch a trope if you think it's ready. Sometimes some friendly encouragement is needed. But being nasty or pushy about it is not the way to go about it.
to:
Don't misunderstand: there is nothing inherently wrong with encouraging someone to launch a trope if you think it's ready. Sometimes some friendly encouragement is needed. But [[{{Jerkass}} being nasty or pushy about it it]] is not the way to go about it.
Is there an issue? Send a MessageReason:
None
Changed line(s) 8,9 (click to see context) from:
This can admittedly be a frustrating situation, which sometimes leads some of the more impatient members of our community to start shouting ''"Just Launch It Already!"''
to:
This can admittedly be a frustrating situation, which sometimes leads some of the more impatient members of our community to start shouting ''"Just Launch It Already!"''
''"[[TitleDrop Just launch it already]]!"''
Is there an issue? Send a MessageReason:
None
Changed line(s) 4,14 (click to see context) from:
->''"GET '''ON''' WITH IT!"''
--> -- '''{{God}}''', ''Film/MontyPythonAndTheHolyGrail''
Oh, c'mon, people, this proposal has has been slumbering at the bottom of the TropeLaunchPad for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome among TropeLaunchPad entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the entry stays in discussion for weeks, repeatedly [[Administrivia/TLPBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring an entry Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
No matter how ready you think a draft is, don't push a sponsor to launch the TLP draft. We all have lives and personal schedules, so there is no right time to launch a well-developed draft.
--> -- '''{{God}}''', ''Film/MontyPythonAndTheHolyGrail''
Oh, c'mon, people, this proposal has has been slumbering at the bottom of the TropeLaunchPad for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome among TropeLaunchPad entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the entry stays in discussion for weeks, repeatedly [[Administrivia/TLPBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring an entry Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
No matter how ready you think a draft is, don't push a sponsor to launch the TLP draft. We all have lives and personal schedules, so there is no right time to launch a well-developed draft.
to:
--> -- '''{{God}}''', ''Film/MontyPythonAndTheHolyGrail''
Oh, c'mon, people, this proposal has has been slumbering at
A common syndrome among TropeLaunchPad entries is when the original poster of the entry for
Given this kind of timeframe, it's only natural that not everyone who
This can admittedly be a frustrating situation, which sometimes leads some of
Also,
Don't misunderstand: there is nothing inherently wrong with encouraging someone to launch a trope if you think
If the sponsor is actively working on the draft, give them space and don't harrass or push them. Everyone works at their own pace, and everyone has different ideas of what makes a TLP draft "ready" for
If the draft is actually ''abandoned'' and has become Administrivia/UpForGrabs, then you do have the option of adopting and launching it yourself. However, be mindful that if you do this, ''you assume responsibility for
No
Whatever the case, no matter how ready you think a draft is, don't push a sponsor to launch the TLP draft. We all have lives and personal schedules, so there is no
Is there an issue? Send a MessageReason:
Removed per outdated pages thread.
Deleted line(s) 15 (click to see context) :
However, the same corollary applies here as in GodwinsLaw in that this rule cannot be invoked deliberately in order to steal proposals. Yeah, like that's gonna happen.
Is there an issue? Send a MessageReason:
Changed per Outdated Pages thread.
Changed line(s) 13,14 (click to see context) from:
The wiki's official made-up rule on the use of this trope is as follows: If Just Launch It Already is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and Just Launch It Already!
to:
Is there an issue? Send a MessageReason:
None
Changed line(s) 7,8 (click to see context) from:
Oh, c'mon, people, this proposal has has been slumbering at the bottom of the TropeLaunchPad page for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
to:
Oh, c'mon, people, this proposal has has been slumbering at the bottom of the TropeLaunchPad page for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
Is there an issue? Send a MessageReason:
None
Changed line(s) 9,10 (click to see context) from:
A common syndrome among TropeLaunchPad entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the entry stays in discussion for weeks, repeatedly [[Administrivia/YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
to:
A common syndrome among TropeLaunchPad entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the entry stays in discussion for weeks, repeatedly [[Administrivia/YKTTWBump [[Administrivia/TLPBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Is there an issue? Send a MessageReason:
None
Changed line(s) 7,12 (click to see context) from:
Oh, c'mon, people, this YKTTW has been slumbering at the bottom of the page for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[Administrivia/YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTW Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[Administrivia/YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTW Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
to:
Oh, c'mon, people, this YKTTW proposal has has been slumbering at the bottom of the TropeLaunchPad page for eons now! It already has over 30 replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome amongYKTTW TropeLaunchPad entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[Administrivia/YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaringa YKTTW an entry Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
A common syndrome among
Also, if you think yourself smart for declaring
Is there an issue? Send a MessageReason:
None
Changed line(s) 7,8 (click to see context) from:
Oh, c'mon, people, this YKTTW has been slumbering at the bottom of the page for eons now! It already has over 30 replies! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
to:
Oh, c'mon, people, this YKTTW has been slumbering at the bottom of the page for eons now! It already has over 30 replies! replies and ''who knows'' how many hats! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
Is there an issue? Send a MessageReason:
None
Changed line(s) 9,10 (click to see context) from:
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
to:
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump [[Administrivia/YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Is there an issue? Send a MessageReason:
Changed line(s) 13,14 (click to see context) from:
The wiki's official made-up rule on the use of this trope is as follows: If Administrivia/JustLaunchItAlready is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and Administrivia/JustLaunchItAlready!
to:
The wiki's official made-up rule on the use of this trope is as follows: If Administrivia/JustLaunchItAlready Just Launch It Already is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and Administrivia/JustLaunchItAlready!
Just Launch It Already!
Is there an issue? Send a MessageReason:
minor cleanup
Changed line(s) 1,6 (click to see context) from:
[[VisualPun http://static.tvtropes.org/pmwiki/pub/images/ReadyForLaunch.jpg]]
[[caption-width:193:It's all prepped and ready! Just [[FallingIntoTheCockpit strap in]] and push the BigRedButton!]]
''GET '''ON''' WITH IT!''
->'''{{God}}''' - ''Film/MontyPythonAndTheHolyGrail''
[[caption-width:193:It's all prepped and ready! Just [[FallingIntoTheCockpit strap in]] and push the BigRedButton!]]
''GET '''ON''' WITH IT!''
->'''{{God}}''' - ''Film/MontyPythonAndTheHolyGrail''
to:
[[caption-width:193:It's
[[caption-width-right:193:It's all prepped and ready! Just [[FallingIntoTheCockpit strap in]] and push the BigRedButton!]]
->'''{{God}}''' -
--> -- '''{{God}}''', ''Film/MontyPythonAndTheHolyGrail''
Is there an issue? Send a MessageReason:
Namespace shift
Changed line(s) 9,12 (click to see context) from:
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTW UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
Also, if you think yourself smart for declaring a YKTTW UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
to:
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it UpForGrabs.Administrivia/UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTWUpForGrabs Administrivia/UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
Also, if you think yourself smart for declaring a YKTTW
Is there an issue? Send a MessageReason:
Namespace shift
Changed line(s) 13,14 (click to see context) from:
The wiki's official made-up rule on the use of this trope is as follows: If JustLaunchItAlready is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and JustLaunchItAlready!
to:
The wiki's official made-up rule on the use of this trope is as follows: If JustLaunchItAlready Administrivia/JustLaunchItAlready is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and JustLaunchItAlready!
Administrivia/JustLaunchItAlready!
Is there an issue? Send a MessageReason:
None
Added DiffLines:
[[VisualPun http://static.tvtropes.org/pmwiki/pub/images/ReadyForLaunch.jpg]]
[[caption-width:193:It's all prepped and ready! Just [[FallingIntoTheCockpit strap in]] and push the BigRedButton!]]
''GET '''ON''' WITH IT!''
->'''{{God}}''' - ''Film/MontyPythonAndTheHolyGrail''
Oh, c'mon, people, this YKTTW has been slumbering at the bottom of the page for eons now! It already has over 30 replies! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTW UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
The wiki's official made-up rule on the use of this trope is as follows: If JustLaunchItAlready is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and JustLaunchItAlready!
However, the same corollary applies here as in GodwinsLaw in that this rule cannot be invoked deliberately in order to steal proposals. Yeah, like that's gonna happen.
----
[[caption-width:193:It's all prepped and ready! Just [[FallingIntoTheCockpit strap in]] and push the BigRedButton!]]
''GET '''ON''' WITH IT!''
->'''{{God}}''' - ''Film/MontyPythonAndTheHolyGrail''
Oh, c'mon, people, this YKTTW has been slumbering at the bottom of the page for eons now! It already has over 30 replies! Do you realize what a pain in the ass sorting all these examples will be? Just launch this monster already, before it [[{{Kaiju}} grows even more]] and [[TheTokyoFireball starts rampaging across downtown Tokyo]]!
A common syndrome among YKTTW entries is when the original poster of the entry for some reason (forgot about it/had no internet/write your own excuse) starts ignoring it without previously declaring it UpForGrabs. In this case, instead of being launched immediately after accumulating a critical example mass and [[Administrivia/NeedsABetterName finding a nice name]], the YKTTW entry stays in discussion for weeks, repeatedly [[YKTTWBump bumped]] by people who find it tropeworthy but dare not launch it themselves out of fear to offend the original poster.
Also, if you think yourself smart for declaring a YKTTW UpForGrabs and hope that somebody will launch it, we have bad news for you: no one will. Instead, the entry will accumulate another 60 replies and go down because nobody would ever want to sort that mess out. Or just go down as it is, because everybody is busy monitoring and launching their own tropes. Either way, your trope ain't gonna get launched, period. So take responsibility for your creations, damn it.
The wiki's official made-up rule on the use of this trope is as follows: If JustLaunchItAlready is used twice in a single proposal, "ownership" of the proposal falls from whoever made it to whoever has been demanding a launch. So quit yer yappin' and JustLaunchItAlready!
However, the same corollary applies here as in GodwinsLaw in that this rule cannot be invoked deliberately in order to steal proposals. Yeah, like that's gonna happen.
----