You know, Patrick has e-mail address, which is available somewhere within slackware documentation. I believe it is written in a greeting letter root user receives after successful installation.

I don't see any mention of the fact Slackware welcomes contributions on any of the following pages (where I'd expect it):

http://slackware.com/contact/ (two emails there, but neither are suited to sending in non-critical patches)
http://slackware.com/info/
http://slackware.com/support/

If there is something that I've missed, please direct my attention to it. This is getting off topic a bit, suffice to say I think the way thinks works does work, and it /is/ open, but you could quite easily make it more obvious for new users/developers how to get involved with development - and in that respect you could make it more open.

Anyone qualified to *make* contributions is expected to be able to figure out where to send them.

What, and that means you shouldn't make it as easy as possible? Really not following how that matters at all.

Maybe I'm in the minority, but it seems to me sort of par for the course in open source development that anyone can contribute -- with the obvious caveat that there is no guarantee a contribution will be accepted or used, of course. I didn't really think it was something that needed to be explicitly stated.

Perhaps, maybe I should have said one thing on the website which tells you where to send them in. There's also the slight problem of this misconception that in Slackware Pat does everything and that there is no teamwork involved. It might be worth overcompensating just to finally put that to rest.

And where it is said (on these pages) that contributions to slackware aren't welcome?

I don't think it is necessarry, really. Even projects which are supposed to welcome everyone with "contributions" aren't that easy to make your contributions accepted. In case of slackware if you have something interesting to offer, contact information is provided. If your changes aren't accepted, you can always fork entire distribution.

Besides, if slackware is supposed to "keep it simple", doesn't use "bleeding edge" sources, and keeps minimal number of distribution-specific changes, where and what are you going to contribute?
Do you have some change you want to be accepted *right now*?

*I'd* like to see postgres included ;} as an alternative to
MySQL, and would be happy to provide a package (and
a patch to PHP).



Cheers,
Tink

http://slackbuilds.org/result/?search=postgres&sv=12.1

Not the same as being part of slack?

Hahaha ... LOL

Patrick,

I'd suggest changing the logo with every release so users don't get too complacent. Yes, the current logo is way out there ahead of the pack, but so is Slackware. Substitute the logo for the name of a release, I say. Keep 'em guessing.

wow.. there seem to be a lot of people getting offended in this thread on all sides.. moderators, slack contributers, users and even logo enthusiasts. And I was told to chill out.. hahaahahhaaaa

As for slackware being open or closed... It is obviously open as it is completely open source and available but I know what some mean in regards to contributions being limited... but is that really a bad thing? Now get back on topic before this gets locked!!

I have been following this thread for some time now and am surprised - in a positive way - how passionate we all can become about a simple change of a logo.

This is a good thing, as it is a sign we all care a lot about Slackware. I myself have a 'relationship' with Slackware that's enduring for more than 10 years now. I have been seduced in the past by other distributions (used RH / Fedora at work so installed it at home), but was disappointed so I returned to my old love... There is no distribution I know better and feel more 'intimate' with than Slackware, so I can also become passionate about it.

The new logo is like when your wife/girlfriend suddenly comes home with a new style or color of hair, surprising you completely. In the beginning you might find it strange... But it is still your wife, with the same qualities / personality.

Slackware is also still the same, the logo doesn't change that.
I had to get used to it too, but I already changed my boot screens and last Friday (Slackware-day here in São Paulo - Brazil) I bought myself a sticker with the new logo to put on my laptop.
When it's closed, I can read "Slackware".
When it's opened, anyone in front of me can also read "Slackware".
This is only possible with a 'flippy' logo!

Let's all remember that this is GNU/Linux we're talking about: If you don't like it: change it.
We don't need to use the new logo on our computers. Heck, you can even take the penguin out of the kernel if you don't like Tux.

Happy computing!

Don't get me wrong. I like the logo, but I still wear paisley shirts...
Every time I see the 'flippy' logo, I think of the Rod Stewart tune, "You Wear It Well".


j/k

Flippy's King Of the Logos... KEEP IT!

P.S. I've got a flash of inspiration. Patrick, Let's brand Slackware with paisley shirts and the 'flippy' logo sung to Foreigner's tune, "Double Vision". Can you imagine the marketing appeal? OOOOOOOOKKKKKKKKKKK. I'll stop now.

I've actually sent several possible logos to the e-mail on the propaganda page, but they seem to have not gotten approved. Oh well, I tried. Here's one of the better ones (I think it's not that bad):
http://draconishinobi.50webs.com/slackware.gif