Roadmap 2017

Peter Lindener lindener.peter at ...9...
Sun Jan 8 02:30:50 CET 2017

Fellow genodians-

   Now that Genode's base API is going totally async..

   it would be great to see an example of some cooperating processes where
each might have the flexibility to across the network of different
   I realize there are plenty systems for supporting an RPC...
but I gather Genode's new Async perspective, might also better inform how
one might best configure and synchronize / clean_up a set of processes
exchanging data and running possibly on different machines..

   That is: an example of how one might best do RPC like things within the
philosophy of the new Genode API would be very helpful...   it could start
as more of a toy program, but the thought here is that we might polish and
maintain it as part of Genode's getting started / coding style

    Is there an existing Genode RPC like example that might be a good
starting point ?


On Sat, Jan 7, 2017 at 6:33 AM, Josef Söntgen <
josef.soentgen at ...1...> wrote:

> Hello everyone,
> looking back at the the roadmap of 2016 it is clear that we missed some
> items; nevertheless, I think all in all the year went well. Norman already
> noted some observations, namely prioritizing the existing user base
> over the future one. Looking back at this week's clean-up efforts I
> believe that spending more time on refining the base APIs was indeed the
> right decision. Using the new interface or switching the used kernel
> seamlessly while testing components feels so natural now and with the
> ABI mechanism provides a great foundation for building the infrastructure
> for package/deployment management.
> That being said, one thing I missed from last year's roadmap discussion
> (although I am not sure if that was actually discussed on the ML or only
> at a coffee break) is the intention of making more information about
> Genode available to and by the community, i.e. in the form of writing
> how-tos for specific tasks or just by writing informally about interesting
> things that happend while working on Genode. Since parts of the APIs were
> or are still in flux I understand that it is difficult to write detailed
> articles that are valid for the years to come and probably one of the
> reason why one hesitates to spend time on that. That merely leaves the
> more informal part. Judging by the huge amount of out-dated information
> for <insert your favourite topic here> in all the weblogs on the internet
> I am not sure if spending time on that is a good idea either. Than again,
> were is the harm in documenting the process of writing a new component or
> porting existing software [1] to Genode? After all it should be fine if
> the focus is more on the process or the methodology. So, that is a goal of
> mine for 2017 — scheduled (emphasis on that) writing about what I do with
> Genode in hope that it is useful to somebody or even that others join in
> :-)
> [1] FWIW
> Apart from that, I am afraid I have no precise items for this year's
> roadmap. I agree with Norman; we need the infrastructure to keep a
> running Genode system in sync to the latest changes to provide better
> test coverage. I imagine that this will keep us busy for some time and
> there are still some items from the old roadmap left that needs to be
> addressed as well.
> Regards
> Josef
> --
> Josef Söntgen
> Genode Labs
> ·
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites,!
> _______________________________________________
> genode-main mailing list
> genode-main at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list