Hi All,

I was looking through emails and saw that issue #42 for
csound.github.io is an open issue:

https://github.com/csound/csound.github.io/issues/42

Which is talking about this page:

http://csound.github.io/contribute.html

Could we get some volunteers to write up text for these sections?  I
think even a small blurb of text would be enough to get things started
and it can be refined over time.  I think once there is some text
there, it would be extremely valuable for reviews by others to see if
anything is missing so that we can make sure we are not missing
anything.

Thanks!
steven

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Steven Yi, Jun 29 2016:

> Hi All,
>
> I was looking through emails and saw that issue #42 for
> csound.github.io is an open issue:
>
> https://github.com/csound/csound.github.io/issues/42
>
> Which is talking about this page:
>
> http://csound.github.io/contribute.html
What sort of thing should go into "community"? What about "User-Defined Opcodes"? A list from the "official archive"? -- As such it shouldn't be too difficult, since most of the info can be extracted from the Csound Reference Manual and the UDO archive.

Do you use a CMS for the Csound material pages? If so, it would be very nice if you could put in links to "skip the menu". I could supply a sort of template.
...

Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter:  http://twitter.com/ffanci_silvain
* GitHub:   https://github.com/fsilvain

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Ffanci,

The csound.github.io website is generated using Jekyll and is itself
an open source project:

https://github.com/csound/csound.github.io

There are instructions in the README.md on how to build and test the
project locally.  Some users have contributed text just here on the
mailing list, others have used issues to write text that other
maintainers have integrated in, while others have forked the project
and submitted pull requests.

I think the contribute page was intended to give guidance on how to
contribute back to Csound, whether it's core code, plugins, UDOs,
documentation, and so on.  We have READMEs available, but the page
would have more visibility and be a sort of general guide.  Links to
READMEs might be appropriate where the contribute page describes the
basics the README describes the more technical details.

The link to the contribute page is located on the front page of the
site, near the bottom left in green.

steven

On Wed, Jun 29, 2016 at 3:37 PM, Ffanci Silvain  wrote:
> Steven Yi, Jun 29 2016:
>
>> Hi All,
>>
>> I was looking through emails and saw that issue #42 for
>> csound.github.io is an open issue:
>>
>> https://github.com/csound/csound.github.io/issues/42
>>
>> Which is talking about this page:
>>
>> http://csound.github.io/contribute.html
>
> What sort of thing should go into "community"? What about "User-Defined
> Opcodes"? A list from the "official archive"? -- As such it shouldn't be too
> difficult, since most of the info can be extracted from the Csound Reference
> Manual and the UDO archive.
>
> Do you use a CMS for the Csound material pages? If so, it would be very nice
> if you could put in links to "skip the menu". I could supply a sort of
> template.
> ...
>
> Ta-ta,
> ----
> Ffanci
> * Homepage: https://freeshell.de/~silvain
> * Twitter:  http://twitter.com/ffanci_silvain
> * GitHub:   https://github.com/fsilvain
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here