[Slackbuilds-users] Package versions

Harald Achitz harald.achitz at gmail.com
Sat Jan 21 10:23:46 UTC 2017

I makes me tired of hearing that if you do not find something is good, the
words complain, hugely exaggerating and others come.
This are passive aggressive communication patters, please don't. Please
focus on facts and the topic, what was not reacting maintainers.
As written, even if I point to, what I see as, problems, I try to help, and
was actually helpful, maybe not for you because you might miss some basic
difference between low and high entry barriers,
difference between sending a patch / pull request to a project that simply
apply it if it passes QA,
 difference between such workflows, and that one of SBo, where you need to
contact maintainer
mention this makes everything bad? oh come on. experience the difference,
than think, than provide feedback


2017-01-21 10:23 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:

> On 21/01/17 08:21, Harald Achitz wrote:
>> Hi,
>> help is difficult,
>> the SBo rules are clear,
>> If you sent an updated version of a package, you need the OK of the
>> maintainer.
>> If you contact a maintainer, and there is no response, what than?
>> This is a barrier, unnecessary.
>> Git stable & testing, branch.
>> pull requests to testing,
>> when some have reviewed && tested a package in testing, it goes to stable.
>> all this public.
>> you will see, this is much more productive and delivers better results.
>> I try to help, e.g. I would have submitted an update for Qt, but without
>> maintainer permission....
>> The bureaucracy of SBo was long, and still is, an impediment for me.
>> We should be aware of that.
>> It is more easy for me to contribute to any opensouce project on github
>> (I do this) than to SBo.
>> Why? is this adequate for 2017?
>> I do not want to criticize, I want to offer help, by questioning the
>> project structure and suggest alternatives, I think I do this.
>> /Harald
> I think you hugely exaggerating.
> The flow isn't perfect, but I can't agree it is as bad as you describe it.
> Some maintainers are more responsive, other not.
> Some will complain, other not.
> Like in real life.
> But it doesn't mean the project as a whole is bad.
> I can't see the bureaucracy you mention.
> What do you mean by that?
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170121/a2167eed/attachment.html>

More information about the SlackBuilds-users mailing list