WormBase / WormBase/ACKnowledge

ACKnowledge transition to the Alliance

Open
#397 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

How do we want to refer to WormBase in the context of the Alliance? Should it be Allicance/WormBase?
This should be standardized and consistent across the form, emails, GitHub, and prohect pages

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

Review the WormBase references across the form, emails, GitHub, and project pages mentioned in the issue. First identify the current wording in each location and determine the standardized Alliance/WormBase naming that should be used. Done means the terminology is consistent across all listed surfaces.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.