Merge all usages into {{ Infobox engine}}.
Split off other data to spec templates. Maybe offer the specs as nested templates?
Already uses the politically correct header(n), label(n) and data(n).
Add image_size, alt, type parameters.
Discussion/consensus needed: Should image_border and/or long_caption also be added, for compatibility with Aircraft begin?
The idea is to merge all these into a single template. {{ Infobox engine}} is the obvious page title, so merging the others into it looks the way to go.
However several of these templates, including the destination one, include technical details which appear to go against the spirit of WP:INFOBOXPURPOSE, if not the letter. But that tech stuff should not be deleted or ignored, it needs to be moved to a better home. This should be done before the templates are merged. Templated in-article sections on the engine specification are used for aero engines, including {{ pistonspecs}}, {{ jetspecs}}, {{ rocketspecs}} and {{ electricspecs}}, so these might point a way forward, although the adopted solutions are not within scope of this RfM.
The purpose of this RfM is to reach a consensus on whether the merge is, in itself, to be proceeded with or not.
To summarise the infoboxes in scope (if there are more, I cannot find them):
Before getting started, wait for the clone/merge into {{ Infobox aircraft}} to see how it deals with deprecated fields, e.g.:
Merge across non-deprecated fields from {{ Infobox aircraft begin}}, which are missing in {{ Infobox aircraft engine}}. These include the following, together with any of the above which may be kept:
{{ Infobox aircraft}} | {{ Infobox aircraft begin}} | {{ Infobox engine}} | {{ Infobox historic engine}} | {{ Infobox rocket engine}} |
---|---|---|---|---|
|
|
|
|
|
|
|
|
| |
|
|
|
Merge all usages into {{ Infobox engine}}.
Split off other data to spec templates. Maybe offer the specs as nested templates?
Already uses the politically correct header(n), label(n) and data(n).
Add image_size, alt, type parameters.
Discussion/consensus needed: Should image_border and/or long_caption also be added, for compatibility with Aircraft begin?
The idea is to merge all these into a single template. {{ Infobox engine}} is the obvious page title, so merging the others into it looks the way to go.
However several of these templates, including the destination one, include technical details which appear to go against the spirit of WP:INFOBOXPURPOSE, if not the letter. But that tech stuff should not be deleted or ignored, it needs to be moved to a better home. This should be done before the templates are merged. Templated in-article sections on the engine specification are used for aero engines, including {{ pistonspecs}}, {{ jetspecs}}, {{ rocketspecs}} and {{ electricspecs}}, so these might point a way forward, although the adopted solutions are not within scope of this RfM.
The purpose of this RfM is to reach a consensus on whether the merge is, in itself, to be proceeded with or not.
To summarise the infoboxes in scope (if there are more, I cannot find them):
Before getting started, wait for the clone/merge into {{ Infobox aircraft}} to see how it deals with deprecated fields, e.g.:
Merge across non-deprecated fields from {{ Infobox aircraft begin}}, which are missing in {{ Infobox aircraft engine}}. These include the following, together with any of the above which may be kept:
{{ Infobox aircraft}} | {{ Infobox aircraft begin}} | {{ Infobox engine}} | {{ Infobox historic engine}} | {{ Infobox rocket engine}} |
---|---|---|---|---|
|
|
|
|
|
|
|
|
| |
|
|
|