LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-05-2018, 07:19 PM   #16
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,537
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442

Put the Grand kids through school Make slackware Inc. Do an IPO create 10 million shares. I will buy 10k. sell the shares 50 cents that is 5 million dollars we all are happy and Pat can retire and love life. Bob can grow up and just do it like Mike and LeBron and be loved. we all have quality and great dark beer.
We are young stop feeling old. Trust me if you have seen my work in this world. I am sorry no one will. But Slackware is loved by the tops of the tops.
KISS lets do it. Just do make the stock available hire a lawyer Pat to do your quarterly showings your worth 5 million at base.
Slackers put your money where it is needed in 10 years you will be happy with split stock.

Last edited by Drakeo; 08-05-2018 at 07:22 PM.
 
1 members found this post helpful.
Old 08-05-2018, 07:34 PM   #17
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,537
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
Quote:
Originally Posted by saxa View Post
I would like to see a slackware-development mailing list. Instead of having this in a forum.
You see it everyday in the changelog. you have an email to Pat and you can push any fix. IRC:#slackware if your brave go there.
They drink beer and do not put up with cry babies like Jeremy
 
Old 08-05-2018, 08:01 PM   #18
philanc
Member
 
Registered: Jan 2011
Posts: 180

Rep: Reputation: 147Reputation: 147
Web site: make a good first impression on occasional visitors:

Put the changelog of current (for x86_64) on the home page instead of one news from 2016 and another one from 2013.

Not a big change, but it would show to occasional visitors that Slackware is alive and under active development.

A "Last release" link on the left could just point to the Slackware 14.2 announcement.
 
4 members found this post helpful.
Old 08-05-2018, 08:06 PM   #19
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,279
Blog Entries: 1

Rep: Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600Reputation: 1600
Quote:
Originally Posted by philanc View Post
Web site: make a good first impression on occasional visitors:

Put the changelog of current (for x86_64) on the home page instead of one news from 2016 and another one from 2013.

Not a big change, but it would show to occasional visitors that Slackware is alive and under active development.

A "Last release" link on the left could just point to the Slackware 14.2 announcement.
Excellent idea!
 
Old 08-05-2018, 08:11 PM   #20
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 446

Rep: Reputation: 45
Quote:
Originally Posted by Drakeo View Post
You see it everyday in the changelog. you have an email to Pat and you can push any fix. IRC:#slackware if your brave go there.
They drink beer and do not put up with cry babies like Jeremy
I think that the development mailing list gives us more freedom on our time, similar like forums. But for see a forum you need to have a browser, and search through it.
Another think is that you do have to read all the unread messages. On the other hand be in the irc channel you have a similar situation, you still need to idle there
or read the log somewhere. I think this is all not practical for development issues.

From the other hand you have in the mailing lists more freedom to choose where you want to participate and reply to a certain message, others you do not need
they can simply be deleted. I mean, I think you are brave enough to know the differences.

As last, some big projects really community oriented use mailing lists, ex. Linux kernel, and nearly all of the big stuff in linux world. What I see mostly is that
Slackware is not really that community oriented, because it is hard to know where its development goes on.
 
Old 08-05-2018, 08:41 PM   #21
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,537
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
saxa You ever watch the series House. trust me I gave my answer.
 
Old 08-05-2018, 09:17 PM   #22
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 446

Rep: Reputation: 45
yeah I watched it but never liked it much. In any case it is just a matter of how you are used to work on things.
 
Old 08-06-2018, 04:12 AM   #23
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.2 64-bit
Posts: 457

Rep: Reputation: 142Reputation: 142
Quote:
Originally Posted by philanc View Post
Web site: make a good first impression on occasional visitors:

Put the changelog of current (for x86_64) on the home page instead of one news from 2016 and another one from 2013.

Not a big change, but it would show to occasional visitors that Slackware is alive and under active development.

A "Last release" link on the left could just point to the Slackware 14.2 announcement.
Yes, the web site would be more useful with regular updates and also pointing to regularily updated sites like the AlienBob site and Slackblogs site.
 
2 members found this post helpful.
Old 08-07-2018, 08:02 AM   #24
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,375

