Community Support/Minutes 14Apr2016

From Davical
Revision as of 21:21, 15 May 2016 by Fenton (talk | contribs) (Add minutes of 14 April 2016 meeting)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

DAViCal PROJECT MEETING, called for 2016-04-14, 19:00 UTC

People involved in the meeting:

Jim Fenton, Florian Schlichting, Cyril Giraud, Tuxick

Begin time: 19:15 UTC

1. Project infrastructure

1.1. Website and documentation

Discussion of Road Map page on wiki vs. Roadmap category: possible confusion; should we generate category pages when encountering a missing one?

Some gardening on the wiki would probably be a good idea.

Multilanguage issue still alive on the wiki.


1.2. Source code

More discussion (continued from previous meeting) on documentation tools. Leaning towards php-apigen because it's already packaged in Debian.

tuxick will see about setting up a cron job to update documentation, similar to the one that updates the website. running apigen shows there's some redeclaration of classes, this also needs some cleaning up, probably report via gitlab.

1.2.1 Git

1.3. Downloads and binary repositories

1.3.1 Debian/DEB Packages

Florian will look into uploading davical 1.1.4 and awl to jessie-backports, as a more obvious (for our users) alternative to davical-current on people.

1.3.2 RedHat/RPM Packages

1.4. Localization

Running xgettext to update the translation templates should be separated from compiling *.mo files. The latter needs to be done when installing from git or building a package, the former is only necessary before starting a new call for translations via Transifex.

2. Development

2.1. Tickets or bug reports

2.2. Patches or updates

2.3. New features or versions

Cyril suggests improving the installation process, so that a working database connection and web UI is available after package install. For configuration, using a web UI rather than manually editing config.php would make many settings more accessible. However, an authentication process is required to deny access to unexpected Internet users, e.g. with a password created during package install. Some consideration is needed what to do when the installation process finds remains of previous installs.


3.Project community

3.1 Mailing list and meetings

Next meeting: Thursday 2 June 2016, 19:00 UTC

3.2. Roles

3.3. Communication with Andrew McMillan

4. Off topics

Meeting adjourned 21:10 UTC.