interledger / interledger.github.io Goto Github PK

getting 404 on some doc links
from: https://interledger.org/overview.html
under "TECHNICAL DOCUMENTATION"
https://interledgerjs.github.io/js-ilp-connector/apidoc/
https://interledgerjs.github.io/five-bells-wallet/apidoc/

If you click either Docs in the header or Back to Overview in the sidebar from https://interledgerjs.github.io/five-bells-ledger/apidoc/ you end up at https://interledgerjs.github.io/overview.html which is a GH Pages 404

From @mDuo13

I tried making a small change to the website in terms of styling to improve readability, but I noticed none of my CSS changes were showing up in the local jekyll staging. Culprit is that all the resources are basically remote pointing to Interledger.org. Any ideas why it's configured this way? Is there some base URL being applied somewhere that's messing with all the links?

When visiting https://interledger.org/rfcs/0001-interledger-architecture/ the nav bar on the left runs off the page and doesn't scroll so it's not possible to get to the lower content.

Firefox on OSX

Let's add a banner on the front page to advertise the workshop in July.

I can't seem to get the process right for adding the call links to the website after each community call. They currently render without the icons.

What's the best way to do this?

Right now it's impossible to tell what document you're reading unless you scroll to the top:

On mobile, the menu is placed above the content:

So again it's hard to tell what page you're on.

Both could be fixed by adding the page title to the top of the nav.

We should showcase projects being done with Interledger:

• BigChainDB crypto-conditions implementation
• ILP WebTorrent
• GateHub/Bitstamp integration
• Hackathon output

On https://interledger.org/five-bells-ledger/apidoc/ the back to overview link doesn't work

Certain RFCs are still contained in the dactyl-config.yml (see here). If an RFC is no longer defined in the main rfcs repo (for example, it has been moved to the deprecated folder) then we should remove it from the dactyl config.

To determine this, we probably need to perform an audit of all RFC specs defined in the dactyl config file. Additionally, we should compare this against what's actually on interledger.org in the side-bar.

I can't assign this to @LoisRP, but this relates to #132.

@mDuo13 @ryangyoung

Hi all! In an effort to make sure we're fully getting the word out to OpenJS Foundation project communities about the collaborator summit, I'm posting the following message on main or admin repos:

This year, the Node Collaborator summit is opening up to include and welcome all former JS Foundation projects. The Collaborator summit is a space where projects and working groups within projects have the dedicated time and space to get together and get work done. We will have project-specific meetings, cross-project meetings on issues like security and standards, and of course meetings to discuss new programs and patterns for the new CPC.

The event will be in Berlin on May 30-31st at the Courtyard Marriott City Center. It is free to register with the password 'collabsummit.' We are also inviting all projects/attendees to suggest meetings and sessions via our CFP - these are not conference talks, but rather collaborative conversations or meetings you would like to hold with your peers. We ask that you register in advance so that we can allocate meeting room space and resources, and so that we can publish where conversations are scheduled in the day or two leading up to the event.

Links:

• Session Proposals
• Registration (password is collabsummit)
• Information on how to apply for the Travel Fund
• Summit Planning Repo

Table items on the field column are really squashed on Pull Payments

When I ran dactyl_build -S as described in the README, I found other files with differences besides the edited ones.
Like this (3f510c2).

I'm not sure if the command has been updated or if the template has changed, but I think something needs to be done about it.

Version of the command executed

$ python -V
Python 3.8.1

$ dactyl_build -v
Dactyl version 0.12.0

https://interledger.org/five-bells-condition/spec.html should redirect to https://tools.ietf.org/html/draft-thomas-crypto-conditions-01

For quotes and payments, we want people to either write their own test scripts and client software using the ilp module, or use Dennis's new CLI tools, or directly speak CLP on the wire.

We no longer want people to write software that talks to the ilp-kit api. So should we just remove the link to https://interledgerjs.github.io/ilp-kit/apidoc/? There's currently a link from https://interledger.org/overview.html (left Technical Documentation -> ilp-kit).

A number of participants have expressed a desire to build teams with ILP experience and work on ILP related projects. We can add a page to the website (updated via PR) that allows any community member to post job listings that include work on ILP.

Q: Should it be mandatory that any jobs listed included contributing back to the project as a deliverable?

Not sure if this is the proper repo, but the blue.ilpdemo.org demo gives 404s on certain calls (peers and quotes), is this demo deprecated or broken?

https://blue.ilpdemo.org/api/payments/quote 404 (Not Found)

(chrome xhr inspection)

n.b. this only occurs while trying to send to a red wallet demo account (msg: "No quote for the specified recipient or amount"), sending back to the admin's blue wallet works as expected

It seems that a template may not have been updated for the Spec pages on interledger.github.io.

For example, the Simple Payment Setup Protocol (SPSP) Page:

