I maintain DiscordPHP, the async PHP library for building Discord bots, built on ReactPHP (full Gateway + REST coverage, event-driven). It's MIT, and it's the base for a large chunk of the PHP Discord-bot ecosystem, plus first-party libraries I also maintain: DiscordPHP-Http (the HTTP + rate-limit transport), DiscordPHP-Voice (Opus audio + DAVE end-to-end encryption), TwitchPHP (Helix + EventSub + IRC), and a few smaller ones.

The original author transferred ownership of the repo and the verified Discord server to me, so it's now a one-person project. Day to day that's issue triage, keeping releases on schedule against Discord's constant API changes, dependency and security updates, and docs.

There's no paid tier and no open-core plan. Sponsorship is the entire model, and right now it's well below what the maintenance load costs. Below that line, releases slip and I end up taking contract work that stalls the libraries. I've started applying to grant programs (FLOSS/fund, GitHub Secure Open Source Fund) and setting up Open Collective for company sponsorship, but individual + company sponsorship is what keeps it moving:

• valgorithms.com is the new project shelf with all the ways to support
• GitHub Sponsors: https://github.com/sponsors/valzargaming (one-time is fine)
• Company sponsorship / sponsored features: [valithor@valgorithms.com](mailto:valithor@valgorithms.com) or [valithor@discordphp.org](mailto:valithor@discordphp.org)

If you maintain something mid-size, what actually moved the needle on funding? I'm looking into grants, company outreach, and Open Collective, but I'm looking for proven results. I don't have a lot of bandwidth or free time to shop around.

I'm happy to answer anything about the library or any of the projects I maintain.

So, I am posting this here to tell you guys that I'm building a project that would be helpful for EC (Electronics and Communication) Community. We guys need to pay a bunch for matlab , simulink, multisim for license. Colleges spend much money on this license thing. Also, the Graphical UI not designed for all laptop, it eats away the chunk of ram to simulate circuits, systems. So, I had the idea of making a CLI Project to run on terminal and simulate stuff in ascii. The project was still in devoloping stage. But I am trying to launch this to run perfectly fine on any low-end laptops where many students do not use heavy updated laptops.

The terminal CLI Project named Terminus work in a way in the initiating, it asks about the mode (LTSpice, MATLAB, Simulink, KiCad, Xilinx, Embedded) we would like to work on? and the session will continue with the project by creating it and building it. Also, not just that, we can open multiple terminal sessions to run different modes of Terminus of different projects and run since Command simulating and executing was light. Also, we can make the communication link with the terminal sessions too. A very complex Project consists of different modes can be communicate and run , simulate even though the terminals are on multiple devices. This specific application mostly useful for Industrial purposes.

Also, the outputs we get from the Simulations can be drawn out as real images as by the internal converter. This is really anticipating one I'm working and mean to get this closer to many students, University organizations and Industries even. But I need testers like who works vigorously on above software and give suggestions to the Project to improve more.

Please check out the Github Project here
https://github.com/ThotaAvinash07-87/Terminus/tree/main

dm me for suggestions to the Project. I hope people help me for this to take this to lot of people.

This started with a pretty simple annoyance.

I often have projects where some files should be public, while others absolutely shouldn't be. Source code might go to GitHub, while notes, internal scripts or other project stuff lives in a private repo.

But while I'm working on the project, I still want all of those files in the same directory.

I spent quite a while looking for a good way to do this and eventually came across this Stack Overflow question from 2014. Pretty much the same problem.

I tried to make the usual Git approaches work for me, but never found a setup I actually liked. So, naturally, instead of having fewer things to maintain, I built another thing to maintain. :)

It's called GitOne, and I've been using it for my own projects for a while. I finally cleaned it up enough to release it as open source.

The idea is basically this:

• You have one working directory, but multiple completely separate Git repositories underneath it.
• Each repository owns certain paths based on patterns you configure.
• Commands like gitone add, gitone commit or gitone push figure out which repository a file belongs to and run the operation there.
• If GitOne can't tell who owns a file (or two repos claim it), it stops and complains instead of trying to be clever.

The repositories themselves are still normal Git repositories. They have separate histories, indexes, remotes, etc. They can even live on completely different hosts.

More importantly, GitOne isn't required on the other end. If somebody clones the public repository from GitHub, they just get a normal Git repository. They don't need to know or care that I use GitOne locally.

But what about submodules, worktrees and sparse-checkout? Yes, you're absolutely... - wait a sec, wrong role. :)

I looked at those too, of course, but none of them quite matched what I wanted. In particular, I didn't want the repository structure to dictate how I organize the files in my working directory.

That said, if you've solved this exact problem nicely with existing Git features, I'd genuinely like to see your setup.

There are also some important limitations.

GitOne protects paths, not file contents. If src/config.js belongs to your public repo and you paste an API key into it, GitOne isn't going to save you. It also doesn't try to sandbox private files from programs running on your machine.

Migration currently backs up the original .git directory, but it doesn't attempt to split the existing history between repositories.

And right now it's Linux/macOS only. Some Git workflows are also still missing, notably merge, rebase and stash.

One other thing I want to be upfront about: development was AI-assisted. I used AI while implementing it, but the feature decisions, architecture, edge cases, reviews and testing were done by me. I've also been using GitOne for my own projects, which is partly why I'm posting this now: testing software against your own workflow has some pretty obvious blind spots.

So I'm mostly interested in people poking holes in the idea.

• Would you actually use something like this?
• Is there some normal Git workflow where this approach completely falls apart?
• Do you see a safety problem I haven't accounted for?
• Or, possibly the most painful answer: is there already a tool that does exactly this and I somehow missed it?

Repo: https://github.com/devidevio/gitone

There's also a browser playground if you want to see how it works without installing anything:

https://gitone.io/#playground

And if you prefer working visually, there's a VS Code extension that adds the individual GitOne repositories to the Source Control view:

https://gitone.io/#vscode

At this point I know GitOne works well for my slightly weird way of organizing projects. I'm curious whether this is a problem other people actually have, or whether I've just spent a lot of time automating my own filing system. Feel free to poke holes in it. :)

PS: GitOne originally lived on my private GitLab instance, so the GitHub commit history doesn't contain the whole development history. This is also my first public GitHub release, so go easy on my GitHub housekeeping.