 |
 |
Thanks, Luciano. I am an advocate for the show-me-the-code method. In this case I'm going to give the contracted developer a chance to get a head start before the code is made publicly available. Peter On Jul 27, 2011, at 3:22 AM, Luciano Ramalho wrote: > Congrats on this project, Peter. > > On Tue, Jul 26, 2011 at 4:28 PM, Peter Murray <[log in to unmask]> wrote: >> Great questions, Lori. Thanks for prompting these clarifications. >> >> We're using Drupal as a foundation and are going to be contracting with a Drupal developer to integrate existing Drupal modules with any custom field design, taxonomy creation, and plug-in development required to meet the goals. One of the conditions we'll put on the development contract is that we can release the code behind the registry as open source itself. My current thinking is that once the core work done we'll put the code up on Google Code or GitHub or a similar code hosting service. > > The best practice in Open Source development is to put the code (and > specs, roadmap etc.) in a public repository on day 1. That way you > give others a chance to contribute with ideas, code reviews and even > code in the form of patches, if they find the project useful. > > Of course, developing in the open does not guarantee that you will get > any volunteer help. But doing it behind closed doors does guarantee > that you won't get any. > > Cheers, -- Peter Murray [log in to unmask] tel:+1-678-235-2955 Ass't Director, Technology Services Development http://dltj.org/about/ LYRASIS -- Great Libraries. Strong Communities. Innovative Answers. The Disruptive Library Technology Jester http://dltj.org/ Attrib-Noncomm-Share http://creativecommons.org/licenses/by-nc-sa/2.5/