Any updates on this? Just curious :-) On Tue, Jun 18, 2013 at 1:40 AM, Ken Wallis <[email protected]> wrote: > We are working on it. ;) Sorry for no response. > > Big thing is planning an update to remove our dependence on the Heroku > instance. > -- > > Ken Wallis > > Product Manager – WebWorks > > BlackBerry > > 289-261-4369 > > ________________________________________ > From: Brent Lintner [[email protected]] > Sent: Monday, June 17, 2013 4:04 PM > To: [email protected] > Subject: Re: Crome store access for unofficial releases > > Any updates on this from BlackBerry? (bump) :-) > > Thanks! > > > On Fri, May 31, 2013 at 11:04 AM, Dan Silivestru > <[email protected]>wrote: > >> Hi Christian, >> >> Agreed, it would be great if BB would donate the account to the ASF. I >> think we can definitely work through all of the things you've mentioned >> if/once that happens. >> >> Cheers, >> >> Dan. >> >> >> On Fri, May 31, 2013 at 7:59 AM, Christian Grobmeier <[email protected] >> >wrote: >> >> > Hi >> > >> > On Thu, May 30, 2013 at 5:31 PM, Dan Silivestru >> > <[email protected]> wrote: >> > > Hi Chris and Ken, >> > > >> > > We would like to request access to publish ripple to the Chrome Store >> as >> > an >> > > unofficial channel for the work being done in Apache. I'm wondering if >> > > BlackBerry would be willing to donate that account to Apache since it >> is >> > > actually branded as The Ripple Emulator and does not have any >> BlackBerry >> > > branding on it, nor does BlackBerry link to it from anywhere. >> > > >> > > I really do feel like this would be in the best interest of the >> community >> > > as well as the 75k users currently using the Chrome extension in the >> > Google >> > > Store. :-) >> > > >> > > Christian, is there a way for us to propose that this kind of a release >> > > become official? Assuming BlackBerry will agree to donate the account? >> > I'm >> > > not sure if a chrome extension will be treated any differently then our >> > NPM >> > > package is. >> > >> > Assuming BB will donate it, the PMC can surely use it to publish >> releases. >> > But please note, the main official channel for our releases must be a >> > source release >> > on our own dist servers. There are a couple of requirements which we >> > might need to match. >> > >> > While the PMC members all should have access to that channel, it is >> > necessary to say >> > that this is not the official distribution channel, but managed from >> > PMC members. We need >> > to make sure people know that there is one canonical source for Ripple. >> > >> > That said, the Chrome Store channel would need to be conform to >> > trademarking requirements. This should be straightforward, when the >> > channel is on hold of the PMC. It is not so easy when BlackBerry keeps >> > it. To my knowledge the Ripple mark has been donated, and thus the use >> > must be agreed with [email protected]. It is most likely that due >> > to the similarity this will not be accepted. >> > >> > tldr: it would safe a lot of problems if BB would donate th chrome >> > webstore channel to the ASF. >> > In addition, the Apache Ripple PMC would need to find a way to >> > securely share the password and to make sure, people understand there >> > is an official canonical source for the releases and the Web store is >> > an personal effort from the PMC. >> > >> > By the way, we make something similar in log4php land. We published >> > log4php as so called composer package. This is going aside to our >> > normal releases. Don't know if the publisher release is more popular >> > than the download release, but i would not be surprised. From my >> > experience is most enough to have up to date releases and say its >> > maintained by the PMC to give a channel credibility, official or not. >> > >> > Cheers >> > Christian >> > >> > > >> > > Thanks in advance, >> > > >> > > -- >> > > Dan Silivestru >> > > +1 (519) 589-3624 >> > >> > >> > >> > -- >> > http://www.grobmeier.de >> > https://www.timeandbill.de >> > >> >> >> >> -- >> Dan Silivestru >> +1 (519) 589-3624 >> > > > > -- > Brent Lintner > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful.
-- http://www.grobmeier.de https://www.timeandbill.de
