From: Greg P. <Gre...@us...> - 2009-09-02 23:26:34
|
A) USQ would like to put their hand up to be institutionally involved. At the moment I am the contact, but we have a couple of people involved here and I discussed this email this morning with my manager and he's committed to ongoing community involvement even if I should leave the Uni. I'd also like to (humbly) suggest that the staff at the NLA would be an excellent choice if they would be willing to participate. I know Mark (at least) lurks on these lists, and NLA have one of (if not THE) largest long running production installations, and there's a lot of enterprise grade experience there. Their VuFind version is presently a long way from the trunk, but we can work on that :) if you're willing that is. B) Done. We have our own internal ticketing system so I've been somewhat passive in use of JIRA, but I think a more concerted effort there as a group is a fantastic idea. I know some members of the community have submitted patches and such into JIRA and the past and been ignored, which ultimately degrades confidence in the community and diminishes the involvement of some really talented people. C) Happy to help. Greg Pendlebury Electronic Services Officer (Systems Team) Division of Academic Information Services University of Southern Queensland Phone: +61 7 4631 1501 Fax: +61 7 4631 1841 ________________________________ From: Demian Katz [mailto:dem...@vi...] Sent: Thursday, 3 September 2009 4:33 AM To: vuf...@li...; vuf...@li... Subject: [VuFind-Tech] VuFind Development: Next Steps Importance: High Please excuse the cross-posting -- I just want to be sure that this reaches the largest possible audience. I've just returned from a meeting between Andrew Nagy and a team from Villanova where we discussed the future of VuFind and did some brainstorming to figure out the best way to keep development on track. We reached three broad conclusions: 1.) We should put together an official group of VuFind admins so that the project has more structured leadership. Andrew's time is too limited to guide the project alone, but it is useful to have a defined authority to make decisions about major directions for development and to set timetables for releases. The exact nature of this admin group will depend on how many people express interest in joining it -- see action items below. 2.) We should be making better use of JIRA. This is a useful tool for tracking problems, coordinating development efforts, and setting milestones. It's more flexible and easier to keep up to date than the static milestone pages on the website. 3.) We need a stable trunk -- much has been said about this already. The bottom line is that once we get the current code stabilized and ready for release, we have to start using development branches to ensure that the trunk itself is always stable. I'm sure we'll discuss this in more detail once the time comes. To turn these conclusions into tangible action, we need a few things from the community at large: A.) If you are interested in being a part of the VuFind admin group, please speak up. If you want to nominate somebody else, that could be helpful too. We want the group to be diverse and representative yet small enough to actually get things done at a reasonable pace. Once we know how much interest is out there, we can determine the ideal size and, if necessary, selection process for the group. B.) Please set up a JIRA account and look around if you haven't already (http://www.vufind.org/jira/). I'm going to be spending some time over the next few days looking over and cleaning up existing entries. If you know of issues that are unresolved and unlisted, please add them. If you entered entries that are now resolved, please close them. If you have opinions about how we could use this tool better, please share them. C.) Any help you can provide toward stabilizing the trunk would be greatly appreciated. Andrew has some outstanding changes that he still needs to commit. I have been doing minor cleanup here and there as I notice issues. If you fix minor bugs and have SVN commit access, please commit fixes. If you don't have commit access, feel free to submit patches through JIRA (and send me an email if you feel like they aren't being noticed quickly enough). If you run into problems but don't know how to fix them, bring them to the tech list for discussion. If you have time, do some generalized testing; click on everything and let us know about anything that doesn't work. Ideally, everything in the interface should either be made to work or turned off until it can be fully implemented. All of your help, past and future, is greatly appreciated, and I look forward to making great progress over the next few months. - Demian This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email. The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt. The University of Southern Queensland is a registered provider of education with the Australian Government (CRICOS Institution Code No's. QLD 00244B / NSW 02225M) |