On 16.06.2013 21:44, Robin H. Johnson wrote:
> […]
>>> - How can we better encourage these to move to an API site?
>> Not sure what you mean with that.
> It needs to be really easy for any developer to throw up a new data
> source w/ scripts onto the API site.
> 
> Even qa-reports is somewhat stalled, and doesn't have good visibility,
> because it's not that easy for any dev to add something new to it.
> 

Currently, it's files in CVS, soon to be files in a Git. That's at least
the same reachability as before. I think solving this problem is a
separate task.

>Image resources:
>>>> These can be uploaded to the Wiki.
>>> How can we ensure later that the media files don't get deleted?
>> Deletion is restricted to administrators, mediawiki also keeps old
>> versions around in case someone reuploads a file.
>> To prevent even that, we can restrict editing certain assets to developers.
> See my other comment about git-mediawiki maybe, that would satisfy my
> needs, just having old versions of the images around as needed (not
> admin-deletable).

Um, got a link for that extension?
I didn't clarify, the Wiki can be configured to keep a revision even if
someone deletes a file.

> 
>>>> Other files and downloads:
>>>> Until proper project file hosting is implemented, again a simple
>>>> git-backed static site, possibly projects.gentoo.org.
>>> Please don't put lots of binary files in Git.
>>>
>> How do we expose that site to developers then? Akin to the mirroring
>> system on d.g.o?
> I need to dust off the project hosting proposal, because there are a lot
> of files that need to move to it (like all the elections & PR
> materials).
> 

…or that.

-- 
Alex Legler <a3li@gentoo.org>
Gentoo Security/Ruby/Infrastructure