[Slackbuilds-users] 3 Slackbuilds looking for new maintainer

[Harald Achitz]

Hi,

as a result of temporarily bans (several days) for nearly each post on LQ I
did in the last months, I decided to cancel my paid LQ subscription. Now
the LQ mod has banned me for ever.
I knew already how horrible LQ is moderated from several mods, but this
tells me the very rest I need to know about LQ.
Since Slackware has decided to use this place, that I can not follow
anymore, as it's community platform I have to wish Slackware all the best
for it's future.
No more development,or financial support from me for Slackware, Slackware
developers or Slackware related projects.

For Slackware this will not make any difference, other OS project and I can
be happy about the resources available.

However, one side effect is that the 3 Slackbuilds I maintain needs new
maintainers.

These are:

slack
https://slackbuilds.org/repository/14.2/network/slack/
slack desktop client
I haven't updated this for a while since it's change to GTK3, and because
if imho it uses insane amount of CPU/memory resources and the web client
works much better.

kcov
https://slackbuilds.org/repository/14.2/development/kcov/
a code ocverage tool for C/C++, python and bash scripts
nice talk from the author:

sbbdep
https://slackbuilds.org/repository/14.2/system/sbbdep/
The tool for exploring binary runtime dependencies on Slackware and
Slackware based system.
This build will barely ever change since what it does is final and works, I
do not think that I now will ever finalise or release the features I have
in the queue.


All 3 builds are super simple, so there should not be any problems with
them.
If there are questions to them, I will for some time have a look at this
thread and help if I can.


Regards and all the best!

[Didier Spaier]

Hello Harald,

as a result of temporarily bans (several days) for nearly each post on LQ I did in the last months, I decided to cancel my paid LQ subscription. Now the LQ mod has banned me for ever.
I knew already how horrible LQ is moderated from several mods, but this tells me the very rest I need to know about LQ.
Since Slackware has decided to use this place, that I can not follow anymore, as it's community platform I have to wish Slackware all the best for it's future.
No more development,or financial support from me for Slackware, Slackware developers or Slackware related projects.

I can understand your feeling about LQ and its moderators.

Meanwhile I am sad to see you leave the Slackware community, as I think that you provided useful contributions (as a4z, for those who don't know).

I have still to look at sbbdep but will certainly do that. Which doesn't mean that I be ready to take it over though ;)

If you want to contribute to Slint, just drop me a line.

Best regards,

Didier

For Slackware this will not make any difference, other OS project and I can be happy about the resources available.
However, one side effect is that the 3 Slackbuilds I maintain needs new maintainers.
slack
https://slackbuilds.org/repository/14.2/network/slack/
slack desktop client
I haven't updated this for a while since it's change to GTK3, and because if imho it uses insane amount of CPU/memory resources and the web client works much better.
kcov
https://slackbuilds.org/repository/14.2/development/kcov/
a code ocverage tool for C/C++, python and bash scripts
http://youtu.be/1QMHbp5LUKg
sbbdep
https://slackbuilds.org/repository/14.2/system/sbbdep/
The tool for exploring binary runtime dependencies on Slackware and Slackware based system.
This build will barely ever change since what it does is final and works, I do not think that I now will ever finalise or release the features I have in the queue.
All 3 builds are super simple, so there should not be any problems with them.
If there are questions to them, I will for some time have a look at this thread and help if I can.
Regards and all the best!
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[B Watson]

Post by Harald Achitz
Hi,
as a result of temporarily bans (several days) for nearly each post on LQ I
did in the last months, I decided to cancel my paid LQ subscription. Now
the LQ mod has banned me for ever.
I knew already how horrible LQ is moderated from several mods, but this
tells me the very rest I need to know about LQ.
Since Slackware has decided to use this place, that I can not follow
anymore, as it's community platform I have to wish Slackware all the best
for it's future.
No more development,or financial support from me for Slackware, Slackware
developers or Slackware related projects.

LQ isn't run by the Slackware project. Please don't dump Slackware
because of LQ.

It's possible to be a part of the community without using LQ. I know
because I never used it (I hate forums, never signed up for it in the
first place).

The various IRC channels and mailing lists are also 'the community'
and generally have a higher singal to noise ratio than a forum anyway.

Come to freenode IRC and talk to us on ##slackware and ##slackbuilds
(and also ##slackware-offtopic).
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Ricardo J. Barberis]

Content preview: El Domingo 07/10/2018 a las 22:12, B Watson escribió: > On
10/7/18, Harald Achitz <***@gmail.com> wrote: > > Hi, > > > > as
a result of temporarily bans (several days) for nearly each post on LQ >

I did in the last months, I decided to cancel my paid LQ subscription. >
Now the LQ mod has banned me for ever. > > I knew already how horrible

LQ is moderated from several mods, but this > > tells me the very rest I need
to know about LQ. > > Since Slackware has decided to use this place, that
I can not follow > > anymore, as it's community platform I have to wish Slackware
all the best > > for it's future. > > No more development,or financial support
from me for Slackware, Slackware > > developers or Slackware related projects.

LQ isn't run by the Slackware project. Please don't dump Slackware >

because of LQ. [...]

Content analysis details: (0.3 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
0.0 SURBL_BLOCKED ADMINISTRATOR NOTICE: The query to SURBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: donweb.com]
-1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP
1.2 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4996]
0.1 BAD_BODY_1 BODY: Filter mails with possible spam in Body
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - c137.dattaweb.com
X-AntiAbuse: Original Domain - slackbuilds.org
X-AntiAbuse: Originator/Caller UID/GID - [502 502] / [502 502]
X-AntiAbuse: Sender Address Domain - palmtx.com.ar
Subject: Re: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer
X-BeenThere: slackbuilds-***@slackbuilds.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "SlackBuilds.org Users List" <slackbuilds-users.slackbuilds.org>
List-Unsubscribe: <https://lists.slackbuilds.org/mailman/options/slackbuilds-users>,
<mailto:slackbuilds-users-***@slackbuilds.org?subject=unsubscribe>
List-Archive: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/>
List-Post: <mailto:slackbuilds-***@slackbuilds.org>
List-Help: <mailto:slackbuilds-users-***@slackbuilds.org?subject=help>
List-Subscribe: <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>,
<mailto:slackbuilds-users-***@slackbuilds.org?subject=subscribe>
Reply-To: "SlackBuilds.org Users List" <slackbuilds-***@slackbuilds.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
as a result of temporarily bans (several days) for nearly each post on LQ
I did in the last months, I decided to cancel my paid LQ subscription.
Now the LQ mod has banned me for ever.
I knew already how horrible LQ is moderated from several mods, but this
tells me the very rest I need to know about LQ.
Since Slackware has decided to use this place, that I can not follow
anymore, as it's community platform I have to wish Slackware all the best
for it's future.
No more development,or financial support from me for Slackware, Slackware
developers or Slackware related projects.

