G> What "communication problems" are you referring to?

 G> A followup: How has that hurt the distribution?
 
Hello,
 
See those times when there is a "holyday" going on and no patches are submitted
for packages known to need the patches? It is not frequent but package updates
have gotten quiet for certain timespans in the past. I
know of people who switched certain systems not because of this, but because the
lack of explanation casted doubt on the usefulness of the distribution as a
tool.
 
The lack of an official roadmap for the release cycle is a bit troublesome for
administrators who are not targetting -current. I have already heard of
administrators who needed feature X that was in -current but not in-stable for
date Y... they didn't know when the new Slackware release would be served, they
didn't want to shoehorn the feature locally, and they didn't want to move to
-current... Uncertainity is bad for people who work on a schedule and in the end
of the day people switches to distributions that have predictable roadmaps.
 
Also, for some reason, lots of people keep asking if Slackweare is a dead
project, which in itself suggests its presentation as a distribution is giving
people weird ideas. That is bad for adoption and hence the ability of the
distribution to raise funds and gather collaborators. As you may know, there is
a lot of dark gossip regarding the finantial status of the whole thing.
This gossip never seems to die.
 

--- Maximus/2 3.01
 * Origin: Micronet World HQ - bbs.outpostbbs.net:10123 (618:618/1)