| |
JCH
Registered: Aug 2008
Posts: 193 |
SID Factory II
Laxity and I have decided to go BETA with SID Factory II to let all curious SID composers also have a go at this cross-platform SID editor.
We have a Facebook group that you are welcome to join. There's also a nifty user manual there. If you're not on Facebook, this thread should serve as another place where we can share questions, ideas, music, bugs, new builds, additional files, etc.
Please note that although SID Factory II is quite stable and more than capable of editing SID tunes at this point, it is still missing a few essential things such as e.g. sub tunes. We have a solid ToDo and will post new builds here as they become available.
The first official BETA build: SIDFactoryII_20200604.zip |
|
... 144 posts hidden. Click here to view all posts....
|
| |
Laxity
Registered: Aug 2005
Posts: 459 |
We’re considering the option of putting it on GitHub. I have 0 experience with this, so a factor is that we’d like to retain control of the project at the time being. I’m not quite sure how that really works on GitHub. It would be excellent if one can have a private development branch and a public ditto. There’s a bit to learn. :) Also, I can't imagine that SID factory II is much of a target for modifications yet, or might even ever be.
Anyway, I appreciate all the input from you guys. Thanks for taking the time to look at it. |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Why not put the repository on chordian.net? Full control. \=D/
(I don't trust github et al. either.) |
| |
spider-j
Registered: Oct 2004
Posts: 444 |
Quoting LaxityIt would be excellent if one can have a private development branch and a public ditto.
I'd guess that actually noone cares about dev branches unless you have a bug in master. In both cases: it's really no problem to also have dev public.
I don't think many people have the hobby to check dev branches and making fun of the ugly code they find there ;-)
Of course – as Krill pointed out – self-hosting is an option to have full control if you're really concerned about that. |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting spider-jOf course – as Krill pointed out – self-hosting is an option to have full control if you're really concerned about that. And it may even be read-only for anyone but the admin. If someone requests merging in a patch, they'd just send a diff with the latest repository version.
Worst that can happen is that they decide to fork the project and put it on github et al. themselves, but that's how it is with free and open source. :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
First of all i wouldnt bother hiding a "development branch" - that only creates more work (someone contributes a fix - and then you cant just apply it, but have to merge it into your development branch). There will be very few ppl actually looking at the code anyway - and those who do should better see the current version, and not something from the last release.
I dont recommend self hosting either if you have no experience with that - again, it only creates more work with very little gain.
If you create a github project, you should get everything you want. You can just not grant anyone write access, so you have full control over whats in the repo. And everyone who wants to contribute fixes can clone the repo and send you a pull request, which is then very easy to merge (with a single click).
I dont like github all that much myself, but thats because i had many years of exposure to subversion before, and i am just too used to it (and it does all i need/want). If you dont know either, starting with git is probably the much better idea :) (warning: it can be very WTF at times) |
| |
Krill
Registered: Apr 2002
Posts: 2839 |
Quoting GroepazI dont like github all that much myself, but thats because i had many years of exposure to subversion before, and i am just too used to it (and it does all i need/want). If you dont know either, starting with git is probably the much better idea :) (warning: it can be very WTF at times) https://docs.github.com/en/github/importing-your-projects-to-gi.. =)
Maybe git is to github what car is to carpet, or Java to JavaScript. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
One thing i seriously do NOT recommend is using github with subversion. That defeats the point and only creates more problems :) |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Ok cool. Lot’s to consider. Thanks. We currently have it in an svn repo, as we’re three people working on it in different aspects of the project. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11108 |
If you already have that, just expose it publicly for read access.... when someone wants to contribute a fix, he can just provide a "svn diff", easy enough :) |
| |
spider-j
Registered: Oct 2004
Posts: 444 |
@Laxity: It looks you're still using very old resid and residfp versions. After manually grabbing current versions from VICE and libsidplayfp for my GT2 fork I saw that Leandro (the guy who seems to do most of the work on them at the moment) has them both as standalone repositories here:
https://github.com/drfiemost/resid
and here:
https://github.com/drfiemost/residfp |
| Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 - Next |
