- kune-devel - lists.ourproject.org

Fwd: WiaB client code usage in the wild (a.k.a Undercurrent in Blogger)
by Vicente J. Ruiz Jurado 17 Jan '12

17 Jan '12

For thouse interested: "Blogger using WiAB client code" :) -------- Mensaje original -------- Asunto: WiaB client code usage in the wild (a.k.a Undercurrent in Blogger) Fecha: Tue, 17 Jan 2012 17:18:26 +1100 De: Patrick Coleman <patcoleman(a)google.com> Responder a: wave-dev(a)incubator.apache.org Para: wave-dev(a)incubator.apache.org Fellow wave-dev'ers; For those who missed the recent announcement, my current project (Blogger) just launched threaded commenting: http://buzz.blogger.com/2012/01/engage-with-your-readers-through.html The reason I'm emailing here though is that all the comment rendering code uses the Undercurrent wave-panel GWT library. (e.g. check out the DOM produced in the comments section of that post, it may look familiar). I'm aware that this alternate usage may add some constraints moving forwards with the codebase, so I was wondering if there was a generally recommended way of sharing code like this - e.g. are there any large changes planned to Undercurrent that mean I should fork my own copy first? Alternatively, if there are changes I hope to make, are they likely to help being submitted into the apache codebase? If it helps, the main two changes I'd hope to work on for our usage are: 1) Removing the dependency from Blip to Document - Comments are just static html, so I have a custom CommentDocument for this, but due to the interfaces it needs to pull in ContentDocument, MutableDocument and DocInitialization which bloats the library size 2) Adding an alternative to UserAgentStaticProperties that is actually dynamic - i.e. removes the requirement to have a different script per user agent. fwiw, thanks to all of those active in this community that've kept this code open and nicely usable for such a different feature such as this. - Pat Coleman -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog (@vjrj) "Cuanto más grande es el caos, más próxima está la solución." [Mao Tse-Tung]

1 0

Re: [kune-devel] [kune issues] #99: Add a recovery password functionality
by kune issues 17 Jan '12

17 Jan '12

#99: Add a recovery password functionality --------------------------+-------------------- 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 Comment: In some hours we'll update the demo, kune.cc and Eurosur... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/99#comment:2> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #180: Remove "confirmation email" message after creating new user
by kune issues 16 Jan '12

16 Jan '12

#180: Remove "confirmation email" message after creating new user -----------------------+------------------- Reporter: samer@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Usability | Version: Keywords: | Blocked By: Blocking: | -----------------------+------------------- When creating a new user, a message appears saying that an email confirmation will be sent. This causes confusion: * A colleague from uni stayed waiting for such email before continuing trying Kune. As she never received it, she never continued. * Stanislav said "I just registered but didn't receive any email confirmation" I would remove the sentence mentioning the email confirmation, and reinsert it when it actually does it. Kune is complicated and confusing enough for newbies, no need to add messages saying things it won't do. Another possibility is to give very high priority to the email interaction and actually send an email confirmation (or at least a welcome email notification, without confirmation). That would give people the feeling they are trying something that works (as they are used to such welcome emails). -- Ticket URL: <http://kune.ourproject.org/issues/ticket/180> kune issues <http://kune.ourproject.org/issues/>

1 1

recuperar usuario/password
by dani 14 Jan '12

14 Jan '12

Hola gentes, gracias Samer por mandar la transcripción de la reunión del 12 de enero. Me siento muy identificado con algunas de las cosas que se dicen. Me gustaría seguir colaborando y empiezo por una sugerencia: que haya una manera de recuperar usuario/password. :-) Besotes. -- _)_/\_|\|_|_ vjrj: so ... the goal is to empower no tech people samer: the ideal thing would be to facilitate the use of Kune by non-geeks millaguie: so... we need betatesters who don't know what a betatester is petrizzo: must have some clues to solve this, I think it is more difficult to convince of the need to use a tool to someone who does not believe he needed someone who does not know how to use it. samer: Kune focuses on 1) collaboration (building things together, not just communicating), 2) work / activism liquidquartz: I repeat my point of to make a podcast, videoblog, in order to attract people without the habit of reading. The Flyer is great, a goood voice will make it perfect in a audio or video release -- _)_/\_|\|_|_

