GitHub user aglinxinyuan edited a discussion: Starter tasks for new contributors

Hi everyone,

This thread tracks beginner-friendly issues carried under the `starter-task` 
label. Each one is self-contained and clearly scoped, picked so a new 
contributor can land a real change without first needing deep knowledge of the 
Amber engine or the distributed runtime.

If you're new to Texera and looking for a first contribution, this is a great 
place to start.

**Browse the live list:** https://github.com/apache/texera/labels/starter-task

> The list below is refreshed periodically as tasks get picked up and 
> completed. The label above is always the source of truth — if an issue 
> already has an assignee (someone commented `/take`), it's taken; pick one 
> that's still unassigned.

## What's available

A fresh batch of **14 unit-test-coverage tasks** — each adds a focused spec for 
one small class/util, with **no production-code changes**. The gentlest 
possible on-ramp: read one file, pin its contract, open a PR.

**Scala engine — Hugging Face codegen specs** (continuation of the merged 
`TextGenCodegen` task; mirror the existing `TextGenCodegenSpec`):
- #6249 — `QaRankingCodegen` (question-answering / zero-shot / similarity / 
ranking payload + parse snippets)
- #6250 — `ImageTaskCodegen` (9 image tasks; raw-binary vs base64+prompt 
routing)
- #6251 — `AudioTaskCodegen` (ASR / audio-classification / text-to-speech)
- #6252 — `MediaGenCodegen` (text-to-image / text-to-video)

**Frontend — pure utility specs** (plain functions, no Angular `TestBed`; 
follow `size-formatter.util.spec.ts`):
- #6253 — `computing-unit.util` resource-parsing / conversion / validation 
helpers
- #6254 — `extractErrorMessage` (normalize an unknown error into a display 
string)
- #6255 — `calculateTotalTranslate3d` (sum `translate3d(...)` offsets)
- #6256 — `replaceOneImmutable` (immutable array replace)
- #6257 — `parseLogicalOperatorPortID` (parse `"input-0"` → `{portNumber, 
portType}`)
- #6258 — `checkIfWorkflowBroken` (detect links referencing a missing operator)
- #6259 — `workflow-compilation-utils` helpers (`areAllPortSchemasEqual`, 
`addCompilationError`)

**Frontend — small-service specs** (Angular `HttpTestingController` / RxJS 
streams — a small step up):
- #6260 — `AdminSettingsService` (site-wide key/value settings REST client)
- #6261 — `ShareAccessService` (grant / revoke / owner / list REST client)
- #6262 — `PanelService` (two-`Subject` event bus)

## How to pick one up

1. Comment `/take` on the issue (on its own line) to self-assign it — `/untake` 
releases it if your plans change.
2. Fork the repo and follow the [contributing 
guide](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the 
fork-based workflow, Conventional-Commit PR titles, and how to run the backend 
(`sbt test`) and frontend (`ng test`) tests.
3. Open a PR with `Closes #<issue>` in the description.

Questions are very welcome — ask right on the issue or reply here, and a 
committer will help you scope it. Looking forward to your first PR!

## In progress

Thanks to everyone who's jumped in — **13 tasks from the earlier batches are 
now claimed and being worked on**, so they're no longer listed above: #1956, 
#3375, #3497, #3524, #3842, #4314, #4315, #4348, #5042, #5474, #5662, #5664, 
#5777. (If any of these frees up, it'll reappear on the label.)

---

### Changelog

- **July 7, 2026** — Refreshed the list: added **14** new unit-test-coverage 
tasks (#6249–#6262), retired **11** completed tasks (#3142, #3406, #3546, 
#3588, #5661, #5663, #5666, #5776, #5778, #5779, #5780), and moved the **13** 
now-claimed tasks into *In progress*.
- **June 18, 2026** — Added 7 tasks (5 unit-test specs, 1 bug fix, 1 small 
feature) and closed two already-resolved items (#4119, #4319).
- **Initial post** — Labeled a first batch of beginner-friendly issues spanning 
unit-test coverage, small bug fixes, frontend/UI polish, and small features.


GitHub link: https://github.com/apache/texera/discussions/5701

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to