luanti-org / luanti-org/luanti-org.github.io

Credits page is likely difficult to understand for someone outside our community due to inconsistent wording

Open
#389 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

@content low priority
Dominant language
SCSS
Stars
141
Forks
82
PR merge metrics
No merged PRs in 30d

Description

I was reading the Grokipedia article about Luanti (https://grokipedia.com/page/Minetest) - which as of now is fairly irrelevant in itself, but gives insight into how a relatively naive AI interprets Luanti's public presence when given the task of writing such an article. The article is a heavily modified version of the corresponding Wikipedia article.

It's mostly reasonably accurate, but one thing it distinctly gets wrong is that it doesn't understand that the core team consists of core developers and other team members. Instead it lists only the non-core-developer members as being part of the core team. Quoting that article:

"Perttu Ahola was the only developer working on the project for about six months, until Ciaran Gultnieks started making code contributions in May 2011. The roster of contributors grew and changed over the years. As of July 2020, there were 9 active core developers and 15 active contributors. As of 2025, the core team consists of 3 active core developers (Zughy, wsor, and Hugo Locurcio) and 2 other active contributors (Lucas OH and Xeno333)."

It would be fairly easy to describe the core team's structure on the Credits page (https://www.luanti.org/en/credits/) in a way where nobody would be able to make this mistake, for example by using consistent wording between the starting paragraph and the list headers below.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the Credits page at https://www.luanti.org/en/credits/ and locate its source content in the luanti-org.github.io repository. Compare the opening description with the list headings, then revise the wording so the distinction between core developers and other team members is unambiguous and verify the rendered page.

Written by the indexing model from the issue text.

Assessment

Tech stack
scss
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.