Dan Fornika <dforn...@gmail.com> writes: > My name is Dan Fornika, I'm a genetics grad student in Canada and > beginning self-taught haskell programmer. I'm making some progress on a > parser for Polyphred XML output (based on HXT).
Great! > I started the project with the intention of contributing it to > BioHaskell, and I'd like to ask about how I can do this. I've never > contributed to an open-source project before. What they said :-) I.e. package your stuff as a library using cabal, put it in a publicly available darcs repo, put it on Hackage in the Bioinformatics category, and tell the world about it, e.g. here, on the haskell-cafe mailing list, and on biohaskell.org. I'm happy to incorporate stuff in 'bio' as well, but so far there seems to be more file formats than developers, so you are likely to be the only person working on e.g. PolyPhred, and then it's probably easier to just make a separate library. We should try to standardize on basic stuff across libraries, like sequence data types and the like, though. > I noticed that there are other XML parsers based on other Haskell > modules (tagsoup). Will my choice of XML library prevent it from being > incorporated into the project? It looks like HXT is the most > full-featured and well-supported XML handling library right now, but it > is a 'bigger' dependency than tagsoup. When I wrote the Blast XML parser, I tried the various options, but tagsoup was the only one that could deal with sizeable files (and Blast output can be several gigabytes). This may have changed since then. > I'm sure my code is pretty fragile and verbose, but I don't know what > the best way is to get some more experienced eyeballs to look at it. > Should I just attach it to a message and send it to the list? If you have specific questions, I'd prefer an excerpt that elucidates it. You could also use haskell-cafe for that, you're more likely to find people with HXT experience. > P.S. I've been trying to get an account for the wiki but I've been > getting error messages: > > Server error: : commitAndReleaseBuffer: hardware fault (Input/output error) Oh dear, that doesn't look too good. Thanks for reporting, I'll take a look. -k -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Biohaskell mailing list Biohaskell@biohaskell.org http://malde.org/cgi-bin/mailman/listinfo/biohaskell
