Tracking issue for tutorial code/documentation parity

Open
#378 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp
Domain
documentation

Research direction

Start by reviewing the related issues #108, #109, #110, #111, #112, #274, #251, #247, #245, #179, #141, #127, #122, and #121. Determine which code and documentation mismatches remain, then update the outdated information so the tutorial's code and documentation are consistent.

Written by the indexing model from the issue text.

Description

As discussed on the last call, we'll use this to track open issues surrounding party of code and documentation esp. in regards to outdated information like the mention of old api concepts. Most of these are left-overs from the initial conversion process and just need to be updated.

Related issues:

  • #108
  • #109
  • #110
  • #111
  • #112
  • #274
  • #251
  • #247
  • #245
  • #179
  • #141
  • #127
  • #122
  • #121
Dominant language
C++
Stars
424
Forks
127
Avg merge
2d 21h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/Vulkan-Tutorial

All issues in KhronosGroup/Vulkan-Tutorial

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.