April 2012 - kune-commits - lists.ourproject.org

[kune issues] #246: Add FAQ link to "More"
by kune issues 19 Apr '12

19 Apr '12

#246: Add FAQ link to "More" -------------------------+------------------- Reporter: samer@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Others | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- I feel many people will have questions about Kune but won't click on "kune development site" if they are not geeks. Maybe it's convenient to place a direct "FAQ" link to solve common questions. I'm thinking on the people that will know kune.cc but not the kune.op.org website -- Ticket URL: <http://kune.ourproject.org/issues/ticket/246> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #248: Wikis aren't editable by anyone by default
by kune issues 19 Apr '12

19 Apr '12

#248: Wikis aren't editable by anyone by default ---------------------------+------------------- Reporter: supercopter@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: Wiki | Blocked By: Blocking: | ---------------------------+------------------- According to the Prezzi-like tutorial for wikis, a wiki "can be edited by anyone". But when creating a wiki wave, the @kune.cc "public" contact isn't added as a participant. I know that it can be made public later but that's not user friendly for newcomers who doesn't know much about Wave. If the tutorial explains that a wiki is editable by anyone, then the expected behavior should IMHO be to have @kune.cc included by default. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/248> kune issues <http://kune.ourproject.org/issues/>

1 2

[kune issues] #251: "Invite" for lists
by kune issues 19 Apr '12

19 Apr '12

#251: "Invite" for lists -------------------------+------------------- Reporter: samer@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- Lists are not lists if we cannot make invitations. It is much easier to be subscribed by accepting an invitation than by searching for the group, going to lists, choosing one, subscribe. It's not trivial for non-geeks, so invitations should be much better. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/251> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #250: Eliminar documentos con nombres repetidos
by kune issues 19 Apr '12

19 Apr '12

#250: Eliminar documentos con nombres repetidos -------------------------------------------------+------------------------- Reporter: jpzafra | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: 0.1.0 Component: Usability | Version: 0.1.0 Keywords: trash, eliminar, nombre, documento, | Blocked By: delete, papelera | Blocking: | -------------------------------------------------+------------------------- Al arrastrar un documento (o cualquier cosa) a la papelera habiendo ya en ella un documento con el mismo nombre que el documento arrastrado no te deja eliminarlo. En mi opnión, eliminar un documento debe ser independiente del nombre del mismo, se supone que hay un id o algo para que la aplicación falle. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/250> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #247: New buddies aren't automatically displayed
by kune issues 19 Apr '12

19 Apr '12

#247: New buddies aren't automatically displayed ---------------------------+------------------- Reporter: supercopter@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: Buddies | Blocked By: Blocking: | ---------------------------+------------------- After accepting a contact as a new buddy, his avatar pic isn't displayed in the "buddies" list unless you manually use the dropdown menu "Users who can view your network" to set it to "anyone", even if it was already set on "anyone" before. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/247> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-commits] [kune issues] #169: Sign-in username is confusing: force lowercase & more
by kune issues 19 Apr '12

19 Apr '12

#169: Sign-in username is confusing: force lowercase & more --------------------------+-------------------- Reporter: samer@… | Owner: vjrj Type: enhancement | Status: closed Priority: critical | Milestone: Component: Group space | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+-------------------- Comment (by samer@…): From #181 (closed)=> also auto-change to lowercase: * the username in the log-in dialog (not just in the sign-in dialog). * the group name in the register-group dialog -- Ticket URL: <http://kune.ourproject.org/issues/ticket/169#comment:4> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-commits] [kune issues] #169: Sign-in username is confusing: force lowercase & more (was: usernames and group short-names)
by kune issues 19 Apr '12

19 Apr '12

#169: Sign-in username is confusing: force lowercase & more --------------------------+-------------------- Reporter: samer@… | Owner: vjrj Type: enhancement | Status: closed Priority: critical | Milestone: Component: Group space | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+-------------------- Changes (by samer@…): * priority: major => critical Comment: I agree with Contraproposal to (3). I'd also do (1). -- Ticket URL: <http://kune.ourproject.org/issues/ticket/169#comment:3> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #245: Click in trash as collaborator=>expels me
by kune issues 19 Apr '12

19 Apr '12

#245: Click in trash as collaborator=>expels me -------------------------+------------------- Reporter: samer@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- If I'm admin of group X and I click on "trash" (papelera), then I can see its contents normally. However, if I click on it when I'm a collaborator of a group, a message appears "You do not have rights to perform that action" (which is ok) and after I am taken to my homepage (which doesn't make sense). It's fine if I don't have permissions, but I should stay in the last page I was already (within the group X), and not go anywhere else. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/245> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-commits] [kune issues] #169: usernames and group short-names
by kune issues 19 Apr '12

19 Apr '12

#169: usernames and group short-names --------------------------+-------------------- Reporter: samer@… | Owner: vjrj Type: enhancement | Status: closed Priority: major | Milestone: Component: Group space | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+-------------------- Changes (by vjrj): * status: new => closed * resolution: => fixed -- Ticket URL: <http://kune.ourproject.org/issues/ticket/169#comment:2> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-commits] [kune issues] #36: Better logging system in the client side (was: Better logging system)
by kune issues 18 Apr '12

18 Apr '12

#36: Better logging system in the client side ---------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Common | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------+------------------ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/36#comment:1> kune issues <http://kune.ourproject.org/issues/>

1 0