Difference between revisions of "Diagrams/Dev"
< Diagrams
Jump to navigation
Jump to search
(info about darcs -> git migration) |
m (→Design notes: fix formatting) |
||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Darcs/patch-tag -> git/github migration == |
== Darcs/patch-tag -> git/github migration == |
||
− | All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization]. |
+ | All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization]. I believe that all references (documentation, .cabal files, etc.) have now been updated as well. |
+ | == Guidelines == |
||
− | What still needs to be done: |
||
+ | * [[Diagrams/Contributing|How to contribute]] |
||
− | * Import issues from [http://code.google.com/p/diagrams/issues/list Google code] into github. However, the github issue trackers are per-repo, so we'll have to import according to 'Component' tag (and the component tags may need to be cleaned up on google code first). fryguybob thinks maybe we can modify [https://github.com/arthur-debert/google-code-issues-migrator/blob/master/migrateissues.py#L100 this] to get something that will work. |
||
+ | |||
− | * Update any and all references to patch-tag to point to github instead. This includes: |
||
+ | * [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. |
||
− | ** The diagrams website |
||
+ | |||
− | ** The user manual and tutorial? |
||
+ | * [[/ReviewingAndMerging|Guidelines for reviewing and merging code]]. For those with push access to one or more repos in the [http://github.com/diagrams github diagrams organization]. |
||
− | ** The packages themselves (in the .cabal files) |
||
== Design notes == |
== Design notes == |
||
Line 18: | Line 18: | ||
* [[/Freezing|Freeze, attribute transformation, and the backend API]] |
* [[/Freezing|Freeze, attribute transformation, and the backend API]] |
||
* [[/Transformations|Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.]] |
* [[/Transformations|Notes on the representation of transformations: linear and affine transformations, inverse, transpose, etc.]] |
||
+ | * [[/Arrows|Arrows]] |
||
== Releases == |
== Releases == |
||
Line 26: | Line 27: | ||
* [http://hackage.haskell.org/trac/ghc/ticket/4921]: 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. |
* [http://hackage.haskell.org/trac/ghc/ticket/4921]: 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. |
||
+ | |||
+ | * [[/BuildStatus|travis-ci build status]] of all diagrams packages. |
||
+ | |||
+ | * byorgey's time spent hacking on diagrams:<br />[https://www.beeminder.com/byorgey/goals/diagrams http://beeminder.com/byorgey/diagrams-thumb.png] |
Revision as of 03:19, 13 December 2012
Darcs/patch-tag -> git/github migration
All the diagrams repos are now migrated to github, under the diagrams organization. I believe that all references (documentation, .cabal files, etc.) have now been updated as well.
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.
- Arrows
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.