[Pkg-giraffe-discuss] update/how to proceed?

Mark Dufour m.dufour at zarafa.com
Sun May 31 18:50:27 UTC 2015


hi all,

as promised, a more general update and inquiry where and how to proceed. 

to start off, we have made several improvements in our SCM corresponding to some of the issues mentioned on the wiki page. unfortunately, there are many things on our plate at every moment, so it will take time to look into every issue. but with webapp 2.1 (which should be out in a few weeks), and ZCP 7.2.1 (_planned_ to be out in several weeks as well) things should have improved quite a bit (and hopefully we can do more before then). 

as for ZCP, some recent improvements:

-we added the new trademark policy as TRADEMARKS.txt to the tarball, so there is no real dependency on the website anymore. here's the updated page though: http://www.zarafa.com/trademark-policy/. we also made sure the various AGPL-3 files are in sync with this.
-as mentioned, we fixed several lintian warnings, and are looking forward to seeing more 
-we made using 'log_file=-' in search.cfg not result in logfile called '-', but only logging to stderr

I'm now personally wondering where to best proceed. some questions, that I know jelle was also wondering a bit about (I'm sorry if you already told this to a zarafian!):

-the SCM mentioned on the wiki does not seem to have recent commits? where can we find your 'master' branch? (based on our 7.2..?)
-would it be possible to divide the issues on the wiki into essential and nice-to-have? for example, complete systemd support might be quite some effort, but is it absolutely needed for a first version? would it be enough for now to just be 'compatible'..?
-which of the issues would be hard or annoying to solve for a non zarafa developer?
-which of the (necessary) issues could be considered the nastiest to solve? 
-it looks like some of you are actually looking into packaging webaccess (not webapp). my personal thought about this is (and I've mentioned this before here): please drop it. because it's end-of-life and webapp is its successor..
-in a similar vain, outlook is still mentioned on the wiki, while we are also dropping support for it in the near term (at least, using the current plugin method).
 
I'd personally love to put in quite a bit of time over the next two weeks or so to help solve issues. I just installed jessie in a VM and am looking forward to running your build and start looking around. if anyone on the debian side also has time, please contact me or let's talk in #debian-groupware.
 

thanks again for the work everyone has put in so far, and let's finish this..! ;-) 
mark.

-----Original message-----
> From:Mark Dufour <m.dufour at zarafa.com>
> Sent: Sunday 31st May 2015 17:48
> To: Jelle van der Waa <j.vanderwaa at zarafa.com>; pkg-giraffe-discuss at lists.alioth.debian.org
> Subject: RE: [Pkg-giraffe-discuss] Missing manpages
> 
> hi all,
> 
> > > Compared to last Saturday lintian is already quiet happy now. We need to
> > > rework the lib and python packaging anyway and once done most of this
> > > should be covered.
> 
> great to hear, and thanks to all involved. sorry it took a while to get my feet back on the ground after my vacation. I hope to start contributing again from now on, and will post a general update shortly. 
> 
> about the following lintian errors:
>  
> > >  W: zarafa-dagent: binary-without-manpage usr/bin/zarafa-mr-accept    
> 
> this is not really a binary that a user would start manually. it can be configured in dagent.cfg to deal with meeting requests. would it be a problem to leave this as-is for now..?
> 
> > >  W: zarafa-server: manpage-has-errors-from-man usr/share/man/man5/zarafa-ldap.cfg.5.gz 964: warning [p 11, 5.5i]: can't break line    
> > 
> > Spotted the error here:
> > Optional for OpenLDAP installations: \
> > fI(|(mail=%s*)(uid=%s*)(cn=*%s*)(fullname=*%s*)(givenname=*%s*)(lastname=*%s*)(sn=*%s*))\fR
> > 
> > I'm not an expert on man pages, but adding a space in the LDAP query resolves it but makes the query harder to copy/paste. So I am not certain what the correct solution is.
> 
> adding an 'invisible space', &#x200B; into the respective line in doc/manual.xml seems to solve the problem. no more error, copy-pastability.
> 
> > >  W: zarafa-search-plus: binary-without-manpage usr/bin/zarafa-search
> 
> I updated the search and search cfg manpages for the new search just now and added them to our packages. thanks for spotting this problem!
> 
> > I've created a ticket for these three issues in our internal bugtracker, when we have patches for these issues I'll send them to the list.
> 
> I personally don't think we will be done with this very soon, so I suggest we just put as many fixes as possible into 7.2.1, which should be released in a few weeks, at least as a beta2..? (we can always provide a tarball earlier).
> 
> 
> cheers,
> mark.



More information about the Pkg-giraffe-discuss mailing list