[Kde-games-devel] How to use KNewStuff3?

[Josef Spillner]

Am Freitag, 18. Juni 2010, um 09:18:13 schrieb Ian Wadham:
> So I gather that newstuff.kde.org is read-only unless you have a SVN
> account. That's fine.

That's indeed the case for SVN-maintained repos which are controlled by an 
application author or filetype maintainer. However, WebDAV and FTP can be used 
anonymously. What happens with uploaded items is a per-application or per-
filetype policy: They can show up for download instantly, or might need 
approval by the respective maintainer.

> No problem.  My biggest file is <0.5Mb.  It would be nice to be able to
> put new collections of levels up before official release.  I think it is a
> turn-off for contributors to have to wait till the next release to see
> their work appear.

I see your point. We could accelerate the turnaround times even more by 
implementing something like a local GHNS provider for development purposes. 
Artists could then immediately get an impression of how the items are 
presented to the user. Of course, having a development section in the online 
repository achieves nearly the same effect.

> OK, great.  Re uploading, at first I might have to vet contributions before
> they are uploaded (e.g. to ensure that text follows guidelines for
> translation and non-English reading).  A high-score bid would probably be
> submitted by the end-user, whenever I get that far ...

See above for a discussion on moderation.

> Released collections of KGoldrunner levels are in a pseudo C++ format,
> so are easy to translate.  My question is more whether/how scripty,
> translators or whatever look in a new stuff repository for translation
> work.

Ah, you talked about the level contents whereas I talked about the associated 
GHNS metadata which the user will see at first sight. Both are subject to 
translation :-)

That's definitely a good question. Technically, it's again trivial to work 
across repositories and automate the conversion processes. The issue is more 
an organisational one, to decide whether our translators can scale to 
potentially hundreds of items in addition to their regular workload. We 
definitely want to have as much content as possible available with 
translations, but on the other hand we should avoid throwing bazillions of 
message catalogues at the translators. One possibility would be to upgrade the 
collaboration features in KNS3 to let users suggest translations. It scales 
better but bypasses the KDE translation process, and thus might have similar 
issues like Launchpad translation synchronisation. I reckon that this is a 
good discussion topic for those who are at Akademy.

Depending on how far you get in which amount of time, we could set up an IRC 
session in mid-July, even according to Australian time, to ensure everything 
works just after Akademy.

Josef