ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brent Lintner <>
Subject Re: Ripple Docs
Date Sun, 19 Apr 2015 17:15:53 GMT
Thanks TIm!

Perhaps, akin to Cordova, since it is not pure markdown, a tool generated
and uploaded site would be ideal. Perhaps, even as part of: (in the SVN repo)?

>> I believe Blackberry has committers on this project so that shouldn't be
a problem.

I don't believe we have any active, voted in committers, if that matters,
unless you mean ones in the past. :-)

On Fri, 17 Apr 2015 at 03:15 Ross Gardler (MS OPEN TECH) <> wrote:

> This would be great. Note that any significant contribution would have to
> be made under an iCLA. I believe Blackberry has committers on this project
> so that shouldn't be a problem.
> In terms of where to put it I recommend putting it in the existing repo to
> start with and then deciding where you want it to live. For example, do you
> want to use the ASF CMS to manage this content? Do you want a tool
> generated and uploaded site (which is what Cordova do), something else?
> Ross
> -----Original Message-----
> From: Parashuram N (MS OPEN TECH) []
> Sent: Thursday, April 16, 2015 3:29 PM
> To:
> Subject: RE: Ripple Docs
> That would be great - I think that would be a good starting point. Should
> we create a new repo for the docs like Cordova does, and start using that ?
> From: Tim Windsor []
> Sent: Thursday, April 16, 2015 1:55 PM
> To:
> Subject: Ripple Docs
> BlackBerry can provide our existing documentation on Ripple if you'd like
> to use it as a starting point. Just let me know and how you'd like to
> receive the source.
> An example of what we have is here:
> Thanks
> Tim Windsor
> Open Source Technical Lead - Devices
> [BlackBerry]
> ---------------------------------------------------------------------
> 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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message