Debian and software patents (Was: Re: how to donate free program for Debian?)
Qua, 2007-01-31 às 09:21 +0100, Martin Schulze escreveu: I seem to recall Keving mentioning a patent minefield, which I would interpret not only as an area of computer science in which several patents exist but also that they are tried to be enforced. If this is the case, Debian should be careful. See the mp3 encoder issue, Debian hasn't been challenged by the patent holder but still it doesn't distribute them instead of ignoring the patents as your text would assume. You know, this is something I've been thinking for some time... There are places where software patents are not valid and cannot be enforced (Brazil being one of them, for instance). Isn't it time to think about a non-epatents repository hosted in one of this places? daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is it time for non-us again?
Hi, I was backlogging debian-devel today and I found this: [..] Maybe this is because of the increased pressure now that software patents are now being enforced and so on. At the beginning they seemed to just chuck in whatever. (Andrew Donnellan [EMAIL PROTECTED])[1] And I was just thiking that not all the world is inside this patent-crazyness. In Brazil, for instance, software patents doesn't apply and aren't enforceable. It's a pity to have software not being included into Debian because of us-nonsenseness of software patents... And this makes me ask... Isn't it the time to recreate the non-us section? Daniel [1] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is it time for non-epatents (Was: Re: Is it time for non-us again?)
Qua, 2006-10-04 às 14:04 +0200, Pierre Habouzit escreveu:
Le mer 4 octobre 2006 13:25, Daniel Ruoso a écrit :
Isn't it the time to recreate the non-us section?
no, at least not for patent issues. we would need a debian-${COUNTRY}
rather than a non-US if we begin to take that into consideration.
Ok, but this doesn't get to the point... So...
Isn't it the time to create a non-epatents repository hosted at some
place where software patents doesn't apply?
daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On-going anthropologic research about Debian
Hi all, It's been two years since I started to look at Debian with social scientist eyes, and now I started to produce the report of the research. As I live in Brazil, the text is currently being written in Portuguese, but I'm already translating it to english as the time passes (with the help of some perl scripts to provide a gettext-like translation tool). Well, I just finished translating the first section of the work (still metodological, not exactly debian-related) and I would like to know other's opinion on the matter, specially because of some choices I made in the research, that are explained in this first section already translated. The research is being developed in a G-Forge-based site called codigolivre.org.br (freecode, in english) and is licenced under the GNU GPL. The sources of the research are LaTeX and available at project's CVS. The translation is being made using a file I called transml which basically is an XML containing (translate filename=fileporigisto/origtransthis/trans/p/translate) and works just like gettext. You need latex, abntex, latex2html, perl, make, ps2pdf, dvips and the script in #367114 to build the binaries the way I do (there's a Makefile to automate everything). The website of the research is at (the text in english is at the end of the page) http://antropologia.codigolivre.org.br/ The already translated section is available as HTML also (latex2html output): http://antropologia.codigolivre.org.br/debian/en/node2.html#SECTION0021 Well, the research is free, and I'm accepting patches :)... daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About expulsion requests
Em Seg, 2006-04-10 às 21:30 +0200, Sven Luther escreveu: On Thu, Mar 16, 2006 at 03:51:19PM +0100, Christoph Berg wrote: I know that having codified expulsion procedures is tempting to use them, and I do think that they are a good thing to have. But please consider one thing when you think about invoking them: [1] As someone who wasd recently the target of one of those expulsion processes, i believe that what you propose is not enough. Sure. Let's just drop this procedure. It did us no good. I trust more the non-formal regulations inside Debian than this kind of formalism... daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: uol.com.br and petsupermarket
Em Seg, 2006-03-13 às 14:12 -0600, Matthew R. Dempsky escreveu: On Mon, Mar 13, 2006 at 02:19:55PM +1100, Anand Kumria wrote: That means that as of now, uol.com.br are now considered spam addresses and anyone with that address (uol.com.br) has now been unceremoniously unsubscribed[1]. I am still receiving those obnoxious messages in response to my posts to debian-user. I should recommend not blacklisting the entire .+uol.com.br addresses. This is one of the biggest ISP in Brasil, it can cause a lot of harm to just blacklist it. This anti-spam feature is optional. Only some lo^H^Husers uses it. I would recomend sending a private message for those who have this stupid antispam asking them to remove or just killfile him or disable him from receiving messages until he remove this crap. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian UK (was Re: What the DFSG really says about trademarks)
Em Sex, 2005-09-02 às 18:38 +0100, MJ Ray escreveu: Steve Langasek [EMAIL PROTECTED] wrote: Why should *charities* get special consideration, anyway? Being a charity doesn't automatically make them aligned with Debian's goals. Indeed, which is why debian should reach consensus before they trade. I think charities should get some special consideration because law enforces some level of openness and honour not required of other organisations. I must remember that you're restrictive to UK law. In Brasil, for instance, there is no such thing as charity organization. We have NGO's which are simply civil associations, not-for-profit, in general. If a NGO fullfill a set of requirements, it can be certified as a Civil Organization for the Public Interest (OCIP), which means that it can receive gov's money, and just that. So, a NGO (even a OCIP) is allowed to trade things, because the question (in the brazillian sense) is if there is profit or not. I mean, selling something for a value greater than the cost is *not* profit. Profit (in the brazillian sense) is the value that is shared among share-holders after the balance. So, let's not stick to country-specific laws... daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian UK (was Re: What the DFSG really says about trademarks)
Em Seg, 2005-09-05 às 21:31 +0100, MJ Ray escreveu: Charity is not country-specific. At the very least, Japan (according to JACO) and Canada (CharityVillage) also have charities with similar conditions of openness to the UK. Well... That's not true for Brasil, and may be the case for other countries too. DUS is not registered as a charity, so just like organisations in a country with no charity concept, it could use one of the other ways I mentioned. So, are we going to stablish the criterias for organizations to have the right of using the Debian name? Like a type of fair-use? It can be a good idea... something like... Organizations that follows x,y,z will have an automatic license of using the Debian trademark... ... but ... I'm just remembering that if we say charity, we'll have to say... * In UK, charity organizations * In Brasil, Civil Organizations for the Public Interest and so on... And this could be a bigger problem for informal organizations, like user groups around the world... ... so ... Couldn't we just avoid the problem by acting reactivelly? I mean, do you really think that DUS is not a fair-use of the Debian trademark? Do you realize that it will impact all user groups around which uses the Debian name? Same rules should apply to all. Agreed? Yes! That's all I'm saying, and that's what worries me. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian UK (was Re: What the DFSG really says about trademarks)
Em Qui, 2005-09-01 às 13:53 +0100, MJ Ray escreveu: I think there are reasons to dislike it, not enough to act on: * DUS was developed at a meeting for another purpose and just announced to those (is Cambridge the new Vancouver?). * It has a very weak link to the debian project. * Its leadership discourage and belittle democratic control - it looks like bureaucratic empire-building, to maximise the number of members but have none of the responsibilities. * Opt-out membership associations seem a very shady practice - can anyone clearly opt-out without DUS recording personal data? * Its beer-mat constitution does not cover some basic points. * I doubt the will/ability of DUS to follow regulations. * I don't like donations marked debian endangered. * I'm not a fan of bureaucracy or hierarchy, nor do I see the benefit of them for DUS. * I don't like DUS carrying on business as Debian-UK. * DUS leaders and members suggest things are lies when they are actually either different opinions or true. I see nothing on this that can be considered a Debian (as The Debian Project) problem, it's an internal problem of the Uk Debian Fellows Group (as groups around the world, which has their internal problems too), except for: * I don't like DUS carrying on business as Debian-UK. So, are you suggesting that every group around the world, such as debian-br, which does sell branding clothes and other stuff should take a different name? daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {SPAM} Re: Debian Core Consortium
Em Dom, 2005-07-24 às 10:44 -0500, Ian Murdock escreveu: But I don't see anything in here that's incompatible with what we're doing--for one, this isn't a business (it's not even really a consortium, since there won't be any formal organization behind it--the best way to describe it is that it's an open-source project). I have a little question... Even if this organization is called Debian Core Consortium, it *is* referring to Debian itself, isn't it? Maybe I'm just missing the point, but... Wouldn't I be allowed[1] to create a Debian Users Consortium? daniel [1] I'm not sure if it's written correctly, sorry... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thinking about (mis)use of -private
Em Ter, 2005-04-05 às 10:37, Michael Banck escreveu: On Tue, Apr 05, 2005 at 04:59:46AM -0700, Steve Langasek wrote: On the contrary, I think a mail intended to reach all developers is the *definition* of an announcement (wrt d-d-a). Also, there's a difference between 'Every DD should/must read this' and 'I'd like to reach every DD'. We want DDs to read d-d-a with high priority (even the less active ones), so I suggest only important be posted there. That's the concern more people seems to have. Many of the off-topic messages in -private are in the limbo between d-d and d-d-a. I made this confusion once, and it's pretty common to see this happening on -private. Maybe I'm having a wrong impression, but I do think the reason for most of the misuse of -private is related to this. The issue with -devel being too high traffic and off-topic is of course still there; That's something important. the GNOME dudes seems to somehow manage that by making up new lists and more recently to vigorously silence non-developers when matters get off-topic. Silence off-topic threads is a suggestion that was already considered in debian. Maybe it's not a bad idea. However, this implies that all developers are reasonably discussing on the devel list, which may be true for GNOME (most of the time), but less so for Debian :-/ Yeah, mostly because the too-high-traffic on -devel, i think. In this way I thought about a moderated list to ensure a lower traffic. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thinking about (mis)use of -private
Hi, I was recently thinking about the misuse of debian-private mailing list, and I saw that most of the bad-uses of -private were made with the intention of reaching all developers. Is this wrong? Yes, and no. The question is that debian-devel has too much traffic and it's difficult to follow all the threads, so often some messages are not read by most developers (not by lack of interest, but just because the message was not seen because of the traffic on -devel). On the other side, d-d-a is a list which has a very low traffic, and certainly almost every developer see the posts in d-d-a, but... not every email that intends to reach all developers is appropriate to d-d-a since it's not allways an announce. So, thinking about all of this, I have a question... Isn't a public mailing list (with public logs), but moderated to @debian.org posters, a possible solution to the current misuse of debian-private? daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Use of -private archive
Hi, [I've sent this to -private before, but then I realized it was off-topic for -private (thanks, mj)] Disclaimer: First of all, I'd like to say that I didn't use the archives, and that I won't do it if any objection is made. The email itself: As some may know, I'm starting to develop a sociologic/anthropologic research about Free Software and, more precisely, about Debian. The object of interest in my research is the proccess of legitimation of both people and ideas inside the Debian Community. How the proccess of some idea being adopted works? Debian names itself as merithocratic, but what exactly that means? what kind of behaviour is considered good? Well, my research itself isn't the subject of this email. I'd like to ask you if I can consider using the -private archives as a source of information for my research? and if so, in which conditions? The main reason for this question is that many threads in -private shows many of the aspects of the question I'm trying to investigate, and also, many of these threads are off-topic for -private, i mean, there are a lot of emails which actually shouldn't be in -private (but I don't want to discuss about this in this thread, please keep on the question I made or start a new thread). daniel signature.asc Description: Esta =?ISO-8859-1?Q?=E9?= uma parte de mensagem assinada digitalmente
Re: Etch Release Tracking in debbugs (Was: Re: Bits (Nybbles?) from the Vancouver release team meeting)
Em Qua, 2005-03-16 às 15:03, Martin Michlmayr escreveu: * Daniel Ruoso [EMAIL PROTECTED] [2005-03-16 14:38]: Also, we don't have any pseudo package for edge or release management stuff yet, so someone has to request it (and before requesting it think about how it will be used and what we really need). That's what I'm trying to do here. But maybe I should start this discussion in -release to be more productive. Sorry, I hope my reply didn't appear as unproductive or hostile. Since your last mail was sent directly to me with a CC to the list, I thought I'd just point out that it's not me making a decision here. Hostile, no, I understood that you were saying it was off-topic for -project. Anyway, I'd personally like to see more discussion about how to use this feature before actually going ahead and using it. Sure, that's why I'm starting it even before the patch is applied on debbugs and the pseudo-package is created, because, at this time, it's just a proposal. There are the obvious use scenarios of actually using it to track real bug dependencies. I can also imagine an edge pseudo package to track some issues. Yes, that's how I see it. However, how far should this go? Should we have a bug report for *every* issue and have 'edge' depend on it? I mean, every issue that afects the release as a whole, like the example I made of init setting the locale variables at boot time. Like the examples given by vorlon (gcc 4.0, python 2.4, xorg-x11 6.8.2, apt 0.6). But I certainly don't see it depending on every RC bug in the BTS. On the other hand, we use the BTS for WNPP and I feel a specific system would be more suitable for it than the BTS (for example, using the BTS for WNPP makes it really hard to figure out when the status of a WNPP bug last changed). Yes, because the huge amount of data. The tracking made for the release would be only for major issues, issues that need qualitative information more than quantitative, that's why I see debbugs as appropriate. While I'm a great fan of proper tracking (including archival), I just wonder if the BTS is suitable, or maybe it just needs more features. This points to the other concern I have, how can we know if it needs more features if we don't have almost any release tracking (I mean, more than the reports from the release team, which are great)? For example, to keep track of tasks, it would also be helpful to have some kind of overview of the completion of a task (70% done). The BTS doesn't have this feature at the moment, maybe it should... or maybe we need some specific task tracking system. I personally haven't thought about it enough. The point I'm making is that we don't need much quantitative information, but if the release team can make comments in the issues inside debbugs, pointing dependencies, more people will know what are we waiting to be ready, and then more people (who wants faster releases) can help in the specific points holding the release. That's an important step, i think. Maybe these thoughts will lead to some discussion. I hope so, as I think this tracking (or any other tracking technique choosen) should start *before* sarge release, to make it easier to keep it on track later. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to track release status (Re: Bits (Nybbles?) from the Vancouver release team meeting)
Em Ter, 2005-03-15 às 02:15, Martin Michlmayr escreveu: Someone recently pointed the Scrum process out to me (see e.g. http://c2.com/cgi/wiki?ScrumProcess) which might have some ideas we could adopt. In any case, it's important to employ a process and tools people will actually *use*, so I'd like to see more concrete discussions of your proposed system before you go ahead implementing it. Well, as far as I could see, it's very similar to the eXtreme Programming (XP) metodology. That can be used as a reference also. http://www.extremeprogramming.org/ http://www.xprogramming.com/ http://www.jera.com/techinfo/xpfaq.html daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits (Nybbles?) from the Vancouver release team meeting
Em Seg, 2005-03-14 às 01:45, Steve Langasek escreveu: As promised earlier on -project[0], after the release team/ftpmaster team meeting-of-minds last weekend, we have some news to share with the rest of the project. I would like to congratulate the release team for the good job, but specially for something completely new for Debian, the fact that we know which are the target milestones for etch. And I'd like to suggest the formalization and tracking of these milestones in the etch's release page at Debian site. Yes, Debian release when it's ready, and know more people may know what it means. []'s daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits (Nybbles?) from the Vancouver release team meeting
Em Seg, 2005-03-14 às 14:20, David Nusinow escreveu: On Mon, Mar 14, 2005 at 02:10:45PM -0300, Daniel Ruoso wrote: And I'd like to suggest the formalization and tracking of these milestones in the etch's release page at Debian site. I've begun work on a tool to just that. If anyone is interested in helping develop it, contact me and we can work on setting up an alioth project and such. Maybe I'm a bit silly, but I do think that debbugs can handle it, i mean, creating a virtual package called etch and asigning these milestones as bugs to this virtual package. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits (Nybbles?) from the Vancouver release team meeting
Em Seg, 2005-03-14 às 14:51, Martin Michlmayr escreveu: Bugzilla has the concept of a bug depending on another bug (or bugs) which is commonly used to track release issues and progress. I think they also have nice visualization tools to show the dependency tree. Yes, I used bugzilla as a user and as a project manager and it does it very good. I do think this could be a good feature to be added to debbugs, and, actually, it shouldn't be so hard to do. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debbugs reimplementation (was: Re: Bits (Nybbles?) from the Vancouver release team meeting)
Em Seg, 2005-03-14 às 19:48, Joey Hess escreveu: Daniel Ruoso wrote: Yes, I used bugzilla as a user and as a project manager and it does it very good. I do think this could be a good feature to be added to debbugs, and, actually, it shouldn't be so hard to do. Hard enough that bug #129781 has sat unfixed for 3 years now with no reply from anyone, I guess.. I had take a look at the debbugs source code right now, and now I undestand why this bug is untouched for 3 years. Debbugs needs a rewrite from scratch, maybe using some modern technologies like, hmmm, relational databases. I think that can be done, as debbugs has so few features (comparing to another BTS around). But it's even harder to know the exact API that debbugs implements today, should a re-implementation cares just about what is described in the documentation at bugs.debian.org? P.S.: I'm not saying I am starting to rewrite it, but I'm considering... daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: Open Letter to Debian Community]
- Forwarded message from [EMAIL PROTECTED] - Subject: Open Letter to Debian Community With apt-get, you have to know exactly which packages you need to make a software system work. Let's take MySQL for example. To make it work, you need the mysql-common, mysql-server, and mysql-client packages. Technically, mysql-common will install without mysql-server and mysql-client. But it doesn't do you much good. With apt-get, you have to already know this. You also have to know the package name of any addons you might want, like graphical administration tools or Apache plugins. And yes, I was using the graphical interface to apt-get, not the command line. Ok, this email is a lot like a number of other emails about the user-frendlyness of dselect, just moving the topic for apt-get. But... Yes, there is something we can think about. We have do admit that Debian has too many packages in a way it's really hard to find something when you know a little about the software. But, fortunally there is a project called debtags[1], which address exactly this issue. The problem is that probably most people (I mean people outside Debian) doesn't even know about it, and what I am saying we can think about is a plan of having debtags as a core infraestructure of debian, just like apt is today. Maybe we could do it for etch, but maybe it wouldn't be ready at the time etch releases *if* Debian don't say debtags will be in the core infraestructure for etch, I mean, if Debian puts debtags as a priority for the next release, we will probably have the issue of package search user-friendliness, if not solved, at least better than it is today. One example of how debian could help debtags being integrated is a policy which makes the developer the responsible of tagging the packages (s)he maintains. Or even including the tag information in the control file, generating a file that would complement the Packages file, like Package-tags, or even including this information on the Packages file (the last option doesn't sound good to me). daniel [1] http://debtags.alioth.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thinking about Debian Release Process
Preface Please, I don't intend to hurt anyone. I'll try to be as polite as possible. And if you think this subject may make you angry, please take a cup of camomila tea before reading this email. Thinking about Debian Release Process I would like to make some points about the release process, I hope this discussion can make some difference in the release for etch. 1) Debian releases when it's ready This is a well-known Debian behaviour. And for several reasons it is considered a good idea (at least this is the current practice). And I don't want to change that. What I do think we can think about is the meaning of it in the phrase above, i mean, what exactly are we waiting to be ready? Maybe this is already known by some people, and I even understand how it happens. Let me make an example: Let's say that after sarge releases the init maintainers decide that the locale environment variables will be set at boot. This will cause a lot of trouble and we will have to wait the entire distribution to be fixed before the next release. What I am suggesting is to predict this structural changes and say: Hey, we are going to do A, B and C for the next release, and D, E and F will be made only in the release after that and then Debian will release when it's ready. The only difference is that more people will know what the it means. 2) When the release starts, or, for how long testing will be accepting anything? This is something even more obscure, I think it's caused by the 1st point I made. For most of the people this sounds like that someone at some point simply says Hey, it's a good time to start a release, huh? and then someone replies Yeah, sure... let's do it... how many RC bugs do we have? Well, I hope this discussion helps in making our release process less painfull. daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Not-for-profit doesn't mean Never-get-money (Was: Re: Google ads on debian.org)
Em Ter, 2004-12-14 às 00:59, Stephen Frost escreveu: I agree w/ tbm, I don't see the issues as all that problematic. I find it disappointing, but not exactly suprising, that alot of the project members disagree outright at the very notion. Not very open-minded, in my view. :) I agree. In some messages in this thread it was said that if Debian starts to put google ads the Debian Organization won't be not-for-profit anymore. I just want to make it clear. Not-for-profit doesn't mean Without-any-money. A non-profit organization can have several ways of getting money to raise its projects. I think it's completely acceptable that Debian rents a space on its webpage as a way of getting money to raise its projects, this doesn't mean profit. Economically-speaking, profit is what some company have as a positive result of a period. In for-profit organizations, this profit is generally distributed among the share-holders. In a non-profit organization, the profit is called leftovers (I don't know if this is the correct word in english, in portuguese is superavit) which is never distributed among share-holders (which actually don't exist), but it's reinvested into the organization. I hope this help getting some things clear... daniel
Sender ID, Mono and Debian
Hi, Recently Debian stated[1] about Microsoft Sender ID technology, which, given the choosen Royalty-Free, Reasonable and Non-Discriminatory License (RAND+Royalty-free), couldn't be distributed by Debian. The reasons are pretty clear, and I agree with them. This is not the question. The question is: Why Mono[2] has a different treatment, given that the C#/CLI standards are licensed in the same way[3]? This, IMHO, is a dangerous inconsistency to Debian. What do you think? daniel [1] http://www.debian.org/News/2004/20040904 [2] http://packages.debian.org/unstable/interpreters/mono [3] http://www.gnome.org/~seth/blog/mono P.S.: I have sent a message about this to debian-private on the Sender ID thread, but it didn't echoed.
Re: internationalization
Em Ter, 2004-08-24 às 21:29, MJ Ray escreveu: what the heck is it with the euro? [...] By the way, I've not set up the euro specifically on my systems, but I pressed AltGr and 4 and it just appeared. I do have utf8 encoding, though, so maybe I'm unusual. me too, I do use ISO-8859-1 and when I press compose+e+= the euro symbol just came up... And I didn't configure anything about it... but... it only works in gnome (which seems to use UTF8 even if I don't configure it to)... xterm doesn't understand that character... BTW... € (do you see this symbol?)...
Re: Debian, lists and discrimination
Em Sex, 2004-08-06 às 11:35, MJ Ray escreveu: against non-icelandic speakers, it also discourages from people posting in english there. As far as I am aware, anyone could learn more Icelandic if wanted. (I only know my IRC nick's meaning in Icelandic.) Even if a man wanted to become a woman, it is unlikely that they could do so to everyone's satisfaction. It seems that you are not aware that male or female is not a sex matter, but a gender matter (which is very much different). We are not talking about sex, we are talking about equal rights to males and females. (do you really believe that everybody have the same opportunities?) At least men are still allowed to post on debian-women. ...only if it is about discussion or collaboration involving women. That is what defines the TOPIC of the list. Usually, OFF-TOPIC messages are not welcome. There's no equivalent list for men because no one has requested it. So there is no barrier to any group? Would a listmaster create debian-christian-middleclass-middleage-hetero-white-males only for discussion or collaboration involving them, even if it has unpleasant consequences? Now that is *negative* discrimination... will also point out to you some unrepresented demographics that have lists. For example, debian-accessibility, debian-lex, debian-hams or debian-jr No, all of those seem primarily about making the debian operating system suitable for use by those groups, not socially engineering the debian project in the style of debian-women. I think legal offices and ham radio are fields of use rather than groups of people. Further, I suspect that hams are over-represented relative to world population proportion. What you didn't understand is that Debian is more than a group of techical people doing technical things... We fight for freedom in software, why wouldn't we fight for freedom for people? What does Amaya's website have to do with anything? The email questionnaire was presented as a survey of DDs and I was told my answers would appear on the supporters page, which they have not. A copy of the email sent out can be seen in http://lists.debian.org/debian-women/2004/07/msg00247.html when Amaya apparently gives up on it. If you read carefully Amaya's website, you'll see that the site only representes amaya's point of view. So, amaya is free to say whatever she wants... Many times surveys were made to debian developers, what's wrong with this one?
Re: Debian, lists and discrimination
Em Sex, 2004-08-06 às 14:47, Jaldhar H. Vyas escreveu: What is left unexamined in all these discussions is why Debian (as a project) should be doing anything to tackle inequalities? For the same reason we work with free software. As far as I can tell my microwave oven was made exclusively by atheistic communist Chinese. But it hasn't affected this religious, Republican, Indian-Americans' ability to make cheese on toast any. Sure, but I hope you worry about the chinese ways of making your microwave oven. Does the fact that Debian is produced mainly by men prevent, say, a rape crisis centre from using it? Or is the contention that there is some barrier to involvement by women (and only women) in the project itself? Because such an allegation should be backed up with some solid facts. It seems you simply didn't get the point.
Re: Debian, lists and discrimination
Em Sex, 2004-08-06 às 15:58, Jaldhar H. Vyas escreveu: So we won't get viruses, have to pay lots of money or have to put up with unfixable bugs I think you're being rather presumptious about why we work with free software. This affirmation explain everything... You just don't care about the problem that debian-women is trying to deal. I just don't understand why you want to stop them doing that...
Re: log on and password
Em Qua, 2004-03-31 às 11:13, Martin Schulze escreveu: The easiest way to get access to the installed system is by booting a Knoppix variant and erasing the root password. Or, if you don't have such CDs, you can boot passing init=/bin/bash then remount the root filesystem as read/write, edit /etc/shadow, /etc/shadow- copying the password from an user you know the password, or just leave it blank (I'm not sure if it's still possible), then remount again as read-only and reboot... example boot command... LILO: Linux root=/dev/hda1 init=/bin/bash # to remount as readwrite mount -o remount,rw / # to remount as readonly mount -o remount,ro /
