My problems with Linux Lite so far, a brief summary of problems Linux Lite has.

[AdrianKoshka]

If you to read want my secret gist I put on gist.github.com that I wrote in markdown click the link https://gist.github.com/AdrianKoshka/d25...e37b72f6e8
Otherwise this will pretty much be a reiteration of my gist post.

Through the short time I've been helping a community member with his projects I've seen a little bit of the development process of Linux Lite...and to be honest it terrifies me. This will serve as a brief overview of what I find wrong with the Linux Lite Development Model.

Linux Lite Issues

This document will serve to hopefully compile all issues I see with various projects done by Linux Lite. I feel this is a better way to do things as the current system is not oriented towards teamwork (the lack of a github organization really needs to be fixed, no offense).

Documentation

Documentation is severely lacking in Linux lite, and the manual is--not the best either. I don't say these accusations though without providing suggestions, also I've started my own person rewrite of the Linux Lite Manual in gitbook, which can be found here https://www.gitbook.com/book/adriankoshk...al/details It's a WIP.

Github Organization

NOTE: DON'T GET BUTTHURT READING THIS, KEEP YOUR COOL, I'M BEING SERIOUS

To give proper credit to authors, whether it be for documentation, code, etc a github organization NEEDS to be setup. This hacky method of keeping a distributions projects under a user account is simply not acceptable. Some reasons this isn't accept are:

• It makes it look like authors have COPIED their ORIGINAL works!
  
• It doesn't foster a sense of community.
  
• It makes it harder for people who want to help contribute.
  
• It slows down progress.
  

that is just a short list of reasons why. A github organization will allow for Linux Lite to grow faster, for reasons such as:

• The community has more involvement.
  
• More people can take time to fix things.
  
• More work can be done independently
  
• More issues can be addressed
  
• A smoother work flow can be achieved.
  
• Less overhead.
  

Things That NEED fixing

These applications at this point don't have what I feel would meet minimum documentation requirements.

• Lite Software https://github.com/linuxlite/litesoftware
  
• Lite Control Center (almost, but not quite there) https://github.com/linuxlite/litecontrolcenter
  
• Lite Manual (Official, not my gitbook rewrite) https://github.com/linuxlite/litemanual
  
• Lite Welcome https://github.com/linuxlite/litewelcome/issues/5
  
• Lite Tweaks https://github.com/linuxlite/litetweaks
  
• xfce4-whiskermenu-plugin (Almost...not quite) https://github.com/linuxlite/xfce4-whiskermenu-plugin
  
• Lite Builder https://github.com/linuxlite/litebuilder
  
• Lite User Manager https://github.com/linuxlite/liteusermanager
  
• Linux Lite Kernel Build Script (IMPORTANT) https://github.com/linuxlite/kernelbuildscript
  
• Lite Login (Doesn't seem like you'd need much for a theme) https://github.com/linuxlite/litelogin
  

Minimum "Documentation" Requirements for README.md

You may see this and say "woah! That's a majority of the repos in your list!" and sadly this is true. Though I have very basic requirements for the README.md file of all repos.

• A short description of the applications' function.
  
• A screenshot or two, depends on what the application is I suppose.
  
• A list of Depends
  
• there is no arguing here, it'll make the job of future devs easier!
  
• An Alphabetically sorted, bulleted list of authors.
  
• Credits
  

for an example of this, see the lite-updater repo. https://github.com/linuxlite/lite-updater

Belongs somewhere ELSE

A list of repos/software that is not in the "correct" location.

• Lite Upgrade https://github.com/linuxlite/liteupgrade <-- shouldn't exist anymore in my opinion
  
• Lite Tasker https://github.com/linuxlite/litetasker
  
• Lite Projects 2.0 <-- This is what milestones are for in github https://github.com/linuxlite/liteprojects2.0
  

Clean up "Abandonware"

This section is for stuff I don't know whether LL uses anymore, that should be cleaned up.

• laughing-avanger https://github.com/linuxlite/laughing-avenger
  
• Lite Backup https://github.com/linuxlite/litebackup
  
• Lite Time https://github.com/linuxlite/litetime
  
• Lite Boot Screen https://github.com/linuxlite/litebootscreen
  

[Teddy]

Jesus Christ dude! Let Jerry and the team do what they want to do. It's their github account. Who are you to say what they should do. It isn't your project. Get over it. Be at least a *little* thankful that the team is taking time away from their families to develop this distro for the benefit of the community. Seriously!

I understand your intentions of trying to improve upon the development process, but there is a clear line between friendly suggestions & improvements, and elitist demands & personal preferences. This leads more toward the elitist side, and organization is a personal preference thing, for the most part. However,  some of the improvements you mention are definitely worthwhile to implement in the future. Brutally criticizing the Lite team isn't going help the project, or help get those problems fixed.

If you want to improve for them & join the team, by all means, DO IT. You'll be helping a great cause for a great purpose.

¿If any moderators/admins are reading, close the thread for further discussion, maybe?

Typed & Sent from my Samsung Galaxy Note 3 [SM-N900T] using the Tapatalk Android app.

[shaggytwodope]

Jesus Christ dude! Let Jerry and the team do what they want to do. It's their github account. Who are you to say what they should do. It isn't your project. Get over it. Be at least a *little* thankful that the team is taking time away from their families to develop this distro for the benefit of the community. Seriously!

