[manjaro-dev] my report on the mate basic image

kendell clark coffeekingms at gmail.com
Fri Dec 16 20:26:23 CET 2016


Got it. I'll save these instructions so I can look at them. So basic 
first, then full. This means I'll build a mate basic image and burn it 
on a flash drive after I test the mate full image I've already built. 
Completely agreed, basic means basic, not a lot of other stuff. If that 
doesn't work it doesn't matter how much extra stuff you cram in if what 
it's designed for doesn't work.


Kendell Clark

On 12/16/2016 1:01 PM, Philip Müller wrote:
> Hi all,
> maybe you guys didn't got my proposal on how Manjaro-Developers fix
> ISO-Profiles when doing a new profile or recreate it from scratch.
> That is exactly why some developers don't get it. We have different ways
> to create stuff. Developers with sight use branches and pull requests
> and review the code before it gets merged line by line and discuss them
> first a lot. This results in better quality. Only if at least two other
> developers than the author approve it, we merge it normally.
> Then there are the core developers originally working on the tools and
> such. In the development phase you can just commit all your changes and
> fix them on the go as you wish. Then, when it is considered stable we
> create a new branch and go on with bugfixes using the pull request
> approach when needed. However at least another core developer checks the
> codes afterwards.
> That out in the open we agreed to help you guys out. We saw a lot of
> caveats with your code, so Stefano stripped it down and removed all the
> nonsense. Then he started to fix the basics and asked you just to review
> it and report back your findings. We never asked you to change any code.
> That will be done by Manjaro developers first until we have a solid base.
> We use always the basic profiles first for development. The full images
> are only the same with additionally added applications. The basic images
> always include the minimalistic desktop with basic features and not
> extra applications and eye candy.
> So we had the issue with 'Thus' not working, which was a major issue for
> you guys. Then we had some issue with key-binding and orca not starting.
> Good. At least in the live session we have fixed that.
> Next step would be to install it on real hardware and review the missing
> points and issues given with that fact. Then we pick one or two issues
> and prioritise them. We will work then together on these to get them
> solved. Only when all the showstopper bugs are gone we decide on which
> applications may be useful or we still have missed.
> So please, review the given profiles as they are without code changes on
> your own and point out what should be fixed first. We dedicate some time
> for you guys, so we also don't want to waste it.
> If we don't get to an agreement on it soon we are sorry and have to move
> on without Sonar using Manjaro as base.
> I hope this approach is to everybody clear now. If we make it before
> Christmas we can't tell, as Sonar doesn't have yet any high priority
> from Manjaro Development point of view. That is why Stefano, a community
> maintainer invests some time on it and I support him if I find some free
> time. He is lead and what he tells should be accepted.
> Some issues are so complex, that they might need somebody who works with
> the new tools more often than you guys did in the past couple of month.
> Sometimes the issues are logical and easy to solve. Before changing
> something, ask for advice. Maybe there exists already an solution.
> greez, Grumpy Phil
> _______________________________________________
> manjaro-dev mailing list
> manjaro-dev at manjaro.org
> http://lists.manjaro.org/mailman/listinfo/manjaro-dev

More information about the manjaro-dev mailing list