community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <>
Subject Re: adding keys to FOAF
Date Mon, 16 May 2016 22:25:08 GMT
The tools used for this kind of stuff are evolving.  In particular, some
tools are core services - maintained by infra with SLAs and the like -
and other tools are non-core, and are maintained by the volunteers here
in Community Development (comdev).  So the docs are lagging as to how
the bits tie together. is the official supported infra service for updating info
related to your committer account, and it's integrated into the various
LDAP and authz/repo access control bits, so that's always the first
place to start.

Things like people.a.o/home.a.o, the FOAF connections, the speaker and
mentor and location listings, are all essentially comdev projects
maintained by volunteers, so we're behind on docs and ensuring stuff is
tied together.

There's a lot of work happening to upgrade many core data storage bits
from old-fashioned .txt files in subversion to someplace useful.
Looking at the code behind projects.a.o is one place to start learning
if you want to volunteer; it "cron"s a variety of JSON files at stable
URLs from underlying sources.  The Whimsy project is also a good place
to look at how we're repurposing Foundation data for better use.

- Shane

Daniel Ruggeri wrote on 5/16/16 3:32 PM:
> On 2016-05-11 20:07, Stefan <> wrote:
>> Hi,
>> recently I went through the process to create an OpenPGP key for code
>> signing purposes and now wonder whether this section here is outdated:
> Could be - I'm not sure how it all glues together, but I added my PGP
> key info at and it shows up in
> maybe that's the right
> place?
> FWIW, I uploaded/updated my FOAF file ages ago as well as put them into
> the local-outreach and speakers rdf files but the updates never made it
> into the zones page here maybe
> FOAF isn't used at all or perhaps some of the stuff driven by it doesn't
> work.

View raw message