Gesendet von meinem BlackBerry 10-Smartphone. � Originalnachricht � Von: Christian Grobmeier Gesendet: Donnerstag, 26. Juni 2014 19:31 An: [email protected] Antwort an: [email protected] Betreff: Re: Pushing Changes to NPM
> Christian Grobmeier <[email protected]> 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 > > <[email protected]> > > 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 > >> <[email protected]> > >> 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 > >>> <[email protected]> > >>> 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 < > >>> [email protected]> > >>>> 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 < > >>> [email protected]> > >>>>> 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 : [email protected] > >>>>> Blog : www.raymondcamden.com > >>>>> Twitter: raymondcamden > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Brent Lintner > >>>> > >>> > >>> > >>> > >>> -- > >>> > >>> =========================================================================== > >>> Raymond Camden, Web Developer for Adobe > >>> > >>> Email : [email protected] > >>> Blog : www.raymondcamden.com > >>> Twitter: raymondcamden > >>> > >> > >> > >> > >> -- > >> Brent Lintner > >> > > > > > > > > -- > > Brent Lintner > > > --- > http://www.grobmeier.de > The Zen Programmer: http://bit.ly/12lC6DL > @grobmeier > GPG: 0xA5CC90DB >
