Hi All,

I have started the process of moving source code, issues, and wiki
from Sourceforge to Github.  I will reply here once the process is
complete and will write instructions on how you can update your
repositories for the new location.

Thanks,
steven

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Hi All,

I have completed the move to Github. The Csound project page on Github
is located at:

https://github.com/csound/csound

This is part of the larger organization account at github:

https://github.com/csound

I have moved the git repo for csound6 (now just called 'csound'),
migrated the issues, and imported wiki pages.  The following are notes
for users and developers:

== FOR USERS ==

* Csound releases will still be distributed at SourceForge. Github
also has its own file release system. Currently it auto-generates a
source release for all tags that are committed to the git repo. We
have not discussed whether to move the file releases to Github; for
now, please continue to download and expect new file releases at
SourceForge until otherwise noted.

* For issues and requests, please report new items at:
https://github.com/csound/csound/issues.  Also to note, the migration
script--due to security--only allowed me to migrate tickets by adding
them as being from me. The script was modified per-requests on the dev
list to add information, such as the original Sourceforge user who
reported the issue.  If you entered an issue on Sourceforge, you may
want to find the corresponding ticket on Github and subscribe to the
ticket for notifications.

* The wiki is set to open to allow contributions from non-developers.
Let's see how that goes; if it starts to get spammed out we'll tighten
the permissions.


== FOR DEVELOPERS ==

* If you have an existing git repo for Csound cloned to your system,
you will want to update your remote (where you push/pull code to/from)
to point to Github instead of Sourceforge.  There is some information
here:

http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git

The easiest way is to use:

git remote set-url origin [url for github repo]

For my account, I have something like:

git remote set-url origin git@github.com:csound/csound.git

That is for SSH access.  If you are using https (the read-only repo),
you can use something like:

git remote set-url origin https://github.com/csound/csound.git

