[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Mar 15 23:04:30 CET 2013
Hi, >> - No CLI, knowing of filenames or such things must be necessary > > CLI offers this, you are not forced to use CLI to arrive at this. Which CLI offers this? Remember: we are not talking about specific implementations of a system like git, we are defining requirements :-) > If you know you want to compare ripe-XXX and ripe-YYY, you have the > file names. How could you compare two files without knowing their file > names? For example with links on the webpage of ripe-XXX. The web page of ripe-554 contains a link 'Updates: ripe-501'. Adding a link 'Compare to ripe-501' would be very useful. >> - A way must be provided for users to clone the RIPE document repository and perform the same analysis as the RIPE NCC offers on their own system > > That is one of the pivotal points of my proposal. Please note the > anonymous pull I explicitly mention in the proposal. When I say "CLI", > I mean "CLI on your own computer on a fully offline clone of all > data". I understand, but we need to specify that without specifying the tool to do it with. That's how you build requirements ;-) Cheers, Sander
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]