[aur-general] Popular new Chinese fonts looking for TU adoption

Grigorios Bouzakis grbzks at gmail.com
Mon Jan 28 13:14:18 EST 2008

On Mon, Jan 28, 2008 at 11:02:15AM -0500, w9ya at qrparci.net wrote:
> Hey Qianqian and the gang;
> I am glad that you decided to write.
> There are a couple of things that are important for you and the submitters
> you mention to understand about the "community" package repository.
> First, the TU's are expected to maintain the trust of the user community
> by maintaining the quality of the packages they take 'responsibility' for
> when adopting. SO.... unless the TU understands your language
> requirements, they should NOT be willing to adopt your packages.
> Second, ANYONE can petition to become a TU, including the submitters of
> the packages you mention below. One merely has to ask to be sponsored. I
> am sure the submitters you mentioned will find sponsors if the packages
> they have submitted are of sufficient quality.
> SO ... the problem you outline below is easily solved and should be
> corrected within a couple of weeks of your submitters petitioning to
> become a TU.
> Once becoming a TU the only three requirements to remain a TU are to vote
> when asked to on matters concerning TUs, maintain good and non-destructive
> packages to the *outlined* standards, and not be destructive when using
> the  repository storage facilities.
> I hope this helps.
> Very best regards;
> Bob Finch
> > hi all
> >
> > I am not sure if this is the right place to post an adoption
> > request, if not, please advise me the appropriate mailing list.
> >
> > I am an upstream author of a set of popular Chinese fonts.
> > My team and I spent the past 3.5 years developing high
> > quality free fonts for CJK users, including the first manually
> > fine-tuned multi-strike bitmap font with full coverage to GB18030
> > charset (WenQuanYi Bitmap Song), and the first open-source
> > Hei Ti (sans-serif) vector font (WenQuanYi Zen Hei).
> >
> > These fonts are quite popular in the Chinese community,
> > and widely distributed by Debian, Fedora, Ubuntu etc.
> > Contributors also packaged these fonts for ArchLinux,
> > with the hope of benefiting ArchLinux Chinese users.
> > The links to these packages can be found at
> >
> > http://aur.archlinux.org/packages.php?K=wqy
> >
> > The submitters of the packages recently contacted
> > me and expressed their desires of pushing these fonts
> > to "community", as both fonts got reasonable votes
> > and popularity among the users. However, they have not
> > yet been able to locate a TU to adopt these packages.
> >
> > So, we are looking for TU(s) who is able to take
> > and help maintaining these Chinese font packages.
> > The package submitters (CCed) and the upstream
> > are willing to help and clarify things in the process of
> > packaging.
> >
> > Please let us know if you are interested.
> > thank you for your attention.
> >
> > Qianqian

The above are a fine example of what i was talking about in my previous
emails on this list, stating that TU's  should provide as binaries
packages that the community wants and not only the packages they want to
Here we have a TU who has uploaded 29 packages in community, without
getting them to unsupported first. One of his packages has 2 votes,
half of the remaining ones have 1 and the rest 0.
Yet he finds it very easy to reply when someone requests for some much
more popular packages than the ones he is maintaining to get into 
community, that a TU should be interested in them to adopt them and he
should know chinese to maintain them.
As if Eric Belanger aka Snowman knows arabic, greek  and simplified chinese 
in order to maintain his xpdf packages.
I dont  remember nor really care what the TU guidelines say about
this, but behaviours like this by "Trusted Users" IMO are not
acceptable. I clearly remember "Remember to vote for your favourite
packages! The most popular packages will be provided as binary packages
in [community]." though.
If the Guidelines dont state the above, IMO it should be added. The AUR
as well as the Arch community have got much bigger than when those
guidelines were written.


More information about the aur-general mailing list