• Outdated links in side nav, such as https://interledger.org/sending-value-programmatically.html, resulting in 404 Not Found errors
• 'Get Started' link in top right is outdated (https://interledger.org/getting-started.html), resulting in 404 Not Found error
• Slightly different formatting for "On This Page"

For comparison, here's the Overview Page:

Perhaps it's because https://github.com/interledger/rfcs/blob/master/tmpl/rfc.ejs.html hasn't been updated? The content/format on the Spec pages seem to match what's in this file.

@kincaidoneil I had an error with the first docker command in the tutorial. I wonder if there is a permissions issue for me.

REM-ZN4L2L-M:ko-test lpatterson$ docker pull interledgerrs/ilp-cli
Using default tag: latest
Error response from daemon: dial unix docker.raw.sock: connect: connection refused

In contract, I have no problem with the second command.

REM-ZN4L2L-M:ko-test lpatterson$ docker pull interledgerrs/ilp-settlement-ethereum
Using default tag: latest
latest: Pulling from interledgerrs/ilp-settlement-ethereum
c9b1b535fdd9: Pull complete
e5798d4291ca: Pull complete
54e8f7f818a4: Pull complete
6c5e7c352108: Pull complete
Digest: sha256:c1b341d438743204a1a3fbfc835c8d3d77c9974dad50051ea348528293f3d3bf
Status: Downloaded newer image for interledgerrs/ilp-settlement-ethereum:latest
docker.io/interledgerrs/ilp-settlement-ethereum:latest

Now that Amundsen and Interfaucet are live, we can point people to them from the main website.

The normal way to find out about the testnet would probably be by studying the tutorials, but I think it would be weird not to also mention the testnet separately.

As Interledger's whitepaper is very out of date compared to the current spec, it may confuse or mislead people looking to learn more about Interledger. I think we should consider some of these options:

• Removing the link altogether from the "About" page, or explaining that it's outdated and only linked for historical purposes
• Excluding the paper with a robots.txt so it can't be directly found by Googling "Interledger paper"
• Updating the whitepaper with a note that it's outdated, or... (dare I say) updating the whitepaper with the ILPv4 architecture?

https://interledger.org/five-bells-condition/jsdoc/

The table of contents has various links to later in the document, which it assumes will work like on GitHub. They don't.

Compare with the original, where (most of) the links work:
https://github.com/interledger/five-bells-condition#table-of-contents

The page on interledger.org doesn't have IDs for the headers. That's probably the fault of whatever parser is generating the HTML from Markdown. (Some parsers have an option to generate IDs. Some parsers just... don't generate IDs.)

Context

As part of the new OpenJS Foundation's bylaws, the Cross Project Council (CPC) has been chartered to serve as the primary governing body for programs and regular support of Foundation projects. For example, it will be responsible for things like infrastructure, travel assistance, CoC support, accepting new projects into the foundation, and mentorship programs to name a few. It will also be responsible for electing board representative(s) to the OpenJS Foundation board of directors.

Any interested person from our project communities can attend CPC meetings and volunteer to participate in tasks. For most programs, the CPC is expected to operate on the consensus of OpenJS Foundation project members. Issues that require a vote - namely the election of Board representatives and accepting a new project - will be memorialized by a voting CPC membership comprised of up to 2 representatives from Impact level projects and 2 representatives from Growth and At-Large stages.

If you'd like more info/context on the governance of the OpenJS Foundation, please let me know or follow this repo. The main point I hope you take away is that the foundation is to be run by and for the projects, and to do that we need participants from the project community.

Request

As an At Large stage project, Interledger is encouraged to send representatives to participate in CPC meetings, to advise on programs and support that will be helpful to it, and to nominate someone from the project community to serve in a voting capacity.

We anticipate having our first 'official' CPC meeting on May 30 or 31 at the Collaborator Summit in Berlin (sidebar, you should come!). In the interim, we would love for project members to participate in the Bootstrap CPC meetings which are currently held on Mondays (watch this repo for meeting details).

If this is not the correct forum to raise this, please let me know and I will close the issue and post it in the preferred channel. Note that I'm posting essentially the same message to all OpenJS Foundation project repos, because I want to get the word out and make sure we all have the same information.

your pal,
Jory

Multiple people have come to the website and said they didn't realize it was open source. We should add the Github logo next to the link text to draw a little more attention to that.

The code samples on the home page use import so they won't work in nodejs. I also can't see how they would work in the browser. When you click 'Try it out', you get pointed to ilp-kit, and we know from the questions people ask in gitter, that the ilp-kit API is what most developers focus on.

As we start merging the tutorials, we should probably remove the code samples from the interledger.org homepage, and point to the Letter Shop tutorial instead?

In the footer, "interledger team" has no link.

in https://interledger.org/rfcs/0001-interledger-architecture/#application-layer-2, the "interledger team" is mixed with the side menu text. This is caused by the footer having no restrictions to invade the content's area. It happens in other pages if you scroll down.

The tutorials are out of date and should either be updated or removed to avoid confusing newcomers