Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#321 コメント 9 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c
領域
desktop-dev, documentation

調査の方向性

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分
マージ済み PR（30日）
1

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

FriendsofECCE/ECCE のほかの issue

FriendsofECCE/ECCE の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。