RIPE Labs is a new platform designed by the RIPE NCC for network operators, developers and industry experts to expose, test and discuss innovative Internet-related tools, ideas and analysis that can benefit the RIPE community and RIPE NCC members.
It’s the place to showcase new and interesting things. Anyone can:
- Present research
- Showcase prototype tools
- Share operational experience
- Exchange ideas
Even if you don't have any new ideas at the moment, but are interested in reviewing the ideas and tools of others, please dive in.
RIPE Labs is a platform from the RIPE community for the RIPE community.
Anyone can read what’s on RIPE Labs. But you’ll need to register before you can contribute to RIPE Labs. Registration is free and open to anyone.
RIPE NCC staff will use RIPE Labs to show new ideas and potential new services or new features of existing services to the community at an early stage. This will allow the RIPE NCC members and the wider community a much faster feedback mechanism. Rather than having to wait until something has been developed into a full service, the RIPE NCC can ask the community during the development phase if this is going into the right direction.
In addition to that RIPE Labs will also be open to community members to present their own ideas and prototypes, gather feedback from others and engage into discuss with each other (Hence it is called RIPE Labs and not RIPE NCC Labs). We will provide and maintain discussion forums for various topics and tools.
How does this benefit you?
- Get involved in the development of tools and ideas right from the start
- Influence what new tools will do – (RIPE NCC tools or those contributed by others)
- Follow developments quickly and first-hand
- Contribute your own ideas or tools and
- Enjoy rapid feedback from the RIPE community - your network of highly competent and like-minded colleagues
- Interact faster and more closely with the RIPE NCC through open and easy feedback methods
You can contact us at firstname.lastname@example.org or use the contact form at the top of this page.
Comments are disabled on articles published more than a year ago. If you'd like to inform us of any issues, please reach out to us via the contact form here.
<div class="content legacycomment"> <p> So far this looks good. The layout could be a bit "tighter", maybe font-wise/size-wise. A "remember me" button so one doesn't always have to remember one's password (or maybe that's the default ?). </p> <p> </p> <p> Also, if you can read this, then the comment system is working :) </p> <p> </p> <p> I'll read through the rest and come with more comments if required. </p> <p> </p> </div>
Hide 4 replies
<div class="content legacycomment"> <p> Glad you like it. I can tell you that the design involved several people with strong opinions and a number of changes. The good news is that the platform we built this on allows the use of "skins". So we may offer different layouts and presentations if people feel strongly enough about this. </p> <p> </p> <p> Remembering the user is the default behaviour until you explicitly log out using the button at the extreme right of the menu bar next to your username. We opted for convenience rather than absolute security here. </p> <p> </p> <p> We would <strong> <em> love </em> </strong> to hear more comments from you or anyone. </p> <p> </p> </div>
Hide 3 replies
<div class="content legacycomment"> <p> ...but I can see a couple of rough edges (page layout/formatting) here and there, which I'll take up with the mechanics off-line (unless we want to see them discussed here?) </p> <p> </p> <p> Just as a minor suggestion up-front, it would be nice to see the client's IP address (v4 / v6 ) echoed like on the "regular" website. </p> <p> </p> <p> Thanks for coming up with the idea and the implementation, "we" already started to think about using it for Database-related exchange of ideas. </p> </div>
Hide 2 replies
<div class="content legacycomment"> <p> Hi Wilfried, </p> <p> </p> <p> Thanks for your comments. I am happy to talk more about your suggestions here in Lisbon. </p> <p> And I am glad to hear that you find the platform useful and want to use it for RIPE DB related discussions. </p> <p> </p> <p> Mirjam </p> </div>
<div class="content legacycomment"> <p> Making the user's IP address visible isn't too difficult, so lets see a show of hands: </p> <p> </p> <p> <strong> If you'd like to see your IP address echoed back to you somewhere in the site layout, post below! :) </strong> </p> </div>
<div class="content legacycomment"> <p> I would like to suggest that in the profile settings page ( <a href="http://labs.ripe.net/user/*/edit" title="http://labs.ripe.net/user/*/edit"> http://labs.ripe.net/user/*/edit </a> ) that instead of time offsets you use location because I am not going to remember to change it when we switch between normal (CET) and daylight saving time (CEST). For example:- "Europe/Copenhagen" instead of "Tuesday, October 6, 2009 - 12:35 +0200". </p> </div>
Hide one reply
<div class="content legacycomment"> <p> Thanks for your suggestion. I discussed this with our Drupal experts: Drupal's existing solution isn't perfect, but seems to be workable for now. Currently people can localise themselves and correct for Daylight Savings if needed. If there are more requests to change this, we are happy to explore this further. </p> <p> </p> <p> Mirjam </p> </div>