Skip to content

Openspice #393

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 115 commits into
base: master
Choose a base branch
from
Open

Openspice #393

wants to merge 115 commits into from

Conversation

Kreijstal
Copy link

There was someone doing OpenSpice, they quit 2 years ago, maybe you'd like the changes merged!
https://github.com/TheArchiver/OpenSPICE

Kreijstal and others added 30 commits November 23, 2024 18:33
…und_thread_running at 0x000000004999c720>, trying to convert the result back to C:
@neotod
Copy link

neotod commented Jan 19, 2025

@Kreijstal sadly i think this repo is dead too :(

@Kreijstal
Copy link
Author

@Kreijstal sadly i think this repo is dead too :(

I'll accept prs on my fork

@pepijndevos
Copy link

@tapegoji @thejackal360 @FabriceSalvaire and everyone involved here:

I see there are a few forks that have some activity in them and that Fabrice seems occupied.
What would be the best way forward?
Could we add a few people as maintainers to PySpice-org?

For projects I maintain that I'm too busy for, it has worked well for me to just give people who submit good PRs commit access. Nothing bad happened, and now improvements happen without me.

If Fabrice is completely unavailable, is there one clear fork with significant activity, work, and history?
I think it'd be good to give that a distinct name, and I am a firm believer that without full time staff it is critical to have as many maintainers as possible who come and go as time allows.
If OpenSpice is taken and dead, I'd propose LibreSpice lol

@Kreijstal
Copy link
Author

@tapegoji @thejackal360 @FabriceSalvaire and everyone involved here:

I see there are a few forks that have some activity in them and that Fabrice seems occupied. What would be the best way forward? Could we add a few people as maintainers to PySpice-org?

For projects I maintain that I'm too busy for, it has worked well for me to just give people who submit good PRs commit access. Nothing bad happened, and now improvements happen without me.

If Fabrice is completely unavailable, is there one clear fork with significant activity, work, and history? I think it'd be good to give that a distinct name, and I am a firm believer that without full time staff it is critical to have as many maintainers as possible who come and go as time allows. If OpenSpice is taken and dead, I'd propose LibreSpice lol

@tapegoji updates frequently, honestly I am just using my own fork for my own ends, but if you want to fork pyspice and merge our changes I will not complain and probably do prs from time to time, the openspice changes are not mine, what is mostly important is testers are most forks have so many problems...

@tapegoji
Copy link

@pepijndevos and @Kreijstal and @thejackal360
I like this idea. Count me in.
My fork is from the devel branch (PySpice 1.6). It is in an a good condition. However, needs a lot of more work to be done.

How can we start. Let me know who is in so I can spearhead this.

@pepijndevos
Copy link

Well, let's give Fabrice a chance to respond, as keeping development under the PySpice organization would avoid a lot of trouble and confusion.

But if that fails I'd suggest setting up a new github organization, moving your fork there, and adding contributors as you see fit.

fwiw I'm at this time not an active contributor to this project, but intend to use it to simplify https://github.com/NyanCAD/Pyttoresque/ and plan to add support for gnucap. I'd be happy to first prove myself with some PRs, or help triaging open PRs to get in relevant fixes.

@tapegoji
Copy link

@pepijndevos I have been trying to reach him for months. Not sure, he wants to come back.

@pepijndevos
Copy link

Well, let's go then

@tapegoji
Copy link

Check InSpice

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants