You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by Brent Lintner <br...@gmail.com> on 2014/06/26 15:45:04 UTC
Pushing Changes to NPM
Hey All,
I'm going to push some minor changes to NPM based on some lingering PRs on
GitHub.
If anyone does not agree, please post here.
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
Feel free to modify or just cut and paste. ;)
Updates (June 26, 2014)
Today we pushed three updates for Ripple. The first change is to default
the proxy to the local server instead of the old, possibly defunct, remote
proxy managed by Blackberry. Now when you perform cross domain XHR
requests, they will be proxied locally. (Details:
https://github.com/apache/incubator-ripple/pull/25)
The second fixes an issue with the cordova command not be available
globally. This would cause Ripple to fail silently. (Details:
https://github.com/apache/incubator-ripple/pull/24)
The final fix corrects an issue with detecting JSON responses. Ripple will
now properly handle them. (Details:
https://github.com/apache/incubator-ripple/pull/23)
On Thu, Jun 26, 2014 at 9:37 AM, Brent Lintner <br...@gmail.com>
wrote:
> Pushed: https://www.npmjs.org/package/ripple-emulator
>
>
> On Thu, Jun 26, 2014 at 10:33 AM, Brent Lintner <br...@gmail.com>
> wrote:
>
> > I definitely don't disagree with that! :-)
> >
> > Maybe we can remove the CHANGELOG file once we have that, to keep things
> > succinct and not duplicated.
> >
> >
> > On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden <
> raymondcamden@gmail.com>
> > wrote:
> >
> >> Yes - the home page should have (imo), a paragraph or two of nice text.
> >> Below that, a list of changelists.
> >>
> >> So basically, a nice review of what changed in plain speak followed by
> the
> >> list of changes with further details.
> >>
> >> As an end user, I want the first part so I can quickly see if I care and
> >> the second part if I want to look deeper.
> >>
> >>
> >>
> >> On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <brent.lintner@gmail.com
> >
> >> wrote:
> >>
> >> > Hey Raymond,
> >> >
> >> > Sure thing! (Definitely need you to get access though- that vote
> thread
> >> was
> >> > an almost ghost town :-()
> >> >
> >> > Once you have a commit, I can push that to SVN!
> >> >
> >> > Here are the PRs in doc/CHANGELOG.md (that I am about to push):
> >> >
> >> > ## v0.9.23 - Jun 26, 2014
> >> >
> >> > * RIPPLE-63 Ripple should default to local proxy, not remote
> >> > https://github.com/apache/incubator-ripple/pull/25
> >> >
> >> > * Fix RIPPLE-61: search for locally installed cordova module before
> >> > expecting to find it globally installed
> >> > https://github.com/apache/incubator-ripple/pull/24
> >> >
> >> > * Fix RIPPLE-60 - proxy not detecting json properly
> >> > https://github.com/apache/incubator-ripple/pull/23
> >> >
> >> >
> >> > In hindsight: perhaps we should move that CHANGELOG (in general) to
> the
> >> > site, or?
> >> >
> >> >
> >> >
> >> > On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
> >> raymondcamden@gmail.com>
> >> > wrote:
> >> >
> >> > > Would it be possible, when you are done, to make a list of PRs? We
> >> should
> >> > > document what has been fixed, specifically somewhere on the
> homepage.
> >> I
> >> > > don't think I have access to that, but I'd gladly do the writing if
> >> you
> >> > > could get it in.
> >> > >
> >> > >
> >> > > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
> >> brent.lintner@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > Hey All,
> >> > > >
> >> > > > I'm going to push some minor changes to NPM based on some
> lingering
> >> PRs
> >> > > on
> >> > > > GitHub.
> >> > > >
> >> > > > If anyone does not agree, please post here.
> >> > > >
> >> > > > --
> >> > > > Brent Lintner
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > >
> >> >
> >>
> ===========================================================================
> >> > > Raymond Camden, Web Developer for Adobe
> >> > >
> >> > > Email : raymondcamden@gmail.com
> >> > > Blog : www.raymondcamden.com
> >> > > Twitter: raymondcamden
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Brent Lintner
> >> >
> >>
> >>
> >>
> >> --
> >>
> >>
> ===========================================================================
> >> Raymond Camden, Web Developer for Adobe
> >>
> >> Email : raymondcamden@gmail.com
> >> Blog : www.raymondcamden.com
> >> Twitter: raymondcamden
> >>
> >
> >
> >
> > --
> > Brent Lintner
> >
>
>
>
> --
> Brent Lintner
>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
PS:
Oops. Disregard my GitHub comment. I realized GitHub was mentioned in
another thread talking about what to do with Ripple (catching up).
On Wed, Jul 2, 2014 at 5:17 PM, Brent Lintner <br...@gmail.com>
wrote:
> Hey Christian,
>
> >>>>
> Please note, this push can't be considered a release in the Apache way. I
> am aware this is how lots of open source projects work to day, but it's not
> how the ASF does releases. In fact, the ASF has quite a bunch of
> requirements to release. These requirements need to be met because they
> protect us before legal issues, and also our users.
> >>>>
>
> Indeed! I do apologize. Like before, I am more so pushing it voluntarily
> (outside ASF) to get it out there and used- which seems OK (given your
> reply about NPM). I hope I don't come off as ignoring anything that you
> have mentioned!!! :-)
>
> For me though: This is how I (personally) prefer to work in open source
> (without restriction), so such ASF requirements (compared to merging PRs
> and getting code out) are on the lowest of my list (if at all)- but that is
> *certainly* not an excuse. :-s
>
> Not sure what others think of being fully on GitHub- I was not quite sure
> if that was an option, vs going into Cordova. Not sure who would own the
> code, etc?
>
> In the meantime, I will try my best to get into those ASF requirements
> (images, for one), while we figure out what to do with the project in
> general.
>
> Cheers,
>
>
> On Fri, Jun 27, 2014 at 10:33 AM, Raymond Camden <ra...@gmail.com>
> wrote:
>
>> I suppose so. Thanks.
>>
>>
>> On Thu, Jun 26, 2014 at 4:11 PM, Christian Grobmeier <grobmeier@gmail.com
>> >
>> wrote:
>>
>> > On 26 Jun 2014, at 20:19, Raymond Camden wrote:
>> >
>> > So to be clear, an Apache project can't use npm? Or it can't *only* use
>> >> npm?
>> >>
>> >
>> > Not quite. An Apache project releases artifacts which can be downloaded
>> > from Apache hardware. These artifacts are signed and voted upon.
>> > That aside, if there are volunteers wanting to maintain something like
>> npm
>> > its perfectly fine. projects can also say they maintain it: but I would
>> > give guarantees on services which are controlled by the ASF.
>> >
>> > In other words: "these npm artifacts are uploaded by members of the
>> ripple
>> > projects, but if you need to make sure about them, go to the canonical
>> > project and download from apache.org/dist which is the official channel
>> > to get it."
>> >
>> > See how we did it on Log4php:
>> > http://logging.apache.org/log4php/download.html
>> > (packagist the npm for php people)
>> >
>> > We provide the source packages as requested and added an alternate
>> > distribution channel. Whoever needs to check the sigs, can still use our
>> > own package.
>> >
>> > Makes sense?
>> >
>> > Cheers
>> >
>> >
>> >
>> >
>> >>
>> >> On Thu, Jun 26, 2014 at 12:29 PM, Christian Grobmeier <
>> >> grobmeier@gmail.com>
>> >> wrote:
>> >>
>> >> Hey guys,
>> >>>
>> >>> glad you have found some time working on Ripple.
>> >>>
>> >>> Please note, this push can't be considered a release in the Apache
>> way. I
>> >>> am aware this is how lots of open source projects work to day, but
>> it's
>> >>> not
>> >>> how the ASF does releases. In fact, the ASF has quite a bunch of
>> >>> requirements to release. These requirements need to be met because
>> they
>> >>> protect us before legal issues, and also our users.
>> >>>
>> >>> Here is a document about that:
>> >>> http://apache.org/dev/release.html#what-must-every-release-contain
>> >>>
>> >>> A few important requirements:
>> >>>
>> >>> a release must be available in source format and from apache.org as a
>> >>> download as well.
>> >>> It must get 3 +1 votes from PMC members, in the incubator it must also
>> >>> get
>> >>> 3 +1 votes
>> >>> from Incubator members.
>> >>>
>> >>> A release must have LICENSE file, NOTICE file etc and must contain
>> only
>> >>> AL
>> >>> 2.0 files
>> >>> or files compatible to the license (in example BSD, but not GPL).
>> >>>
>> >>> Also the release artifact must be signed cryptograhpically.
>> >>>
>> >>> This is what currently doesn't seem to work with npm. It doesn't
>> support
>> >>> key signing.
>> >>>
>> >>> That being said, npmjs can't be considered an official source of
>> Ripple,
>> >>> as we can't
>> >>> tell people they actually get what we promise (no signing).
>> >>> Also we miss the +1 of the project team which in fact means that
>> >>> releasing
>> >>> this
>> >>> would make the release manager responsible personally for the
>> artifact.
>> >>> Knowing
>> >>> that there are images in the package of which do not own the rights,
>> this
>> >>> is a problem.
>> >>>
>> >>> I absolutely do know that the ASF requirements are tough, but I think
>> >>> they
>> >>> are worth it.
>> >>> If the team thinks they are not of use, then we need to move out to
>> >>> GitHub.
>> >>> If the team thinks they are good - in example some enterprise
>> customers
>> >>> are having tough
>> >>> requirements of what they can use and what not too - then we need to
>> work
>> >>> towards a first,
>> >>> official release.
>> >>>
>> >>>
>> >>>
>> >>>>>>>
>> >> --
>> >> ============================================================
>> >> ===============
>> >> Raymond Camden, Web Developer for Adobe
>> >>
>> >> Email : raymondcamden@gmail.com
>> >> Blog : www.raymondcamden.com
>> >> Twitter: raymondcamden
>> >>
>> >
>> >
>> > ---
>> > http://www.grobmeier.de
>> > The Zen Programmer: http://bit.ly/12lC6DL
>> > @grobmeier
>> > GPG: 0xA5CC90DB
>> >
>>
>>
>>
>> --
>>
>> ===========================================================================
>> Raymond Camden, Web Developer for Adobe
>>
>> Email : raymondcamden@gmail.com
>> Blog : www.raymondcamden.com
>> Twitter: raymondcamden
>>
>
>
>
> --
> Brent Lintner
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
Hey Christian,
>>>>
Please note, this push can't be considered a release in the Apache way. I
am aware this is how lots of open source projects work to day, but it's not
how the ASF does releases. In fact, the ASF has quite a bunch of
requirements to release. These requirements need to be met because they
protect us before legal issues, and also our users.
>>>>
Indeed! I do apologize. Like before, I am more so pushing it voluntarily
(outside ASF) to get it out there and used- which seems OK (given your
reply about NPM). I hope I don't come off as ignoring anything that you
have mentioned!!! :-)
For me though: This is how I (personally) prefer to work in open source
(without restriction), so such ASF requirements (compared to merging PRs
and getting code out) are on the lowest of my list (if at all)- but that is
*certainly* not an excuse. :-s
Not sure what others think of being fully on GitHub- I was not quite sure
if that was an option, vs going into Cordova. Not sure who would own the
code, etc?
In the meantime, I will try my best to get into those ASF requirements
(images, for one), while we figure out what to do with the project in
general.
Cheers,
On Fri, Jun 27, 2014 at 10:33 AM, Raymond Camden <ra...@gmail.com>
wrote:
> I suppose so. Thanks.
>
>
> On Thu, Jun 26, 2014 at 4:11 PM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>
> > On 26 Jun 2014, at 20:19, Raymond Camden wrote:
> >
> > So to be clear, an Apache project can't use npm? Or it can't *only* use
> >> npm?
> >>
> >
> > Not quite. An Apache project releases artifacts which can be downloaded
> > from Apache hardware. These artifacts are signed and voted upon.
> > That aside, if there are volunteers wanting to maintain something like
> npm
> > its perfectly fine. projects can also say they maintain it: but I would
> > give guarantees on services which are controlled by the ASF.
> >
> > In other words: "these npm artifacts are uploaded by members of the
> ripple
> > projects, but if you need to make sure about them, go to the canonical
> > project and download from apache.org/dist which is the official channel
> > to get it."
> >
> > See how we did it on Log4php:
> > http://logging.apache.org/log4php/download.html
> > (packagist the npm for php people)
> >
> > We provide the source packages as requested and added an alternate
> > distribution channel. Whoever needs to check the sigs, can still use our
> > own package.
> >
> > Makes sense?
> >
> > Cheers
> >
> >
> >
> >
> >>
> >> On Thu, Jun 26, 2014 at 12:29 PM, Christian Grobmeier <
> >> grobmeier@gmail.com>
> >> wrote:
> >>
> >> Hey guys,
> >>>
> >>> glad you have found some time working on Ripple.
> >>>
> >>> Please note, this push can't be considered a release in the Apache
> way. I
> >>> am aware this is how lots of open source projects work to day, but it's
> >>> not
> >>> how the ASF does releases. In fact, the ASF has quite a bunch of
> >>> requirements to release. These requirements need to be met because they
> >>> protect us before legal issues, and also our users.
> >>>
> >>> Here is a document about that:
> >>> http://apache.org/dev/release.html#what-must-every-release-contain
> >>>
> >>> A few important requirements:
> >>>
> >>> a release must be available in source format and from apache.org as a
> >>> download as well.
> >>> It must get 3 +1 votes from PMC members, in the incubator it must also
> >>> get
> >>> 3 +1 votes
> >>> from Incubator members.
> >>>
> >>> A release must have LICENSE file, NOTICE file etc and must contain only
> >>> AL
> >>> 2.0 files
> >>> or files compatible to the license (in example BSD, but not GPL).
> >>>
> >>> Also the release artifact must be signed cryptograhpically.
> >>>
> >>> This is what currently doesn't seem to work with npm. It doesn't
> support
> >>> key signing.
> >>>
> >>> That being said, npmjs can't be considered an official source of
> Ripple,
> >>> as we can't
> >>> tell people they actually get what we promise (no signing).
> >>> Also we miss the +1 of the project team which in fact means that
> >>> releasing
> >>> this
> >>> would make the release manager responsible personally for the artifact.
> >>> Knowing
> >>> that there are images in the package of which do not own the rights,
> this
> >>> is a problem.
> >>>
> >>> I absolutely do know that the ASF requirements are tough, but I think
> >>> they
> >>> are worth it.
> >>> If the team thinks they are not of use, then we need to move out to
> >>> GitHub.
> >>> If the team thinks they are good - in example some enterprise customers
> >>> are having tough
> >>> requirements of what they can use and what not too - then we need to
> work
> >>> towards a first,
> >>> official release.
> >>>
> >>>
> >>>
> >>>>>>>
> >> --
> >> ============================================================
> >> ===============
> >> Raymond Camden, Web Developer for Adobe
> >>
> >> Email : raymondcamden@gmail.com
> >> Blog : www.raymondcamden.com
> >> Twitter: raymondcamden
> >>
> >
> >
> > ---
> > http://www.grobmeier.de
> > The Zen Programmer: http://bit.ly/12lC6DL
> > @grobmeier
> > GPG: 0xA5CC90DB
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Web Developer for Adobe
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
I suppose so. Thanks.
On Thu, Jun 26, 2014 at 4:11 PM, Christian Grobmeier <gr...@gmail.com>
wrote:
> On 26 Jun 2014, at 20:19, Raymond Camden wrote:
>
> So to be clear, an Apache project can't use npm? Or it can't *only* use
>> npm?
>>
>
> Not quite. An Apache project releases artifacts which can be downloaded
> from Apache hardware. These artifacts are signed and voted upon.
> That aside, if there are volunteers wanting to maintain something like npm
> its perfectly fine. projects can also say they maintain it: but I would
> give guarantees on services which are controlled by the ASF.
>
> In other words: "these npm artifacts are uploaded by members of the ripple
> projects, but if you need to make sure about them, go to the canonical
> project and download from apache.org/dist which is the official channel
> to get it."
>
> See how we did it on Log4php:
> http://logging.apache.org/log4php/download.html
> (packagist the npm for php people)
>
> We provide the source packages as requested and added an alternate
> distribution channel. Whoever needs to check the sigs, can still use our
> own package.
>
> Makes sense?
>
> Cheers
>
>
>
>
>>
>> On Thu, Jun 26, 2014 at 12:29 PM, Christian Grobmeier <
>> grobmeier@gmail.com>
>> wrote:
>>
>> Hey guys,
>>>
>>> glad you have found some time working on Ripple.
>>>
>>> Please note, this push can't be considered a release in the Apache way. I
>>> am aware this is how lots of open source projects work to day, but it's
>>> not
>>> how the ASF does releases. In fact, the ASF has quite a bunch of
>>> requirements to release. These requirements need to be met because they
>>> protect us before legal issues, and also our users.
>>>
>>> Here is a document about that:
>>> http://apache.org/dev/release.html#what-must-every-release-contain
>>>
>>> A few important requirements:
>>>
>>> a release must be available in source format and from apache.org as a
>>> download as well.
>>> It must get 3 +1 votes from PMC members, in the incubator it must also
>>> get
>>> 3 +1 votes
>>> from Incubator members.
>>>
>>> A release must have LICENSE file, NOTICE file etc and must contain only
>>> AL
>>> 2.0 files
>>> or files compatible to the license (in example BSD, but not GPL).
>>>
>>> Also the release artifact must be signed cryptograhpically.
>>>
>>> This is what currently doesn't seem to work with npm. It doesn't support
>>> key signing.
>>>
>>> That being said, npmjs can't be considered an official source of Ripple,
>>> as we can't
>>> tell people they actually get what we promise (no signing).
>>> Also we miss the +1 of the project team which in fact means that
>>> releasing
>>> this
>>> would make the release manager responsible personally for the artifact.
>>> Knowing
>>> that there are images in the package of which do not own the rights, this
>>> is a problem.
>>>
>>> I absolutely do know that the ASF requirements are tough, but I think
>>> they
>>> are worth it.
>>> If the team thinks they are not of use, then we need to move out to
>>> GitHub.
>>> If the team thinks they are good - in example some enterprise customers
>>> are having tough
>>> requirements of what they can use and what not too - then we need to work
>>> towards a first,
>>> official release.
>>>
>>>
>>>
>>>>>>>
>> --
>> ============================================================
>> ===============
>> Raymond Camden, Web Developer for Adobe
>>
>> Email : raymondcamden@gmail.com
>> Blog : www.raymondcamden.com
>> Twitter: raymondcamden
>>
>
>
> ---
> http://www.grobmeier.de
> The Zen Programmer: http://bit.ly/12lC6DL
> @grobmeier
> GPG: 0xA5CC90DB
>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Re: Pushing Changes to NPM
Posted by Christian Grobmeier <gr...@gmail.com>.
On 26 Jun 2014, at 20:19, Raymond Camden wrote:
> So to be clear, an Apache project can't use npm? Or it can't *only*
> use npm?
Not quite. An Apache project releases artifacts which can be downloaded
from Apache hardware. These artifacts are signed and voted upon.
That aside, if there are volunteers wanting to maintain something like
npm its perfectly fine. projects can also say they maintain it: but I
would give guarantees on services which are controlled by the ASF.
In other words: "these npm artifacts are uploaded by members of the
ripple projects, but if you need to make sure about them, go to the
canonical project and download from apache.org/dist which is the
official channel to get it."
See how we did it on Log4php:
http://logging.apache.org/log4php/download.html
(packagist the npm for php people)
We provide the source packages as requested and added an alternate
distribution channel. Whoever needs to check the sigs, can still use our
own package.
Makes sense?
Cheers
>
>
> On Thu, Jun 26, 2014 at 12:29 PM, Christian Grobmeier
> <gr...@gmail.com>
> wrote:
>
>> Hey guys,
>>
>> glad you have found some time working on Ripple.
>>
>> Please note, this push can't be considered a release in the Apache
>> way. I
>> am aware this is how lots of open source projects work to day, but
>> it's not
>> how the ASF does releases. In fact, the ASF has quite a bunch of
>> requirements to release. These requirements need to be met because
>> they
>> protect us before legal issues, and also our users.
>>
>> Here is a document about that:
>> http://apache.org/dev/release.html#what-must-every-release-contain
>>
>> A few important requirements:
>>
>> a release must be available in source format and from apache.org as a
>> download as well.
>> It must get 3 +1 votes from PMC members, in the incubator it must
>> also get
>> 3 +1 votes
>> from Incubator members.
>>
>> A release must have LICENSE file, NOTICE file etc and must contain
>> only AL
>> 2.0 files
>> or files compatible to the license (in example BSD, but not GPL).
>>
>> Also the release artifact must be signed cryptograhpically.
>>
>> This is what currently doesn't seem to work with npm. It doesn't
>> support
>> key signing.
>>
>> That being said, npmjs can't be considered an official source of
>> Ripple,
>> as we can't
>> tell people they actually get what we promise (no signing).
>> Also we miss the +1 of the project team which in fact means that
>> releasing
>> this
>> would make the release manager responsible personally for the
>> artifact.
>> Knowing
>> that there are images in the package of which do not own the rights,
>> this
>> is a problem.
>>
>> I absolutely do know that the ASF requirements are tough, but I think
>> they
>> are worth it.
>> If the team thinks they are not of use, then we need to move out to
>> GitHub.
>> If the team thinks they are good - in example some enterprise
>> customers
>> are having tough
>> requirements of what they can use and what not too - then we need to
>> work
>> towards a first,
>> official release.
>>
>>
>>>>>>
>
> --
> ===========================================================================
> Raymond Camden, Web Developer for Adobe
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
So to be clear, an Apache project can't use npm? Or it can't *only* use npm?
On Thu, Jun 26, 2014 at 12:29 PM, Christian Grobmeier <gr...@gmail.com>
wrote:
> Hey guys,
>
> glad you have found some time working on Ripple.
>
> Please note, this push can't be considered a release in the Apache way. I
> am aware this is how lots of open source projects work to day, but it's not
> how the ASF does releases. In fact, the ASF has quite a bunch of
> requirements to release. These requirements need to be met because they
> protect us before legal issues, and also our users.
>
> Here is a document about that:
> http://apache.org/dev/release.html#what-must-every-release-contain
>
> A few important requirements:
>
> a release must be available in source format and from apache.org as a
> download as well.
> It must get 3 +1 votes from PMC members, in the incubator it must also get
> 3 +1 votes
> from Incubator members.
>
> A release must have LICENSE file, NOTICE file etc and must contain only AL
> 2.0 files
> or files compatible to the license (in example BSD, but not GPL).
>
> Also the release artifact must be signed cryptograhpically.
>
> This is what currently doesn't seem to work with npm. It doesn't support
> key signing.
>
> That being said, npmjs can't be considered an official source of Ripple,
> as we can't
> tell people they actually get what we promise (no signing).
> Also we miss the +1 of the project team which in fact means that releasing
> this
> would make the release manager responsible personally for the artifact.
> Knowing
> that there are images in the package of which do not own the rights, this
> is a problem.
>
> I absolutely do know that the ASF requirements are tough, but I think they
> are worth it.
> If the team thinks they are not of use, then we need to move out to GitHub.
> If the team thinks they are good - in example some enterprise customers
> are having tough
> requirements of what they can use and what not too - then we need to work
> towards a first,
> official release.
>
>
>>>>>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
AW: Pushing Changes to NPM
Posted by Felix Weber <fe...@lixam.de>.
Gesendet von meinem BlackBerry 10-Smartphone.
� Originalnachricht �
Von: Christian Grobmeier
Gesendet: Donnerstag, 26. Juni 2014 19:31
An: dev@ripple.incubator.apache.org
Antwort an: dev@ripple.incubator.apache.org
Betreff: Re: Pushing Changes to NPM
> Christian Grobmeier <gr...@gmail.com> hat am 26. Juni 2014 um 19:29 geschrieben:
>
>
> Hey guys,
>
> glad you have found some time working on Ripple.
>
> Please note, this push can't be considered a release in the Apache way.
> I am aware this is how lots of open source projects work to day, but
> it's not how the ASF does releases. In fact, the ASF has quite a bunch
> of requirements to release. These requirements need to be met because
> they protect us before legal issues, and also our users.
>
> Here is a document about that:
> http://apache.org/dev/release.html#what-must-every-release-contain
>
> A few important requirements:
>
> a release must be available in source format and from apache.org as a
> download as well.
> It must get 3 +1 votes from PMC members, in the incubator it must also
> get 3 +1 votes
> from Incubator members.
>
> A release must have LICENSE file, NOTICE file etc and must contain only
> AL 2.0 files
> or files compatible to the license (in example BSD, but not GPL).
>
> Also the release artifact must be signed cryptograhpically.
>
> This is what currently doesn't seem to work with npm. It doesn't support
> key signing.
>
> That being said, npmjs can't be considered an official source of Ripple,
> as we can't
> tell people they actually get what we promise (no signing).
> Also we miss the +1 of the project team which in fact means that
> releasing this
> would make the release manager responsible personally for the artifact.
> Knowing
> that there are images in the package of which do not own the rights,
> this is a problem.
>
> I absolutely do know that the ASF requirements are tough, but I think
> they are worth it.
> If the team thinks they are not of use, then we need to move out to
> GitHub.
> If the team thinks they are good - in example some enterprise customers
> are having tough
> requirements of what they can use and what not too - then we need to
> work towards a first,
> official release.
>
> I am willing to assist you folks here, thats why I am mentoring.
>
> I just want to make sure that you understand that there is a difference
> between releasing here vs github and that we cannot push things that
> easily without making proper ASF releases first.
>
> Please let me hear your thoughts,
>
> Regards
> Christian
>
>
> On 26 Jun 2014, at 16:37, Brent Lintner wrote:
>
> > Pushed: https://www.npmjs.org/package/ripple-emulator
> >
> >
> > On Thu, Jun 26, 2014 at 10:33 AM, Brent Lintner
> > <br...@gmail.com>
> > wrote:
> >
> >> I definitely don't disagree with that! :-)
> >>
> >> Maybe we can remove the CHANGELOG file once we have that, to keep
> >> things
> >> succinct and not duplicated.
> >>
> >>
> >> On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden
> >> <ra...@gmail.com>
> >> wrote:
> >>
> >>> Yes - the home page should have (imo), a paragraph or two of nice
> >>> text.
> >>> Below that, a list of changelists.
> >>>
> >>> So basically, a nice review of what changed in plain speak followed
> >>> by the
> >>> list of changes with further details.
> >>>
> >>> As an end user, I want the first part so I can quickly see if I care
> >>> and
> >>> the second part if I want to look deeper.
> >>>
> >>>
> >>>
> >>> On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner
> >>> <br...@gmail.com>
> >>> wrote:
> >>>
> >>>> Hey Raymond,
> >>>>
> >>>> Sure thing! (Definitely need you to get access though- that vote
> >>>> thread
> >>> was
> >>>> an almost ghost town :-()
> >>>>
> >>>> Once you have a commit, I can push that to SVN!
> >>>>
> >>>> Here are the PRs in doc/CHANGELOG.md (that I am about to push):
> >>>>
> >>>> ## v0.9.23 - Jun 26, 2014
> >>>>
> >>>> * RIPPLE-63 Ripple should default to local proxy, not remote
> >>>> https://github.com/apache/incubator-ripple/pull/25
> >>>>
> >>>> * Fix RIPPLE-61: search for locally installed cordova module before
> >>>> expecting to find it globally installed
> >>>> https://github.com/apache/incubator-ripple/pull/24
> >>>>
> >>>> * Fix RIPPLE-60 - proxy not detecting json properly
> >>>> https://github.com/apache/incubator-ripple/pull/23
> >>>>
> >>>>
> >>>> In hindsight: perhaps we should move that CHANGELOG (in general) to
> >>>> the
> >>>> site, or?
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
> >>> raymondcamden@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Would it be possible, when you are done, to make a list of PRs? We
> >>> should
> >>>>> document what has been fixed, specifically somewhere on the
> >>>>> homepage.
> >>> I
> >>>>> don't think I have access to that, but I'd gladly do the writing
> >>>>> if
> >>> you
> >>>>> could get it in.
> >>>>>
> >>>>>
> >>>>> On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
> >>> brent.lintner@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Hey All,
> >>>>>>
> >>>>>> I'm going to push some minor changes to NPM based on some
> >>>>>> lingering
> >>> PRs
> >>>>> on
> >>>>>> GitHub.
> >>>>>>
> >>>>>> If anyone does not agree, please post here.
> >>>>>>
> >>>>>> --
> >>>>>> Brent Lintner
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>
> >>> ===========================================================================
> >>>>> Raymond Camden, Web Developer for Adobe
> >>>>>
> >>>>> Email : raymondcamden@gmail.com
> >>>>> Blog : www.raymondcamden.com
> >>>>> Twitter: raymondcamden
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Brent Lintner
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> ===========================================================================
> >>> Raymond Camden, Web Developer for Adobe
> >>>
> >>> Email : raymondcamden@gmail.com
> >>> Blog : www.raymondcamden.com
> >>> Twitter: raymondcamden
> >>>
> >>
> >>
> >>
> >> --
> >> Brent Lintner
> >>
> >
> >
> >
> > --
> > Brent Lintner
>
>
> ---
> http://www.grobmeier.de
> The Zen Programmer: http://bit.ly/12lC6DL
> @grobmeier
> GPG: 0xA5CC90DB
>
Re: Pushing Changes to NPM
Posted by Christian Grobmeier <gr...@gmail.com>.
Hey guys,
glad you have found some time working on Ripple.
Please note, this push can't be considered a release in the Apache way.
I am aware this is how lots of open source projects work to day, but
it's not how the ASF does releases. In fact, the ASF has quite a bunch
of requirements to release. These requirements need to be met because
they protect us before legal issues, and also our users.
Here is a document about that:
http://apache.org/dev/release.html#what-must-every-release-contain
A few important requirements:
a release must be available in source format and from apache.org as a
download as well.
It must get 3 +1 votes from PMC members, in the incubator it must also
get 3 +1 votes
from Incubator members.
A release must have LICENSE file, NOTICE file etc and must contain only
AL 2.0 files
or files compatible to the license (in example BSD, but not GPL).
Also the release artifact must be signed cryptograhpically.
This is what currently doesn't seem to work with npm. It doesn't support
key signing.
That being said, npmjs can't be considered an official source of Ripple,
as we can't
tell people they actually get what we promise (no signing).
Also we miss the +1 of the project team which in fact means that
releasing this
would make the release manager responsible personally for the artifact.
Knowing
that there are images in the package of which do not own the rights,
this is a problem.
I absolutely do know that the ASF requirements are tough, but I think
they are worth it.
If the team thinks they are not of use, then we need to move out to
GitHub.
If the team thinks they are good - in example some enterprise customers
are having tough
requirements of what they can use and what not too - then we need to
work towards a first,
official release.
I am willing to assist you folks here, thats why I am mentoring.
I just want to make sure that you understand that there is a difference
between releasing here vs github and that we cannot push things that
easily without making proper ASF releases first.
Please let me hear your thoughts,
Regards
Christian
On 26 Jun 2014, at 16:37, Brent Lintner wrote:
> Pushed: https://www.npmjs.org/package/ripple-emulator
>
>
> On Thu, Jun 26, 2014 at 10:33 AM, Brent Lintner
> <br...@gmail.com>
> wrote:
>
>> I definitely don't disagree with that! :-)
>>
>> Maybe we can remove the CHANGELOG file once we have that, to keep
>> things
>> succinct and not duplicated.
>>
>>
>> On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden
>> <ra...@gmail.com>
>> wrote:
>>
>>> Yes - the home page should have (imo), a paragraph or two of nice
>>> text.
>>> Below that, a list of changelists.
>>>
>>> So basically, a nice review of what changed in plain speak followed
>>> by the
>>> list of changes with further details.
>>>
>>> As an end user, I want the first part so I can quickly see if I care
>>> and
>>> the second part if I want to look deeper.
>>>
>>>
>>>
>>> On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner
>>> <br...@gmail.com>
>>> wrote:
>>>
>>>> Hey Raymond,
>>>>
>>>> Sure thing! (Definitely need you to get access though- that vote
>>>> thread
>>> was
>>>> an almost ghost town :-()
>>>>
>>>> Once you have a commit, I can push that to SVN!
>>>>
>>>> Here are the PRs in doc/CHANGELOG.md (that I am about to push):
>>>>
>>>> ## v0.9.23 - Jun 26, 2014
>>>>
>>>> * RIPPLE-63 Ripple should default to local proxy, not remote
>>>> https://github.com/apache/incubator-ripple/pull/25
>>>>
>>>> * Fix RIPPLE-61: search for locally installed cordova module before
>>>> expecting to find it globally installed
>>>> https://github.com/apache/incubator-ripple/pull/24
>>>>
>>>> * Fix RIPPLE-60 - proxy not detecting json properly
>>>> https://github.com/apache/incubator-ripple/pull/23
>>>>
>>>>
>>>> In hindsight: perhaps we should move that CHANGELOG (in general) to
>>>> the
>>>> site, or?
>>>>
>>>>
>>>>
>>>> On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
>>> raymondcamden@gmail.com>
>>>> wrote:
>>>>
>>>>> Would it be possible, when you are done, to make a list of PRs? We
>>> should
>>>>> document what has been fixed, specifically somewhere on the
>>>>> homepage.
>>> I
>>>>> don't think I have access to that, but I'd gladly do the writing
>>>>> if
>>> you
>>>>> could get it in.
>>>>>
>>>>>
>>>>> On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
>>> brent.lintner@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hey All,
>>>>>>
>>>>>> I'm going to push some minor changes to NPM based on some
>>>>>> lingering
>>> PRs
>>>>> on
>>>>>> GitHub.
>>>>>>
>>>>>> If anyone does not agree, please post here.
>>>>>>
>>>>>> --
>>>>>> Brent Lintner
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>
>>> ===========================================================================
>>>>> Raymond Camden, Web Developer for Adobe
>>>>>
>>>>> Email : raymondcamden@gmail.com
>>>>> Blog : www.raymondcamden.com
>>>>> Twitter: raymondcamden
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Brent Lintner
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> ===========================================================================
>>> Raymond Camden, Web Developer for Adobe
>>>
>>> Email : raymondcamden@gmail.com
>>> Blog : www.raymondcamden.com
>>> Twitter: raymondcamden
>>>
>>
>>
>>
>> --
>> Brent Lintner
>>
>
>
>
> --
> Brent Lintner
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
Pushed: https://www.npmjs.org/package/ripple-emulator
On Thu, Jun 26, 2014 at 10:33 AM, Brent Lintner <br...@gmail.com>
wrote:
> I definitely don't disagree with that! :-)
>
> Maybe we can remove the CHANGELOG file once we have that, to keep things
> succinct and not duplicated.
>
>
> On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden <ra...@gmail.com>
> wrote:
>
>> Yes - the home page should have (imo), a paragraph or two of nice text.
>> Below that, a list of changelists.
>>
>> So basically, a nice review of what changed in plain speak followed by the
>> list of changes with further details.
>>
>> As an end user, I want the first part so I can quickly see if I care and
>> the second part if I want to look deeper.
>>
>>
>>
>> On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <br...@gmail.com>
>> wrote:
>>
>> > Hey Raymond,
>> >
>> > Sure thing! (Definitely need you to get access though- that vote thread
>> was
>> > an almost ghost town :-()
>> >
>> > Once you have a commit, I can push that to SVN!
>> >
>> > Here are the PRs in doc/CHANGELOG.md (that I am about to push):
>> >
>> > ## v0.9.23 - Jun 26, 2014
>> >
>> > * RIPPLE-63 Ripple should default to local proxy, not remote
>> > https://github.com/apache/incubator-ripple/pull/25
>> >
>> > * Fix RIPPLE-61: search for locally installed cordova module before
>> > expecting to find it globally installed
>> > https://github.com/apache/incubator-ripple/pull/24
>> >
>> > * Fix RIPPLE-60 - proxy not detecting json properly
>> > https://github.com/apache/incubator-ripple/pull/23
>> >
>> >
>> > In hindsight: perhaps we should move that CHANGELOG (in general) to the
>> > site, or?
>> >
>> >
>> >
>> > On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
>> raymondcamden@gmail.com>
>> > wrote:
>> >
>> > > Would it be possible, when you are done, to make a list of PRs? We
>> should
>> > > document what has been fixed, specifically somewhere on the homepage.
>> I
>> > > don't think I have access to that, but I'd gladly do the writing if
>> you
>> > > could get it in.
>> > >
>> > >
>> > > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
>> brent.lintner@gmail.com>
>> > > wrote:
>> > >
>> > > > Hey All,
>> > > >
>> > > > I'm going to push some minor changes to NPM based on some lingering
>> PRs
>> > > on
>> > > > GitHub.
>> > > >
>> > > > If anyone does not agree, please post here.
>> > > >
>> > > > --
>> > > > Brent Lintner
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > >
>> >
>> ===========================================================================
>> > > Raymond Camden, Web Developer for Adobe
>> > >
>> > > Email : raymondcamden@gmail.com
>> > > Blog : www.raymondcamden.com
>> > > Twitter: raymondcamden
>> > >
>> >
>> >
>> >
>> > --
>> > Brent Lintner
>> >
>>
>>
>>
>> --
>>
>> ===========================================================================
>> Raymond Camden, Web Developer for Adobe
>>
>> Email : raymondcamden@gmail.com
>> Blog : www.raymondcamden.com
>> Twitter: raymondcamden
>>
>
>
>
> --
> Brent Lintner
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
Sounds good to me. :-)
On Thu, Jun 26, 2014 at 10:38 AM, Raymond Camden <ra...@gmail.com>
wrote:
> Personally I'd do both. Nothing wrong with being a bit verbose in terms of
> what has changed.
>
>
> On Thu, Jun 26, 2014 at 9:33 AM, Brent Lintner <br...@gmail.com>
> wrote:
>
> > I definitely don't disagree with that! :-)
> >
> > Maybe we can remove the CHANGELOG file once we have that, to keep things
> > succinct and not duplicated.
> >
> >
> > On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden <
> raymondcamden@gmail.com>
> > wrote:
> >
> > > Yes - the home page should have (imo), a paragraph or two of nice text.
> > > Below that, a list of changelists.
> > >
> > > So basically, a nice review of what changed in plain speak followed by
> > the
> > > list of changes with further details.
> > >
> > > As an end user, I want the first part so I can quickly see if I care
> and
> > > the second part if I want to look deeper.
> > >
> > >
> > >
> > > On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <
> brent.lintner@gmail.com>
> > > wrote:
> > >
> > > > Hey Raymond,
> > > >
> > > > Sure thing! (Definitely need you to get access though- that vote
> thread
> > > was
> > > > an almost ghost town :-()
> > > >
> > > > Once you have a commit, I can push that to SVN!
> > > >
> > > > Here are the PRs in doc/CHANGELOG.md (that I am about to push):
> > > >
> > > > ## v0.9.23 - Jun 26, 2014
> > > >
> > > > * RIPPLE-63 Ripple should default to local proxy, not remote
> > > > https://github.com/apache/incubator-ripple/pull/25
> > > >
> > > > * Fix RIPPLE-61: search for locally installed cordova module before
> > > > expecting to find it globally installed
> > > > https://github.com/apache/incubator-ripple/pull/24
> > > >
> > > > * Fix RIPPLE-60 - proxy not detecting json properly
> > > > https://github.com/apache/incubator-ripple/pull/23
> > > >
> > > >
> > > > In hindsight: perhaps we should move that CHANGELOG (in general) to
> the
> > > > site, or?
> > > >
> > > >
> > > >
> > > > On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
> > > raymondcamden@gmail.com>
> > > > wrote:
> > > >
> > > > > Would it be possible, when you are done, to make a list of PRs? We
> > > should
> > > > > document what has been fixed, specifically somewhere on the
> > homepage. I
> > > > > don't think I have access to that, but I'd gladly do the writing if
> > you
> > > > > could get it in.
> > > > >
> > > > >
> > > > > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
> > > brent.lintner@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hey All,
> > > > > >
> > > > > > I'm going to push some minor changes to NPM based on some
> lingering
> > > PRs
> > > > > on
> > > > > > GitHub.
> > > > > >
> > > > > > If anyone does not agree, please post here.
> > > > > >
> > > > > > --
> > > > > > Brent Lintner
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > >
> > >
> >
> ===========================================================================
> > > > > Raymond Camden, Web Developer for Adobe
> > > > >
> > > > > Email : raymondcamden@gmail.com
> > > > > Blog : www.raymondcamden.com
> > > > > Twitter: raymondcamden
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Brent Lintner
> > > >
> > >
> > >
> > >
> > > --
> > >
> >
> ===========================================================================
> > > Raymond Camden, Web Developer for Adobe
> > >
> > > Email : raymondcamden@gmail.com
> > > Blog : www.raymondcamden.com
> > > Twitter: raymondcamden
> > >
> >
> >
> >
> > --
> > Brent Lintner
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Web Developer for Adobe
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
Personally I'd do both. Nothing wrong with being a bit verbose in terms of
what has changed.
On Thu, Jun 26, 2014 at 9:33 AM, Brent Lintner <br...@gmail.com>
wrote:
> I definitely don't disagree with that! :-)
>
> Maybe we can remove the CHANGELOG file once we have that, to keep things
> succinct and not duplicated.
>
>
> On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden <ra...@gmail.com>
> wrote:
>
> > Yes - the home page should have (imo), a paragraph or two of nice text.
> > Below that, a list of changelists.
> >
> > So basically, a nice review of what changed in plain speak followed by
> the
> > list of changes with further details.
> >
> > As an end user, I want the first part so I can quickly see if I care and
> > the second part if I want to look deeper.
> >
> >
> >
> > On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <br...@gmail.com>
> > wrote:
> >
> > > Hey Raymond,
> > >
> > > Sure thing! (Definitely need you to get access though- that vote thread
> > was
> > > an almost ghost town :-()
> > >
> > > Once you have a commit, I can push that to SVN!
> > >
> > > Here are the PRs in doc/CHANGELOG.md (that I am about to push):
> > >
> > > ## v0.9.23 - Jun 26, 2014
> > >
> > > * RIPPLE-63 Ripple should default to local proxy, not remote
> > > https://github.com/apache/incubator-ripple/pull/25
> > >
> > > * Fix RIPPLE-61: search for locally installed cordova module before
> > > expecting to find it globally installed
> > > https://github.com/apache/incubator-ripple/pull/24
> > >
> > > * Fix RIPPLE-60 - proxy not detecting json properly
> > > https://github.com/apache/incubator-ripple/pull/23
> > >
> > >
> > > In hindsight: perhaps we should move that CHANGELOG (in general) to the
> > > site, or?
> > >
> > >
> > >
> > > On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
> > raymondcamden@gmail.com>
> > > wrote:
> > >
> > > > Would it be possible, when you are done, to make a list of PRs? We
> > should
> > > > document what has been fixed, specifically somewhere on the
> homepage. I
> > > > don't think I have access to that, but I'd gladly do the writing if
> you
> > > > could get it in.
> > > >
> > > >
> > > > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
> > brent.lintner@gmail.com>
> > > > wrote:
> > > >
> > > > > Hey All,
> > > > >
> > > > > I'm going to push some minor changes to NPM based on some lingering
> > PRs
> > > > on
> > > > > GitHub.
> > > > >
> > > > > If anyone does not agree, please post here.
> > > > >
> > > > > --
> > > > > Brent Lintner
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > >
> >
> ===========================================================================
> > > > Raymond Camden, Web Developer for Adobe
> > > >
> > > > Email : raymondcamden@gmail.com
> > > > Blog : www.raymondcamden.com
> > > > Twitter: raymondcamden
> > > >
> > >
> > >
> > >
> > > --
> > > Brent Lintner
> > >
> >
> >
> >
> > --
> >
> ===========================================================================
> > Raymond Camden, Web Developer for Adobe
> >
> > Email : raymondcamden@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: raymondcamden
> >
>
>
>
> --
> Brent Lintner
>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
I definitely don't disagree with that! :-)
Maybe we can remove the CHANGELOG file once we have that, to keep things
succinct and not duplicated.
On Thu, Jun 26, 2014 at 10:30 AM, Raymond Camden <ra...@gmail.com>
wrote:
> Yes - the home page should have (imo), a paragraph or two of nice text.
> Below that, a list of changelists.
>
> So basically, a nice review of what changed in plain speak followed by the
> list of changes with further details.
>
> As an end user, I want the first part so I can quickly see if I care and
> the second part if I want to look deeper.
>
>
>
> On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <br...@gmail.com>
> wrote:
>
> > Hey Raymond,
> >
> > Sure thing! (Definitely need you to get access though- that vote thread
> was
> > an almost ghost town :-()
> >
> > Once you have a commit, I can push that to SVN!
> >
> > Here are the PRs in doc/CHANGELOG.md (that I am about to push):
> >
> > ## v0.9.23 - Jun 26, 2014
> >
> > * RIPPLE-63 Ripple should default to local proxy, not remote
> > https://github.com/apache/incubator-ripple/pull/25
> >
> > * Fix RIPPLE-61: search for locally installed cordova module before
> > expecting to find it globally installed
> > https://github.com/apache/incubator-ripple/pull/24
> >
> > * Fix RIPPLE-60 - proxy not detecting json properly
> > https://github.com/apache/incubator-ripple/pull/23
> >
> >
> > In hindsight: perhaps we should move that CHANGELOG (in general) to the
> > site, or?
> >
> >
> >
> > On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <
> raymondcamden@gmail.com>
> > wrote:
> >
> > > Would it be possible, when you are done, to make a list of PRs? We
> should
> > > document what has been fixed, specifically somewhere on the homepage. I
> > > don't think I have access to that, but I'd gladly do the writing if you
> > > could get it in.
> > >
> > >
> > > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <
> brent.lintner@gmail.com>
> > > wrote:
> > >
> > > > Hey All,
> > > >
> > > > I'm going to push some minor changes to NPM based on some lingering
> PRs
> > > on
> > > > GitHub.
> > > >
> > > > If anyone does not agree, please post here.
> > > >
> > > > --
> > > > Brent Lintner
> > > >
> > >
> > >
> > >
> > > --
> > >
> >
> ===========================================================================
> > > Raymond Camden, Web Developer for Adobe
> > >
> > > Email : raymondcamden@gmail.com
> > > Blog : www.raymondcamden.com
> > > Twitter: raymondcamden
> > >
> >
> >
> >
> > --
> > Brent Lintner
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Web Developer for Adobe
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
Yes - the home page should have (imo), a paragraph or two of nice text.
Below that, a list of changelists.
So basically, a nice review of what changed in plain speak followed by the
list of changes with further details.
As an end user, I want the first part so I can quickly see if I care and
the second part if I want to look deeper.
On Thu, Jun 26, 2014 at 9:23 AM, Brent Lintner <br...@gmail.com>
wrote:
> Hey Raymond,
>
> Sure thing! (Definitely need you to get access though- that vote thread was
> an almost ghost town :-()
>
> Once you have a commit, I can push that to SVN!
>
> Here are the PRs in doc/CHANGELOG.md (that I am about to push):
>
> ## v0.9.23 - Jun 26, 2014
>
> * RIPPLE-63 Ripple should default to local proxy, not remote
> https://github.com/apache/incubator-ripple/pull/25
>
> * Fix RIPPLE-61: search for locally installed cordova module before
> expecting to find it globally installed
> https://github.com/apache/incubator-ripple/pull/24
>
> * Fix RIPPLE-60 - proxy not detecting json properly
> https://github.com/apache/incubator-ripple/pull/23
>
>
> In hindsight: perhaps we should move that CHANGELOG (in general) to the
> site, or?
>
>
>
> On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <ra...@gmail.com>
> wrote:
>
> > Would it be possible, when you are done, to make a list of PRs? We should
> > document what has been fixed, specifically somewhere on the homepage. I
> > don't think I have access to that, but I'd gladly do the writing if you
> > could get it in.
> >
> >
> > On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <br...@gmail.com>
> > wrote:
> >
> > > Hey All,
> > >
> > > I'm going to push some minor changes to NPM based on some lingering PRs
> > on
> > > GitHub.
> > >
> > > If anyone does not agree, please post here.
> > >
> > > --
> > > Brent Lintner
> > >
> >
> >
> >
> > --
> >
> ===========================================================================
> > Raymond Camden, Web Developer for Adobe
> >
> > Email : raymondcamden@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: raymondcamden
> >
>
>
>
> --
> Brent Lintner
>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Re: Pushing Changes to NPM
Posted by Brent Lintner <br...@gmail.com>.
Hey Raymond,
Sure thing! (Definitely need you to get access though- that vote thread was
an almost ghost town :-()
Once you have a commit, I can push that to SVN!
Here are the PRs in doc/CHANGELOG.md (that I am about to push):
## v0.9.23 - Jun 26, 2014
* RIPPLE-63 Ripple should default to local proxy, not remote
https://github.com/apache/incubator-ripple/pull/25
* Fix RIPPLE-61: search for locally installed cordova module before
expecting to find it globally installed
https://github.com/apache/incubator-ripple/pull/24
* Fix RIPPLE-60 - proxy not detecting json properly
https://github.com/apache/incubator-ripple/pull/23
In hindsight: perhaps we should move that CHANGELOG (in general) to the
site, or?
On Thu, Jun 26, 2014 at 10:00 AM, Raymond Camden <ra...@gmail.com>
wrote:
> Would it be possible, when you are done, to make a list of PRs? We should
> document what has been fixed, specifically somewhere on the homepage. I
> don't think I have access to that, but I'd gladly do the writing if you
> could get it in.
>
>
> On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <br...@gmail.com>
> wrote:
>
> > Hey All,
> >
> > I'm going to push some minor changes to NPM based on some lingering PRs
> on
> > GitHub.
> >
> > If anyone does not agree, please post here.
> >
> > --
> > Brent Lintner
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Web Developer for Adobe
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
--
Brent Lintner
Re: Pushing Changes to NPM
Posted by Raymond Camden <ra...@gmail.com>.
Would it be possible, when you are done, to make a list of PRs? We should
document what has been fixed, specifically somewhere on the homepage. I
don't think I have access to that, but I'd gladly do the writing if you
could get it in.
On Thu, Jun 26, 2014 at 8:45 AM, Brent Lintner <br...@gmail.com>
wrote:
> Hey All,
>
> I'm going to push some minor changes to NPM based on some lingering PRs on
> GitHub.
>
> If anyone does not agree, please post here.
>
> --
> Brent Lintner
>
--
===========================================================================
Raymond Camden, Web Developer for Adobe
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden