Difference between revisions of "Kerbal Space Program Wiki:Tasks"

Revision as of 03:12, 6 May 2015

This is a list of tasks. Feel free to add something you want to be checked/done and others can then claim those.

To avoid that multiple people work at the same time at the same task you should claim tasks by answering to them. Also answer to a task to remove your claim if you aren't working on it anymore and want others to finish the task.

For saving the place, delete the sequence if the task is finished, and everyone is pleased with the result!

Add a new task

Version 1.0 release

With version 1.0 we need to do some stuff:

• Thrust is now depending on pressure not flow. {{Infobox/Part/FuelConsumption}} could become obsolete and {{Infobox/Part/Thrust}} should be verified and used in the relevant templates. Also {{Thrust}} should be checked. If it's like the other template it should be merged into that and then removed.
  • The {{Infobox/Part/Thrust}} is now working and in use. {{Infobox/Part/FuelConsumption}} is only used directly by {{Infobox/Part/jet engine}}. After that dependency is fixed, the page could be moved to {{Infobox/Part/consumption}}} and the variable fuel flow specific code could be removed (moving the page to verify that nothing is using that template then).
• Updating {{Parts}} and {{Stats Table…}}

Feel free to add additional point and cross out/delete handled points. — xZise [talk] 20:52, 29 April 2015 (UTC)

UPDATING

Updating some element:

Pictures

keep the original name, just update it!

• 

  some new part has arrived since... - Done

• 

  some new part has arrived since... - Done as well

• 

  still 0.25 - check if new version changed before update - if it has remained same: just report it!

• 

  New version needed - please, without background!

• 

  “Merge” with File:Gilly Biome Map 0.90.0.png?

Shall we delete this section? Kamiakze (talk) 19:02, 22 March 2015 (CST)

This section remains, as updating is frequent (only the pictures will change). Just some friendly notes for the pictures: taken from too close - and the perspective deformed the shapes (both), the neutral background - as blue sky - is preferred (docking), and the shading each others should be avoided. A thumb up from me. NWM (talk) 17:46, 22 March 2015 (CDT) (PS: put four "~" on the end of your comment as a sign)

Its been my first attempts on these collection photos, so, thanks for the notice :) i will update them as soon as i have time (probably tomorrow) Kamiakze (talk) 20:38, 22 March 2015 (CDT)

And a further note: is the claw docking port? NWM (talk) 06:07, 28 March 2015 (CDT)

Well it works similar to one but the image is used where only the docking ports are listed. And to be honest I think it doesn't belong there but that is only my personal preference.

Regarding the image I'd have three suggestions:

• Make it when the Sun is not so high so that there aren't so many shadows making the image so dark.
• Prevent as much background as possible (my version before had only the sky as background)
• Don't look directly at it. The difference between the two lateral docking ports (the ones in the top left) is marginal from that viewpoint. You don't really see that the lower one has the Mk2 shape.

— xZise [talk] 05:33, 29 March 2015 (CDT)

Regarding the Gilly biome image: I think the low resolution image is superfluous and the only difference (which is why I haven't deleted it yet) to the high resultion image is that it has the legend. I personally would prefer if the legend is in the text below and not in the image, and in fact the list on Gilly itself could use the legend. — xZise [talk] 05:33, 29 March 2015 (CDT)

Very much agree. Text in images isn't a good practice for a multilingual resource. Also, it just clutters up the image when a separate legend does the same job. --Brendan (talk) 23:10, 29 March 2015 (CDT)

The picture can be placed in a .svg - easy to translate, but separated file for each language. A second option is a more advanced template NWM (talk) 09:13, 19 April 2015 (CDT)

What advantage would have an svg have? You need to translate it and upload a separate file. The question is if that is translatable because they are names. When someone is reading a non English article to find out which biomes there are they will see some translated ones but can't compare it to the names they have ingame. There are projects to translate KSP but even if they change the names of the biomes they might be different from the names here. — xZise [talk] 10:29, 19 April 2015 (CDT)

Yep - thats the point, why I always write the original name too. I personally prefer the second option, as we have poorly colored non informative maps NWM (talk) 12:08, 19 April 2015 (CDT)

Templates

{{TechTree}} - still 0.25 - Moderate difficulty, save game with all nodes appeared tech tree is needed. NWM (talk) 09:08, 7 March 2015 (CST)

Authors/editors look for native speaker correctors

For English speaker:

• Tutorial:Learning basics of rocket building - a step by step tutorial, only the first section of the three is ready. NWM (talk) 09:13, 19 April 2015 (CDT)

Edited up to "Action Groups" — Bob Kerman(talk) 20:10, 5 May 2015 (PST)

Name change in Rockomax Mark 55 Radial Mount Liquid Engine

The name in the description changed in Rockomax Mark 55 Radial Mount Liquid Engine. Please determine in which version that was done and update the related pages (Rockomax Mark 55 Radial Mount Liquid Engine and Eumon Kerman) respectively and maybe create Eugene Kerman (or request a move of Eumon to Eugene Kerman).

(See the comment by User:Brendan in this diff) — xZise [talk] 06:18, 3 March 2015 (CST)

For .svg mages

Creating the more informative .svg version of some picture:

• 

  Exley maneuver

• 

Make the texts correctable!

For "Orbit_Synchronization_how_to.png" - pictures by stages of the maneuver would be more preferable!

Calculate version numbers

With {{Check version/ver}} and {{Check version/Rev}} it's possible to calculate version numbers now and templates like {{Infobox/Version}} could profit from it. For example getting the version after 0.23.5 one can do {{Check version/ver|{{#expr: {{Check version/Rev|0.23.5}} + 1}}}} and get 0.24. So it's possible to get the next and previous version numbers.

It only does support version numbers since 0.20.2, so both templates probably need to be extended to support prior versions. But at no point a specific revision number should be used so that is easier to change the numbers later when I miscounted and 0.20.2 wasn't the 38^th revision. — xZise [talk] 07:41, 12 March 2015 (CDT)