Nushell core team meeting 2023-04-26

Attendees

  • Darren
  • Antoine
  • JT
  • Stefan
  • WindSoilder
  • Reilly
  • Andres

Agenda

  • Rapid release reactions
  • Orga
    • QC without exhausting ourselves/contributors/users
    • Issue backlog

Discussed Topics

Reactions to the release

  • good reception on social media
    • IDE support
  • old-alias
    • small fraction of breaking changes
  • Release of the extension
    • interest in a non-JS LSP shim from the community

0.80 coming up

  • is our mental milestone
  • JTs impression: parser2 is much easier to work with
  • JTs side project tells us about the fun of quick build times

Building out the 1.0 wish-/checklist

QC - reaching the quality for 1.0

JT from other projects reaching 1.0: there are features that are not 1.0 ready
role of a roadmap:
this is where we are going
point people to the roadmap to steer contributions, new features should fit in
clarifies for the contributors as well (we can focus on the quality, don't need to argue about direction)

Darren:
How do we determine a command is "ready" > stability
when are we done to commit

JT: with rust for 1.0 write out what the main goals are, strip out the loose ends
-> relates to Michael's core cmd-lang effort

Thought exercise: define the quality goals for ls

Is the first command implemented in nushell proper

  • globbing inconsistency with glob/ nu-glob vs wax
  • permission mess
    • network
    • empty dir
    • platform consistency
  • performance
  • ls colors

Goal checklist to a feature freeze for each command in the core set we want to commit to

Issue volume

with the growth of the project volume will grow inevitable

low quality as well as high quality issues (they still take time to triage or investigate)

buckets for 1.0 and not 1.0

Label publicly, move to milestones/project boards

Antoine: label based on need for triage/response from core team/response from issue author

Engage the community

  • check back in with your old issues
  • encourage people to look at the backlog
    • try out first
    • then give permissions to the ones sticking with us

PR's

gh pr list –json url,number,author,title | from json | each i| \("- [(\)i.number)]((\(i.url)\) (\)i.title) (@($i.author.login))" | reverse | to text

Select a repo