Bug#619347: Any progress with packaging Jappix?
On 2016-02-05 14:31, Daniel Pocock wrote: On 5 February 2016 20:12:13 CET, "W. Martin Borgert" <deba...@debian.org> wrote: Hi, the link to mentors seems to be dead. Is there any progress with Jappix packaging? Are there any problems? Missing JS dependencies? I tested it briefly but haven't had time to do any more. Sorry for having abandoned the project for so long. Upstream completely reorganized the directory layout of the source code and it's a festival of imported third-party code that is in different stages of being available in Debian. Also I've started tracking and rebuilding the debian/copyright file but got discouraged at some point. -- Philippe Gauthier <philippe.gauth...@deuxpi.ca> https://www.deuxpi.ca/@deuxpi
Bug#619347: Jappix - clarification
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, Thanks for your efforts to make a package of Jappix, I am also interested in trying it The source and binary packages are available now on the Debian Mentors page [0]. Even if they are not yet in the Debian archives, I try to keep those packages up to date. I recently evaluated Candy, I notice it can only really do MUC chat rooms and it had problems with doing private chats. Is the Jappix client known to be stable for both types of chat? I run a test instance on https://jabber.deuxpi.ca/ that runs over Prosody. It seems to work well enough for me. In the past, that same server was running ejabberd and I remember it had major limitations. One thing that is not clear from the description: does it provide any server-side capabilities? I notice a lot of PHP code, I haven't looked inside that, but is it doing any of the XMPP server-side functionality in that code? Can the JavaScript chat client be used standalone without the PHP code, e.g. JavaScript just talking to the BOSH server (e.g. ejabberd)? You are right. Jappix does not provide any server-side capabilities. The JavaScript client is JSJac, which is also used by JWChat. If you are looking for a simpler web client, you could look at that program instead. Based on the above question, is it possible that the package could be split into multiple packages, e.g. one package for the JavaScript client and another package with the PHP stuff just for those people who want that? This is a question that should be asked to the Jappix developer themselves. I know they have a mini mode already so that the Jappix code can be embedded into larger web apps. [0] https://mentors.debian.net/package/jappix Regards, Philippe Gauthier philippe.gauth...@deuxpi.ca http://www.deuxpi.ca/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHlZ2UACgkQdX62PscofCSO+wCgk+1Kr+bcI4MflYPjvsfn15gO eVsAn0qwC6VRGBvdFrluHn7Ztqfp7Mfj =0OEy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e56766.9000...@deuxpi.ca
Bug#619347: testing the Jappix package from mentors
Hi Daniel, Thanks for testing the package. I am not a member of the upstream developers, but they have been very responsive to our comments so far. My testing is biased: I already had ejabberd running and I had already used BOSH to integrate with the Candy chat client so my server was able to run Jappix very quickly. It took me all of about 5 minutes to get it going. So far, I feel the Jappix chat client is more reliable for both group chat and private chat than the Candy client. The Candy client would get into a bad state after trying to start any private chat. It was very easy for me to just disable the stuff in /etc/apache2/conf.d/jappix.conf and set it up in a virtual host. In my Apache2 virtual host, I used the following to force it to work with my ejabberd: RewriteEngine On # for Candy: RewriteRule ^/example/http-bind/ http://ejabberd-host:5280/http-bind/ [P] # for Jappix: RewriteRule ^/http-bind http://ejabberd-host:5280/http-bind/ [P] I will add this line to the /etc/apache2/conf.d/jappix.conf file (possibly commented out). This is also the configuration I was using on Apache. Various issues: - I feel there are a lot of options in the Jappix setup wizard. People not familiar with Jabber may not know all the server names they need to insert and the guesses are not going to be correct for a high percentage of users. This is an issue for upstream to improve. - the user login form: there should be an easy way to customize it, many people will just want the user logged in anonymously, without the full form. Candy has various login modes, in one case, it just asks the user to choose a nick name. - at one point, my Firefox test login dropped out of the chat session with Internal server error but it was happy to log in again 5 seconds later and showed the missed messages Ouch. The Debian bug tracker will probably not permit bug reports against the package yet. It should be added to the upstream bug tracker. Anonymous mode by default should not be difficult to implement and I think it would be useful. - I don't think the setup wizard should appear the first time somebody browses to the page: the admin password should be set during installation perhaps. With Drupal, it is necessary to browse to install.php to force the setup wizard to run, so random visitors don't start Drupal setup by accident. This is not highly secure either, but it removes some risk of random chance. Great idea. I will ask the Jappix developers for guidance and adapt the default configuration based on their answer. - Please add a README.Debian - if you can, include something in README.Debian about how people can integrate Jappix into their existing web site This is definitely needed. - it would be particularly interesting if you provide, under /usr/share/doc/jappix some sample ejabberd.cfg or a diff from the default Debian ejabberd.cfg - I had to enable the mod_http_bind module, declare a new domain for my anonymous web users and then declare that http_bind was permitted for that domain. I have been running Prosody for some time so I'm a bit unfamiliar with ejabberd. If you can describe the changes to the configuration, I will include them in the aforementioned README.Debian file :) - when I installed the .deb package, it tries to restart apache although I have apache2, so it gives an error: [ ok ] Reloading web server config: apache2. Setting up jappix (0.9.8+dfsg-1) ... invoke-rc.d: unknown initscript, /etc/init.d/apache not found. [ ok ] Reloading web server config: apache2. The postinstall script detects the presence of Apache (apache or apache2) and attemps to restart both. This could be improved and I will look into that. On my system running nginx, the script tries to restart both inexisting servers. - the font you mentioned in an earlier email - is there any reason it couldn't be listed in a separate source package in your control file? I just assumed that is might not be the best practice to generate unrelated packages from the same source. Still, it would be technically easy to do. Thank you and best regards, -- Philippe Gauthier philippe.gauth...@deuxpi.ca http://www.deuxpi.ca/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e56e9f.3090...@deuxpi.ca
Bug#619347: ITP: jappix -- The first full-featured XMPP web-client in the world
On Wed, 23 Mar 2011 09:37:57 +0100, Olivier Berger olivier.ber...@it-sudparis.eu wrote: I'm not sure this description is really accurate, given the meaning that cloud confers nowadays. I'd suggest to rephrase for something less buzz word oriented, and more accurate of what the program allows to do. Thanks! The description has been changed and an updated package has been uploaded to mentors.debian.net: Description: a full-featured XMPP (Jabber) web-client Jappix is a social platform based on the XMPP protocol. It supports instant messaging, presence, multi-party chat, and account and roster management. Jappix also has capabilities for integrating media such as YouTube, Dailymotion, Vimeo or Theora videos, audio or images, and can be used as a simple music player. . Jappix presents a full-featured web-based interface that users can access without installing any additional software. It may also allow the use of XMPP in restricted networking environments like some corporate networks on which XMPP ports are blocked. Users can also choose an alternative interface that has been simplified for mobile devices. Also, the debian/README.source template was removed from the package. -- Philippe Gauthier philippe.gauth...@deuxpi.ca http://www.deuxpi.ca/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/98c204f80b3a8293376fec2dc118e...@deuxpi.ca
Bug#619347: ITP: jappix -- The first full-featured XMPP web-client in the world
Package: wnpp Severity: wishlist Owner: Philippe Gauthier philippe.gauth...@deuxpi.ca * Package name: jappix Version : 0.4 Upstream Author : Valérian Saliou vanar...@vanaryon.eu * URL : http://project.jappix.com/ * License : AGPL Programming Lang: PHP, JavaScript Description : The first full-featured XMPP web-client in the world Jappix is a fresh new open social platform which enables you to create your own cloud, wherever you want to. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110323015831.21447.84035.reportbug@phil-ThinkPad-T500
