[OrcasoundDev] Orcasound dev resources (as of 2021)
Scott Veirs
sveirs at gmail.com
Tue Jun 1 13:01:53 PDT 2021
Re-sending this test message (now that I've properly set the archive
and subscriber
list <http://listserver-kant.dreamhost.com/roster.cgi/dev-orcasound.net> to
be public).
--Scott
On Tue, Jun 1, 2021 at 12:53 PM Scott Veirs <sveirs at gmail.com> wrote:
> As a first/test post to this Orcasound-dev listserv (thanks Mailman!),
> here are some resources we've been developing/organizing over the winter:
>
> 1. Top-level on-boarding Google doc
> <https://docs.google.com/document/d/1Pjh5juthsG0sv7hYCtwgeXgNSlkmIt0p0bw17Y4VXco/edit#> (revised
> annually in winter)
> 2. Orcasound Github organization <https://github.com/orcasound> (only
> public repositories, mostly MIT/GPL licenses)
> 3. Overall Orcasound Roadmap
> <https://trello.com/b/wBg0qhss/orcasound-roadmap> (Trello-based,
> accumulating feature requests from listeners; has to dev boards in Trello
> or Github projects)
> 4. Scott's schematic of Orcasound roadmap across repos/projects
> <https://docs.google.com/drawings/d/123vU0ntak4t5VU0YZmSkaCD3_TESKvCIaBJIDOhkVVI/edit>
> (stay tuned for Paul's version soon...)
> 5. Standing invitation to the Orcasound Slack workspace
> <https://join.slack.com/t/orcasound/shared_invite/zt-bd1jk2q9-FjeWr3OzocDBwDgS0g1FdQ>
> (current day-to-day chat environment)
>
> More soon as our communication systems evolve. Any feedback or suggestions
> about other, more open ways to collaborate as a community of developers are
> always welcome!
>
> Stay well,
> Scott in Seattle
>
> P.S. This message is partially a way for me to test how Mailman formats
> hypertext references and a list! ;)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.orcasound.net/pipermail/dev-orcasound.net/attachments/20210601/f2eb962c/attachment.htm>
More information about the Dev
mailing list