blog: Feedback on cargo-info to prepare it for merging

[Rustin170506]

rendered

[Rustin170506]

cc: @epage Would you like to review the document before it's posted on the internal forum? If you're short on time, you can also provide feedback after publication. Thanks in advance.

[epage]

rendered

[epage]

I went ahead and did #109 real quick but overall, I think the question is what is your goal.

• This is written for your blog but generally things like this would be posted to Internals
• This is titled as a Pre-RFC but we don't generally use RFCs for subcommands. Instead, we use a form of a change proposal.
  • Examples: Import cargo remove into cargo rust-lang/cargo#11099, feat: Import cargo-add into cargo rust-lang/cargo#10472
  • We should probably document this
• When I've worked to merge commands, I focused on getting feedback on the unknown or uncertain areas from Internals
  • https://internals.rust-lang.org/t/feedback-on-cargo-upgrade-to-prepare-it-for-merging/17101/130
  • https://internals.rust-lang.org/t/feedback-on-cargo-add-before-its-merged/16024

[Rustin170506]

• This is titled as a Pre-RFC but we don't generally use RFCs for subcommands. Instead, we use a form of a change proposal.

Thanks! I forgot it. I've changed the title of this blog.

I think the question is what is your goal?

I want to focus on getting feedback on the unknown or uncertain designs and issues. I should emphasize the goal at the beginning or I may have too many details in this blog. What do you think? Should we put that many details in it or not?

[epage]

I want to focus on getting feedback on the unknown or uncertain designs and issues. I should emphasize the goal at the beginning or I may have too many details in this blog. What do you think? Should we put that many details in it or not?

Would Internals be a better place, than your blog?

So the goal (and now title) is about feedback but the structure doesn't show that.

For cargo add and cargo upgade,

• Opened with a very brief piece of context (related issue, that I'm looking for feedback)
• Provided a brief summary of what is done today titled "background". The title is important. "Summary" makes it sound like it'll be about your post. "Background" makes it clear that you are providing context for the questions you want answered.
• The background section is brief. I did this by focusing on the screenshot and then calling out some non-obvious points
• The remainder should be focused on the areas of concern with what context you can provide

[Rustin170506]

Would Internals be a better place, than your blog?

Yes, I will post it in the Internals. I utilize this blog as a platform to review the code(content) before publishing it.

[Rustin170506]

@epage I updated it again. I deleted the scenario demos. Mentioned some background on the command. Also emphasized that I want to discuss those issues that are still undecided. Do you think this is ok for now?

[Rustin170506]

I am going to merge this PR. I will publish it on internals later and if you have anything want to add I think you can comment on the internals forum.

Thanks for your review!

[Rustin170506]

Live now: https://internals.rust-lang.org/t/feedback-on-cargo-info-to-prepare-it-for-merging/20369