public inbox for gentoo-keys@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pavlos Ratis <dastergon@gentoo.org>
To: gentoo-keys@lists.gentoo.org
Subject: [gentoo-keys] Fwd: Gentoo Keys -- introductory report
Date: Mon, 19 May 2014 20:20:50 +0300	[thread overview]
Message-ID: <CAOgmxWy_N58xDO2X6Qo5y3=uz1=9CCe9JYpHsOrLkwO9MAb88A@mail.gmail.com> (raw)
In-Reply-To: <CAOgmxWwrm4pd=HHoVPUd-_6rY3vaf7GO3PYNfk0eLrtPzRSX7Q@mail.gmail.com>

Hello,

This year I've been accepted for Google Summer of Code 2014 with
Gentoo Foundation for the  Gentoo Keys project and my mentor will be
Brian Dolbec(dol-sen)[1]. As I mentioned in my previous email[2] I am
going to work on improving and expanding the features of Gentoo Keys.

Gentoo Keys is a Python based project that aims to manage the GPG
keys used for validation on users and Gentoo's infrastructure
servers. These keys will be any/all of the release keys, developer keys
and any other third party keys or keyrings available or needed.

Plans for this week:
 - Switch the current seed files format to JSON.
 - Create functions for keys remove/move/update operations.
 - Provide some improvements and fixes in the current implemented code.

Source code: https://github.com/gentoo/gentoo-keys or
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-keys.git

Wiki page for Gentoo keys: https://wiki.gentoo.org/wiki/Project:Gentoo-keys

Mailing list for Gentoo keys: gentoo-keys@lists.gentoo.org

[1] https://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/dastergon/5662278724616192

[2]  http://thread.gmane.org/gmane.linux.gentoo.summer-of-code/1535

--
Best regards,
Pavlos Ratis


           reply	other threads:[~2014-05-19 17:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAOgmxWwrm4pd=HHoVPUd-_6rY3vaf7GO3PYNfk0eLrtPzRSX7Q@mail.gmail.com>]

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

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

  git send-email \
    --in-reply-to='CAOgmxWy_N58xDO2X6Qo5y3=uz1=9CCe9JYpHsOrLkwO9MAb88A@mail.gmail.com' \
    --to=dastergon@gentoo.org \
    --cc=gentoo-keys@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox