Gabriele Mambrini
2015-01-20 16:08:42 UTC
Hi developers,
my name is Gabriele and I work for an Italian public institution,
where I was asked to implement a corporate survey solution based on
Limesurvey 2.
I'm writing some plugins to let my user authenticate on LS2 using our
identity management infrastructure and to manage LS2 permission using
LDAP groups. These plugins are tailored for our custom infrastructures
so I think I won't release them, however now I'm going to face some
issues that requires new features to be added to Limesurvey and I'd
like to contribute my patches to the community.
I've started playing with Limesurvey code implementing a new Central
Participant Database use case, where an user wants to share a
participant with all the other LS users. In corporate scenarios it may
happen that the CPDB is like an address book, feed by an admin (or a
scheduled job) and automatically shared among all the other users, so
my idea is to add a "public" flag to a participant when it should be
shared in such a way. The patch (I'm still working on it) is on github
https://github.com/gmambro/LimeSurvey/tree/publicparticipant
I've mostly been a system administrator for 10 years but I've
developed some applications for system monitoring, configuration and
documentation. I've been developing my web interfaces mainly with
Perl, using Catalyst and DBIX::Class, or Python, with Django, but I'm
scared by working with PHP.
So, if you think I can be useful, here I am.
Gabriele
my name is Gabriele and I work for an Italian public institution,
where I was asked to implement a corporate survey solution based on
Limesurvey 2.
I'm writing some plugins to let my user authenticate on LS2 using our
identity management infrastructure and to manage LS2 permission using
LDAP groups. These plugins are tailored for our custom infrastructures
so I think I won't release them, however now I'm going to face some
issues that requires new features to be added to Limesurvey and I'd
like to contribute my patches to the community.
I've started playing with Limesurvey code implementing a new Central
Participant Database use case, where an user wants to share a
participant with all the other LS users. In corporate scenarios it may
happen that the CPDB is like an address book, feed by an admin (or a
scheduled job) and automatically shared among all the other users, so
my idea is to add a "public" flag to a participant when it should be
shared in such a way. The patch (I'm still working on it) is on github
https://github.com/gmambro/LimeSurvey/tree/publicparticipant
I've mostly been a system administrator for 10 years but I've
developed some applications for system monitoring, configuration and
documentation. I've been developing my web interfaces mainly with
Perl, using Catalyst and DBIX::Class, or Python, with Django, but I'm
scared by working with PHP.
So, if you think I can be useful, here I am.
Gabriele