The repository information is found on the right hand side of the main
project page (https://github.com/csound/csound).

* If you are a main developer or plan to regularly contribute and do
not have access to commit to Csound, please contact John, Victor, or
myself with your Github ID to add you to the repo as a collaborator.
We will setup a github team for Csound developers.

* If you would like to contribute a patch or set of changes, but do
not imagine you will be doing so frequently, please use Github's
fork/pull-request system.  This is a great way to make changes and
contribute back to Csound, and allows changes to be reviewed and
discussed before merging into the main repo.

* I pushed the master, develop, feature/vs2013, and feature/config-h
branches to Github. These were the ones that looked active to me.  If
you want to migrate one of the other branches from Sourceforge, please
feel free to do so or let me know which one you'd like migrated.


== FUTURE WORK ==

* We currently have a mock-up project page for Csound at:

http://csound.github.io

We need to sort out what technology to use to update the page (to
discuss on the dev list).

* We will need to add a README.md to the Csound repo.

* For future major versions of Csound (i.e. 7.0, 8.0, etc.) we should
not create a separate repository as we did with cs5 and cs6.  Instead,
we can create maintenance branches for CS6 when we move to CS7, and so
on. That will keep the entire history of all versions in one
repository.

* We will need to close out the repo, issue trackers, and wiki on
Sourceforge. We should also write notes on the SF project page to
point users to the Github page.


If you have further questions or issues to report, please reply here
(or use the new Github issue tracker!).

Thanks!
steven



On Sun, Mar 23, 2014 at 8:48 PM, Steven Yi  wrote:
> Hi All,
>
> I have started the process of moving source code, issues, and wiki
> from Sourceforge to Github.  I will reply here once the process is
> complete and will write instructions on how you can update your
> repositories for the new location.
>
> Thanks,
> steven

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Hi Francois,

Thanks for mentioning them; I will migrate the repositories later this
morning and will reply here once complete.

Thanks!
steven

On Mon, Mar 24, 2014 at 3:07 AM, Francois PINOT  wrote:
> Hello Steven,
>
> what about the manual (manual6 and manual6-fr) ?
>
> Regards
>
> Francois
>
>
> 2014-03-24 1:48 GMT+01:00 Steven Yi :
>>
>> Hi All,
>>
>> I have started the process of moving source code, issues, and wiki
>> from Sourceforge to Github.  I will reply here once the process is
>> complete and will write instructions on how you can update your
>> repositories for the new location.
>>
>> Thanks,
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Francois,

I have setup two more repositories for the manual and manual-fr:

https://github.com/csound/manual
https://github.com/csound/manual-fr

I created these from the manual6 and manual6-fr Sourceforge repositories.

I have also created a Documentation team and added you to that team.
I have added the Documentation and Developer teams as collaborators
two the manual repositories so that we can all have push access.

If you have the manual repository already cloned from Sourceforge, you
can do the following to switch remote URL's for origin (done within
the manual and manual-fr repo's on your local system):

git remote set-url origin git@github.com:csound/manual.git
git remote set-url origin git@github.com:csound/manual-fr.git

One thing I noticed is that the readme.txt could be modified to use
Markdown.  The readme gets automatically shown on the site.  Also to
note, and I think it's a very nice feature, users with push access can
edit code within the browser while browsing files.

Let me know if there are any issues with permissions or anything.

Thanks!
steven

On Mon, Mar 24, 2014 at 7:38 AM, Steven Yi  wrote:
> Hi Francois,
>
> Thanks for mentioning them; I will migrate the repositories later this
> morning and will reply here once complete.
>
> Thanks!
> steven
>
> On Mon, Mar 24, 2014 at 3:07 AM, Francois PINOT  wrote:
>> Hello Steven,
>>
>> what about the manual (manual6 and manual6-fr) ?
>>
>> Regards
>>
>> Francois
>>
>>
>> 2014-03-24 1:48 GMT+01:00 Steven Yi :
>>>
>>> Hi All,
>>>
>>> I have started the process of moving source code, issues, and wiki
>>> from Sourceforge to Github.  I will reply here once the process is
>>> complete and will write instructions on how you can update your
>>> repositories for the new location.
>>>
>>> Thanks,
>>> steven
>>>
>>>
>>> Send bugs reports to the Sourceforge bug trackers
>>> csound6:
>>>             https://sourceforge.net/p/csound/tickets/
>>> csound5:
>>>             https://sourceforge.net/p/csound/bugs/
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Andres,

Thanks for pushing that branch; sorry I missed it!

steven

On Mon, Mar 24, 2014 at 10:23 AM, Andres Cabrera  wrote:
> Hi Steven,
>
> Thanks for this. I hope all this work will translate in making it easier for
> people to contribute.
>
> I've added the csdebugger branch. I'll get back to it soon, hopefully.
>
> Cheers,
> Andrés
>
>
> On Sun, Mar 23, 2014 at 7:12 PM, Steven Yi  wrote:
>>
>> Hi All,
>>
>> I have completed the move to Github. The Csound project page on Github
>> is located at:
>>
>> https://github.com/csound/csound
>>
>> This is part of the larger organization account at github:
>>
>> https://github.com/csound
>>
>> I have moved the git repo for csound6 (now just called 'csound'),
>> migrated the issues, and imported wiki pages.  The following are notes
>> for users and developers:
>>
>> == FOR USERS ==
>>
>> * Csound releases will still be distributed at SourceForge. Github
>> also has its own file release system. Currently it auto-generates a
>> source release for all tags that are committed to the git repo. We
>> have not discussed whether to move the file releases to Github; for
>> now, please continue to download and expect new file releases at
>> SourceForge until otherwise noted.
>>
>> * For issues and requests, please report new items at:
>> https://github.com/csound/csound/issues.  Also to note, the migration
>> script--due to security--only allowed me to migrate tickets by adding
>> them as being from me. The script was modified per-requests on the dev
>> list to add information, such as the original Sourceforge user who
>> reported the issue.  If you entered an issue on Sourceforge, you may
>> want to find the corresponding ticket on Github and subscribe to the
>> ticket for notifications.
>>
>> * The wiki is set to open to allow contributions from non-developers.
>> Let's see how that goes; if it starts to get spammed out we'll tighten
>> the permissions.
>>
>>
>> == FOR DEVELOPERS ==
>>
>> * If you have an existing git repo for Csound cloned to your system,
>> you will want to update your remote (where you push/pull code to/from)
>> to point to Github instead of Sourceforge.  There is some information
>> here:
>>
>>
>> http://stackoverflow.com/questions/2432764/how-to-change-a-remote-repository-uri-using-git
>>
>> The easiest way is to use:
>>
>> git remote set-url origin [url for github repo]
>>
>> For my account, I have something like:
>>
>> git remote set-url origin git@github.com:csound/csound.git
>>
>> That is for SSH access.  If you are using https (the read-only repo),
>> you can use something like:
>>
>> git remote set-url origin https://github.com/csound/csound.git
>>
>> The repository information is found on the right hand side of the main
>> project page (https://github.com/csound/csound).
>>
>> * If you are a main developer or plan to regularly contribute and do
>> not have access to commit to Csound, please contact John, Victor, or
>> myself with your Github ID to add you to the repo as a collaborator.
>> We will setup a github team for Csound developers.
>>
>> * If you would like to contribute a patch or set of changes, but do
>> not imagine you will be doing so frequently, please use Github's
>> fork/pull-request system.  This is a great way to make changes and
>> contribute back to Csound, and allows changes to be reviewed and
>> discussed before merging into the main repo.
>>
>> * I pushed the master, develop, feature/vs2013, and feature/config-h
>> branches to Github. These were the ones that looked active to me.  If
>> you want to migrate one of the other branches from Sourceforge, please
>> feel free to do so or let me know which one you'd like migrated.
>>
>>
>> == FUTURE WORK ==
>>
>> * We currently have a mock-up project page for Csound at:
>>
>> http://csound.github.io
>>
>> We need to sort out what technology to use to update the page (to
>> discuss on the dev list).
>>
>> * We will need to add a README.md to the Csound repo.
>>
>> * For future major versions of Csound (i.e. 7.0, 8.0, etc.) we should
>> not create a separate repository as we did with cs5 and cs6.  Instead,
>> we can create maintenance branches for CS6 when we move to CS7, and so
>> on. That will keep the entire history of all versions in one
>> repository.
>>
>> * We will need to close out the repo, issue trackers, and wiki on
>> Sourceforge. We should also write notes on the SF project page to
>> point users to the Github page.
>>
>>
>> If you have further questions or issues to report, please reply here
>> (or use the new Github issue tracker!).
>>
>> Thanks!
>> steven
>>
>>
>>
>> On Sun, Mar 23, 2014 at 8:48 PM, Steven Yi  wrote:
>> > Hi All,
>> >
>> > I have started the process of moving source code, issues, and wiki
>> > from Sourceforge to Github.  I will reply here once the process is
>> > complete and will write instructions on how you can update your
>> > repositories for the new location.
>> >
>> > Thanks,
>> > steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

i wanted to reply to an open issue in GitHub. When attaching a csd i get
this:

Unfortunately, we don't support that file type. Try again with a PNG, GIF,
or JPG. 

Can you influence the settings so that is does accept csd or texts?



--
View this message in context: http://csound.1045644.n5.nabble.com/Moving-to-Github-tp5733478p5733574.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I don't think Github allows anything beyond those.  You can post the
CSD in a Gist (http://gist.github.com) then paste a link to the gist
from the issue.

On Thu, Mar 27, 2014 at 10:06 AM, menno  wrote:
> i wanted to reply to an open issue in GitHub. When attaching a csd i get
> this:
>
> Unfortunately, we don't support that file type. Try again with a PNG, GIF,
> or JPG.
>
> Can you influence the settings so that is does accept csd or texts?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Moving-to-Github-tp5733478p5733574.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Thu, 27 Mar 2014, menno wrote:
> i wanted to reply to an open issue in GitHub. When attaching a csd i get
> this:
>
> Unfortunately, we don't support that file type. Try again with a PNG, GIF,
> or JPG.
>
> Can you influence the settings so that is does accept csd or texts?

Unlikely.  We faced a similar issue in another project I'm involved with
on Github.  The "attach" feature is really only intended for images.

Probably the best thing to do with a .csd file is include it in the body
of the issue report, marked up with ``` (three backticks) as described
under "Fenced code blocks" on this help page:
   https://help.github.com/articles/github-flavored-markdown

That way it's easy to read and to cut'n'paste from.

There is also a service called "gist" for posting small chunks of text
that will be downloadable and can be linked to, and people sometimes use
that for this kind of thing, but I've never used it myself.

What we did in my other project was create a separate repository for
issue-related files; that seemed worthwhile because many of the relevant
files in that project are multi-megabyte binaries.  But I'm not sure it
would be appropriate for Csound.