Rep: Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969Reputation: 1969
Quote:
Originally Posted by jostber View Post
Yes, the web site would be more useful with regular updates and also pointing to regularily updated sites like the AlienBob site and Slackblogs site.
And maybe get rid of the "Installation Help" page that explains how to create boot and root floppies using RAWRITE.EXE?

http://www.slackware.com/install/
 
1 members found this post helpful.
Old 08-07-2018, 11:22 AM   #25
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware 14.2 || Slackware-current && CentOS
Posts: 1,322

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
Quote:
Originally Posted by jostber View Post
Yes, the web site would be more useful with regular updates and also pointing to regularily updated sites like the AlienBob site and Slackblogs site.
I like this idea too. But it would make more sense to create an official Slackware blog (in addition to the main site) that is updated monthly for changes / updates to the supported stable releases and to Slackware-current. It wouldn't need to use anything complicated. A static web site generator would do nicely and everything can be written in text files (markdown or similar syntax).

Quote:
Originally Posted by kikinovak View Post
And maybe get rid of the "Installation Help" page that explains how to create boot and root floppies using RAWRITE.EXE?

http://www.slackware.com/install/
Yes! Point to the Slackware documentation project to handle all documentation in a central location. Increase the frequency of updates to outdated documents too. This was very confusing several years ago when I converted to Slackware from Debian because the official Slackware site is written like it's the year 1995. It might even make sense to update the Slackbook and republish it with the changes to the installation process for Slackware 15.0.
 
4 members found this post helpful.
Old 08-07-2018, 11:33 AM   #26
chemfire
Member
 
Registered: Sep 2012
Posts: 210

Rep: Reputation: Disabled
One thing that might be kinda fun is just a little status update.

Only changes that actually get committed make the change log so when time is being spend on that stuff that never sees the light of day nobody knows about it. It makes it look like work has stopped when that isn't really accurate.

If even really short little status updates that would take no time got posted and that could be as simply as echoing them to text file a php script on the website sweeps up it would be nice. I am thinking things like:

'Investigating synchronizing main boot scripts with those used for LXC containers'

let system report the modified time.. That would let people have a little visibility into the private side of the development process. It also might steer the topics on these boards a bit so information useful to the dev team comes to light.
 
1 members found this post helpful.
Old 08-09-2018, 07:48 AM   #27
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 446

Rep: Reputation: 45
start using Aliens git and put the development visible on the web site.
 
Old 08-09-2018, 09:46 AM   #28
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware 14.2 || Slackware-current && CentOS
Posts: 1,322

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
Quote:
Originally Posted by saxa View Post
start using Aliens git and put the development visible on the web site.
Last I checked it is possible to follow Slackware-current development here: http://cgit.notk.org/adrien/slackwar...rrent.ext.git/

Still, it would be excellent if there was an official Git repository available to the public for viewing, even if it was read-only.
 
Old 08-09-2018, 10:19 AM   #29
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,303

Rep: Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461Reputation: 5461
Quote:
Originally Posted by mralk3 View Post
Last I checked it is possible to follow Slackware-current development here: http://cgit.notk.org/adrien/slackwar...rrent.ext.git/
The two are similar, but not the same. I pay homage to Adrien's git repository, he has been tracking -current in git for years and it has been quite useful at times to look back at prior changes.
My own git repository is still young but it attempts to do several things which I found lacking in Adrien's git repository.
 
2 members found this post helpful.
Old 08-09-2018, 11:15 AM   #30
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 446

Rep: Reputation: 45
@mralk3, yeah, I am aware of those git repos. In fact what I tried to say is exactly what you wrote, would be nice to have it as official repo. No matter which one , I think the dev team has to decide eventually what is best for them. I am sure they all can benefit from that, but more, whole the comunity would benefit, and I think that the thing of push requests is even better thing to simplify corrections and submissions to code.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Suggestions for Linux OS for home server. Open to suggestions. wh33t Linux - Server 6 08-20-2016 08:47 AM
Creating a open Fuse mount point sethusubbiah Linux - Newbie 2 07-27-2010 02:19 PM
suggestions for using xslt to view base64-encoded floating point data in an xml file? zero79 Programming 0 01-10-2006 07:52 PM
open shortest point first Z4pp4 Linux - Security 3 05-22-2002 12:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration