[Csnd-dev] github reorganisation -- next steps.

classic Classic list List threaded Threaded
28 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
Thanks everyone for voting, looks like we have a consensus. Here’s what
we should do next.

There are two kinds of projects in the csound.git repo that need to be moved
out. Projects that have been collaboratively worked on, and individual projects.
We can tell this by git history or even git blame, as well as author’s lists.

For the individual projects, these should go to private repos (in the same
way that Blue, Cabbage and CsoundQt do) and become third-party projects,
even if the author collaborates on the core project.

For collaborative/community based projects, we will place these in
the Csound project.

From my original list, I have:

Csound6~ (community: several contributors, users)
Csound~  (community: several contributors, users)
csladspa  (community: two authors, users)
CsoundAC (private: single author)
CsoundVST (private: single author)
CS6Editor (private: single author)
winsound (community:  several contributors, users)
nwjs (private: single author)
icsound (private: single author)
beats (community:  several contributors, users)
Csound Android App (private: single author)

So I propose that the respective authors for the private projects above
move these to their private repositories.

I am happy to work with Steven, Rory, and other colleagues to
make the new repositories and coordinate them with csound.git

We should set a deadline for the move of private code out of the
repo so that we can do some tidying up of scripts and files. I
would tentatively say one week from today.

best regards
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

rorywalsh
I think makes sense. Especially when the projects are still being actively maintained by their authors. The less moving parts the better. I think one week from today sounds a little ambitious, but it would be great to see movement on this sooner rather than later.

On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]> wrote:
Thanks everyone for voting, looks like we have a consensus. Here’s what
we should do next.

There are two kinds of projects in the csound.git repo that need to be moved
out. Projects that have been collaboratively worked on, and individual projects.
We can tell this by git history or even git blame, as well as author’s lists.

For the individual projects, these should go to private repos (in the same
way that Blue, Cabbage and CsoundQt do) and become third-party projects,
even if the author collaborates on the core project.

For collaborative/community based projects, we will place these in
the Csound project.

From my original list, I have:

Csound6~ (community: several contributors, users)
Csound~  (community: several contributors, users)
csladspa  (community: two authors, users)
CsoundAC (private: single author)
CsoundVST (private: single author)
CS6Editor (private: single author)
winsound (community:  several contributors, users)
nwjs (private: single author)
icsound (private: single author)
beats (community:  several contributors, users)
Csound Android App (private: single author)

So I propose that the respective authors for the private projects above
move these to their private repositories.

I am happy to work with Steven, Rory, and other colleagues to
make the new repositories and coordinate them with csound.git

We should set a deadline for the move of private code out of the
repo so that we can do some tidying up of scripts and files. I
would tentatively say one week from today.

best regards
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952


Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Steven Yi
Sounds good to me too, though also like Rory one week seems tricky.  I
will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
(will move to csound/csound~ or something like that, depending on if
tildes are okay for Github project names).

I would suggest one thing though: we should make a FindCsound.cmake
module that will search for Csound and return the library to expected
things (library to link to, compiler flags, include folder, etc.).
This could be set to search in a set of typical directories and also
have an override for custom setting.  Once this is made once, it could
be copied and used by other projects moved out that use CMake.



On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:

