Project strategy

Open
#6 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
cli, developer-experience

Research direction

Start by reviewing the project's packaging behavior on Windows and the Shell Conflicts discussion. Clarify the intended target developers, command coverage, and adoption goals before identifying a concrete change; the issue does not name a file, test, or entry point.

Written by the indexing model from the issue text.

Description

While we welcome this kind of activities from Microsoft teams, the set of conflicts and commands dropped from the packaging kind of raises questions who is the target group of such project.

Having the commands just blow on Windows and having to come to a table like "Shell Conflicts" isn't really that great developer experience.

Additionally having several dropped commands, which prevent porting scripts that depend on it, when projects like mingw and cygwin have them, also raises some questions.

In the end what is the goal of the project, between shell conflicts and dropped commands, in regards to developers' adoption?

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

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.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.