I understand your intentions of trying to improve upon the development process, but there is a clear line between friendly suggestions & improvements, and elitist demands & personal preferences. This leads more toward the elitist side, and organization is a personal preference thing, for the most part. However,  some of the improvements you mention are definitely worthwhile to implement in the future. Brutally criticizing the Lite team isn't going help the project, or help get those problems fixed.

If you want to improve for them & join the team, by all means, DO IT. You'll be helping a great cause for a great purpose.

¿If any moderators/admins are reading, close the thread for further discussion, maybe?

Typed & Sent from my Samsung Galaxy Note 3 [SM-N900T] using the Tapatalk Android app.

To be totally fair... everything you said is a personal view. Of which we should all respect. But there is nothing wrong with honestly or opinions... if you start silencing people then you be come the jerks imo.

As long as the language remains within reason, I see no need to censor people.. remember we're all about Linux and opensource. Part of which is debate and criticism.

[newtusmaximus]

  Adrian,
As a user of LL and linux newbie, I have very little to no understanding of what goes on "under the hood" All I can do is appreciate the time and effort that has been given freely to get this project off the ground and the commitment to develop “easy” path for newbies like myself to migrate to Linux.
There are always ways to improve and it is refreshing when new eyes look at what has been done and can make helpful suggestions and put their contribution to the process.
However I do think that the way it is initiated is always a sensitive matter.  Your contribution would have been more diplomatic by contacting Jerry direct and with not such a blunt  “public” approach.
The amount of work / thought you have put into your structured appraisal / critique is acknowledged (github),  and I for one hope that you can find a way to put that enthusiasm into the project, but as a team member and in a collaborative manner..
My layman's 2C worth

[AdrianKoshka]

Thanks for your feeeback! Also I want to state I do want to help with the development of Linux Lite and help fix the things I stated, and I understand it's a project done in free time. Though I still stand by what I've said. I thought the public approach would be better to be entirely honest, instead instead of keeping it "under wraps" and to a select group of people.

[Wirezfree]

In my day to day life I do Business Analysis, Project Management, Requirements Gathering et al.
There are many "standards" and "methods" for doing these things, But some times you have to deviate from the "ideal" standards & methods.

Everybody will have an opinion on what is, what isn't the best/right way to move forward, in this case LL Development/Management.

As an outside observer(and user) of LL I'm not "technically" qualified to comment on is it being done correctly.?
What I can say, "as a user of LL" is what ever process is being used appears to be working...
I would hate to see LL get bogged down, stumble just because it "appears" to be not following a certain way of doing things.

Ultimately it's down to the owner & developers of LL to make the "right call"
Do they feel comfortable in their methods/approach, and what are the risks.?

Just my 2p/c worth...

[valtam]

I will be commenting on this thread, but only after the community has had their say, so that I don't appear to influence anyone's point of view. Cheers.

Sent from my Nexus 6 using Tapatalk

[shaggytwodope]

In my day to day life I do Business Analysis, Project Management, Requirements Gathering et al.
There are many "standards" and "methods" for doing these things, But some times you have to deviate from the "ideal" standards & methods.

Everybody will have an opinion on what is, what isn't the best/right way to move forward, in this case LL Development/Management.

As an outside observer(and user) of LL I'm not "technically" qualified to comment on is it being done correctly.?
What I can say, "as a user of LL" is what ever process is being used appears to be working...
I would hate to see LL get bogged down, stumble just because it "appears" to be not following a certain way of doing things.

Ultimately it's down to the owner & developers of LL to make the "right call"
Do they feel comfortable in their methods/approach, and what are the risks.?

Just my 2p/c worth...

Sorta reminds me of https://xkcd.com/927/ lol

[nomko]

Jesus Christ dude! Let Jerry and the team do what they want to do. It's their github account. Who are you to say what they should do.

And who are you to silence other's when they express their opinion and/or personal view?

To AdrianKoshka:
As this is more a personal experience and/or opinion and/or personal view it's good to see that you took the time to write down your comments. Just a hint, next time don't add all those big bold lines as it looks like you're shouting. I think some might be worth looking at by the LL team. Other's might come down as just a personal experience.

As i learned over the years, Linux will never come in a package and configuration you like and want. Some users distro hop for months experimenting with any distro out there before they can choose the distro that meet their requirements the closed. As i'm used to Linux Mint, i feel that some good options the Mint team added in the Linux Mint distro is completely missing in Linux Lite, and visa versa. I'm using LL since some time but it shoot me back into learning mode while with Mint i was an experienced user. Every distro has it's con's and pro's, it's up to you to decide which distro suits your needs the most.

[AdrianKoshka]

In my day to day life I do Business Analysis, Project Management, Requirements Gathering et al.
There are many "standards" and "methods" for doing these things, But some times you have to deviate from the "ideal" standards & methods.

Everybody will have an opinion on what is, what isn't the best/right way to move forward, in this case LL Development/Management.

As an outside observer(and user) of LL I'm not "technically" qualified to comment on is it being done correctly.?
What I can say, "as a user of LL" is what ever process is being used appears to be working...
I would hate to see LL get bogged down, stumble just because it "appears" to be not following a certain way of doing things.

Ultimately it's down to the owner & developers of LL to make the "right call"


Do they feel comfortable in their methods/approach, and what are the risks.?

Just my 2p/c worth...

I can totally agree with you. Thanks for the feedback!