[Slackbuilds-users] Maintainer(s) needed for SlackBuilds

[Willy Sudiarto Raharjo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Blimey, that was quick!

i announced it on #slackbuilds channel on IRC and he responded there

> Well, what I was thinking is that a certain amount of the packages are
> done because a Slack user 'uses them' and makes an SB available.
> Obviously people are only really interested in what they use.
>
> Now, as in this case the user releases the builds, if nobody else did
> use them, is it worth keeping just because?

There are some packages that are still working since the first time
they submitted and may be used by other applications.
Since it doesn't change much, there won't be many download counts on
this package since most people that needs this package will have
installed it long time ago
I don't think we will remove that right? :)

The condition we will remove a package will be:
- - No longer build on newer Slackware release
- - Broken package and no longer maintained upstream
- - Maintainer decided to abandon the package and no one is willing to
take over


- --
Willy Sudiarto Raharjo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKiioIACgkQiHuDdNczM4E6WQCdGmtHcOGgO0ztUCqJ49EGEMqz
wGEAn326/8t4ykqeD6PECdEtZPCmw1Ib
=yItg
-----END PGP SIGNATURE-----