unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Ideas for Summer of Code 2018 anyone?
Date: Sat, 13 Jan 2018 21:12:19 +0100	[thread overview]
Message-ID: <CAE4v=pg7rcG17_KU0+Y5KmV4E2HmM+mewt6qfxBYBq3y-njkqg@mail.gmail.com> (raw)
In-Reply-To: <20180113193229.qvz4jyj46744s23j@abyayala>

[-- Attachment #1: Type: text/plain, Size: 5263 bytes --]

2018-01-13 20:32 GMT+01:00 ng0 <ng0@n0.is>:

> Gábor Boskovits transcribed 6.9K bytes:
> > I've checked last the list from last year.
> >
> > It seems to me that the RISCV port might be more important than ever in
> the
> > face of Spectre.
>
> It doesn't really fix that and suffer from it aswell, but a port to it
> would be great for the other obvious reasons.
>
>
Current implementations seem not to be affected.
Also mitigating problems like this, provided that we have rtl level
open source designs have a much better chance. We have this
for example for Freedom: https://github.com/sifive/freedom.
And yes, porting would be great for other reasons too.

What I currently miss from the field of open hardware the most
is an open source FPGA. This could really close the gap we
are now having, and we could make really fully open hardware.
An open sourced FPGA design would be important not for
manifaturing, but to allow checking it. It is not unheard of
buggy FPGA-s. However,I don't think that this will happen any
time soon.

> The shepherd systemd semantics would be also nice to have.
> > I consider the syntax less important.
> > It would be also nice to create a service or set of services to make
> > administration experience
> > similar to a systemd sytem. For example the functionality of journalctl
> > would be nice to have.
>
> That is one goal that can be defined 'log view' and discussed.
> The rest above is not very clear, lots of guessing.
>
> > Even a howto on configuring guixds to have the equivalent services of
> > systemd would
> > benefit adoptation, and it could point to functionality missing in our
> > system compared to
> > systemd.
>
>
What I actually is journalctl, and a status display like systemctl status.
It is great that work is in progress in this area, I was not aware of 'log
view'.

I think it would also be great if we could give pointers how to replicate:

localectl
networkctl
resolved
systemctl
timedatectl

functions. People coming from a systemd background could have a
document to find the appropriate sections in our manuals.


> I don't think we need everything systemd has, or do we?
> What are you personally or work related missing, besides the obvious
> amount of services?
>
> I myself was missing an easy, less scheme focused way to create operating
> systems, so I'm working on that. To get to why I mention this: I thought it
> was too obvious, but most of the time the things that are too obvious
> are not being worked on because they are too obvious.
>
> I would very much like to have an build log reader+browser as mentioned
> here
> in the past. Today I've pointed someone to /var/log/guix/drvs/ and just
> gave
> the note to use `find -name '*thingtosearchfor*'` and copy it to $home,
> extract and view it.
>
> >
> > 2018-01-11 21:42 GMT+01:00 Ludovic Courtès <ludo@gnu.org>:
> >
> > > Hello Guix!
> > >
> > > It’s time to prepare for GSoC again!
> > >
> > > We need to collect ideas, presumably based on
> > > <https://libreplanet.org/wiki/Group:Guix/GSoC-2017>, in a new
> > > “GSoC-2018” page on that wiki.
> > >
> > > Let’s add new ideas to
> > > <https://libreplanet.org/wiki/Group:Guix/GSoC-2018>!
> > >
> > > Does someone want to take care of coordinating with Giuseppe Scrivano
> > > and others at summer-of-code@gnu.org?  (Essentially sending them the
> URL
> > > of the idea list and monitoring the list.)
> > >
> > > Ludo’.
> > >
> > >
> > >
> > > ---------- Továbított levél ----------
> > > From: Giuseppe Scrivano <gscrivano@gnu.org>
> > > To: GNU Summer Of Code <summer-of-code@gnu.org>
> > > Cc:
> > > Bcc:
> > > Date: Tue, 09 Jan 2018 11:06:53 +0100
> > > Subject: [IMPORTANT] Ideas for Summer of Code 2018
> > > Hi!
> > >
> > > Google is accepting applications for the next Summer of Code and as
> > > usual we are going to apply for it. José, Darshit and myself are going
> > > to manage the presence of GNU.
> > >
> > > We should start thinking about a list of ideas for the next Summer of
> > > Code and potential mentors.
> > >
> > > This is the list of ideas we had last year:
> > >
> > >   http://www.gnu.org/software/soc-projects/ideas-2017.html
> > >
> > > Is there anything left undone that can be reused this year?
> > >
> > > Please start sending ideas to add to the page and link them to the
> > > potential mentors that can help with it.
> > >
> > > Please send the html snippet for the ideas page, something like:
> > >
> > > ------------------------------------------------------------
> > > ---------------------
> > > <h3 id="foo"><a href="http://www.gnu.org/software/foo";>GNU
> FOO</a></h3>
> > >
> > > <p>GNU FOO maintains their list of ideas for GSOC in an external
> > >   webpage: <a
> > > href="http://foo.org/wanted.html";>http://foo.org/wanted.html</a>.
> > > </p>
> > > ------------------------------------------------------------
> > > ---------------------
> > >
> > > so that it can be embedded in the page as it is.
> > >
> > > Regards,
> > > Giuseppe
> > >
> > >
> > >
>
> --
> ng0 :: https://ea.n0.is
> A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/
>

[-- Attachment #2: Type: text/html, Size: 8109 bytes --]

  reply	other threads:[~2018-01-13 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 20:42 Ideas for Summer of Code 2018 anyone? Ludovic Courtès
2018-01-13 18:10 ` Gábor Boskovits
2018-01-13 19:32   ` ng0
2018-01-13 20:12     ` Gábor Boskovits [this message]
2018-01-13 21:18       ` ng0
2018-01-13 21:16   ` Ludovic Courtès
2018-01-13 21:24 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=pg7rcG17_KU0+Y5KmV4E2HmM+mewt6qfxBYBq3y-njkqg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).