Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Nathaniel McCallum
    @npmccallum
    That being said it isn't an unsolvable problem. Just one for which we don't have a solution today.
    axel simon
    @axelsimon
    @MikeCamel Good to see this ball rolling! @m-dombrowski had a quick chat where we discussed this, as well as trying to improve "ingress paths" for newcomers looking to contribute, and came out of that with several useful ideas, which i'm working on putting into action in the documentation
    (step 1: don't use language like "ingress paths", probably)
    talking of potential contributors to the project, i'm wondering if it would be useful to have a list of skills that are or have been used on the project, to illustrate that indeed, a wide array of things are needed and yes, you potential contributor have a role to play and our welcome… thoughts?
    Mike Dombrowski
    @m-dombrowski
    @npmccallum Ah, a challenge! Good stuff. I'll be the first to admit that most of Enarx is still well beyond my understanding so I appreciate you breaking it down Barney style for me. I'm curious, is the vision for Enarx practical application broad or somewhat narrow given limitations such as the before mentioned I/O issue?
    Nathaniel McCallum
    @npmccallum
    @m-dombrowski Our visions are much larger than our code base. :)
    Mike Dombrowski
    @m-dombrowski

    @axelsimon I am going to plead ignorance (day 7, I can still do that, right?). At a minimum, perhaps consider embedding the Red Hat Summit Enarx recruitment video or a snippet of it that discusses contribution opportunities. From a marketing and recruitment perspective, people respond very well to video content. The consumption rate on video content is often much higher than other forms of media. Recruitment video + written supplement is a great combo if that functionality is permitted by GitHub. The Wiki page (+video) could also pull double duty for quality social media outreach.

    The project already has a great start to video content based on what I saw at Summit. If it hasn't already been distributed via social media, it should be considered.

    axel simon
    @axelsimon
    it is being considered, but not done yet
    but clearly, you're right, we should have the Introduction to Enarx video on the README and on the main wiki page
    Mark Bestavros
    @mbestavros
    I obviously don't expect review right away, but when you all have a moment, please have a look at my proposal for sprints: https://github.com/mbestavros/rfcs/tree/sprints/concepts/00001-enarx-sprint-framework
    Mike Bursell
    @MikeCamel
    Comments submitted.
    Mike Bursell
    @MikeCamel
    I won't make the stand-up today (CCC GB meeting). Some points from me:
    1. we now have a YouTube channel, which needs populating. We already have some material. axel, Nathaniel, Ben, Shaun & Mike all admins.
    1. Any news on the threat analysis work?
    1. worth Mike D, axel and Mike B. having a discussion on use cases?
    1. Agile process RFC draft - comments from Mike B done.
    1. Thanks to Lily for reviews on the trust process. More folks, please...
    1. What should our next RFCs be from an architectural point of view? I have a few ideas queued, but suggestions welcomed.
    1. Hopeful for an update on Rocket.chat...
    matrixbot
    @matrixbot
    @kobevrancken:matrix.org was kicked by @appservice-irc:matrix.org ("Idle for 30+ days").
    Mike Bursell
    @MikeCamel
    All - I would like this week to be the week that we get a bunch of our RFCs sorted, please. If you look at this list, you'll see that we have 7 open pull requests on RFCs: https://github.com/enarx/rfcs/pulls?q=is%3Apr+is%3Aopen+sort%3Acreated-asc
    I've sorted them by date opened.
    axel simon
    @axelsimon
    @KobeVrancken @m-dombrowski @CyberEpsilon Just to let you krow / remind you there is an https://gitter.im/enarx/banter room should you be interested in low-traffic, quality banter :)
    1. worth Mike D, axel and Mike B. having a discussion on use cases?
    I would say in a week or so, to give Mike D more time to digest, most probably yes!
    Nathaniel McCallum
    @npmccallum
    @ebeasant-arm I just was alerted to Arm DevSummit. Any interest in doing a joint talk with Enarx?
    Edwin Beasant
    @ebeasant-arm
    @npmccallum Hi there - I suspect that there would be definite interest - We also have multiple points of Enarx contact now (Simon F, myself, Mark H, Charles GT). Personally, I'm ramping back up on Enarx, given that we've managed to kick wasmtime into shape on aarch64 - I'm also very interested in understanding a little more on your Kernel/Runtime story ! ). For joint talks, Charles G-T would probably be a great direct point of contact for the higher level discussions, I'm happy to kick this around too :-)
    Mike Bursell
    @MikeCamel
    I've touched base with Charles GT and Grant L on this, too.
    Edwin Beasant
    @ebeasant-arm
    @npmccallum Cool - Charles GT is fielding this, @MikeCamel - He's seen your email and will respond ASAP :-)
    Mike Bursell
    @MikeCamel
    Win! I love it when a plan comes together (and people talk to each other...).
    Mike Bursell
    @MikeCamel
    I won't make it to the stand-up today (nor the first ByteCode Alliance Summit session). Enjoy.
    axel simon
    @axelsimon
    same for me, sorry for warning late
    i'm trying to push through the DNS stuff + RFCs
    axel simon
    @axelsimon
    hey everyone, i've got the afternoon off courtesy of Steve, but just to give you an update, i'm trying to get the enarx.io domain transfer to happen and jumping through the right hoops to do so
    Nathaniel McCallum
    @npmccallum
    @axelsimon Any progress on the sprint rfc?
    liamcoffey
    @liamcoffey
    0/
    Connor Kuehl
    @connorkuehl
    hi @liamcoffey!
    Nathaniel McCallum
    @npmccallum
    @liamcoffey Welcome!
    Mark Bestavros
    @mbestavros
    Welcome!
    liamcoffey
    @liamcoffey
    Thanks all
    Mike Bursell
    @MikeCamel
    @lkatalin - you mentioned a good slack channel for Rust. Could you provide a URL, please?
    Edwin Beasant
    @ebeasant-arm
    Hi all - just an oddity I picked up: payload/link.json seems to use an explicit location for rcrt1.o that breaks on Ubuntu 20.04: Ubuntu puts rcrt.o under /usr/lib/<target arch> rather than /usr/<target arch>/lib64 What's the usual development OS ? Cheers!
    Edwin Beasant
    @ebeasant-arm
    Hi all - if one of the team might have a little time sometime to walk me through the current structure of the Enarx Builder/crt0stack, I'd really appreciate it: Can do here, F2F, whichever is most convenient :-) Thanks!
    Lily Sturmann
    @lkatalin
    @MikeCamel The link for the Rust Slack channel is https://rust-slack.herokuapp.com/
    @ebeasant-arm We use a patched Fedora. I need to refresh myself on the details very soon, but @connorkuehl would know more I bet
    Edwin Beasant
    @ebeasant-arm
    @lkatalin Thats great - thanks! I'm just using what I had handy. It does build on Ubuntu 20.04 LTS once that change is made though :-)
    Nathaniel McCallum
    @npmccallum
    @ebeasant-arm Our solution there isn't great. @haraldh Any ideas?
    @ebeasant-arm Oh wait. I just realized the reason for this workaround is this: rust-lang/rust#70740
    Nathaniel McCallum
    @npmccallum
    @ebeasant-arm The person who is currently assigned for reviews is a RHer. I'm following up.
    @ebeasant-arm But it should absolutely be a goal to compile everywhere.
    Edwin Beasant
    @ebeasant-arm
    @npmccallum Thats cool - tiny change to the .json and its all built up nicely on x86. I've managed to get a build minus ($ANYTHING_X86) to complete on an aarch64 platform.