YaST2 for Debian (aka nYaST)
Good morning Abstract: I search a person (or more than one) who is interested to port Yast2 from Novell/SuSE to Debian. I'd like to spend some money and/or hardware for this task (I can't spend that much because I'm a student who lives from grants) and perhaps some organizational help. Longer version: I like or better love Debian but Debian still lacks some features to become a good desktop distribution. One thing is an admin tool. There are other tools in development for this task (KaST [1], DControl [2], etc.) which I don't want to substitute with YaST for Debian but to complete. Because Yast2's source code become free for some time now I see a chance to port a well-known (by new users) tool to my preferred distribution. But my programming skills are too poor and so the only thing I can offer to bring YaST2 to Debian is some money or hardware and organizational help. This (or a similar) email goes to the following mailinglists (I'm subscribed to all of them): - debian-desktop [3] - debian-devel [4] - kalyxo and kalyxo-devel [5] & [6] - debian-cdd [7] If you think there are other lists which could be valuable please forward this mail to these lists. So if you're interested and have the skills to port YaST2 to Debian, contact me. But please, first read the following tasks or levels. For the work or porting of YaST2 I see the following levels: 1. Contact me (by private email or mailinglist) and tell me something about your intentions and skills (and work you've already done for e.g. Debian). 2. Clarification about the license of YaST2 and it's location on the web. See if Novell/SuSE is interested to contribute or at least help to port Yast2 (make it more portable and widely used => becoming an industry standard). 3. Look into the source code to see what work needs to be done. Amount of the work. Say me how much money or hardware or help do you expect from me. Can YaST2 work with Debian even if you change some conf files by hand? 4. Port YaST2 to Debian. 5. Maintain and enhance YaST2 for Debian. And here a last thing: I'm not interested in a discussion about the sense of this work (but nonetheless you can discuss this ;-) but in the search of skilled people to work on this tasks. Thanks and greets Mario [1] http://www.kalyxo.org/twiki/bin/view/Main/KaST [2] http://wiki.debian.net/index.cgi?DebianControlCenter [3] http://lists.debian.org/debian-desktop/ [4] http://lists.debian.org/debian-devel/ [5] https://mail.kde.org/mailman/listinfo/kalyxo [6] https://mail.kde.org/mailman/listinfo/kalyxo-devel [7] http://lists.debian.org/debian-custom/
Re: YaST2 for Debian (aka nYaST)
Am Sonntag, 7. November 2004 15.32 schrieb Jaldhar H. Vyas: Good morning First of all. The further discussion for the porting work will be consolidated on the debian-desktop lists only. > > Abstract: > > I search a person (or more than one) who is interested to port Yast2 from > > Novell/SuSE to Debian. I'd like to spend some money and/or hardware for > > this task (I can't spend that much because I'm a student who lives from > > grants) and perhaps some organizational help. > > Dear Mario, > > I was until recently the Debian maintainer of webmin/usermin. I have > filed an ITP (Intent to Package) for Yast2. And I intend to look into it, > the hold up at the moment is I am expecting the birth of a baby boy almost Oh, that's nice. And that's more important than some software. I wish you and your wife all the best for the birth of your baby boy. > any day now. Certainly financial help would speed things up a little but > thats the main block. > > The first time I brought this up there were concerns about the license > iirc but according to a Novell rep I talked to once, they do intend it to Which Novell rep? I thought the license of YaST2 is the GNU GPL. > be used by other distros so we can hopefully count on them to help resolve Good to here. I hope they are interested in code to make YaST2 more portable. > any problems. I doubt if they would contribute any money though but > asking is worth a try. That's the same way I think. > It's going to take a _lot_ of work to adapt yast2 to Debian, more than > just tweaking a few config files. Ok, but what means "a _lot_ of work" in a timely fashion: - One-man-year? - A few weeks of hard work? I think, YaST2 is quite modular. This way the porting could be in levels. Say, first the skeleton/framework and then the single modules. So we could show something working relatively soon? > > This (or a similar) email goes to the following mailinglists (I'm > > subscribed to all of them): > > - debian-desktop [3] > > - debian-devel [4] > > - kalyxo and kalyxo-devel [5] & [6] > > - debian-cdd [7] > > We should probably consolidate discussion on, say, debian-desktop. See above. Thx Mario
KDE4stable - a proposal
Good morning I hate double made work. But I love debian and I love KDE. The only problem is that Debian stable has an outdated KDE version after some time. The solution is backporting the current KDE version to Debian stable. It's done by different projects (see below) and different projects need a backport of the current KDE version. So why shouldn't we join forces and work together on a backport of KDE for Debian stable (and derivate distributions). My proposal follows now in less and more detail. Short version: -- Lets cooperate with the backport of current KDE. Create an alioth [1] project with a mailinglist, a repository (debian packages and svn) and some FAQs. More details: - Here are some more ideas: - Some releaseplan: -> make quickly first packages (together with the Debian KDE/Qt Team and Kubuntu team) (State: unusable) -> announce workable packages (State: testable) -> declare them stable for productive use (state: usable) (States similar to stable, testing and unstable. This way the user sees the state of the packages at once.) - Provide security support for the packages declared 'usable'. - We restrict on some architectures (i386, amd64, powerpc, ...) - We garantee a smooth migration path to the next stable version of Debian (i.e. the backported KDE version should always be a version less than the version in Debian testing/unstable). - Additional backport of further KDE applications. Future perspective: --- Debian Etch will probably released with KDE 3.5.x and not KDE 4.x. So if we have to infrastructure we could shortly after present a Debian stable etch version with the current KDE. I'm (and surely others too) interested in your opinion and if you like to work with us. And last but not least, here are some information about me: Primary school teacher, student in education and computer sciences. Longstanding Debian user and trying to give something back (e.g. DDTP translations and YaST4Debian [2]). My best skills are not (yet) programming but coordination, documentation and organisation. Why specifically this mailing list (different in each mail)? I choose this list and set the Reply-To: to it because it's the central point of Debian development. This mail is sent to the following mailing lists: - - http://lists.debian.org/debian-devel/ -> main Debian development mailing list - http://lists.debian.org/debian-qt-kde/ -> mailing list of the Debian KDE/Qt Team - http://lists.debian.org/debian-edu/ -> mailing list of the Debian Edu/Skolelinux project - http://lists.dccalliance.org/mailman/listinfo/dcc-devel -> development list of the DCC Alliance (with members like Linspire, Knoppix and Progeny) - https://mail.kde.org/mailman/listinfo/kalyxo-devel -> development list of the Ekhis/Kalyxo project - http://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -> development list of the Kubuntu distribution Reply-To: is set to debian-devel@lists.debian.org Possible next steps: - If there is some possible feedback to this mail I'll request for an alioth project and setup a short FAQ and mailing list. - As the release of KDE 3.5 is imminent we could together start with the packaging work of KDE 3.5 (based on the work Last not: I don't intent to steal some work of any project but I think we could join the forces which would facilitate a lot. I appreciate all the work you all do! I wish you all a good week Mario [1] http://alioth.debian.org [2] http://alioth.debian.org/projects/yast4debian PS: I'm subscribed to every mailing list I'll post this message to. So it's not necessary to CC: me. PPS: Sorry for the unperfect english ;-). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mplayer 1.0pre7
Am Dienstag, 26. April 2005 01.29 schrieb Jeroen van Wolffelaar: Morning Thanks for your explanations and don't take my mail as rant, it's just a question. > On Mon, Apr 25, 2005 at 04:34:41PM +0200, A Mennucc wrote: > > mplayer 1.0pre7 is ready and packaged at > > http://tonelli.sns.it/pub/mplayer/sarge > > > > a. > > > > ps: still no news from ftpmasters... hope they at least will try to read > > http://people.debian.org/~mjr/mplayer.html [snip] > - Patents: The big issue with mplayer a.t.m. I'm myself not very > following the patent stuff, but as far as I understood, certain > patents hold by the MPEG organisation, esp. those w.r.t. encoding of > MPEG data streams, are actively being enforced, (again afaik) in the > United States in particular. See [1] for more information of what I > believe is relevant here. Unfortunately, links there mostly either > shine in unavailability (404 etc) or utter vagueness and > non-information (I couldn't find any bit of useful patenting > information at [2], for example). The FFII had more useful information > at [3]. > > All this seems to concentrate on MPEG-related *encoding* though, and > not to decoding. Moreover, Debian contains plenty of MPEG-related > decoding software, and the FTP-master policy at least w.r.t. audio > MPEG decoding has always been to not let supposed patents in this area > stand in the way of distributing this software, on the basis that it > seems to be an unenforceable patent, or at least, it isn't enforced > (and giving in to any patent would mean Debian could not distribute > anything). I see no reason why MPEG videa decoding would be different in > this respect, again, to the best of my knowledge. > > So, adding these two tentative[4] conclusions together, it seems > likely that if mplayer were demonstrated with reasonable certainty to be > free of MPEG-encoding code, it would be acceptable for inclusion in > main as far as the FTP-masters are concerned (note: We're not (yet?) > saying it's *required* to strip MPEG encoding stuff, but in my personal > opinion, it seems likely that this is what it'll turn out to be. Don't > take my words on too much value though, maybe stripping this won't be > required after all, but in any case, if it isn't there, we don't need to > think/discuss about it -- reinclusion of the encoding stuff can then > later separately be discussed). But what is the difference of mplayers encoding capabilities to ffmpegs encoding capabilities (from it's description: "encoding formats (MPEG, DivX, MPEG4, AC3, DV, ...).") which is in unstable and testing? [snip] thx for all your work Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rekall for Debian ?
Am Mittwoch, 4. Mai 2005 13.08 schrieb Michelle Konzack: Morning > > On Wed, 4 May 2005, Michelle Konzack wrote: > > >does anyone know, whether there is a > > >Debian Package for Rekall or not ? > > > > There seems so: > > > > $ apt-cache search rekall > > rekall - graphical database front-end ^ > Strange, I was searching with > > apt-cache showsrc knoda recall kexi ^ > and gotten only results to "knoda" and "kexi" See that recall and rekall aren't the same thing. griits Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Results of the meeting in Helsinki about the Vancouver proposal
Am Sonntag, 21. August 2005 03.58 schrieb Wouter Verhelst: > Hi all, Good morning Most of the time I only read on this list and so I've done with this discussion. But sometimes I dare to write something and suggest somthing ;-) (see below). > Initial: > - must be publically available to buy new > - must be freely usable (without NDA) > - must be able to run a buildd 24/7 without crashing > - must have an actual, working buildd > - must include basic UNIX functionality > - 5 developers must send in a signed request for the addition > - must demonstrate to have at least 50 users > - must be able to keep up with unstable with 2 buildd machines, and must > have one redundant buildd machine > > Overall: > - must have successfully compiled 98% of the archive's source (excluding > arch-specific packages) > - must have a working, tested installer > - security team, DSA, and release team must not veto inclusion > - must be a developer-accessible debian.org machine for the > architecture > - binary packages must be built from unmodified Debian source > - binaries must have been built and signed by official Debian > Developers It seems that a lot of people discuss this topic on a fairly theoretic base which I think wouldn't be necessary if one could see which architectures pass which condition. Then you could discuss about specific items and not just theoretically (which is not by definition bad). I think the work for such an architecture list isn't that heavy and would even do it myself but I'm just a user and "promoter" of Debian and don't know the sites where I find the information. Anyway thx for your great work I use every day Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#331072: ITP: cinelerra-cvs -- non-linear video editor and compositor for Linux.
Am Samstag, 1. Oktober 2005 15.31 schrieb Kurt Roeckx: Morning > On Sat, Oct 01, 2005 at 03:05:08PM +0200, Riccardo Setti wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Riccardo Setti <[EMAIL PROTECTED]> > > > > > > * Package name: cinelerra-cvs > > Version : 2.0-cvs > > Upstream Author : > > * URL : http://www.example.org/ > > * License : GPL > > Description : non-linear video editor and compositor for Linux. > > > > Cinelerra, the first Linux based real-time editing and special effects > > system is a revolutionary Open Source HD media editing system. > > You know there has been an RFP on cinelerra itself for a very > long time, almost 5 years. See bugs.debian.org/78209, 156614, > 239570. > > Why do you want to have a CVS version from the package if there > even isn't a normal version of it in the archive? cinelerra-cvs is not really a cvs version but a version of cinelerra with is targeted at new users and not professionel video cutter. > Kurt Hope to help Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the Debian Installer team
Am Mittwoch, 24. Dezember 2008 schrieb Michael Tautschnig: Good morning > [...] > > > - New features: > > [...] > > > support for realtime mount options > > I think this^ was meant to be "relatime", and it is a single mount > option. Yes. Sorry it's my fault. I thought it was a typo and changed it in the wiki. Sorry. > [...] > > Thanks for the great work, > Michael Thx for Debian! Mario a user -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#652433: ITP: v3c-qt -- v3c/automake wrapper for QT
Am Samstag 17 Dezember 2011, 07.10:06 schrieb Philip Ashmore: > Package: wnpp > Severity: wishlist > Owner: Philip Ashmore > > * Package name: v3c-qt > Version : 0.7.0-01 > Upstream Author : Philip Ashmore > * URL : http://sourceforge.net/projects/v3c-qt/ > * License : LGPL > Programming Lang: m4 > Description : v3c/automake wrapper for QT I think this should be "Qt" (for the Qt Framework from Nokia) and not "QT" for Quicktime? And yes I saw that's wrong upstream (see URL above) as well. thx Mario -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112171725.56980.debian...@unormal.org
Diploma thesis about media choice and usage in Free Software communities: I need your help.
Dear Free Software contributor* I'm currently in the process of writing my diploma thesis. I've worked hard during the last few weeks and months on a questionnaire [1] which shall collect some data for my thesis. Furthermore the data of this survey will be interesting for the Free Software communities as well. So please take some time or add it to your todo list or, even better, go directly to my questionnaire [1] and help me make a great diploma thesis and improve the Free Software community in some ways. The questionnaire [1] takes some 20 to 30 minutes. At the end of the questionnaire you'll find a way to participate in a draw where you can even win something nice. In a first round I got the feedback that the length of the questionnaire [1] and that some questions (mostly the ones at the beginning of the questionnaire about the 12 different tasks) are quite abstract and difficult. But please try it, try your best and take the time and brain power. The remaining part of the questionnaire [1] (after these two pages with the tasks questions) is quite easy and quickly done. And you have the possibility to come back to where you have left filling in the questionnaire [1] after a shorter or longer break. And if there are any questions, feedback or you need help don't hesitate a moment to write me an email or ping me on IRC (freenode.net and oftc.net) as unormal. This survey will be open till Sunday, the 9th of March 2014, 23.59 UTC. Thanks to all for reading and helping and towards the summer of 2014 you can read here what all the data you gave me showed us and where we can learn and improve. Thanks in advance and best regards Mario Fux [1] http://survey.kde.org/index.php/783182/lang-en * By contributor I mean not just developers but translators, artist, usability people, documentation writers and many more. Everybody who contributes in one way or the other to Free Software. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201403011518.13208.debian...@unormal.org
