Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5836898FE for ; Mon, 26 Mar 2012 12:51:31 +0000 (UTC) Received: (qmail 42336 invoked by uid 500); 26 Mar 2012 12:51:31 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 42280 invoked by uid 500); 26 Mar 2012 12:51:31 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 42269 invoked by uid 99); 26 Mar 2012 12:51:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 12:51:30 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rgaloppini@geek.net designates 74.125.149.155 as permitted sender) Received: from [74.125.149.155] (HELO na3sys009aog126.obsmtp.com) (74.125.149.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 12:51:23 +0000 Received: from mail-yw0-f41.google.com ([209.85.213.41]) (using TLSv1) by na3sys009aob126.postini.com ([74.125.148.12]) with SMTP ID DSNKT3BmNV8VZWiSwFZa6wnC8DwRoyJ1PIGv@postini.com; Mon, 26 Mar 2012 05:51:02 PDT Received: by mail-yw0-f41.google.com with SMTP id 47so4415714yhr.0 for ; Mon, 26 Mar 2012 05:51:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=Ky0TSlSZv3CPsU2hpzH0XNIOD+AOK6qRu+CsBjnMlBw=; b=WjpVfn75o3gGhRmUX6ufocZNU7+MF3crp1mvUfSPbfB9qCVKYYz/2jX3SkxQhzJGno 0SlYi6VMFsBXNRWjcf9NhFavu4ev/4J6MkaKsSiskI1BNx8dgbDdoTYxljYtY91RNc3t tpSejaP1nLA0PfjpQvox00XMaFznSS1z5RuwIt5JcexMgmX+zDZByZw7xaPgCwrUiS2n 5mVeiI0M2vXQy09qytPntVhz0eAkWdsj/lMjVJy4W0fYpt5Wb8hGhQWtGcJ6XdvfOt6j 6j8bs+38+RkydfQSbHIhBe4wenaoPK+BcizUxgGu325qg1XA65/eV8jQPF0BcjyrjbR7 I7kQ== MIME-Version: 1.0 Received: by 10.68.223.67 with SMTP id qs3mr53249140pbc.142.1332766261452; Mon, 26 Mar 2012 05:51:01 -0700 (PDT) Received: by 10.68.138.202 with HTTP; Mon, 26 Mar 2012 05:51:01 -0700 (PDT) In-Reply-To: References: <4F4B7E81.2040201@googlemail.com> <4F50006D.5050306@oracle.com> <4F5EF505.70607@googlemail.com> Date: Mon, 26 Mar 2012 14:51:01 +0200 Message-ID: Subject: Re: Apache OpenOffice Extensions Website restored at SourceForge From: Roberto Galoppini To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmA491BwjDtfAlZ0mZ6Mijg/g1TtAcL9+AaUkMs46zkEiIYIGS4opuq/xYJXNAr48SOrqHl On Tue, Mar 13, 2012 at 5:53 PM, Kay Schenk wrote: > On Tue, Mar 13, 2012 at 5:54 AM, Roberto Galoppini w= rote: > >> 2012/3/13 J=FCrgen Schmidt : >> > On 3/13/12 8:09 AM, Roberto Galoppini wrote: >> >> >> >> Here a quick update, see below. >> >> >> >>>>> >> >>>>> The plan is to transparently migrate users authenticating at >> >>>>> OpenOffice.org to the Extensions, by storing locally their >> >>>>> credentials. For the time being their email addresses will stay >> >>>>> @openoffice.org, but the idea is to migrate them all if we can get >> >>>>> their alternative emails. In fact we assume many of them won't acc= ess >> >>>>> the Extensions website before the Oracle authentication system wil= l >> >>>>> shut down. >> >>>> >> >>>> >> >>>> AFAIK Oracle will not divulge alternative email. So, I think you wi= ll >> >>>> need >> >>>> to let them recreate openoffice.org accounts and immediately >> associate >> >>>> these >> >>>> with their issues. >> >>> >> >>> >> >>> I'm working with Roberto on this - I think we have a reasonable >> solution >> >>> in >> >>> the works. >> >> >> >> >> >> We collaboratevely find a solution to the problem, and we are going t= o >> >> migrate Extensions and Templates users' accounts as soon as we'll get >> >> all the necessary information. Once done users will be able to reset >> >> their passwords through the "Lost password?" function. >> >> >> >> Keep in mind that starting from the 15th of March users will >> >> eventually loose the opportunity to login using their openoffice.org >> >> passwords, though. >> >> >> > thanks fir the update Roberto, can you tell me where we are with the >> > extension update Url and the service behind. Do you need help to >> understand >> > what the service has done? We have to check the code to figure out how >> the >> > requests look in detail ... >> >> We have already investigated how it works, and we do actually serve >> updates requests answering that there are no updates. This is just as >> it was configured before. >> >> Any information about how the update protocol works would be helpful >> for the future, though. >> >> Roberto >> > > OK, I have an odd question. Is this the same "update protocol" that is us= ed > to update the actual base package -- i.e. OOo -- the same "update" > capability that is currently missing from, say, the existing Linux 32-bit > build? > > Roberto-- where can we get more info on what is actually being "served" i= n > response to update request? That is, the URL for it. The two URLs are slightly different. AOO Updates: http://www.openoffice.org/ProductUpdateService/check.Update Extensions Updates: http://extensions.services.openoffice.org/ExtensionUpdateService/check.Upda= te And we do manage the second one. > *IF* the same "update protocol" is used for everything, base package and > extensions, here is what I (we) know. Apparently, there was some > proprietary tool in place from what I gather in which entries were > (manually?) entered for "products". That tool created atom feeds at a > specified URL which the "products/extensions" would then reference for > updates. I expect the two protocols to be nearly the same, but I do know very little about how do they work, and we do know only how to return the no updates available feedback at the moment. Roberto > In building, both Regina and Ariel were able to successfully test an > "update" by creating an atom feed with a single entry for their respectiv= e > platforms (windows, linux-64 with debian packaging), and I think actually > perform the update. > > There is information on the "format" of the feed on the wiki: > > http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol > > but NOTHING about how the feed gets constructed. > > I have been wanting to experiment with adding more than one entry to the > existing sample feed I ported =A0(usign Ariel's test) to: > > http://www.openoffice.org/ProductUpdateService/check.Update > > If someone knows enough to add more "entries" to this feed complying to > "atom" rules, that would be great. I don't know anything about how > "matches" occur in this context. > > >> > In the extension manager dialog the user can ask for updates of instal= led >> > extensions ... But I am sure you are aware of this ;-) >> > >> > Juergen >> =3D=3D=3D=3D >> This e- mail message is intended only for the named recipient(s) above. = It >> may contain confidential and privileged information. If you are not the >> intended recipient you are hereby notified that any dissemination, >> distribution or copying of this e-mail and any attachment(s) is strictly >> prohibited. If you have received this e-mail in error, please immediatel= y >> notify the sender by replying to this e-mail and delete the message and = any >> attachment(s) from your system. Thank you. >> >> > > > -- > -------------------------------------------------------------------------= --------------- > MzK > > "Follow your bliss." > =A0 =A0 =A0 =A0 -- attributed to Joseph Campbell =3D=3D=3D=3D This e- mail message is intended only for the named recipient(s) above. I= t may contain confidential and privileged information. If you are not the= intended recipient you are hereby notified that any dissemination, distr= ibution or copying of this e-mail and any attachment(s) is strictly prohi= bited. If you have received this e-mail in error, please immediately noti= fy the sender by replying to this e-mail and delete the message and any a= ttachment(s) from your system. Thank you. =0D