- kune-devel - lists.ourproject.org

[kune issues] #130: When starting assemblies ask for minutes doc creation
by kune issues 10 Oct '11

10 Oct '11

#130: When starting assemblies ask for minutes doc creation --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: minor | Milestone: Component: Chat | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/130> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #138: Add change password functionality to the User Interface
by kune issues 09 Oct '11

09 Oct '11

#138: Add change password functionality to the User Interface --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: blocker | Milestone: Component: User space | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/138> kune issues <http://kune.ourproject.org/issues/>

1 1

Comunes general meeting October
by Samer 09 Oct '11

09 Oct '11

Hi there, We continue the online general meetings of Comunes (including its projects including Kune and Move Commons) on the 14th of each month. Thus, next Friday at 16:00 (Madrid time) we'll be connected in gmail/jabber for whomever is interested. Hope you can make it although it's slightly earlier than usual. Cheers PS: If you are interested to join but you never did before, please send me your gmail or jabber account so we can include you. -- Samer http://comunes.org "No son tiempos para hacer cualquier cosa"

1 0

Screencast + Testing
by Vicente J. Ruiz Jurado 07 Oct '11

07 Oct '11

Hola majos: Reenvío esto a la lista por si a alguien le apetece/puede echar un cable. Estoy generando vídeos automáticamente a partir de test de selenium. Todavía queda ajustar tiempos etc (encima no se pq el vídeo se grabó más rápido de lo que realmente iban los test), pero os podéis hacer una idea. La idea doble es que los subtítulos que salen se pueden usar tb además para procesos de guiado de los usuarios/as... es decir, ahora te recomendamos que hagas esto, u esto otro. El subtítulo es una url también (codifica el título, subtítulo y la url a donde ir después de pulsar algo). Ejemplo: http://blip.tv/vjrj/sample-of-kune-automated-screencast-5618999 Ese vídeo lo genera esto: http://ourproject.org/plugins/scmsvn/viewcvs.php/trunk/src/test/java/cc/kun… leer a partir de "basicRegister", es decir, que con poco código, podemos probar Kune y hacer de paso vídeos, y ... también guiar en plan intro de Kune. También es una forma fácil de que gente nos ayude a documentar y testear creando tests/vídeos de ese tipo. Un pelín verde aún, pero apunta a quitarnos mucho curro de documentación (ahora genérame el mismo vídeo en español, pero con la nueva versión de kune y con el look-feel de tal instalacción de kune, etc) Abrazotes, -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog "The preservation of the means of knowledge among the lowest ranks is of more importance to the public than all the property of the rich men in the country." [John Adams (1735-1826)]

1 0

[kune issues] #133: Messages not clear: "this site"?
by kune issues 06 Oct '11

06 Oct '11

#133: Messages not clear: "this site"? -----------------------+------------------- Reporter: samer@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Usability | Version: Keywords: | Blocked By: Blocking: | -----------------------+------------------- I understand that the word "Kune" shouldn't be relevant and appear everywhere such as Google or Facebook do. I see that everywhere (descriptions, mouse-over, introductory wave...), instead of Kune it talks about "this site". This is useful when a third party adapts Kune for their needs, so the word "Kune" doesn't appear. For example: "This is only a preview of how this webpage looks like to the general public on the internet, outside this site" However, it's not clear at all when read by a random user. That is, it's not clear that "this site" means Kune, and not this page, this group space, this document, this website, this platform... Rana's suggestion: use a variable that can be changed by each installation. That is, if Iepala wants to call it Gloobal, in that message it would show: "This is only a preview of how this webpage looks like to the general public on the internet, outside Gloobal" and in Kune.cc, for example: "This is only a preview of how this webpage looks like to the general public on the internet, outside Kune.cc" This would be far much clearer. I find it important as one of the main problems of Kune right now is to reduce confussion and maximize communication/usability for new users. Juan was disappointed solely because of this issue... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/133> kune issues <http://kune.ourproject.org/issues/>

3 3

Las issues
by Vicente J. Ruiz Jurado 06 Oct '11

06 Oct '11

Bueno Aitor, Muy chula reu y tus explicaciones como siempre. Aquí están la lista de issues activas: http://kune.ourproject.org/issues/report/1 Para añadir: http://kune.ourproject.org/issues/newticket pero vamos, puedes escribir a kune-devel(a)lists.ourproject.org si quieres directamente y ya lo pasamos a issues. Un abrazote, -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog "La mejor forma de decir es hacer" [José Martí]

1 0

Re: [kune-devel] [kune issues] #79: I18n refactorization
by kune issues 04 Oct '11

04 Oct '11

#79: I18n refactorization --------------------------+-------------------- Reporter: vjrj | Owner: vjrj Type: enhancement | Status: closed Priority: major | Milestone: Component: Common | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+-------------------- Changes (by vjrj): * status: new => closed * resolution: => fixed -- Ticket URL: <http://kune.ourproject.org/issues/ticket/79#comment:1> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-devel] [kune issues] #122: To revise our UI English
by kune issues 03 Oct '11

03 Oct '11

#122: To revise our UI English -----------------------------------+-------------------- Reporter: vjrj | Owner: vjrj Type: enhancement | Status: closed Priority: critical | Milestone: Component: Internationalization | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: -----------------------------------+-------------------- Changes (by vjrj): * status: new => closed * resolution: => fixed Comment: Fixed: Thanks indeed to Rana and Samer... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/122#comment:3> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #131: Secure register/sign in and autologin
by kune issues 28 Sep '11

28 Sep '11

#131: Secure register/sign in and autologin --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Common | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ The goal: - Register accounts - Sign in with user/pass - and auto login with a cookie for some days in both Kune+Wave+XMPP Also we have to permit xmpp auth to non kune/emite xmpp clients. The current status: Kune/WIAB register users with digest SHA-512 + salt auth plaintext user + pass (see WaveClientSimpleAuthenticator). Aka: We should use https Autologin is done via a hash in a cookie. A proposed non secure solution (server specific) is to implement a custom: http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/jav… http://community.igniterealtime.org/thread/35365 and for autologin, try to auth to xmpp with user+cookie-hash as a second option using: http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/jav… This permits normal xmpp use (with external and emite client) and autologin for xmpp also in kune. Problem: we need to store plain passwords (even with a SASL client I think). See: http://svn.igniterealtime.org/svn/repos/openfire/trunk/src/java/org/jivesof… http://svn.igniterealtime.org/svn/repos/openfire/trunk/src/java/org/jivesof… http://java-monitor.com/forum/showthread.php?t=453 This is not secure: "But hey, management wants encrypted passwords in the database, management gets encrypted passwords in the database. :-)" TODO: study a way to make a compatible secure plain+digest AuthProvider compatible with our SHA-512 stored pass... Work in progress -- Ticket URL: <http://kune.ourproject.org/issues/ticket/131> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #126: Not realizing you have to "Sign-in"
by kune issues 28 Sep '11

28 Sep '11

#126: Not realizing you have to "Sign-in" -------------------------+------------------- Reporter: samer@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- Non-technical users enter Kune, play a bit in the group-space, but don't know what to as they don't notice they must click in "Sign-in to collaborate" and from there in "Create one" (account). I think it'd be recommended to highligh much more the Sign-in, blinking or however it's clearer, to attract attention towards it and make sure the new users actually use it. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/126> kune issues <http://kune.ourproject.org/issues/>

1 1