Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Tuesday February 19, 2008
08:40 AM

Talking About Code You Haven't Released

[ #35695 ]

All things considered, I'm quite happy that I've not yet released Bermuda (I wish use.perl supported tags!). Currently I'm working on a conceptual problem dealing with separating the generation of data structures with the serialization of said structures. By making the separation more explicit, much of my code has simplified quite a bit and I now see an issue with some class names being confusing. Had I already released this code, I would be much more concerned with others using it when I still want to break the API. By talking about it, I've gotten a lot of excellent feedback about design issues, but even when I haven't received feedback (hint, hint!), merely talking about it has clarified issues for me.

The downside, however, is obvious: who cares? Aside from a couple of people telling me in email that they're very interested in this project and are looking forward to its release, short of releasing code, it's very difficult to tell if it scratches anyone's itch but my own. Programming in a vacuum lets me do exactly what I think I need to do (that helped when I started the TAP::Parser project), but my needs and yours might be radically different. Does Bermuda sound even remotely relevant to what you do?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • All of this doesn't stop you throwing some under-documented subject-to-extensive-change dev releases up.
  • Have you publicized the repository? That's a way to make it available to people who share your itch without committing yourself to a "release" on CPAN.

    --dagolden
    • I'm looking into that. I was going to ask a friend if I could set it up on his box with git, but the BBC is talking about a "BBC Open" programme which would rather be like SourceForge or Google Code, but with our imprimatur on it, using code that we've developed in-house. Repositories would be open and others could easily commit patches and, perhaps, get commit bits. The reason for this is that they want to strongly brand the BBC as being a company behind open source. There's a bit more to it than that,