Thread: [Sv1-devel] A few questions ...
Brought to you by:
cannam
Menu
▾
▴
sv1-devel
|
From: Ólafur E. <ol...@gm...> - 2017-04-09 22:02:50
|
Hi, I have a few questions related to SV development. 1. Where is the best place to ask SV related (not vamp) dev questions? 2. Is there a build instructions somewhere (apart from INSTALL.txt). 3. Do you take code submissions from the community (for bugs and features)? If so, do we have a formal/ideal protocol for such submissions (discussion, code style, how to submit, etc?) (I do have a few lines of code submission related to playback which makes my life much easier when transcribing a solo. I think it might be useful for others). 4. Has there been any discussion on moving to Git (where all the cool kids are :) ) Thanks! |
|
From: Chris C. <ca...@al...> - 2017-04-10 09:09:33
|
On Sun, 9 Apr 2017, at 23:02, Ólafur Egilsson wrote: > 1. Where is the best place to ask SV related (not vamp) dev questions? This list is not a bad place. It doesn't get much traffic at the moment, but your questions should be noticed. > 2. Is there a build instructions somewhere (apart from INSTALL.txt). For Windows there is this wiki page: https://code.soundsoftware.ac.uk/projects/sonic-visualiser/wiki/WindowsBuild30 I've also just updated the INSTALL file in the repo with a few more notes. I'm intending to make an updated source tarball with more details in this file than the 3.0.2 one had, so please do let me know what other obstacles you have run into. > 3. Do you take code submissions from the community (for bugs and > features)? Yes. > If so, do we have a formal/ideal protocol for such submissions > (discussion, code style, how to submit, etc?) Discussion here or in a tracker issue (on SourceForge for example) is good. Code style is primarily follow what exists already (camel case, 4-char indentation, avoid tab characters, opening brace at end of leading line etc). As for submissions, I'd say in the first instance send patches (here or off-list). Then we can work out repo access. > (I do have a few lines of code submission related to playback which makes > my life much easier when transcribing a solo. I think it might be useful > for others). Sounds good. > 4. Has there been any discussion on moving to Git I would like to get the repo (at the very least) mirrored on github, primarily because at the moment the situation about where to file and discuss issues is so unfriendly to new contributors. There are obstacles to do with the heavy use SV makes of Mercurial subrepositories. I've been looking into various options for dealing with that, but that work is still pending. Chris |
|
From: Ólafur E. <ol...@gm...> - 2017-09-18 20:04:31
|
Regarding moving to Git and the hg sub repo problem: Are the subrepositories every used on their own (in a different project?) Could you dump the project onto github as a fresh one with no history and no subrepos and keep repository on code.soundsoftware.ac.uk locked for the archaeologist? It's not an ideal solution, but is it worth the effort to try to include the history and repos on github? A developer interested in the project has to be incredibly dedicated if he's to fight both Hg and Qt oddities at the same time. >I would like to get the repo (at the very least) mirrored on github, >primarily because at the moment the situation about where to file and >discuss issues is so unfriendly to new contributors. There are obstacles >to do with the heavy use SV makes of Mercurial subrepositories. I've >been looking into various options for dealing with that, but that work >s still pending. On Mon, Apr 10, 2017 at 10:09 AM, Chris Cannam <ca...@al... > wrote: > > On Sun, 9 Apr 2017, at 23:02, Ólafur Egilsson wrote: > > 1. Where is the best place to ask SV related (not vamp) dev questions? > > This list is not a bad place. It doesn't get much traffic at the moment, > but your questions should be noticed. > > > 2. Is there a build instructions somewhere (apart from INSTALL.txt). > > For Windows there is this wiki page: > https://code.soundsoftware.ac.uk/projects/sonic-visualiser/ > wiki/WindowsBuild30 > > I've also just updated the INSTALL file in the repo with a few more > notes. I'm intending to make an updated source tarball with more details > in this file than the 3.0.2 one had, so please do let me know what other > obstacles you have run into. > > > 3. Do you take code submissions from the community (for bugs and > > features)? > > Yes. > > > If so, do we have a formal/ideal protocol for such submissions > > (discussion, code style, how to submit, etc?) > > Discussion here or in a tracker issue (on SourceForge for example) is > good. Code style is primarily follow what exists already (camel case, > 4-char indentation, avoid tab characters, opening brace at end of > leading line etc). > > As for submissions, I'd say in the first instance send patches (here or > off-list). Then we can work out repo access. > > > (I do have a few lines of code submission related to playback which makes > > my life much easier when transcribing a solo. I think it might be useful > > for others). > > Sounds good. > > > 4. Has there been any discussion on moving to Git > > I would like to get the repo (at the very least) mirrored on github, > primarily because at the moment the situation about where to file and > discuss issues is so unfriendly to new contributors. There are obstacles > to do with the heavy use SV makes of Mercurial subrepositories. I've > been looking into various options for dealing with that, but that work > is still pending. > > > Chris > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Sv1-devel mailing list > Sv1...@li... > https://lists.sourceforge.net/lists/listinfo/sv1-devel > |
|
From: Chris C. <ca...@al...> - 2017-09-22 15:13:23
|
On Mon, 18 Sep 2017, at 21:04, Ólafur Egilsson wrote: > Are the subrepositories every used on their own (in a different project?) Yep, SV uses a dozen or so subrepos almost all of which have an independent existence and are used in other projects. I'm also not keen on any solution that involves either moving everything into a monorepo or moving everything (including dependent libraries) to git. If moving an application repo to a different VCS means moving all its libraries as well, that's a problem I think. I have started on a github presence for SV, which you can find under its own organisation at https://github.com/sonic-visualiser. Currently this is only a mirror -- the canonical repo is the soundsoftware hg one, and that isn't going to change instantly. It somewhat experimentally uses a tool called Vext for managing external repos rather than using a specific version control system's subrepos/submodules. The short-term goal is to support CI builds through Travis and AppVeyor (that part is working) and to make this a better place to present issues, replacing both of the current trackers which are both rather obscure. After that we'll take stock again. > A developer interested in the project has to be incredibly dedicated if > he's to fight both Hg and Qt oddities at the same time. Maybe, but looked at from the other side, a developer who can meaningfully contribute to a project in C++ (complex, massive, pitfall-strewn language) using Qt (big framework) can surely cope with Mercurial! At least it's relatively simple compared to other version control systems. Chris |
Thanks for helping keep SourceForge clean.
X