Difference between revisions of "Diagrams/Dev"

Revision as of 17:31, 25 July 2012

All the diagrams repos are now migrated to github, under the diagrams organization.

What still needs to be done:

Import issues from 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 this to get something that will work.
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)

[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.

@@ Line 1: / Line 1: @@
+== Darcs/patch-tag -> git/github migration ==
+All the diagrams repos are now migrated to github, under the [https://github.com/diagrams diagrams organization].
+What still needs to be done:
+* 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:
+** The diagrams website
+** The user manual and tutorial?
+** The packages themselves (in the .cabal files)
 == Design notes ==