LQ isn't run by the Slackware project. Please don't dump Slackware
because of LQ.

I second that!

It's possible to be a part of the community without using LQ. I know
because I never used it (I hate forums, never signed up for it in the
first place).

This is also pretty much my case, I think I have a user on LQ but I only read
the Slackware forum when there's some big news that I hear somewhere else.

The various IRC channels and mailing lists are also 'the community'
and generally have a higher singal to noise ratio than a forum anyway.
Come to freenode IRC and talk to us on ##slackware and ##slackbuilds
(and also ##slackware-offtopic).

I didn't know about those channels, not a big user of IRC but still better
than forums for me :)

Cheers,
--
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Willy Sudiarto Raharjo]

Post by Harald Achitz
slack
https://slackbuilds.org/repository/14.2/network/slack/
slack desktop client
I haven't updated this for a while since it's change to GTK3, and
because if imho it uses insane amount of CPU/memory resources and the
web client works much better.

I will take slack

[Daniel Prosser]

I can take sbbdep. Thanks for your contributions.

Dan

Post by Harald Achitz
Hi,
as a result of temporarily bans (several days) for nearly each post on LQ I
did in the last months, I decided to cancel my paid LQ subscription. Now
the LQ mod has banned me for ever.
I knew already how horrible LQ is moderated from several mods, but this
tells me the very rest I need to know about LQ.
Since Slackware has decided to use this place, that I can not follow
anymore, as it's community platform I have to wish Slackware all the best
for it's future.
No more development,or financial support from me for Slackware, Slackware
developers or Slackware related projects.
For Slackware this will not make any difference, other OS project and I can
be happy about the resources available.
However, one side effect is that the 3 Slackbuilds I maintain needs new
maintainers.
slack
https://slackbuilds.org/repository/14.2/network/slack/
slack desktop client
I haven't updated this for a while since it's change to GTK3, and because
if imho it uses insane amount of CPU/memory resources and the web client
works much better.
kcov
https://slackbuilds.org/repository/14.2/development/kcov/
a code ocverage tool for C/C++, python and bash scripts
http://youtu.be/1QMHbp5LUKg
sbbdep
https://slackbuilds.org/repository/14.2/system/sbbdep/
The tool for exploring binary runtime dependencies on Slackware and
Slackware based system.
This build will barely ever change since what it does is final and works, I
do not think that I now will ever finalise or release the features I have
in the queue.
All 3 builds are super simple, so there should not be any problems with
them.
If there are questions to them, I will for some time have a look at this
thread and help if I can.
Regards and all the best!

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/