2 1

Wave gadgets => G+ gadgets =>? Kune gadgets?
by Samer 14 Jan '12

14 Jan '12

Hey there, I don't know if you were aware, but Google decided last year to provide a space for wave gadgets to run (so they continue being usable after google wave closure): http://googlewave.blogspot.com/2010/12/announcing-google-shared-spaces.html and now they have merged that into Google+ (specifically, into G+ Hangouts): https://developers.google.com/+/hangouts/ That meants that developers can already use their wave gadgets in Google+... It's not as powerful as wave as it is all centralized, but still it is something to take into account. At least, if they are going to use the same API, those gadgets built for G+ might also work in wave and therefore in Kune*. *: For those unaware, Kune includes Apache Wave, the free/libre software version of Google Wave. -- Samer http://comunes.org "No son tiempos para hacer cualquier cosa"

1 0

[kune issues] #186: Doc not showing properly for non-members
by kune issues 14 Jan '12

14 Jan '12

#186: Doc not showing properly for non-members -------------------------+------------------- Reporter: samer@… | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Group space | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- * Group X has a document, and spreads the URL of the document. E.g. http://kune.cc/#comunes.docs.427.341 * If an anonymous user connects, the user sees: two avatars on top of each other; text without fonts/sizes (all uniform and big size font). * If a logged in user connects, but he/she is not member of the group X, the same result happens. * Only if a logged in user and member of the group opens the link, he/she can see properly the document. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/186> kune issues <http://kune.ourproject.org/issues/>

1 0

General meeting Comunes / Kune / Move Commons / Ourproject
by Samer 13 Jan '12

13 Jan '12

Hey there! Happy new year to everybody :) As usual, it's time for a general meeting of Comunes (including its projects Kune and Move Commons). Following up last time, we call for both an online chat meeting and a face-to-face meeting in Madrid (for those living close by). Thus: - Online meeting: this Thursday, 12th of January, at 18:00 (Madrid timing). We'll be connected in a chat-room of Kune ( http://kune.cc/#comunes.chats.390 ) and do the meeting from there. You need to register a user in Kune.cc if you don't have one. If you need help, just contact me (we can chat by gmail and I'll aid you). - Face to face meeting: the same Thursday 12th January, at 20:00, in Vinícola Mentridana, C/San Eugenio, nº 9, Metro Antón Martín: http://g.co/maps/fwymj These are open meetings, so everyone is invited. It would be nice if many of you can make it :) If you have any question, just reply to this email. Cheers! PS: The face-to-face meetings of the next months (beginning in February) will take place in Medialab-Prado. -- Samer http://comunes.org "No son tiempos para hacer cualquier cosa"

1 1

[kune issues] #185: Implement notification levels (hourly and daily) similar to Google Wave
by kune issues 12 Jan '12

12 Jan '12

#185: Implement notification levels (hourly and daily) similar to Google Wave --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: minor | Milestone: Component: Server side | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Currently there is only one level of email notifications (to receive or not), but we want to implement the rest: public enum EmailNotificationFrequency implements IsSerializable { daily, // at most daily, (not used yet) hourly, // at most hourly (not used yet) immediately, // almost immediately (currently used) no // I don't need email notifications (currently used) } The cron part is partially implemented, see CronServerTasksManager and package cc.kune.core.server.scheduler But we need a db table to store the notifications, so the cron task use it. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/185> kune issues <http://kune.ourproject.org/issues/>

1 1

Re: [kune-devel] [kune issues] #99: Add a recovery password functionality
by kune issues 10 Jan '12

10 Jan '12

#99: Add a recovery password functionality --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Common | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by anonymous): Please add this feature!!!! -- Ticket URL: <http://kune.ourproject.org/issues/ticket/99#comment:1> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #164: NotificationManager in server side
by kune issues 01 Jan '12

01 Jan '12

#164: NotificationManager in server side --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Server side | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Should notify us via email/waves when something relevant happens. Phase I Notify when pending/approved members via Wave Phase II Notify when pending/approved members via email Phase III Notify when new waves via email Phase IV Configurable the level of notifications desired via client -- Ticket URL: <http://kune.ourproject.org/issues/ticket/164> kune issues <http://kune.ourproject.org/issues/>

1 1