On Mon, 07 Apr 2014, Tibor Simko wrote: > Today, we thought of continuing our informal discussion on topics such > as developer ecosystem tools (blog, chat, wiki, alternating forums, > topics, minutes); on the documentation (rst, user, developer); on the > automated code kwalitee tools (must-have vs nice-to-have pylint/pep8).
I've just posted a summary of our discussions on: http://invenio-software.org/wiki/Talk/TicketingMergingTools For convenience, here it is copied: [Tibor: time passes during which we were discussing pros and cons and various options and on how to improve project ecosystem tools and communication more generally.] Secound voting round 2014-04-07: (summary by Tibor) 1. We ended up preferring GitHub to Phabricator for merging and ticketing. E.g. classical pull requests vs "arc land", e.g. visibility of work for young developers for their further careers, e.g. usefulness of using the most popular tools, e.g. maintenance costs. 2. As for Monday's Invenio Development Forum, to facilitate people's presence and to improve the communication: a. the forum will be rotating again between IT and GS buildings, provided the audio-video room near GS will be found. (This was the original plan that somehow never materialised since there was no A/V room.) b. The topics for forum will be announced sooner and may consist of blitz 10-minutes short presentations on interesting ongoing developments e.g. "code harvester", so that the forum will be always more useful to people without laptops. c. A forum may always start with a five-minute summary of blockers from last week in order to re-prioritise issues arising between various components/teams. d. It was deemed that one hour long forum is not enough for any sensible common code sprinting. e. In all cases it would be nice if participation is bigger. 3. We then discussed establishing common developer blog platform, the idea that stemmed from the Phabricator debate. We discussed topics like personal vs group blogging, how to differentiate between Invenio-related topics and tool-generic ones, how to use similar markup (if possible reST) so that some blogs may be promoted up to the official documentation. After a short discussion it seems that the aggregation of individual blogs was more popular than establishing an integrated platform. It was deemed that a web forum like StackOverflow would be more useful and would be answering the original communication need better. 4. Could a web forum enhance (and even replace) our Hangouts and Email discussions? E.g. email is useful but mailing list archives are kind of messy. E.g. Hangouts are good but do not have parallel threads. A forum could perhaps replace both? a. The GS team set up a test Discourse flat forum instance at http://forum.invenio-software.org and give a demo. Could be used for archiving solutions to common issues, but also for RFC'ing perhaps. Let's try it out over a few weeks to see whether it would be useful in addition (or as a replacement) of some of the ecosystem tools we are using. b. There are other available tools to test such as http://social.cern.ch that could be perhaps useful? Best regards -- Tibor Simko
