Tech Committee Agenda 18 June 2013
- Welcome to our new at-large committee members: Bozana Bokan (Free University Berlin), Marc Bria (Autonomous University of Barcelona)
- Quick round of updates
- What have we all been working on PKP-wise?
- Any particular needs that the group can help with?
- At-large membership: one more member to invite
- 3 volunteers from members committee - Brian Owen has asked the Members Committee to appoint 3 people. We hope to have them on board soon, well in advance of the AGM.
- Reviewing our mandate, cont'd.
- Charge #1: provide technical input and advice on PKP’s software development methodologies and priorities. A couple of meetings ago, the group came to the consensus that PKP priorities and methodologies are unclear. We are working towards fixing this so that we can begin to give input.
- James has kindly provided a #Round up of documentation relating to PKP Priorities and Methodologies. Please read and we will discuss. What needs clarification? What would this information ideally look like?
- Barbara has taken a stab at organizing the PKP wiki so that this kind of info can be more easily found (see Main page - New). What do people think?
- Committee communication
- PKP AGM and conference in Mexico City, August 19-21
- Who is going?
- What are our goals for the PKP Tech Committee meeting there?
- Next meeting: how about Tuesday 17 July, 2013?
- Anything else?
Round up of documentation relating to PKP Priorities and Methodologies
-- general priorities are grouped into the general milestones chart: http://pkp.sfu.ca/wiki/index.php?title=General_Software_Milestones
-- each software application has its own individual roadmap as well, eg: http://pkp.sfu.ca/wiki/index.php?title=OJS_Roadmap
-- we have also started individual project pages to help track project progress, priorities, etc. and provide a clear location for pointing interested parties (eg. http://pkp.sfu.ca/wiki/index.php?title=XML_Publishing)
-- we also collect and track bugs etc. in Bugzilla. There are several different priority markers available (priority, severity, version), but as a team we really only use the "version" marker to establish within what timeframe a bug should be completed (eg. all bugs marked 2.4.2 must be closed for OJS 2.4.2 release). We could probably do better here.
-- in terms of tackling development projects or bugs that have been brought to our attention from the community, we use a very ad-hoc method of determining priority, based mostly on subjective terms -- how often we feel something has been brought up, squeaky wheel, etc.
-- Asana for tracking internal PKP tasks and priorities.
-- Our own weekly meetings (PKP Developer meeting on Mondays; general PKP meeting on Fridays)
-- Various interminable Google Docs
-- There's a fair bit of developer documentation on the wiki: http://pkp.sfu.ca/wiki/index.php?title=Main_Page#Development_Topics. This covers getting the code, contributing patches, interacting with github, etc. The documentation could probably stand a going-over and simplified, and needs to be promoted.
-- we have only recently cleaned up our patch submission guidelines to favour git, for example.
-- There's also the currently fairly out-of-date OJS Technical Reference (http://pkp.sfu.ca/ojs/docs/technicalreference/2.1/index.html). While out of date, this is as far as I know the only place that gives a really good breakdown of PKP's coding conventions, the MVC framework that we use, and a thorough (though let's stress, out of date) breakdown of the OJS database. It may be worth considering how we adapt this document to the wiki, and to our other applications.
-- PKP also stores a fair bit of documentation on hosting practices, whether for our team (eg. how to install a journal on our servers) or for our clients (how to use the Custom Block Manager in conjunction with Static Pages). While most of our internal methodology should remain internal, the client-based documentation should be opened up to the wider community. It's the sort of questions we find ourselves answering over and over (how to set up DOIs; how to add content like a CMS) that our current documentation doesn't adequately cover.