In reply to Mark C. Wilson.

It’s really not a question of number of developers but commitment to community management, and resourcing of community managers. There are more than enough people doing work on OJS worldwide, and more than enough organisations with some actual resource to contribute dev resource either in kind or as money. The challenge is building the community structures that make it work and resourcing those. That’s where many OS projects go wrong in my view - failing to see that its about much more than dev resource.

If you look at something like the Apache foundation then I think there is very little actual dev resource at the centre but lots of infrastructures to support communities (and lots of argument as to whether they are the right shape/form). The dev resource flows from the community to the centre precisely because those infrastructures mean a lot of value is added to any contribution.

Add to that, as Kevin says the technical problem. OJS 2 is not well set up for contributions, but as a result of its structure almost every instance of OJS in the wild is a fork that’s not compatible with 3.0. How to shift is very hard. This is why I think the collaboration with Collaborative Knowledge Foundation is so exciting. It provides some technical space to help bring those forks back to a central plan.

Cameron NeylonProfessor of Research Communications

Centre for Culture & Technology, Curtin University cn@cameronneylon.net - http://cameronneylon.net

@cameronneylon -Â http://orcid.org/0000-0002-0068-716X