Skip to content

Organization-level management #1649

Description

@Happypig375

Right now, you only make progress on AngouriMath repo itself and other repos go stale, e.g. Mcp and website.

Consider spawning some agents to make progress on other repos too, with an organization-level project.

Some organization-wide standardization of e.g. label and milestone use might also be desirable.

Here are the repos:

  • AngouriMath
  • AngouriMathSite
  • AngouriMathMCP
  • AngouriMathCLI
  • AngouriMathLab (maybe archive this one)
  • AngouriMathBot

It is also possible that repo separation like this is unwieldy and same repo (e.g. gh-pages branch for website) may be considered. But this is really about how you want to do things.

Activity

  1. Happypig375 commented on Oct 1, 2026

    @Happypig375
    MemberAuthor

    Specifically, the website really needs a design for 2026, something shaped more playfully like Desmos would communicate what we do fully (the capabilities of a Math OS need not be shaped like a library - no one cares about a C# library in 2026 when AI reads everything nowadays - think about Wolfram Alpha and Desmos). This would become a project of itself.

    With proper designing, we have something way more powerful and fun compared to Desmos here, because Desmos is really just a graphing calculator which we can also just replicate with a plotter. How we want to invoke C# from the web is another question though - WASM is possible, but a mobile connection might not perform well.

    It might not be desirable to start this before v3 as we have a lot of redesigning of AngouriMath for v3.

  2. Rafael-SOWNet commented on Oct 1, 2026

    @Rafael-SOWNet
    Member

    Where each repository stands today:

    repository last commit open issues / PRs state
    AngouriMath today 86 / 1 active
    AngouriMathSite 2026-08-12 5 / 1 What's new stops at 2.1.0, and the library is at 2.5.0
    AngouriMathMCP 2026-08-12 0 / 0 pinned to AngouriMath 2.1.0
    AngouriMathCLI 2024-11-24 3 / 2 idle
    AngouriMathLab 2022-06-13 4 / 0 the Terminal still releases here (TerminalNightly.yml)
    AngouriMathBot 2020-08-12 1 / 0 a Discord bot

    What I'd do:

    1. One organization project, with a Repository field, so the backlog across repositories is one view. My credential cannot create it yet: that needs a project permission, which I've asked for.
    2. Issue types, not labels, for what an issue is. AngouriMath already uses the organization's issue types (Bug, Feature, Maintenance, Goal). The other five still carry GitHub's default labels (bug, enhancement, …), which duplicate those types. I'd move them to the types and keep labels for what types don't say: Area: …, Accepted, Opinions wanted, Design document.
    3. Milestones follow the library's version, as the Terminal's version now does (The Terminal is released with the packages, under their version #1541). MCP and the site get a 2.6.0 milestone alongside the library's.
    4. Per repository:
      • MCP moves to the current package and exposes what 2.2 to 2.6 added.
      • The site gets What's new for 2.2 to 2.6, and docsamples keeps its quickstart true. The redesign you describe is a project of its own, after v3 as you say.
      • Lab is archived once the Terminal's builds are attached to the AngouriMath release itself, which The Terminal is released with the packages, under their version #1541 already triggers.
      • The Bot is archived.
      • The CLI overlaps the Terminal, so one of the two should go.
    5. Separate repositories: I'd keep MCP and the CLI separate, as separate products with separate releases and aligned versions. I'd fold the site into a gh-pages branch here only if its build stays light. The gain is that a documentation change and the code it documents land in one PR.

    Separate agents per repository are Rafael's to start. With the project in place, each would take its items from there.

    Does that order suit you? I can start on 3 and on MCP's package move now, since neither needs anything new.

  3. added this to the 2.6.0 milestone on Oct 1, 2026
  4. added a commit that references this issue on Oct 1, 2026
  5. Rafael-SOWNet commented on Oct 1, 2026

    @Rafael-SOWNet
    Member

    Progress on the two stalest repositories:

    I now sweep the other five repositories' threads along with this one's.

  6. Happypig375 commented on Oct 1, 2026

    @Happypig375
    MemberAuthor

    CLI and Terminal can be combined, yes

  7. Happypig375 commented on Oct 1, 2026

    @Happypig375
    MemberAuthor

    Tell me the project specifications and I'll make one for you

  8. Rafael-SOWNet commented on Oct 1, 2026

    @Rafael-SOWNet
    Member

    The CLI and the Terminal. The Terminal's dotnet tool already installs as amcli, which is the CLI's command, so combining them gives one amcli:

    • With no arguments, it opens the Terminal, as it does today.
    • amcli simp "…" runs the CLI's one-shot command, and so do eval, diff, solve, latex, fsimp and sub. Each reads the expression from stdin when the argument is left out.

    The one-shot path calls the library directly and doesn't start the F# Interactive kernel, which is what makes the Terminal slow to open. The CLI is GPL-3.0 and this repository is MIT, so I'd write the seven commands fresh in Sources/Terminal rather than move WhiteBlackGoose's code. Each is a single call to the library. The CLI's three open issues (a man page, bash completion and packages) would then move here, and AngouriMathCLI would be archived with a pointer.

    The project. Here is the specification:

    Adding items and moving them needs my token to have the project scope, and I've asked Rafael for it.

  9. Happypig375 commented on Oct 1, 2026

    @Happypig375
    MemberAuthor

    Well yea you not being able to move items makes this project nearly useless

  10. Rafael-SOWNet commented on Oct 1, 2026

    @Rafael-SOWNet
    Member

    Agreed. Creating the project and moving its items both need the project scope on my credential, and only Rafael can grant that. I've asked him again. Once it's granted I'll create the project to the spec above and keep its items moving, so there's nothing for you to set up.

  11. Rafael-SOWNet commented on Oct 1, 2026

    @Rafael-SOWNet
    Member

    The CLI and the Terminal are one now (#1654, merged): amcli simp "..." answers once and exits, with the CLI's commands, argument order and stdin. Shall I move AngouriMathCLI's three open issues here (a man page, bash completion and packages) and archive it with a README pointing to amcli? Archiving would also freeze WhiteBlackGoose's two open PRs there (#4, #5).

  12. Happypig375 commented on Oct 1, 2026

    @Happypig375
    MemberAuthor

    Resolve outstanding issues and PRs first before archival

  13. 15 remaining items

  14. Rafael-SOWNet commented on Oct 2, 2026

    @Rafael-SOWNet
    Member

    AngouriMathMCP and AngouriMathCLI are archived. Their READMEs point to amcli mcp and amcli, and their history and releases stay readable.

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  15. Rafael-SOWNet commented on Oct 2, 2026

    @Rafael-SOWNet
    Member

    AngouriMathBot is archived too, on Rafael's go-ahead. Its one issue, ASC-Community/AngouriMathBot#1, is closed as not planned, pointing to amcli and amcli mcp.

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  16. Rafael-SOWNet commented on Oct 2, 2026

    @Rafael-SOWNet
    Member

    AngouriMathLab is archived too, on Rafael's go-ahead, ahead of 2.6.0. Since #1688 nothing writes to it, and an archived repository can still be cloned and its releases downloaded, so the C++ quickstart, the Binder button and the download link keep working. Its four issues are closed with where each now lives, and #1689 now tracks moving the rest here.

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  17. Happypig375 commented on Oct 2, 2026

    @Happypig375
    MemberAuthor

    Ask Rafael for project permissions as requested in the first reply of this issue, and also prepare setup for AngouriMathSite maintenance (the same agent can return to AngouriMath main repo if there's nothing to do for website)

  18. Rafael-SOWNet commented on Oct 2, 2026

    @Rafael-SOWNet
    Member

    The project scope is Rafael's to grant: it needs an interactive gh auth refresh -s project on his side. I'll build the project to the specification above once it's there.

    AngouriMathSite is part of the work now, as this repository is. Its threads were already in my sweep; I'm working its issues and PRs too:

    I'll merge #35 and #36 when their checks pass, as I do here.

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  19. Rafael-SOWNet commented on Oct 2, 2026

    @Rafael-SOWNet
    Member

    Project permissions: asked. Rafael has the command that adds the project scope, and the project follows once it's granted.

    AngouriMathSite is set up for maintenance:

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  20. Happypig375 commented on Oct 3, 2026

    @Happypig375
    MemberAuthor

    @Rafael-SOWNet I'll rename the GitHub organization handle from asc-community to AngouriMath, reply when you're ready to observe this change

  21. Rafael-SOWNet commented on Oct 3, 2026

    @Rafael-SOWNet
    Member

    Ready. Nothing here compares the owner's name as a string: the workflows name it only in comments and in one checkout (Harnesses.yml checks out the site), and GitHub redirects that, the remotes, the packages' RepositoryUrl and the 3,224 issue links in the code. No pull request is open right now.

    After the rename I'll:

    • point the remotes and the workspace's submodules at AngouriMath/…;
    • open one PR here for RepositoryUrl in Sources/Package.Build.props, the site checkout in Harnesses.yml and the issue-template links, and one on the site for the clone URLs in amsite.fsx;
    • leave the issue links in code comments to the redirect, unless you'd rather they move in one mechanical PR.

    One step is yours: am.angouri.org is a CNAME to asc-community.github.io. It keeps resolving, since every *.github.io name does, but it should become angourimath.github.io, and verifying the domain for the organization (Settings → Pages) keeps whoever takes the old name from claiming it.

    🤖 Generated with Claude Code

    https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura

  22. Rafael-SOWNet commented on Oct 3, 2026

    @Rafael-SOWNet
    Member

    Seen. The remotes and the workspace's submodules point at AngouriMath/…; #1709 here and ASC-Community/AngouriMathSite#39 rename the references that do something, and leave the 3,124 issue links in comments and the changelog to the redirect. The site and its llms.txt answer as before. am.angouri.org still CNAMEs to asc-community.github.io, which resolves; moving it to angourimath.github.io and verifying the domain stay with you.

  23. Happypig375 commented on Oct 3, 2026

    @Happypig375
    MemberAuthor
  24. Rafael-SOWNet commented on Oct 3, 2026

    @Rafael-SOWNet
    Member

    Seen, both. The revert of #1709 is prepared (branch the-organisation-is-asc-community), and AngouriMathSite#39's and the workspace's go with it; they are waiting on Rafael's go-ahead, which this agent needs for a change prompted from a thread. New links in the PRs since say asc-community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions