A thing or two could be said about the system-model. - Wow, your system is set up exactly the way I like. Can you please email me a list of all the programs/packages you've installed? - I'll do you one better... Here's my system-model. Just replace yours and sync!
It could be argued that Fedora is the hardest of all the big distros to get programs into (PPA in Ubuntu, buildservice in opensuse and so on) and making sure that Foresight is a distro for "grown-ups" (who don't have the time to reinvent the wheel every time they need to access Lync in Pidgin or whatever, accessing a Citrix server at work, want to Skype or listen to Spotify and so on) with stability in mind that don't want to run Windows would go a long way. :-) 2 april 2014, Mark Trompell <[email protected]> skrev: > On Wed, Apr 2, 2014 at 9:57 AM, Roger Karlsson <<[email protected]>> wrote: > > Hi Martin! > > > > If I were in the audience I guess I would have a hard time grasping all > > that information in a short while and would therefore more probably ask > > something about Foresight than the underlying technology. > > One question that might pop up is why we choose to go from an indipendent > > "Because your distro should be cool" distribution to a Fedora respin? > > Another possible question is how an end user would/could notice the > > differens between runnig Fedora and Foresight? More questions on the "user > > level". But then again, I'm only guessing... > > > > Well that is especially in the first time where foresight doesn't > differ that much a tough question. > The reason to base on fedora is mainly manpower. We don't have a lot > of devs. So we drop parts of the stack others can do better. Why build > all the lowlevel stuff like kernel, systemd, xorg/wayland, mesa > ourself. > redhat/fedora people are pretty good at that. > Probably we would do only minor tweaks on gnome/kde and xfce too but > it's well possible to build native conary packages on top of the > encapsulated fedora. And I'm pretty sure it will happen. > So we will start as a pure encapsulated fedora with some artwork > trademark tweaks. But that's not where we want to stop. > Actually in the end if we do it well we could even replace the whole > underlying stack with our own custum built one (if done with caution). > So our aim is not beiing a fedora respin, but using fedora as a > platform to work and build on. Using as many upstream fedora as we > want. > Actually right now in fl2 we use parts of some other distributions > too. Our kernel reuses a lot of fedoras srpms (That is all pathces > they have). At times (and maybe still, I need to check) Our Xorg was > built from Suse srpms. We are quite flexible there. > The essence is: We use a base that is stable and alive, already close > to how foresight was built (filesystem wise) and build on that to > concentrate on the things we like. Building a Desktop distribution > with conary. > > > > > // Roger > > > > Mark > > > > 2 april 2014, Martin Bähr <<[email protected]>> skrev: > > > why conary is interesting in itself is a separate topic that i'd like to > > > frame > > > more as "why do we want to use conary on top of fedora instead of just > > > using > > > fedora as it is" > > > > > > this should not be about conary features. but about benefits that come > > > from our > > > work to fedora as a whole, even if they don't use conary: > > > > > > here is what i have so far: > > > > > > * the process finds bugs in fedora and fedora packages that we report > > > back. > > > we could use this on rawhide to test packages before they are released. > > > > > > * conary finds more dependencies and can ensure that all dependencies are > > > met. > > > these can be reported to improve fedora packages. > > > > > > * conary keeps all packages in revision control, so every version of every > > > package released will remain available for the future. this helps server > > > users who need to downgrade individual packages after an upgrade broke > > > their > > > server. (this issue is currently being discussed in the Fedora Server WG) > > > > > > any others? > > > > > > can we make a list of issues reported? > > > > > > mkj: could you possibly share some email conversations you had about bugs > > > you found. > > > including current fedora but also centOS since some issues there may have > > > made > > > it into fedora as well. you can send that to me privately. > > > i'd like to make a picture of things reported. and what impact that had. > > > not > > > really listing them in the talk, but give an overview of maybe how many > > > issues > > > were found and what classes of issues those were and possibly mention an > > > example or two. > > > > > > greetings, martin. > > > > > > -- > > > eKita - the online platform for your entire academic life > > > hackerspace beijing - <<http://qike.info>> > > > -- > > > chief engineer eKita.co > > > pike programmer pike.lysator.liu.se caudium.net societyserver.org > > > BLUG secretary beijinglug.org > > > foresight developer foresightlinux.org realss.com > > > unix sysadmin > > > Martin Bähr working in china <<http://societyserver.org/mbaehr/>> > > > > > > _______________________________________________ > > > Foresight-devel mailing list > > > [email protected] > > > <<https://lists.foresightlinux.org/mailman/listinfo/foresight-devel>> > > > > > > _______________________________________________ > > Foresight-devel mailing list > > [email protected] > > <https://lists.foresightlinux.org/mailman/listinfo/foresight-devel> > > > > > -- > Mark Trompell > > Foresight Linux Xfce Edition > Cause your desktop should be freaking cool > (and Xfce) > _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
