Comments on: “Show Me The Code!!!” -or- It Isn’t Open Source Until We Can See the Source http://dltj.org/article/show-me-the-code/ We're Disrupted, We're Librarians, and We're Not Going to Take It Anymore Wed, 23 May 2012 16:01:37 +0000 hourly 1 By: Jordi Serranohttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-160813 Jordi Serrano Thu, 13 Jan 2011 23:40:40 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-160813 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">“Show Me The Code!!!” -or- It Isn’t Open Source Until We Can See the Source | Disruptive Library Technology http://t.co/z5JZSgQ #biblioteca</span></span> “Show Me The Code!!!” -or- It Isn’t Open Source Until We Can See the Source | Disruptive Library Technology http://t.co/z5JZSgQ #biblioteca

]]> By: Hendrietta Kohahttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-38372 Hendrietta Koha Fri, 23 Oct 2009 01:49:13 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-38372 About the source code, if i'am doing a software test and find some problems with the software and its regarding the code, how will i make changes and intergrate code into production environment. About the source code, if i’am doing a software test and find some problems with the software and its regarding the code, how will i make changes and intergrate code into production environment.

]]> By: Walt Lessunhttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-19583 Walt Lessun Fri, 27 Jul 2007 15:55:12 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-19583 wouldn’t you rather learn one small thing a week than 104 every two years? Well, I would ;-)Hmmm. I think I'm going for the 104 every two years. When the 104 were scheduled, I'd take vacation. By the time I got back the 104 things that were taught would be obsolete anyway. wouldn’t you rather learn one small thing a week than 104 every two years? Well, I would ;-)

Hmmm. I think I’m going for the 104 every two years. When the 104 were scheduled, I’d take vacation. By the time I got back the 104 things that were taught would be obsolete anyway.

]]> By: K.G. Schneiderhttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-19552 K.G. Schneider Thu, 26 Jul 2007 18:38:23 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-19552 That's a good point, Peter. Maybe the key is to show them that the "sip not gulp" model of upgrading is healthier all around. it does require library staff who can roll with incremental changes... but that's a training issue as well; wouldn't you rather learn one small thing a week than 104 every two years? Well, I would ;-) That’s a good point, Peter. Maybe the key is to show them that the “sip not gulp” model of upgrading is healthier all around. it does require library staff who can roll with incremental changes… but that’s a training issue as well; wouldn’t you rather learn one small thing a week than 104 every two years? Well, I would ;-)

]]> By: the jesterhttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-19550 the jester Thu, 26 Jul 2007 18:06:54 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-19550 [quote comment="19548"]Tried using your blockquote tags and couldn't figure them out (and "quote selected text" was making me nutty as well).[/quote]The quoting scheme uses JavaScript to push the text-to-be-quoted into the comment form. I'll have to take a look at it to make sure it's working right. 'salright, though -- you got the point across, and that is the point, right?Thanks for the comment about 'release early, release often'. I'll take a small exception to it, though, to say that we should prepare our administrators (and our systems) for small, incremental updates. Much of the software in the library arena is still based on the monolithic release paradigm. We've got version 2.0 of the software now, and our vendor just release version 2.1 -- it is going to take us a week to reprofile, upgrade the screens, rewrite documentation, prepare staff, etc... Note that the "Web 2.0" style doesn't have "releases" <i>per se</i> -- there isn't a big announcement when Amazon, Google, Technorati, Flickr, and the like bring out 'new versions.' Stuff just incrementally appears. [quote comment="19548"]Tried using your blockquote tags and couldn’t figure them out (and “quote selected text” was making me nutty as well).[/quote]

The quoting scheme uses JavaScript to push the text-to-be-quoted into the comment form. I’ll have to take a look at it to make sure it’s working right. ‘salright, though — you got the point across, and that is the point, right?

Thanks for the comment about ‘release early, release often’. I’ll take a small exception to it, though, to say that we should prepare our administrators (and our systems) for small, incremental updates. Much of the software in the library arena is still based on the monolithic release paradigm. We’ve got version 2.0 of the software now, and our vendor just release version 2.1 — it is going to take us a week to reprofile, upgrade the screens, rewrite documentation, prepare staff, etc… Note that the “Web 2.0″ style doesn’t have “releases” per se — there isn’t a big announcement when Amazon, Google, Technorati, Flickr, and the like bring out ‘new versions.’ Stuff just incrementally appears.

]]> By: K.G. Schneiderhttp://dltj.org/article/show-me-the-code/comment-page-1/#comment-19548 K.G. Schneider Thu, 26 Jul 2007 17:30:29 +0000 http://dltj.org/2007/07/show-me-the-code/#comment-19548 <em>Other instances include various discussions with people that tend to drift off at the point of "well, I’ll release it when I get a chance to clean it up" or "you know, there are so many institution-specific hard coded things in it"</em>Tried using your blockquote tags and couldn't figure them out (and "quote selected text" was making me nutty as well). But wanted to say that in a Former Place Of Work, I lived this life. Open source that isn't open source, ain't open source.Note that "release early, release often" needs to be explained to admin-types in a way that doesn't mean you're committing your institution to devoting most of its time to upgrading the same software over and over again. Other instances include various discussions with people that tend to drift off at the point of “well, I’ll release it when I get a chance to clean it up” or “you know, there are so many institution-specific hard coded things in it”

Tried using your blockquote tags and couldn’t figure them out (and “quote selected text” was making me nutty as well). But wanted to say that in a Former Place Of Work, I lived this life. Open source that isn’t open source, ain’t open source.

Note that “release early, release often” needs to be explained to admin-types in a way that doesn’t mean you’re committing your institution to devoting most of its time to upgrading the same software over and over again.

]]>