Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
purr-data
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Rishabh Gupta
purr-data
Commits
1b1f8698
Commit
1b1f8698
authored
Mar 18, 2018
by
Jonathan Wilkes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
clean up contributor guidelines, add rule about external library dependencies
parent
7a019fe7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
2 deletions
+9
-2
README.md
README.md
+9
-2
No files found.
README.md
View file @
1b1f8698
...
...
@@ -287,11 +287,16 @@ A few guidelines:
and libraries must be stable, consistent, well-documented, and easy to use.
*
Develop incrementally. Small, solid improvements to the software are
preferable to large, disruptive ones.
*
Make sure you aren't duplicating existing functionality, especially core
functionality.
For backwards compatibility Purr Data ships many legacy
*
Try not to duplicate existing functionality.
For backwards compatibility Purr Data ships many legacy
libraries which unfortunately duplicate the same functionality. This makes
it harder to learn how to use Pd, and makes it burdensome to read patches
and keep track of all the disparate implementations.
*
Keep dependencies to a minimum. Cross-platform dependency handling is
unfortunately still an open research problem. In the even that you need
an external library dependency, please mirror it at git.purrdata.net
so that the build system doesn't depend on the availability of external
infrastructure.
Here are some of the current tasks:
...
...
@@ -313,6 +318,8 @@ Here are some of the current tasks:
*
status: some externals have their own testing environments, but they are
limited as they require manual intervention to run and read the
results inside a graphical window.
We currently have a crude test system that at least ensures that each
external library instantiates without crashing.
Here's an email thread with Katja Vetter's design, which looks to
be automatable:
http://markmail.org/message/t7yitfc55anus76i#query:+page:1+mid:chb56ve7kea2qumn+state:results
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment