Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Discoverability: first steps a new user has to be told about

未關閉
#321 9 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
15/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
c

研究方向

Start from the Help menu entry "on Organizer…", the File menu that changes with tree selection, the right-click menu on "Local data", and the New Calculation code choice, since the issue names these as the places to change. The help index holds the "Running codes" pages the issue wants linked, and the Help → Support diagnostics zip is the item to surface. The issue is a set of six discoverability changes with no agreed design yet, so it needs maintainer decisions before code work. Done means each step is either implemented or split into its own issue.

由索引模型根據 Issue 內容生成。

描述

Collected from the first-use instructions written for a new macOS (Apple silicon) tester of 9.1.0. Each step below had to be explained in prose because the program does not lead to it. Discoverability and bug fixes are the focus of the next releases; reports from testers will be added here or filed separately.

Steps that needed explaining

  1. Help → "on Organizer…" is the entry point for all of the help, including the platform pages, but its label suggests a page about the Organizer only. Rename it (e.g. "ECCE Help") and keep Ctrl+H.
  2. Running other codes. After a local start only ECCE-QM is available. How to get ORCA, NWChem etc. is in "Running codes on macOS" (and the Linux/Windows equivalents), reachable only through the help index. The program should point there when a user looks for a code that is not set up (e.g. from New Calculation's code choice, or a Help menu entry "Running codes on this computer").
  3. Register Machines is under Tools, where a new user does not look for the place to make a code available. Link it from the same places as item 2.
  4. Creating a project or calculation is offered on right-click of "Local data" and in a File menu that changes with the tree selection. With nothing selected there is no visible way to start. Offer New Project / New Calculation in the File menu regardless of selection (defaulting to Local data), and say that a project is a folder.
  5. Example calculations. File → Open Example Calculations is the quickest way to see what ECCE does, but nothing suggests it. Import the examples automatically on the first start, into their own project ("Examples"), and record that this was done, so that deleting them does not bring them back. Applies to every deployment mode (each user's own data on a central server). File → Open Example Calculations stays, to restore them.
  6. Help → Support builds the diagnostics zip for a ticket; testers need to be told it exists. Mention it in the help start page and in error dialogs that ask the user to report a problem.

Related: #219 (help rewrite), #264 (first-calculation walkthroughs), #240 (first start).

主要語言
C
星號
10
分支
8
平均合併
21 分鐘
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。