ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: [DISCUSS] Publish Hosted Ripple on NPM
Date Fri, 15 Mar 2013 17:14:18 GMT
OMG! CLI commands!!!11one

On 3/15/13 10:02 AM, "Mark Dineen" <mddineen@gmail.com> wrote:

>Easy guys, it's just a couple cli commands :)
>
>I'll keep the list posted as things progress.
>Sent from my BlackBerry
>+1 226 924 5232
>
>-----Original Message-----
>From: Filip Maj <fil@adobe.com>
>Date: Fri, 15 Mar 2013 08:56:28
>To: dev@ripple.incubator.apache.org<dev@ripple.incubator.apache.org>
>Reply-To: dev@ripple.incubator.apache.org
>Subject: Re: [DISCUSS] Publish Hosted Ripple on NPM
>
>Woot! Thanks Mark!
>
>On 3/15/13 8:19 AM, "Dan Silivestru" <dan.silivestru@gmail.com> wrote:
>
>>Thanks Mark!
>>
>>
>>On Fri, Mar 15, 2013 at 11:11 AM, Gord Tanner <gtanner@gmail.com> wrote:
>>
>>> thanks!
>>>
>>>
>>> On Fri, Mar 15, 2013 at 11:05 AM, Mark Dineen <mddineen@gmail.com>
>>>wrote:
>>>
>>> > Hi everyone,
>>> >
>>> > I'd be happy to make the unofficial push to NPM. I'll make the
>>>release
>>> > this aft.
>>> >
>>> > Thanks,
>>> >
>>> > Mark.
>>> > Sent from my BlackBerry
>>> > +1 226 924 5232
>>> >
>>> > -----Original Message-----
>>> > From: Dan Silivestru <dan.silivestru@gmail.com>
>>> > Date: Fri, 15 Mar 2013 11:00:46
>>> > To: Ripple Dev List [ASF]<dev@ripple.incubator.apache.org>
>>> > Reply-To: dev@ripple.incubator.apache.org
>>> > Subject: Re: [DISCUSS] Publish Hosted Ripple on NPM
>>> >
>>> > Hi Jukka,
>>> >
>>> > Thanks for the feedback. I don't think we would want to do this as a
>>> > BlackBerry (RIM) release since we already have two tested
>>>distributions
>>> > [1][2]. We can do it as an individual release, however, being
>>>BlackBerry
>>> > employees we would need to do some internal work to be able to make
>>>it
>>> > happen and it would definitely take more then a few days.
>>> >
>>> > If members of our community (and Cordova's community) really need
>>>this
>>> > published sooner rather then later, especially so that this can be
>>>easily
>>> > integrated with the Cordova CLI, I would like to ask on here if there
>>>are
>>> > any volunteers that could publish this to NPM as an individual
>>>release.
>>> You
>>> > would need to make sure, as Jukka said, that it is marked as a
>>>non-apache
>>> > endorsed release. I would also ask that you add myself, Gord Tanner,
>>> Brent
>>> > Lintner, and Fillip Maj as contributors.
>>> >
>>> > In the mean time, I think this should go through the proper Apache
>>> channels
>>> > and I will start work on getting everything lined up for an Apache
>>> release.
>>> >
>>> > Thoughts? Comments?
>>> >
>>> > Thanks,
>>> >
>>> > Dan.
>>> >
>>> > [1] https://developer.blackberry.com/html5/download/
>>> > [2]
>>> >
>>> >
>>> 
>>>https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhpha
>>>b
>>>nejjhdalkjhgipohgpdnoc
>>> >
>>> >
>>> > On Tue, Mar 12, 2013 at 4:31 PM, Jukka Zitting
>>><jukka.zitting@gmail.com
>>> > >wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > On Tue, Mar 12, 2013 at 2:45 PM, Gord Tanner <gtanner@gmail.com>
>>> wrote:
>>> > > > I decided to name the package ripple-emulator and have the
>>>command
>>> > still
>>> > > be
>>> > > > ripple
>>> > >
>>> > > An alternative to consider would be to name the package
>>>apache-ripple.
>>> > >
>>> > > > If no one has any problems with this being published I will get
>>>it
>>> into
>>> > > NPM
>>> > > > by the end of the week.
>>> > >
>>> > > There's a somewhat heavy process at Apache about when and how code
>>> > > should get released to outside the development team, and ideally
>>>we'd
>>> > > make sure that anything we push to NPM has gone through that
>>>process
>>> > > as it helps guarantee code and IP quality and provides legal
>>>shelter
>>> > > to the release manager and others involved in making the release.
>>> > >
>>> > > That said, as seen by Cordova, getting through that process the
>>>first
>>> > > time can be quite time-consuming (though I'd expect Ripple with
>>>fewer
>>> > > complex dependencies to have an easier time with an Apache
>>>release),
>>> > > so if you want to do this within a few days, it's best if the
>>>release
>>> > > is clearly marked as a non-Apache one, made by you as an individual
>>>or
>>> > > perhaps RIM as a company.
>>> > >
>>> > > In either case it would be good if we started looking at getting
>>>our
>>> > > first Apache release ready and shipping in near future. See [1] for
>>> > > information on what an Apache release is and what doing one
>>>requires,
>>> > > and [2] for some extra Incubator requirements. There's also an
>>> > > Incubator release guide at [3], but that document is unfortunately
>>> > > rather unwieldy.
>>> > >
>>> > > [1] http://www.apache.org/dev/index.html#releases
>>> > > [2]
>>> > 
>>>http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>>> > > [3] http://incubator.apache.org/guides/releasemanagement.html
>>> > >
>>> > > BR,
>>> > >
>>> > > Jukka Zitting
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Dan Silivestru
>>> > +1 (519) 589-3624
>>> >
>>> >
>>>
>>
>>
>>
>>-- 
>>Dan Silivestru
>>+1 (519) 589-3624
>


Mime
View raw message