Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
(add link to build status) |
m (→Guidelines: add link to contributing page) |
||
| Line 11: | Line 11: | ||
== Guidelines == |
== Guidelines == |
||
| + | |||
| + | * [[Diagrams/Contributing|How to contribute]] |
||
* [https://github.com/tibbe/haskell-style-guide/blob/master/haskell-style.md Coding style guidelines]. It's not worth being super picky about these, but in general they are quite good. |
* [https://github.com/tibbe/haskell-style-guide/blob/master/haskell-style.md Coding style guidelines]. It's not worth being super picky about these, but in general they are quite good. |
||
Revision as of 14:10, 22 October 2012
Darcs/patch-tag -> git/github migration
All the diagrams repos are now migrated to github, under the diagrams organization.
What still needs to be done:
- Update any and all references to patch-tag to point to github instead. This includes:
- The diagrams website
- The user manual and tutorial?
- The packages themselves (in the .cabal files)
Guidelines
- Coding style guidelines. It's not worth being super picky about these, but in general they are quite good.
- Guidelines for reviewing and merging code. For those with push access to one or more repos in the github diagrams organization.
Design notes
- Text support
- Notes on extending support for paths
- Bounding functions
- Freeze, attribute transformation, and the backend API
- Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.
Releases
Miscellaneous links
- [1]: ticket re: GHC error messages with ambiguous type variables. This comes up a lot when using diagrams, it would be nice to see this ticket resolved.
- travis-ci build status of all diagrams packages.