> I think makes sense. Especially when the projects are still being actively
> maintained by their authors. The less moving parts the better. I think one
> week from today sounds a little ambitious, but it would be great to see
> movement on this sooner rather than later.
>
> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
> wrote:
>>
>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>> we should do next.
>>
>> There are two kinds of projects in the csound.git repo that need to be
>> moved
>> out. Projects that have been collaboratively worked on, and individual
>> projects.
>> We can tell this by git history or even git blame, as well as author’s
>> lists.
>>
>> For the individual projects, these should go to private repos (in the same
>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>> even if the author collaborates on the core project.
>>
>> For collaborative/community based projects, we will place these in
>> the Csound project.
>>
>> From my original list, I have:
>>
>> Csound6~ (community: several contributors, users)
>> Csound~  (community: several contributors, users)
>> csladspa  (community: two authors, users)
>> CsoundAC (private: single author)
>> CsoundVST (private: single author)
>> CS6Editor (private: single author)
>> winsound (community:  several contributors, users)
>> nwjs (private: single author)
>> icsound (private: single author)
>> beats (community:  several contributors, users)
>> Csound Android App (private: single author)
>>
>> So I propose that the respective authors for the private projects above
>> move these to their private repositories.
>>
>> I am happy to work with Steven, Rory, and other colleagues to
>> make the new repositories and coordinate them with csound.git
>>
>> We should set a deadline for the move of private code out of the
>> repo so that we can do some tidying up of scripts and files. I
>> would tentatively say one week from today.
>>
>> best regards
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Michael Gogins-2
I am fine with most of this. I had already been talking about moving
CsoundAC out of the Csound repository because, in retrospect, it was a
bit too different in concern.

After recent difficulties with trying to work with people on the
Csound for Android app, I am fine with moving that out as well, and
maintaining the repository and build for that.

No problem with nwjs. I may even quit maintaining this as I have been
working on different ways of quickly creating and editing Csound
pieces that use HTML5.

I think having something like a FindCsound.cmake module will be
essential in proceeding with this plan.

The only thing that I think is a mistake is CsoundVST. This is simple
code, works fine on Windows and Linux, and could easily be gotten to
work on OS X. I don't use this often and I don't do much to maintain
it, but I really think this should stay in the repository.

I also have some questions.

What about opcodes that are dynamically loaded or have extra dependencies?

What about distributions/packages/releases/installers? How do separate
repositories fit in with this? Here I think a package manager for
Csound that can deal with binaries would be very very useful. Then you
could have an installer that includes just core Csound and the package
manager, and people would use the package manager to install plugins
or extra frontends or whatever that they need.

Many big applications with a plugin design use such an internal
package manager, like the major IDEs, LaTex, etc.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 1:39 PM, Steven Yi <[hidden email]> wrote:

> Sounds good to me too, though also like Rory one week seems tricky.  I
> will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
> (will move to csound/csound~ or something like that, depending on if
> tildes are okay for Github project names).
>
> I would suggest one thing though: we should make a FindCsound.cmake
> module that will search for Csound and return the library to expected
> things (library to link to, compiler flags, include folder, etc.).
> This could be set to search in a set of typical directories and also
> have an override for custom setting.  Once this is made once, it could
> be copied and used by other projects moved out that use CMake.
>
>
>
> On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:
>> I think makes sense. Especially when the projects are still being actively
>> maintained by their authors. The less moving parts the better. I think one
>> week from today sounds a little ambitious, but it would be great to see
>> movement on this sooner rather than later.
>>
>> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
>> wrote:
>>>
>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>> we should do next.
>>>
>>> There are two kinds of projects in the csound.git repo that need to be
>>> moved
>>> out. Projects that have been collaboratively worked on, and individual
>>> projects.
>>> We can tell this by git history or even git blame, as well as author’s
>>> lists.
>>>
>>> For the individual projects, these should go to private repos (in the same
>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>> even if the author collaborates on the core project.
>>>
>>> For collaborative/community based projects, we will place these in
>>> the Csound project.
>>>
>>> From my original list, I have:
>>>
>>> Csound6~ (community: several contributors, users)
>>> Csound~  (community: several contributors, users)
>>> csladspa  (community: two authors, users)
>>> CsoundAC (private: single author)
>>> CsoundVST (private: single author)
>>> CS6Editor (private: single author)
>>> winsound (community:  several contributors, users)
>>> nwjs (private: single author)
>>> icsound (private: single author)
>>> beats (community:  several contributors, users)
>>> Csound Android App (private: single author)
>>>
>>> So I propose that the respective authors for the private projects above
>>> move these to their private repositories.
>>>
>>> I am happy to work with Steven, Rory, and other colleagues to
>>> make the new repositories and coordinate them with csound.git
>>>
>>> We should set a deadline for the move of private code out of the
>>> repo so that we can do some tidying up of scripts and files. I
>>> would tentatively say one week from today.
>>>
>>> best regards
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Bernt Isak Wærstad
Makes sense to me as well! Good to keep core Csound as clean as possible. And I agree a packagemanger system would be great.

On 18 January 2018 at 20:03, Michael Gogins <[hidden email]> wrote:
I am fine with most of this. I had already been talking about moving
CsoundAC out of the Csound repository because, in retrospect, it was a
bit too different in concern.

After recent difficulties with trying to work with people on the
Csound for Android app, I am fine with moving that out as well, and
maintaining the repository and build for that.

No problem with nwjs. I may even quit maintaining this as I have been
working on different ways of quickly creating and editing Csound
pieces that use HTML5.

I think having something like a FindCsound.cmake module will be
essential in proceeding with this plan.

The only thing that I think is a mistake is CsoundVST. This is simple
code, works fine on Windows and Linux, and could easily be gotten to
work on OS X. I don't use this often and I don't do much to maintain
it, but I really think this should stay in the repository.

I also have some questions.

What about opcodes that are dynamically loaded or have extra dependencies?

What about distributions/packages/releases/installers? How do separate
repositories fit in with this? Here I think a package manager for
Csound that can deal with binaries would be very very useful. Then you
could have an installer that includes just core Csound and the package
manager, and people would use the package manager to install plugins
or extra frontends or whatever that they need.

Many big applications with a plugin design use such an internal
package manager, like the major IDEs, LaTex, etc.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 1:39 PM, Steven Yi <[hidden email]> wrote:
> Sounds good to me too, though also like Rory one week seems tricky.  I
> will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
> (will move to csound/csound~ or something like that, depending on if
> tildes are okay for Github project names).
>
> I would suggest one thing though: we should make a FindCsound.cmake
> module that will search for Csound and return the library to expected
> things (library to link to, compiler flags, include folder, etc.).
> This could be set to search in a set of typical directories and also
> have an override for custom setting.  Once this is made once, it could
> be copied and used by other projects moved out that use CMake.
>
>
>
> On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:
>> I think makes sense. Especially when the projects are still being actively
>> maintained by their authors. The less moving parts the better. I think one
>> week from today sounds a little ambitious, but it would be great to see
>> movement on this sooner rather than later.
>>
>> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
>> wrote:
>>>
>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>> we should do next.
>>>
>>> There are two kinds of projects in the csound.git repo that need to be
>>> moved
>>> out. Projects that have been collaboratively worked on, and individual
>>> projects.
>>> We can tell this by git history or even git blame, as well as author’s
>>> lists.
>>>
>>> For the individual projects, these should go to private repos (in the same
>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>> even if the author collaborates on the core project.
>>>
>>> For collaborative/community based projects, we will place these in
>>> the Csound project.
>>>
>>> From my original list, I have:
>>>
>>> Csound6~ (community: several contributors, users)
>>> Csound~  (community: several contributors, users)
>>> csladspa  (community: two authors, users)
>>> CsoundAC (private: single author)
>>> CsoundVST (private: single author)
>>> CS6Editor (private: single author)
>>> winsound (community:  several contributors, users)
>>> nwjs (private: single author)
>>> icsound (private: single author)
>>> beats (community:  several contributors, users)
>>> Csound Android App (private: single author)
>>>
>>> So I propose that the respective authors for the private projects above
>>> move these to their private repositories.
>>>
>>> I am happy to work with Steven, Rory, and other colleagues to
>>> make the new repositories and coordinate them with csound.git
>>>
>>> We should set a deadline for the move of private code out of the
>>> repo so that we can do some tidying up of scripts and files. I
>>> would tentatively say one week from today.
>>>
>>> best regards
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>



--
Mvh.

Bernt Isak Wærstad


Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

rorywalsh
In reply to this post by Michael Gogins-2
The package manger / system installer is definitely something that needs to happen. It looks like we have identified the installer framework to use. That's a start. I disagree on CsoundVST. I think keeping only community maintained projects in the repo is cleaner. CsoundVST also adds an SDK dependency.

On 18 January 2018 at 19:03, Michael Gogins <[hidden email]> wrote:
I am fine with most of this. I had already been talking about moving
CsoundAC out of the Csound repository because, in retrospect, it was a
bit too different in concern.

After recent difficulties with trying to work with people on the
Csound for Android app, I am fine with moving that out as well, and
maintaining the repository and build for that.

No problem with nwjs. I may even quit maintaining this as I have been
working on different ways of quickly creating and editing Csound
pieces that use HTML5.

I think having something like a FindCsound.cmake module will be
essential in proceeding with this plan.

The only thing that I think is a mistake is CsoundVST. This is simple
code, works fine on Windows and Linux, and could easily be gotten to
work on OS X. I don't use this often and I don't do much to maintain
it, but I really think this should stay in the repository.

I also have some questions.

What about opcodes that are dynamically loaded or have extra dependencies?

What about distributions/packages/releases/installers? How do separate
repositories fit in with this? Here I think a package manager for
Csound that can deal with binaries would be very very useful. Then you
could have an installer that includes just core Csound and the package
manager, and people would use the package manager to install plugins
or extra frontends or whatever that they need.

Many big applications with a plugin design use such an internal
package manager, like the major IDEs, LaTex, etc.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 1:39 PM, Steven Yi <[hidden email]> wrote:
> Sounds good to me too, though also like Rory one week seems tricky.  I
> will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
> (will move to csound/csound~ or something like that, depending on if
> tildes are okay for Github project names).
>
> I would suggest one thing though: we should make a FindCsound.cmake
> module that will search for Csound and return the library to expected
> things (library to link to, compiler flags, include folder, etc.).
> This could be set to search in a set of typical directories and also
> have an override for custom setting.  Once this is made once, it could
> be copied and used by other projects moved out that use CMake.
>
>
>
> On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:
>> I think makes sense. Especially when the projects are still being actively
>> maintained by their authors. The less moving parts the better. I think one
>> week from today sounds a little ambitious, but it would be great to see
>> movement on this sooner rather than later.
>>
>> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
>> wrote:
>>>
>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>> we should do next.
>>>
>>> There are two kinds of projects in the csound.git repo that need to be
>>> moved
>>> out. Projects that have been collaboratively worked on, and individual
>>> projects.
>>> We can tell this by git history or even git blame, as well as author’s
>>> lists.
>>>
>>> For the individual projects, these should go to private repos (in the same
>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>> even if the author collaborates on the core project.
>>>
>>> For collaborative/community based projects, we will place these in
>>> the Csound project.
>>>
>>> From my original list, I have:
>>>
>>> Csound6~ (community: several contributors, users)
>>> Csound~  (community: several contributors, users)
>>> csladspa  (community: two authors, users)
>>> CsoundAC (private: single author)
>>> CsoundVST (private: single author)
>>> CS6Editor (private: single author)
>>> winsound (community:  several contributors, users)
>>> nwjs (private: single author)
>>> icsound (private: single author)
>>> beats (community:  several contributors, users)
>>> Csound Android App (private: single author)
>>>
>>> So I propose that the respective authors for the private projects above
>>> move these to their private repositories.
>>>
>>> I am happy to work with Steven, Rory, and other colleagues to
>>> make the new repositories and coordinate them with csound.git
>>>
>>> We should set a deadline for the move of private code out of the
>>> repo so that we can do some tidying up of scripts and files. I
>>> would tentatively say one week from today.
>>>
>>> best regards
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Bernt Isak Wærstad
In reply to this post by Bernt Isak Wærstad
There's been several discussions about a package manger before. Perhaps CS7 and namespaces need to happen before we can get it in place?

http://csound.1045644.n5.nabble.com/Csnd-About-the-package-manager-td5758417.html

On 18 January 2018 at 20:11, Bernt Isak Wærstad <[hidden email]> wrote:
Makes sense to me as well! Good to keep core Csound as clean as possible. And I agree a packagemanger system would be great.

On 18 January 2018 at 20:03, Michael Gogins <[hidden email]> wrote:
I am fine with most of this. I had already been talking about moving
CsoundAC out of the Csound repository because, in retrospect, it was a
bit too different in concern.

After recent difficulties with trying to work with people on the
Csound for Android app, I am fine with moving that out as well, and
maintaining the repository and build for that.

No problem with nwjs. I may even quit maintaining this as I have been
working on different ways of quickly creating and editing Csound
pieces that use HTML5.

I think having something like a FindCsound.cmake module will be
essential in proceeding with this plan.

The only thing that I think is a mistake is CsoundVST. This is simple
code, works fine on Windows and Linux, and could easily be gotten to
work on OS X. I don't use this often and I don't do much to maintain
it, but I really think this should stay in the repository.

I also have some questions.

What about opcodes that are dynamically loaded or have extra dependencies?

What about distributions/packages/releases/installers? How do separate
repositories fit in with this? Here I think a package manager for
Csound that can deal with binaries would be very very useful. Then you
could have an installer that includes just core Csound and the package
manager, and people would use the package manager to install plugins
or extra frontends or whatever that they need.

Many big applications with a plugin design use such an internal
package manager, like the major IDEs, LaTex, etc.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 1:39 PM, Steven Yi <[hidden email]> wrote:
> Sounds good to me too, though also like Rory one week seems tricky.  I
> will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
> (will move to csound/csound~ or something like that, depending on if
> tildes are okay for Github project names).
>
> I would suggest one thing though: we should make a FindCsound.cmake
> module that will search for Csound and return the library to expected
> things (library to link to, compiler flags, include folder, etc.).
> This could be set to search in a set of typical directories and also
> have an override for custom setting.  Once this is made once, it could
> be copied and used by other projects moved out that use CMake.
>
>
>
> On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:
>> I think makes sense. Especially when the projects are still being actively
>> maintained by their authors. The less moving parts the better. I think one
>> week from today sounds a little ambitious, but it would be great to see
>> movement on this sooner rather than later.
>>
>> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
>> wrote:
>>>
>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>> we should do next.
>>>
>>> There are two kinds of projects in the csound.git repo that need to be
>>> moved
>>> out. Projects that have been collaboratively worked on, and individual
>>> projects.
>>> We can tell this by git history or even git blame, as well as author’s
>>> lists.
>>>
>>> For the individual projects, these should go to private repos (in the same
>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>> even if the author collaborates on the core project.
>>>
>>> For collaborative/community based projects, we will place these in
>>> the Csound project.
>>>
>>> From my original list, I have:
>>>
>>> Csound6~ (community: several contributors, users)
>>> Csound~  (community: several contributors, users)
>>> csladspa  (community: two authors, users)
>>> CsoundAC (private: single author)
>>> CsoundVST (private: single author)
>>> CS6Editor (private: single author)
>>> winsound (community:  several contributors, users)
>>> nwjs (private: single author)
>>> icsound (private: single author)
>>> beats (community:  several contributors, users)
>>> Csound Android App (private: single author)
>>>
>>> So I propose that the respective authors for the private projects above
>>> move these to their private repositories.
>>>
>>> I am happy to work with Steven, Rory, and other colleagues to
>>> make the new repositories and coordinate them with csound.git
>>>
>>> We should set a deadline for the move of private code out of the
>>> repo so that we can do some tidying up of scripts and files. I
>>> would tentatively say one week from today.
>>>
>>> best regards
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>



--
Mvh.

Bernt Isak Wærstad





--
Mvh.

Bernt Isak Wærstad


Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
In reply to this post by rorywalsh
Yes, once we have a cleaner core repository, it would be easier to think of a package manager.
It’s in the Csound 7 roadmap.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 18 Jan 2018, at 19:14, Rory Walsh <[hidden email]> wrote:
>
> The package manger / system installer is definitely something that needs to happen. It looks like we have identified the installer framework to use. That's a start. I disagree on CsoundVST. I think keeping only community maintained projects in the repo is cleaner. CsoundVST also adds an SDK dependency.
>
> On 18 January 2018 at 19:03, Michael Gogins <[hidden email]> wrote:
> I am fine with most of this. I had already been talking about moving
> CsoundAC out of the Csound repository because, in retrospect, it was a
> bit too different in concern.
>
> After recent difficulties with trying to work with people on the
> Csound for Android app, I am fine with moving that out as well, and
> maintaining the repository and build for that.
>
> No problem with nwjs. I may even quit maintaining this as I have been
> working on different ways of quickly creating and editing Csound
> pieces that use HTML5.
>
> I think having something like a FindCsound.cmake module will be
> essential in proceeding with this plan.
>
> The only thing that I think is a mistake is CsoundVST. This is simple
> code, works fine on Windows and Linux, and could easily be gotten to
> work on OS X. I don't use this often and I don't do much to maintain
> it, but I really think this should stay in the repository.
>
> I also have some questions.
>
> What about opcodes that are dynamically loaded or have extra dependencies?
>
> What about distributions/packages/releases/installers? How do separate
> repositories fit in with this? Here I think a package manager for
> Csound that can deal with binaries would be very very useful. Then you
> could have an installer that includes just core Csound and the package
> manager, and people would use the package manager to install plugins
> or extra frontends or whatever that they need.
>
> Many big applications with a plugin design use such an internal
> package manager, like the major IDEs, LaTex, etc.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Thu, Jan 18, 2018 at 1:39 PM, Steven Yi <[hidden email]> wrote:
> > Sounds good to me too, though also like Rory one week seems tricky.  I
> > will work on CS6Editor (will move to kunstmusik/CS6Editor) and csound~
> > (will move to csound/csound~ or something like that, depending on if
> > tildes are okay for Github project names).
> >
> > I would suggest one thing though: we should make a FindCsound.cmake
> > module that will search for Csound and return the library to expected
> > things (library to link to, compiler flags, include folder, etc.).
> > This could be set to search in a set of typical directories and also
> > have an override for custom setting.  Once this is made once, it could
> > be copied and used by other projects moved out that use CMake.
> >
> >
> >
> > On Thu, Jan 18, 2018 at 1:34 PM, Rory Walsh <[hidden email]> wrote:
> >> I think makes sense. Especially when the projects are still being actively
> >> maintained by their authors. The less moving parts the better. I think one
> >> week from today sounds a little ambitious, but it would be great to see
> >> movement on this sooner rather than later.
> >>
> >> On 18 January 2018 at 18:21, Victor Lazzarini <[hidden email]>
> >> wrote:
> >>>
> >>> Thanks everyone for voting, looks like we have a consensus. Here’s what
> >>> we should do next.
> >>>
> >>> There are two kinds of projects in the csound.git repo that need to be
> >>> moved
> >>> out. Projects that have been collaboratively worked on, and individual
> >>> projects.
> >>> We can tell this by git history or even git blame, as well as author’s
> >>> lists.
> >>>
> >>> For the individual projects, these should go to private repos (in the same
> >>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
> >>> even if the author collaborates on the core project.
> >>>
> >>> For collaborative/community based projects, we will place these in
> >>> the Csound project.
> >>>
> >>> From my original list, I have:
> >>>
> >>> Csound6~ (community: several contributors, users)
> >>> Csound~  (community: several contributors, users)
> >>> csladspa  (community: two authors, users)
> >>> CsoundAC (private: single author)
> >>> CsoundVST (private: single author)
> >>> CS6Editor (private: single author)
> >>> winsound (community:  several contributors, users)
> >>> nwjs (private: single author)
> >>> icsound (private: single author)
> >>> beats (community:  several contributors, users)
> >>> Csound Android App (private: single author)
> >>>
> >>> So I propose that the respective authors for the private projects above
> >>> move these to their private repositories.
> >>>
> >>> I am happy to work with Steven, Rory, and other colleagues to
> >>> make the new repositories and coordinate them with csound.git
> >>>
> >>> We should set a deadline for the move of private code out of the
> >>> repo so that we can do some tidying up of scripts and files. I
> >>> would tentatively say one week from today.
> >>>
> >>> best regards
> >>> ========================
> >>> Prof. Victor Lazzarini
> >>> Dean of Arts, Celtic Studies, and Philosophy,
> >>> Maynooth University,
> >>> Maynooth, Co Kildare, Ireland
> >>> Tel: 00 353 7086936
> >>> Fax: 00 353 1 7086952
> >>>
> >>
>

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Felipe Sateler
In reply to this post by Victor Lazzarini-2
Just a quick note as a downstream packager. In general I agree with
splitting things out, but do note that this also impacts us.

My primary concern is the extra work it implies for me  to have
several upstreams to track as opposed to a single one. Reality is that
I'm already too overloaded so I can't commit to taking up extra
packages. This will probably mean that only the core csound package
will continue to be delivered via the debian repositories, at least
initially. It is possible I could also package up some of the simpler
and less dynamic ones (that is, infrequently updated), but I won't
make any promises.

I do offer to assist if someone wants to take up the work of
maintaining the extra packages, and to do the sponsoring required to
upload to debian. I encourage debian/ubuntu users to try to help
maintaining the csound packages, as I find myself increasignly unable
to keep up (I still haven't uploaded 6.10...).

Saludos



On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
<[hidden email]> wrote:

> Thanks everyone for voting, looks like we have a consensus. Here’s what
> we should do next.
>
> There are two kinds of projects in the csound.git repo that need to be moved
> out. Projects that have been collaboratively worked on, and individual projects.
> We can tell this by git history or even git blame, as well as author’s lists.
>
> For the individual projects, these should go to private repos (in the same
> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
> even if the author collaborates on the core project.
>
> For collaborative/community based projects, we will place these in
> the Csound project.
>
> From my original list, I have:
>
> Csound6~ (community: several contributors, users)
> Csound~  (community: several contributors, users)
> csladspa  (community: two authors, users)
> CsoundAC (private: single author)
> CsoundVST (private: single author)
> CS6Editor (private: single author)
> winsound (community:  several contributors, users)
> nwjs (private: single author)
> icsound (private: single author)
> beats (community:  several contributors, users)
> Csound Android App (private: single author)
>
> So I propose that the respective authors for the private projects above
> move these to their private repositories.
>
> I am happy to work with Steven, Rory, and other colleagues to
> make the new repositories and coordinate them with csound.git
>
> We should set a deadline for the move of private code out of the
> repo so that we can do some tidying up of scripts and files. I
> would tentatively say one week from today.
>
> best regards
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>



--

Saludos,
Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
That sounds OK to me. The Csound core package is what matters most. Maybe this
would simplify things for you in terms of packaging.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>
> Just a quick note as a downstream packager. In general I agree with
> splitting things out, but do note that this also impacts us.
>
> My primary concern is the extra work it implies for me  to have
> several upstreams to track as opposed to a single one. Reality is that
> I'm already too overloaded so I can't commit to taking up extra
> packages. This will probably mean that only the core csound package
> will continue to be delivered via the debian repositories, at least
> initially. It is possible I could also package up some of the simpler
> and less dynamic ones (that is, infrequently updated), but I won't
> make any promises.
>
> I do offer to assist if someone wants to take up the work of
> maintaining the extra packages, and to do the sponsoring required to
> upload to debian. I encourage debian/ubuntu users to try to help
> maintaining the csound packages, as I find myself increasignly unable
> to keep up (I still haven't uploaded 6.10...).
>
> Saludos
>
>
>
> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
> <[hidden email]> wrote:
>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>> we should do next.
>>
>> There are two kinds of projects in the csound.git repo that need to be moved
>> out. Projects that have been collaboratively worked on, and individual projects.
>> We can tell this by git history or even git blame, as well as author’s lists.
>>
>> For the individual projects, these should go to private repos (in the same
>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>> even if the author collaborates on the core project.
>>
>> For collaborative/community based projects, we will place these in
>> the Csound project.
>>
>> From my original list, I have:
>>
>> Csound6~ (community: several contributors, users)
>> Csound~  (community: several contributors, users)
>> csladspa  (community: two authors, users)
>> CsoundAC (private: single author)
>> CsoundVST (private: single author)
>> CS6Editor (private: single author)
>> winsound (community:  several contributors, users)
>> nwjs (private: single author)
>> icsound (private: single author)
>> beats (community:  several contributors, users)
>> Csound Android App (private: single author)
>>
>> So I propose that the respective authors for the private projects above
>> move these to their private repositories.
>>
>> I am happy to work with Steven, Rory, and other colleagues to
>> make the new repositories and coordinate them with csound.git
>>
>> We should set a deadline for the move of private code out of the
>> repo so that we can do some tidying up of scripts and files. I
>> would tentatively say one week from today.
>>
>> best regards
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>
>
>
> --
>
> Saludos,
> Felipe Sateler

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Felipe Sateler
Yes, it will probably simplify things. It should also make it easier
to update, since a full build will take a lot less time.

On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
<[hidden email]> wrote:

> That sounds OK to me. The Csound core package is what matters most. Maybe this
> would simplify things for you in terms of packaging.
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>
>> Just a quick note as a downstream packager. In general I agree with
>> splitting things out, but do note that this also impacts us.
>>
>> My primary concern is the extra work it implies for me  to have
>> several upstreams to track as opposed to a single one. Reality is that
>> I'm already too overloaded so I can't commit to taking up extra
>> packages. This will probably mean that only the core csound package
>> will continue to be delivered via the debian repositories, at least
>> initially. It is possible I could also package up some of the simpler
>> and less dynamic ones (that is, infrequently updated), but I won't
>> make any promises.
>>
>> I do offer to assist if someone wants to take up the work of
>> maintaining the extra packages, and to do the sponsoring required to
>> upload to debian. I encourage debian/ubuntu users to try to help
>> maintaining the csound packages, as I find myself increasignly unable
>> to keep up (I still haven't uploaded 6.10...).
>>
>> Saludos
>>
>>
>>
>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>> <[hidden email]> wrote:
>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>> we should do next.
>>>
>>> There are two kinds of projects in the csound.git repo that need to be moved
>>> out. Projects that have been collaboratively worked on, and individual projects.
>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>
>>> For the individual projects, these should go to private repos (in the same
>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>> even if the author collaborates on the core project.
>>>
>>> For collaborative/community based projects, we will place these in
>>> the Csound project.
>>>
>>> From my original list, I have:
>>>
>>> Csound6~ (community: several contributors, users)
>>> Csound~  (community: several contributors, users)
>>> csladspa  (community: two authors, users)
>>> CsoundAC (private: single author)
>>> CsoundVST (private: single author)
>>> CS6Editor (private: single author)
>>> winsound (community:  several contributors, users)
>>> nwjs (private: single author)
>>> icsound (private: single author)
>>> beats (community:  several contributors, users)
>>> Csound Android App (private: single author)
>>>
>>> So I propose that the respective authors for the private projects above
>>> move these to their private repositories.
>>>
>>> I am happy to work with Steven, Rory, and other colleagues to
>>> make the new repositories and coordinate them with csound.git
>>>
>>> We should set a deadline for the move of private code out of the
>>> repo so that we can do some tidying up of scripts and files. I
>>> would tentatively say one week from today.
>>>
>>> best regards
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>



--

Saludos,
Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Steven Yi
* I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor

* For csound~ (Max), I created a new repository called csound_tilde at
https://github.com/csound/csound_tilde. I did this by locally
splitting off the folder from frontends using git following these
steps:

https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/

Following these steps retains the history for all of the files within
the folder. The new repository is now at:

https://github.com/csound/csound_tilde

As it is now, csound~ is just split off.  The CMake file needs
revisions to look for Csound installation and it probably should be
updated to use Max7 SDK (amongst other things, this hasn't been
compiled in quite some time so who knows).  Or whomever might want to
take it over can do with it as they wish (i.e., create visual studio
and xcode projects, much as it used to be before being redone with
CMake).  We could look at OSSIA for some ideas about updating to pull
down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building

Since csound~ has not been maintained for a while now, I have gone
ahead and removed it from csound/frontends.


On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:

> Yes, it will probably simplify things. It should also make it easier
> to update, since a full build will take a lot less time.
>
> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
> <[hidden email]> wrote:
>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>> would simplify things for you in terms of packaging.
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>
>>> Just a quick note as a downstream packager. In general I agree with
>>> splitting things out, but do note that this also impacts us.
>>>
>>> My primary concern is the extra work it implies for me  to have
>>> several upstreams to track as opposed to a single one. Reality is that
>>> I'm already too overloaded so I can't commit to taking up extra
>>> packages. This will probably mean that only the core csound package
>>> will continue to be delivered via the debian repositories, at least
>>> initially. It is possible I could also package up some of the simpler
>>> and less dynamic ones (that is, infrequently updated), but I won't
>>> make any promises.
>>>
>>> I do offer to assist if someone wants to take up the work of
>>> maintaining the extra packages, and to do the sponsoring required to
>>> upload to debian. I encourage debian/ubuntu users to try to help
>>> maintaining the csound packages, as I find myself increasignly unable
>>> to keep up (I still haven't uploaded 6.10...).
>>>
>>> Saludos
>>>
>>>
>>>
>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>> <[hidden email]> wrote:
>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>> we should do next.
>>>>
>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>
>>>> For the individual projects, these should go to private repos (in the same
>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>> even if the author collaborates on the core project.
>>>>
>>>> For collaborative/community based projects, we will place these in
>>>> the Csound project.
>>>>
>>>> From my original list, I have:
>>>>
>>>> Csound6~ (community: several contributors, users)
>>>> Csound~  (community: several contributors, users)
>>>> csladspa  (community: two authors, users)
>>>> CsoundAC (private: single author)
>>>> CsoundVST (private: single author)
>>>> CS6Editor (private: single author)
>>>> winsound (community:  several contributors, users)
>>>> nwjs (private: single author)
>>>> icsound (private: single author)
>>>> beats (community:  several contributors, users)
>>>> Csound Android App (private: single author)
>>>>
>>>> So I propose that the respective authors for the private projects above
>>>> move these to their private repositories.
>>>>
>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>> make the new repositories and coordinate them with csound.git
>>>>
>>>> We should set a deadline for the move of private code out of the
>>>> repo so that we can do some tidying up of scripts and files. I
>>>> would tentatively say one week from today.
>>>>
>>>> best regards
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Michael Gogins-2
I will do this for CsoundAC, the Csound for Android app, and nwjs,
starting tomorrow (not sure how long it will take).

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:

> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
>
> * For csound~ (Max), I created a new repository called csound_tilde at
> https://github.com/csound/csound_tilde. I did this by locally
> splitting off the folder from frontends using git following these
> steps:
>
> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
>
> Following these steps retains the history for all of the files within
> the folder. The new repository is now at:
>
> https://github.com/csound/csound_tilde
>
> As it is now, csound~ is just split off.  The CMake file needs
> revisions to look for Csound installation and it probably should be
> updated to use Max7 SDK (amongst other things, this hasn't been
> compiled in quite some time so who knows).  Or whomever might want to
> take it over can do with it as they wish (i.e., create visual studio
> and xcode projects, much as it used to be before being redone with
> CMake).  We could look at OSSIA for some ideas about updating to pull
> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
>
> Since csound~ has not been maintained for a while now, I have gone
> ahead and removed it from csound/frontends.
>
>
> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
>> Yes, it will probably simplify things. It should also make it easier
>> to update, since a full build will take a lot less time.
>>
>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
>> <[hidden email]> wrote:
>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>>> would simplify things for you in terms of packaging.
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>>
>>>> Just a quick note as a downstream packager. In general I agree with
>>>> splitting things out, but do note that this also impacts us.
>>>>
>>>> My primary concern is the extra work it implies for me  to have
>>>> several upstreams to track as opposed to a single one. Reality is that
>>>> I'm already too overloaded so I can't commit to taking up extra
>>>> packages. This will probably mean that only the core csound package
>>>> will continue to be delivered via the debian repositories, at least
>>>> initially. It is possible I could also package up some of the simpler
>>>> and less dynamic ones (that is, infrequently updated), but I won't
>>>> make any promises.
>>>>
>>>> I do offer to assist if someone wants to take up the work of
>>>> maintaining the extra packages, and to do the sponsoring required to
>>>> upload to debian. I encourage debian/ubuntu users to try to help
>>>> maintaining the csound packages, as I find myself increasignly unable
>>>> to keep up (I still haven't uploaded 6.10...).
>>>>
>>>> Saludos
>>>>
>>>>
>>>>
>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>>> <[hidden email]> wrote:
>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>>> we should do next.
>>>>>
>>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>>
>>>>> For the individual projects, these should go to private repos (in the same
>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>>> even if the author collaborates on the core project.
>>>>>
>>>>> For collaborative/community based projects, we will place these in
>>>>> the Csound project.
>>>>>
>>>>> From my original list, I have:
>>>>>
>>>>> Csound6~ (community: several contributors, users)
>>>>> Csound~  (community: several contributors, users)
>>>>> csladspa  (community: two authors, users)
>>>>> CsoundAC (private: single author)
>>>>> CsoundVST (private: single author)
>>>>> CS6Editor (private: single author)
>>>>> winsound (community:  several contributors, users)
>>>>> nwjs (private: single author)
>>>>> icsound (private: single author)
>>>>> beats (community:  several contributors, users)
>>>>> Csound Android App (private: single author)
>>>>>
>>>>> So I propose that the respective authors for the private projects above
>>>>> move these to their private repositories.
>>>>>
>>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>>> make the new repositories and coordinate them with csound.git
>>>>>
>>>>> We should set a deadline for the move of private code out of the
>>>>> repo so that we can do some tidying up of scripts and files. I
>>>>> would tentatively say one week from today.
>>>>>
>>>>> best regards
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Saludos,
>>>> Felipe Sateler
>>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
Don’t forget CsoundVST also.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 18 Jan 2018, at 23:44, Michael Gogins <[hidden email]> wrote:
>
> I will do this for CsoundAC, the Csound for Android app, and nwjs,
> starting tomorrow (not sure how long it will take).
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
>> On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
>> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
>>
>> * For csound~ (Max), I created a new repository called csound_tilde at
>> https://github.com/csound/csound_tilde. I did this by locally
>> splitting off the folder from frontends using git following these
>> steps:
>>
>> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
>>
>> Following these steps retains the history for all of the files within
>> the folder. The new repository is now at:
>>
>> https://github.com/csound/csound_tilde
>>
>> As it is now, csound~ is just split off.  The CMake file needs
>> revisions to look for Csound installation and it probably should be
>> updated to use Max7 SDK (amongst other things, this hasn't been
>> compiled in quite some time so who knows).  Or whomever might want to
>> take it over can do with it as they wish (i.e., create visual studio
>> and xcode projects, much as it used to be before being redone with
>> CMake).  We could look at OSSIA for some ideas about updating to pull
>> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
>>
>> Since csound~ has not been maintained for a while now, I have gone
>> ahead and removed it from csound/frontends.
>>
>>
>>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
>>> Yes, it will probably simplify things. It should also make it easier
>>> to update, since a full build will take a lot less time.
>>>
>>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
>>> <[hidden email]> wrote:
>>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>>>> would simplify things for you in terms of packaging.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>>>
>>>>> Just a quick note as a downstream packager. In general I agree with
>>>>> splitting things out, but do note that this also impacts us.
>>>>>
>>>>> My primary concern is the extra work it implies for me  to have
>>>>> several upstreams to track as opposed to a single one. Reality is that
>>>>> I'm already too overloaded so I can't commit to taking up extra
>>>>> packages. This will probably mean that only the core csound package
>>>>> will continue to be delivered via the debian repositories, at least
>>>>> initially. It is possible I could also package up some of the simpler
>>>>> and less dynamic ones (that is, infrequently updated), but I won't
>>>>> make any promises.
>>>>>
>>>>> I do offer to assist if someone wants to take up the work of
>>>>> maintaining the extra packages, and to do the sponsoring required to
>>>>> upload to debian. I encourage debian/ubuntu users to try to help
>>>>> maintaining the csound packages, as I find myself increasignly unable
>>>>> to keep up (I still haven't uploaded 6.10...).
>>>>>
>>>>> Saludos
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>>>> <[hidden email]> wrote:
>>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>>>> we should do next.
>>>>>>
>>>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>>>
>>>>>> For the individual projects, these should go to private repos (in the same
>>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>>>> even if the author collaborates on the core project.
>>>>>>
>>>>>> For collaborative/community based projects, we will place these in
>>>>>> the Csound project.
>>>>>>
>>>>>> From my original list, I have:
>>>>>>
>>>>>> Csound6~ (community: several contributors, users)
>>>>>> Csound~  (community: several contributors, users)
>>>>>> csladspa  (community: two authors, users)
>>>>>> CsoundAC (private: single author)
>>>>>> CsoundVST (private: single author)
>>>>>> CS6Editor (private: single author)
>>>>>> winsound (community:  several contributors, users)
>>>>>> nwjs (private: single author)
>>>>>> icsound (private: single author)
>>>>>> beats (community:  several contributors, users)
>>>>>> Csound Android App (private: single author)
>>>>>>
>>>>>> So I propose that the respective authors for the private projects above
>>>>>> move these to their private repositories.
>>>>>>
>>>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>>>> make the new repositories and coordinate them with csound.git
>>>>>>
>>>>>> We should set a deadline for the move of private code out of the
>>>>>> repo so that we can do some tidying up of scripts and files. I
>>>>>> would tentatively say one week from today.
>>>>>>
>>>>>> best regards
>>>>>> ========================
>>>>>> Prof. Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
In reply to this post by Steven Yi
Who is the author of icsound? Andrés?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 18 Jan 2018, at 22:50, Steven Yi <[hidden email]> wrote:
>
> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
>
> * For csound~ (Max), I created a new repository called csound_tilde at
> https://github.com/csound/csound_tilde. I did this by locally
> splitting off the folder from frontends using git following these
> steps:
>
> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
>
> Following these steps retains the history for all of the files within
> the folder. The new repository is now at:
>
> https://github.com/csound/csound_tilde
>
> As it is now, csound~ is just split off.  The CMake file needs
> revisions to look for Csound installation and it probably should be
> updated to use Max7 SDK (amongst other things, this hasn't been
> compiled in quite some time so who knows).  Or whomever might want to
> take it over can do with it as they wish (i.e., create visual studio
> and xcode projects, much as it used to be before being redone with
> CMake).  We could look at OSSIA for some ideas about updating to pull
> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
>
> Since csound~ has not been maintained for a while now, I have gone
> ahead and removed it from csound/frontends.
>
>
>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
>> Yes, it will probably simplify things. It should also make it easier
>> to update, since a full build will take a lot less time.
>>
>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
>> <[hidden email]> wrote:
>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>>> would simplify things for you in terms of packaging.
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>>
>>>> Just a quick note as a downstream packager. In general I agree with
>>>> splitting things out, but do note that this also impacts us.
>>>>
>>>> My primary concern is the extra work it implies for me  to have
>>>> several upstreams to track as opposed to a single one. Reality is that
>>>> I'm already too overloaded so I can't commit to taking up extra
>>>> packages. This will probably mean that only the core csound package
>>>> will continue to be delivered via the debian repositories, at least
>>>> initially. It is possible I could also package up some of the simpler
>>>> and less dynamic ones (that is, infrequently updated), but I won't
>>>> make any promises.
>>>>
>>>> I do offer to assist if someone wants to take up the work of
>>>> maintaining the extra packages, and to do the sponsoring required to
>>>> upload to debian. I encourage debian/ubuntu users to try to help
>>>> maintaining the csound packages, as I find myself increasignly unable
>>>> to keep up (I still haven't uploaded 6.10...).
>>>>
>>>> Saludos
>>>>
>>>>
>>>>
>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>>> <[hidden email]> wrote:
>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>>> we should do next.
>>>>>
>>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>>
>>>>> For the individual projects, these should go to private repos (in the same
>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>>> even if the author collaborates on the core project.
>>>>>
>>>>> For collaborative/community based projects, we will place these in
>>>>> the Csound project.
>>>>>
>>>>> From my original list, I have:
>>>>>
>>>>> Csound6~ (community: several contributors, users)
>>>>> Csound~  (community: several contributors, users)
>>>>> csladspa  (community: two authors, users)
>>>>> CsoundAC (private: single author)
>>>>> CsoundVST (private: single author)
>>>>> CS6Editor (private: single author)
>>>>> winsound (community:  several contributors, users)
>>>>> nwjs (private: single author)
>>>>> icsound (private: single author)
>>>>> beats (community:  several contributors, users)
>>>>> Csound Android App (private: single author)
>>>>>
>>>>> So I propose that the respective authors for the private projects above
>>>>> move these to their private repositories.
>>>>>
>>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>>> make the new repositories and coordinate them with csound.git
>>>>>
>>>>> We should set a deadline for the move of private code out of the
>>>>> repo so that we can do some tidying up of scripts and files. I
>>>>> would tentatively say one week from today.
>>>>>
>>>>> best regards
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Saludos,
>>>> Felipe Sateler
>>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Michael Gogins-2
In reply to this post by Victor Lazzarini-2
As I said I think CsoundVST should stay in the Csound repo. It's been in there for a long time, works fine, doesn't need much maintenance, and is used. 

Regards, 
Mike

On Jan 19, 2018 01:29, "Victor Lazzarini" <[hidden email]> wrote:
Don’t forget CsoundVST also.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 18 Jan 2018, at 23:44, Michael Gogins <[hidden email]> wrote:
>
> I will do this for CsoundAC, the Csound for Android app, and nwjs,
> starting tomorrow (not sure how long it will take).
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
>> On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
>> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
>>
>> * For csound~ (Max), I created a new repository called csound_tilde at
>> https://github.com/csound/csound_tilde. I did this by locally
>> splitting off the folder from frontends using git following these
>> steps:
>>
>> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
>>
>> Following these steps retains the history for all of the files within
>> the folder. The new repository is now at:
>>
>> https://github.com/csound/csound_tilde
>>
>> As it is now, csound~ is just split off.  The CMake file needs
>> revisions to look for Csound installation and it probably should be
>> updated to use Max7 SDK (amongst other things, this hasn't been
>> compiled in quite some time so who knows).  Or whomever might want to
>> take it over can do with it as they wish (i.e., create visual studio
>> and xcode projects, much as it used to be before being redone with
>> CMake).  We could look at OSSIA for some ideas about updating to pull
>> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
>>
>> Since csound~ has not been maintained for a while now, I have gone
>> ahead and removed it from csound/frontends.
>>
>>
>>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
>>> Yes, it will probably simplify things. It should also make it easier
>>> to update, since a full build will take a lot less time.
>>>
>>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
>>> <[hidden email]> wrote:
>>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>>>> would simplify things for you in terms of packaging.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>>>
>>>>> Just a quick note as a downstream packager. In general I agree with
>>>>> splitting things out, but do note that this also impacts us.
>>>>>
>>>>> My primary concern is the extra work it implies for me  to have
>>>>> several upstreams to track as opposed to a single one. Reality is that
>>>>> I'm already too overloaded so I can't commit to taking up extra
>>>>> packages. This will probably mean that only the core csound package
>>>>> will continue to be delivered via the debian repositories, at least
>>>>> initially. It is possible I could also package up some of the simpler
>>>>> and less dynamic ones (that is, infrequently updated), but I won't
>>>>> make any promises.
>>>>>
>>>>> I do offer to assist if someone wants to take up the work of
>>>>> maintaining the extra packages, and to do the sponsoring required to
>>>>> upload to debian. I encourage debian/ubuntu users to try to help
>>>>> maintaining the csound packages, as I find myself increasignly unable
>>>>> to keep up (I still haven't uploaded 6.10...).
>>>>>
>>>>> Saludos
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>>>> <[hidden email]> wrote:
>>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>>>> we should do next.
>>>>>>
>>>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>>>
>>>>>> For the individual projects, these should go to private repos (in the same
>>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>>>> even if the author collaborates on the core project.
>>>>>>
>>>>>> For collaborative/community based projects, we will place these in
>>>>>> the Csound project.
>>>>>>
>>>>>> From my original list, I have:
>>>>>>
>>>>>> Csound6~ (community: several contributors, users)
>>>>>> Csound~  (community: several contributors, users)
>>>>>> csladspa  (community: two authors, users)
>>>>>> CsoundAC (private: single author)
>>>>>> CsoundVST (private: single author)
>>>>>> CS6Editor (private: single author)
>>>>>> winsound (community:  several contributors, users)
>>>>>> nwjs (private: single author)
>>>>>> icsound (private: single author)
>>>>>> beats (community:  several contributors, users)
>>>>>> Csound Android App (private: single author)
>>>>>>
>>>>>> So I propose that the respective authors for the private projects above
>>>>>> move these to their private repositories.
>>>>>>
>>>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>>>> make the new repositories and coordinate them with csound.git
>>>>>>
>>>>>> We should set a deadline for the move of private code out of the
>>>>>> repo so that we can do some tidying up of scripts and files. I
>>>>>> would tentatively say one week from today.
>>>>>>
>>>>>> best regards
>>>>>> ========================
>>>>>> Prof. Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Michael Gogins-2
In reply to this post by Michael Gogins-2
I note there is now csound/csound~ but kunstmusik/cs6editor. What's the significance of this?

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Thu, Jan 18, 2018 at 6:44 PM, Michael Gogins <[hidden email]> wrote:

> I will do this for CsoundAC, the Csound for Android app, and nwjs,
> starting tomorrow (not sure how long it will take).
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
>> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
>>
>> * For csound~ (Max), I created a new repository called csound_tilde at
>> https://github.com/csound/csound_tilde. I did this by locally
>> splitting off the folder from frontends using git following these
>> steps:
>>
>> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
>>
>> Following these steps retains the history for all of the files within
>> the folder. The new repository is now at:
>>
>> https://github.com/csound/csound_tilde
>>
>> As it is now, csound~ is just split off. The CMake file needs
>> revisions to look for Csound installation and it probably should be
>> updated to use Max7 SDK (amongst other things, this hasn't been
>> compiled in quite some time so who knows). Or whomever might want to
>> take it over can do with it as they wish (i.e., create visual studio
>> and xcode projects, much as it used to be before being redone with
>> CMake). We could look at OSSIA for some ideas about updating to pull
>> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
>>
>> Since csound~ has not been maintained for a while now, I have gone
>> ahead and removed it from csound/frontends.
>>
>>
>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
>>> Yes, it will probably simplify things. It should also make it easier
>>> to update, since a full build will take a lot less time.
>>>
>>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
>>> <[hidden email]> wrote:
>>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
>>>> would simplify things for you in terms of packaging.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
>>>>>
>>>>> Just a quick note as a downstream packager. In general I agree with
>>>>> splitting things out, but do note that this also impacts us.
>>>>>
>>>>> My primary concern is the extra work it implies for me to have
>>>>> several upstreams to track as opposed to a single one. Reality is that
>>>>> I'm already too overloaded so I can't commit to taking up extra
>>>>> packages. This will probably mean that only the core csound package
>>>>> will continue to be delivered via the debian repositories, at least
>>>>> initially. It is possible I could also package up some of the simpler
>>>>> and less dynamic ones (that is, infrequently updated), but I won't
>>>>> make any promises.
>>>>>
>>>>> I do offer to assist if someone wants to take up the work of
>>>>> maintaining the extra packages, and to do the sponsoring required to
>>>>> upload to debian. I encourage debian/ubuntu users to try to help
>>>>> maintaining the csound packages, as I find myself increasignly unable
>>>>> to keep up (I still haven't uploaded 6.10...).
>>>>>
>>>>> Saludos
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
>>>>> <[hidden email]> wrote:
>>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
>>>>>> we should do next.
>>>>>>
>>>>>> There are two kinds of projects in the csound.git repo that need to be moved
>>>>>> out. Projects that have been collaboratively worked on, and individual projects.
>>>>>> We can tell this by git history or even git blame, as well as author’s lists.
>>>>>>
>>>>>> For the individual projects, these should go to private repos (in the same
>>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
>>>>>> even if the author collaborates on the core project.
>>>>>>
>>>>>> For collaborative/community based projects, we will place these in
>>>>>> the Csound project.
>>>>>>
>>>>>> From my original list, I have:
>>>>>>
>>>>>> Csound6~ (community: several contributors, users)
>>>>>> Csound~ (community: several contributors, users)
>>>>>> csladspa (community: two authors, users)
>>>>>> CsoundAC (private: single author)
>>>>>> CsoundVST (private: single author)
>>>>>> CS6Editor (private: single author)
>>>>>> winsound (community: several contributors, users)
>>>>>> nwjs (private: single author)
>>>>>> icsound (private: single author)
>>>>>> beats (community: several contributors, users)
>>>>>> Csound Android App (private: single author)
>>>>>>
>>>>>> So I propose that the respective authors for the private projects above
>>>>>> move these to their private repositories.
>>>>>>
>>>>>> I am happy to work with Steven, Rory, and other colleagues to
>>>>>> make the new repositories and coordinate them with csound.git
>>>>>>
>>>>>> We should set a deadline for the move of private code out of the
>>>>>> repo so that we can do some tidying up of scripts and files. I
>>>>>> would tentatively say one week from today.
>>>>>>
>>>>>> best regards
>>>>>> ========================
>>>>>> Prof. Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
In reply to this post by Michael Gogins-2
I think everyone else has agreed that CsoundVST has to be moved, so please move it.

========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 19 Jan 2018, at 11:45, Michael Gogins <[hidden email]> wrote:
>
> As I said I think CsoundVST should stay in the Csound repo. It's been in there for a long time, works fine, doesn't need much maintenance, and is used.
>
> Regards,
> Mike
>
> On Jan 19, 2018 01:29, "Victor Lazzarini" <[hidden email]> wrote:
> Don’t forget CsoundVST also.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> > On 18 Jan 2018, at 23:44, Michael Gogins <[hidden email]> wrote:
> >
> > I will do this for CsoundAC, the Csound for Android app, and nwjs,
> > starting tomorrow (not sure how long it will take).
> >
> > Regards,
> > Mike
> >
> > -----------------------------------------------------
> > Michael Gogins
> > Irreducible Productions
> > http://michaelgogins.tumblr.com
> > Michael dot Gogins at gmail dot com
> >
> >
> >> On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
> >> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
> >>
> >> * For csound~ (Max), I created a new repository called csound_tilde at
> >> https://github.com/csound/csound_tilde. I did this by locally
> >> splitting off the folder from frontends using git following these
> >> steps:
> >>
> >> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
> >>
> >> Following these steps retains the history for all of the files within
> >> the folder. The new repository is now at:
> >>
> >> https://github.com/csound/csound_tilde
> >>
> >> As it is now, csound~ is just split off.  The CMake file needs
> >> revisions to look for Csound installation and it probably should be
> >> updated to use Max7 SDK (amongst other things, this hasn't been
> >> compiled in quite some time so who knows).  Or whomever might want to
> >> take it over can do with it as they wish (i.e., create visual studio
> >> and xcode projects, much as it used to be before being redone with
> >> CMake).  We could look at OSSIA for some ideas about updating to pull
> >> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
> >>
> >> Since csound~ has not been maintained for a while now, I have gone
> >> ahead and removed it from csound/frontends.
> >>
> >>
> >>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
> >>> Yes, it will probably simplify things. It should also make it easier
> >>> to update, since a full build will take a lot less time.
> >>>
> >>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
> >>> <[hidden email]> wrote:
> >>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
> >>>> would simplify things for you in terms of packaging.
> >>>> ========================
> >>>> Prof. Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
> >>>>>
> >>>>> Just a quick note as a downstream packager. In general I agree with
> >>>>> splitting things out, but do note that this also impacts us.
> >>>>>
> >>>>> My primary concern is the extra work it implies for me  to have
> >>>>> several upstreams to track as opposed to a single one. Reality is that
> >>>>> I'm already too overloaded so I can't commit to taking up extra
> >>>>> packages. This will probably mean that only the core csound package
> >>>>> will continue to be delivered via the debian repositories, at least
> >>>>> initially. It is possible I could also package up some of the simpler
> >>>>> and less dynamic ones (that is, infrequently updated), but I won't
> >>>>> make any promises.
> >>>>>
> >>>>> I do offer to assist if someone wants to take up the work of
> >>>>> maintaining the extra packages, and to do the sponsoring required to
> >>>>> upload to debian. I encourage debian/ubuntu users to try to help
> >>>>> maintaining the csound packages, as I find myself increasignly unable
> >>>>> to keep up (I still haven't uploaded 6.10...).
> >>>>>
> >>>>> Saludos
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
> >>>>> <[hidden email]> wrote:
> >>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
> >>>>>> we should do next.
> >>>>>>
> >>>>>> There are two kinds of projects in the csound.git repo that need to be moved
> >>>>>> out. Projects that have been collaboratively worked on, and individual projects.
> >>>>>> We can tell this by git history or even git blame, as well as author’s lists.
> >>>>>>
> >>>>>> For the individual projects, these should go to private repos (in the same
> >>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
> >>>>>> even if the author collaborates on the core project.
> >>>>>>
> >>>>>> For collaborative/community based projects, we will place these in
> >>>>>> the Csound project.
> >>>>>>
> >>>>>> From my original list, I have:
> >>>>>>
> >>>>>> Csound6~ (community: several contributors, users)
> >>>>>> Csound~  (community: several contributors, users)
> >>>>>> csladspa  (community: two authors, users)
> >>>>>> CsoundAC (private: single author)
> >>>>>> CsoundVST (private: single author)
> >>>>>> CS6Editor (private: single author)
> >>>>>> winsound (community:  several contributors, users)
> >>>>>> nwjs (private: single author)
> >>>>>> icsound (private: single author)
> >>>>>> beats (community:  several contributors, users)
> >>>>>> Csound Android App (private: single author)
> >>>>>>
> >>>>>> So I propose that the respective authors for the private projects above
> >>>>>> move these to their private repositories.
> >>>>>>
> >>>>>> I am happy to work with Steven, Rory, and other colleagues to
> >>>>>> make the new repositories and coordinate them with csound.git
> >>>>>>
> >>>>>> We should set a deadline for the move of private code out of the
> >>>>>> repo so that we can do some tidying up of scripts and files. I
> >>>>>> would tentatively say one week from today.
> >>>>>>
> >>>>>> best regards
> >>>>>> ========================
> >>>>>> Prof. Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Saludos,
> >>>>> Felipe Sateler
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> Saludos,
> >>> Felipe Sateler

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Victor Lazzarini-2
In reply to this post by Michael Gogins-2
There is a csound/csound_tilde in the project. Steven has moved his private project
away. I have also moved csladspa and csoundapi_tilde out this morning.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 19 Jan 2018, at 11:47, Michael Gogins <[hidden email]> wrote:
>
> I note there is now csound/csound~ but kunstmusik/cs6editor. What's the significance of this?
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Thu, Jan 18, 2018 at 6:44 PM, Michael Gogins <[hidden email]> wrote:
> > I will do this for CsoundAC, the Csound for Android app, and nwjs,
> > starting tomorrow (not sure how long it will take).
> >
> > Regards,
> > Mike
> >
> > -----------------------------------------------------
> > Michael Gogins
> > Irreducible Productions
> > http://michaelgogins.tumblr.com
> > Michael dot Gogins at gmail dot com
> >
> >
> > On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
> >> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
> >>
> >> * For csound~ (Max), I created a new repository called csound_tilde at
> >> https://github.com/csound/csound_tilde. I did this by locally
> >> splitting off the folder from frontends using git following these
> >> steps:
> >>
> >> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
> >>
> >> Following these steps retains the history for all of the files within
> >> the folder. The new repository is now at:
> >>
> >> https://github.com/csound/csound_tilde
> >>
> >> As it is now, csound~ is just split off. The CMake file needs
> >> revisions to look for Csound installation and it probably should be
> >> updated to use Max7 SDK (amongst other things, this hasn't been
> >> compiled in quite some time so who knows). Or whomever might want to
> >> take it over can do with it as they wish (i.e., create visual studio
> >> and xcode projects, much as it used to be before being redone with
> >> CMake). We could look at OSSIA for some ideas about updating to pull
> >> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
> >>
> >> Since csound~ has not been maintained for a while now, I have gone
> >> ahead and removed it from csound/frontends.
> >>
> >>
> >> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
> >>> Yes, it will probably simplify things. It should also make it easier
> >>> to update, since a full build will take a lot less time.
> >>>
> >>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
> >>> <[hidden email]> wrote:
> >>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
> >>>> would simplify things for you in terms of packaging.
> >>>> ========================
> >>>> Prof. Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
> >>>>>
> >>>>> Just a quick note as a downstream packager. In general I agree with
> >>>>> splitting things out, but do note that this also impacts us.
> >>>>>
> >>>>> My primary concern is the extra work it implies for me to have
> >>>>> several upstreams to track as opposed to a single one. Reality is that
> >>>>> I'm already too overloaded so I can't commit to taking up extra
> >>>>> packages. This will probably mean that only the core csound package
> >>>>> will continue to be delivered via the debian repositories, at least
> >>>>> initially. It is possible I could also package up some of the simpler
> >>>>> and less dynamic ones (that is, infrequently updated), but I won't
> >>>>> make any promises.
> >>>>>
> >>>>> I do offer to assist if someone wants to take up the work of
> >>>>> maintaining the extra packages, and to do the sponsoring required to
> >>>>> upload to debian. I encourage debian/ubuntu users to try to help
> >>>>> maintaining the csound packages, as I find myself increasignly unable
> >>>>> to keep up (I still haven't uploaded 6.10...).
> >>>>>
> >>>>> Saludos
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
> >>>>> <[hidden email]> wrote:
> >>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
> >>>>>> we should do next.
> >>>>>>
> >>>>>> There are two kinds of projects in the csound.git repo that need to be moved
> >>>>>> out. Projects that have been collaboratively worked on, and individual projects.
> >>>>>> We can tell this by git history or even git blame, as well as author’s lists.
> >>>>>>
> >>>>>> For the individual projects, these should go to private repos (in the same
> >>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
> >>>>>> even if the author collaborates on the core project.
> >>>>>>
> >>>>>> For collaborative/community based projects, we will place these in
> >>>>>> the Csound project.
> >>>>>>
> >>>>>> From my original list, I have:
> >>>>>>
> >>>>>> Csound6~ (community: several contributors, users)
> >>>>>> Csound~ (community: several contributors, users)
> >>>>>> csladspa (community: two authors, users)
> >>>>>> CsoundAC (private: single author)
> >>>>>> CsoundVST (private: single author)
> >>>>>> CS6Editor (private: single author)
> >>>>>> winsound (community: several contributors, users)
> >>>>>> nwjs (private: single author)
> >>>>>> icsound (private: single author)
> >>>>>> beats (community: several contributors, users)
> >>>>>> Csound Android App (private: single author)
> >>>>>>
> >>>>>> So I propose that the respective authors for the private projects above
> >>>>>> move these to their private repositories.
> >>>>>>
> >>>>>> I am happy to work with Steven, Rory, and other colleagues to
> >>>>>> make the new repositories and coordinate them with csound.git
> >>>>>>
> >>>>>> We should set a deadline for the move of private code out of the
> >>>>>> repo so that we can do some tidying up of scripts and files. I
> >>>>>> would tentatively say one week from today.
> >>>>>>
> >>>>>> best regards
> >>>>>> ========================
> >>>>>> Prof. Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Saludos,
> >>>>> Felipe Sateler
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> Saludos,
> >>> Felipe Sateler

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd-dev] github reorganisation -- next steps.

Michael Gogins-2
In reply to this post by Victor Lazzarini-2
I will do it.

Regards,
Mike

On Jan 19, 2018 06:50, "Victor Lazzarini" <[hidden email]> wrote:
I think everyone else has agreed that CsoundVST has to be moved, so please move it.

========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 19 Jan 2018, at 11:45, Michael Gogins <[hidden email]> wrote:
>
> As I said I think CsoundVST should stay in the Csound repo. It's been in there for a long time, works fine, doesn't need much maintenance, and is used.
>
> Regards,
> Mike
>
> On Jan 19, 2018 01:29, "Victor Lazzarini" <[hidden email]> wrote:
> Don’t forget CsoundVST also.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> > On 18 Jan 2018, at 23:44, Michael Gogins <[hidden email]> wrote:
> >
> > I will do this for CsoundAC, the Csound for Android app, and nwjs,
> > starting tomorrow (not sure how long it will take).
> >
> > Regards,
> > Mike
> >
> > -----------------------------------------------------
> > Michael Gogins
> > Irreducible Productions
> > http://michaelgogins.tumblr.com
> > Michael dot Gogins at gmail dot com
> >
> >
> >> On Thu, Jan 18, 2018 at 5:50 PM, Steven Yi <[hidden email]> wrote:
> >> * I've moved CS6Editor to https://github.com/kunstmusik/CS6Editor
> >>
> >> * For csound~ (Max), I created a new repository called csound_tilde at
> >> https://github.com/csound/csound_tilde. I did this by locally
> >> splitting off the folder from frontends using git following these
> >> steps:
> >>
> >> https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/
> >>
> >> Following these steps retains the history for all of the files within
> >> the folder. The new repository is now at:
> >>
> >> https://github.com/csound/csound_tilde
> >>
> >> As it is now, csound~ is just split off.  The CMake file needs
> >> revisions to look for Csound installation and it probably should be
> >> updated to use Max7 SDK (amongst other things, this hasn't been
> >> compiled in quite some time so who knows).  Or whomever might want to
> >> take it over can do with it as they wish (i.e., create visual studio
> >> and xcode projects, much as it used to be before being redone with
> >> CMake).  We could look at OSSIA for some ideas about updating to pull
> >> down Max 7 SDK: https://github.com/OSSIA/libossia/wiki/Building
> >>
> >> Since csound~ has not been maintained for a while now, I have gone
> >> ahead and removed it from csound/frontends.
> >>
> >>
> >>> On Thu, Jan 18, 2018 at 5:18 PM, Felipe Sateler <[hidden email]> wrote:
> >>> Yes, it will probably simplify things. It should also make it easier
> >>> to update, since a full build will take a lot less time.
> >>>
> >>> On Thu, Jan 18, 2018 at 5:11 PM, Victor Lazzarini
> >>> <[hidden email]> wrote:
> >>>> That sounds OK to me. The Csound core package is what matters most. Maybe this
> >>>> would simplify things for you in terms of packaging.
> >>>> ========================
> >>>> Prof. Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 18 Jan 2018, at 20:05, Felipe Sateler <[hidden email]> wrote:
> >>>>>
> >>>>> Just a quick note as a downstream packager. In general I agree with
> >>>>> splitting things out, but do note that this also impacts us.
> >>>>>
> >>>>> My primary concern is the extra work it implies for me  to have
> >>>>> several upstreams to track as opposed to a single one. Reality is that
> >>>>> I'm already too overloaded so I can't commit to taking up extra
> >>>>> packages. This will probably mean that only the core csound package
> >>>>> will continue to be delivered via the debian repositories, at least
> >>>>> initially. It is possible I could also package up some of the simpler
> >>>>> and less dynamic ones (that is, infrequently updated), but I won't
> >>>>> make any promises.
> >>>>>
> >>>>> I do offer to assist if someone wants to take up the work of
> >>>>> maintaining the extra packages, and to do the sponsoring required to
> >>>>> upload to debian. I encourage debian/ubuntu users to try to help
> >>>>> maintaining the csound packages, as I find myself increasignly unable
> >>>>> to keep up (I still haven't uploaded 6.10...).
> >>>>>
> >>>>> Saludos
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Jan 18, 2018 at 3:21 PM, Victor Lazzarini
> >>>>> <[hidden email]> wrote:
> >>>>>> Thanks everyone for voting, looks like we have a consensus. Here’s what
> >>>>>> we should do next.
> >>>>>>
> >>>>>> There are two kinds of projects in the csound.git repo that need to be moved
> >>>>>> out. Projects that have been collaboratively worked on, and individual projects.
> >>>>>> We can tell this by git history or even git blame, as well as author’s lists.
> >>>>>>
> >>>>>> For the individual projects, these should go to private repos (in the same
> >>>>>> way that Blue, Cabbage and CsoundQt do) and become third-party projects,
> >>>>>> even if the author collaborates on the core project.
> >>>>>>
> >>>>>> For collaborative/community based projects, we will place these in
> >>>>>> the Csound project.
> >>>>>>
> >>>>>> From my original list, I have:
> >>>>>>
> >>>>>> Csound6~ (community: several contributors, users)
> >>>>>> Csound~  (community: several contributors, users)
> >>>>>> csladspa  (community: two authors, users)
> >>>>>> CsoundAC (private: single author)
> >>>>>> CsoundVST (private: single author)
> >>>>>> CS6Editor (private: single author)
> >>>>>> winsound (community:  several contributors, users)
> >>>>>> nwjs (private: single author)
> >>>>>> icsound (private: single author)
> >>>>>> beats (community:  several contributors, users)
> >>>>>> Csound Android App (private: single author)
> >>>>>>
> >>>>>> So I propose that the respective authors for the private projects above
> >>>>>> move these to their private repositories.
> >>>>>>
> >>>>>> I am happy to work with Steven, Rory, and other colleagues to
> >>>>>> make the new repositories and coordinate them with csound.git
> >>>>>>
> >>>>>> We should set a deadline for the move of private code out of the
> >>>>>> repo so that we can do some tidying up of scripts and files. I
> >>>>>> would tentatively say one week from today.
> >>>>>>
> >>>>>> best regards
> >>>>>> ========================
> >>>>>> Prof. Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies, and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Saludos,
> >>>>> Felipe Sateler
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> Saludos,
> >>> Felipe Sateler


12