66491 items (51571 unread) in 130 feeds
Linux
(11663 unread)
Gentoo
(516 unread)
Debian
(6557 unread)
Fedora
(5750 unread)
Kde
(2680 unread)
Gnome
(3575 unread)
Mandriva
(396 unread)
MySQL
(3237 unread)
Apache
(3432 unread)
Redhat
(90 unread)
Paul wollte noch eine deutsche Version...er hat es gerade selber übersetzt :-)
Nun ist die Welt mal umgekehrt, sonst übersetzen meistens nicht-englisch sprechende Menschen
Sconfitto da eeedora @ fedora 8 (sincero? una vera schifezza.. un pachiderma instabile) sto tentando di installare fedora 9.
Visto il problema riscontrato con la live di fedora 8 , stavolta ho deciso di “spinnare” un live al volo modificato
Ho eliminato il limite dei 4 Gb necessari per installare (portandolo a 3)… ed in questo momento sta installando sul mio eeepc
Nella live ho riscontrato che il wireless non funziona (il nuovo driver nel kernel ancora non supporta il chip atheros dell’eeepc.
La trackpad deve essere configurata per il “tap” (che poi scriverò come si attiva). i tasti per la luminosità funzionano, gli altri no…. insomma sarà un bell’inferno
Credo e spero oggi sia la giusta giornata per passare a fedora 9 (domani scatta la release candidate NON pubblica). Sul pc fisso continuo a tenere fedora 8… che ormai è inespugnabile
Fedora 9 SPERO vada bene su eeepc… dalle mie prove su fisso avevo notato un minor consumo di ram, ed in generale migliore risposta ai comandi…. sembra più ottimizzata..
vedremo!
stay tuned
The other day, I was having a bit of a down day, as it was just one of those days where I was wishing that I had a job that utilized my creative talents more. When I got to work, my manager noticed something was up but I wasn’t ready to talk at the time, but came clean later that night after I was done with my shift. It was then that she brought up a small project that she had been wanting to get off the ground since January, but never found the time or human resources for. She wanted to produce a small 5″x7″ document that talks about the changes going on in the restaurant and promote some upcoming events, like a small open house in early May. This was the perfect chance for me to exercise some of that creativity that I’d been yearning for, as well as make some small freelance money, as my manager was willing to pay me for my efforts.
Fast forward to last night. My manager had sat down and wrote out what she wanted the document to say, and I took that and created a very basic and not heavily styled layout in Scribus. No problems so far. I got it to all fit and look nice and work within the document dimensions. Then came the time to print the document and hopefully deliver it to my manager. Problems. Printing from Scribus caused my printer to not really respond, other than making random noises. I then went and exported the layout to a PDF and tried printing out of Evince. This created the most problematic results. Apparently printing from evince doesn’t pay attention to document size, as I had to specify within the print setup what size I wanted it to be. Once I got that covered, I had to find a way to make it print away from the upper left corner, which I never fully found out how to do. At least by this point I had it at the right dimensions. I kept trying different pdf export settings and print settings, and none of them worked the way I wanted.
I finally found, after googling a little, that there is a CLI command for printing, “lpr”, I figured what the hey, and tried it on the PDF that I had, and it printed it the correct size, no letters or areas cut off, or anything, but put it in the exact middle of the paper. I basically considered it my first success, although not quite what I had in mind either. I gave my manager a call, and explained what I managed to achieve. She then asked me to e-mail the pdf to her so she could try printing it. A few minutes later, I got a call back saying that everything went fine on their end. I have no idea exactly how it came out for her, but will see the results later this afternoon when I show up for work.
The questions I have regarding this, is what the problem was on my side. Was it my printer? Was it the fact that I’m on Linux in general? I know my manager is on XP at home. Perhaps it was the programs that I was using. What do you designers of Planet Fedora use when printing pdfs? I would like to know because I think I may be doing future documents with more updates going on at work.
On another unrelated note, I have my first real complaint about an order with CDBaby.com. In the past they have been absolutely wonderful and have introduced me to a lot of really good independent music that I most likely wouldn’t have found elsewhere. Shipping has always been super fast, receiving my orders in 2-4 days total(since I have a tendency to order right before the weekend). However, my latest purchase of “Down Easy” by the Noe Venable trio, is going on about 11 days and still hasn’t arrived yet. I contacted CDBaby about this and they requested that we wait until about May 5th before we take more action, due to mail taking longer than usual sometimes depending on where it’s shipping to and what time of year it is. If I don’t see my order by then, then I believe they will resend a copy. Here’s to hoping, as it’s awesome music.
For the past several years I've printed various documents at home by sending them to my wife Amy with a request "Please print...". And after several years we both know that Adobe Acrobat version 5 for Mac works far, far better than any subsequent release from Apple or Adobe, at least for the pdf documents I create on Linux. But how crazy is it that I don't have my own printer?
Last weekend I found myself at Staples and I decided to make a $300 bet with myself that I could get good value from an Epson Stylus Photo 1400 printer (with a maximum format size of 13"x19" borderless prints).
Note: This is a bastardization (and cleanup) of a post I made yesterday to the fedora-marketing-list. I think it’s actually very applicable to EVERYONE in the Fedora project, especially if you deal with users.
It is *absolutely vital* that all of us be on the same page for how to deal with journalists and other media people. Presenting a consistent, positive, and thoughtful message about Fedora is our Number One priority on this team and on this list.
A lot of the message points are already documented on our wiki so there’s no need to rehash them here. Journalists are busy people, just like you and me, and occasionally they make mistakes. Sometimes those mistakes go uncorrected and become embedded in the journalist’s mind. It’s up to us to correct them helpfully, with a gentle touch, and to leave the door open for future interaction with them. A single negative interaction can sometimes close a media door to us for good (or at least for a long time), but consistent, positive interactions make it likely that journalists will return to us for good stories.
WE have the ability to make all the difference.
(By the way, if you’re even the least bit geeky, go read this. Now assume in any future interaction with journalists that only you have read this, and it’s up to you to work with that person’s tact filter.)
The #1 guideline that will make everything else below just icing on the cake: GO OUT OF YOUR WAY TO BE NICE.
It’s especially important to be concise, careful, and polite if you are talking with a person whose native language is different than yours. Cultural norms differ and you want to make sure that:
Again, GO OUT OF YOUR WAY TO BE NICE.
This may be the 14,267th person you’ve had to talk to about what Fedora is, or why we do things a certain way, but you may be the FIRST AND ONLY Fedora person that individual has ever met. Make it an experience so great that by the time you’re done, they’ll want to join up themselves. AND their neighbors.
(And if they want to contribute to FOSS, we’re happy to have them.)
Here are some ideas for how to handle these follow-ups. Please look at these and make comments, since this is certainly a team effort.
For any formal press outlets, if you see something wrong, send a boilerplate letter with an offer to provide more information. Either Cc: or Bcc: the fedora-marketing-list and me. I don’t want all of our ability to get our message out to block on me, but I also want a shot at spinning these offers into interview opportunities.
(Look at it this way — that’s part of my job, so I get to point to these interviews at the end of the year and say “Didn’t I do a great job? Huh? ahem“… followed by the sound of crickets.)
And don’t forget, be nice.
For blogs, don’t just put in a comment. Trackback from your own blog, and tag or categorize it so it gets carried on the Fedora Planet feed!
Wait, you’re not on our Planet feed? Well put this message on hold, go read this, and come back when you’re done following those instructions.
And don’t forget, be nice. (Wait a minute, maybe I said that before…)
Now, I certainly don’t mind at all if people just refer these articles to me, because after all, if only one person is speaking, that makes for a potentially very consistent message. But it’s not a very scalable model going forward. Rather, I’d like to turn these follow-ups into opportunities to speak to media officially.
And if, on top of that, our intrepid Marketing team is following up with a consistent, positive message, especially under the tutelage of Leigh, Kara, and some of the other professional marketing people from Red Hat,
we are going to find ourselves with a very successful press campaign on our hands.
I've finally really read through the reviews of my two papers that got accepted recently to conferences, because I've got to create camera-ready versions in the next couple of weeks. One of them shouldn't be too bad: it's mostly a matter of updating the paper to describe the actual current state of the system and making sure that we cite the background work properly. But the other one, argh ... one of the reviewers (quite rightly) totally poked holes in my amateurish statistical analysis, so I'm going to have to go back to the data and re-do all of the stats. After understanding exactly how to do it. Which itself isn't entirely trivial. The review gives lots of probably-helpful suggestions, but I've got to read a bit more on the background before I can even understand them, let alone put them into practice. Sigh I really, really dislike statistics ...
On a completely different note: since this blog is now syndicated on Planet Fedora, I guess I should introduce myself to possibly a large group of new readers. (Eep!) I'm a Canadian computer science researcher working at the Technical University of Munich, although I spend a lot of time in Edinburgh, Scotland. I maintain a few packages in Fedora including the Ice distributed object middleware, and I also participate in the KDE SIG.
I have used Skype for years, out of the many voip solutions it is the one with the clearest audio quality and it’s much easier to use than say Ekiga (which I despite trying for years never have been able to make even a simple voip call using). Additionally none of the FLOSS alternatives allow me to buy a phone number and have it redirected so people in far away countries can call me cheaply.
Lately though Skype has been bothering me more than usually. Not only have they continually refused to provide a x86_64 build but it’s also impossible to make work with pulseaudio as presented in F9 (or any modern distro really), as such I now use Skype mainly on my Nokia n810 and my cellphone, making it very easy to miss peoples calls since the n810 can’t be on all the time whereas my desktop or laptop could be and the cellphone doesn’t handle SkypeIn calls correctly. Now they’ve added to my pain, I use Skype to call peoples phones outside of Denmark because generally Skype credit is cheaper than paying my cellphone company, however a few days ago they decided to stop taking payments using Paypal instead wanting to verify my credit card with my bank. This does not work because the version of java shipped in F9 is not detected by my netbanking site, so I can’t open an account.. which is required to get the activation thingy that VISA requires me to use (oh joy.. and you just knew somehow Java being the pile of shit it is would ruin my day again..)
More Skype problems, my cellphone comes with Skype installed, this was advertised at fully Skype compliant - I figured that meant it would correctly handle situations where people call my SkypeIn numbers and let me pick them up on my phone… how wrong I was, instead I am required to enable call forwarding which costs an insane amount of money - 0.20€, as a comparison even calling the expensive tier 4 countries on the skype list such as Brazil is 0.17€, it is thus cheaper to call halfway around the world than to call myself.. brilliant. Complaints over said behavior have been filed. The additional joy is that now that I am out of credits and I can refill my account on account of the change in the payment system.. thus call forwarding is completely useless and when I am out of the house now nobody can call my cleverly thought out SkypeIn system.
When people say you don’t get punished for using proprietary software.. they lie.. I plan to market Skype to the CIA as a replacement for waterboarding, now that eBay are thinking about selling it someone should be able to make a quick buck buying it cheap and selling it as a torture device.
After last week I took the initial gears and made them from solid gold, not is time to talk about the completely different approach, old writing on old paper, where we will work on the strokes.![[paper gears]](http://howto.nicubunu.ro/gears/golden_gears_00.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_00.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_01.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_03.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_04.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_07.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_08.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_10.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_11.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_14.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_15.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_17.png)
![[paper gears]](http://howto.nicubunu.ro/gears/paper_gears_18.png)
I’m used to seeing geek shirts. I see them all day at work - GNOME, FSF, thinkgeek shirts. I have a flatmate who is no geek at all but this week he was wearing a pacman shirt. I wear some myself as well. I go to conferences and they’re full of them.
But going into the subway and seeing a guy from across the street wearing a GNOME shirt, in plain daylight, without any conference or company nearby, is new to me. I stopped walking for a second, but he was already past me.
If you know who you are, with the black GNOME shirt with “The international desktop” on the back, coming out of the Rocafort metro this morning - say hello next time :)
* Très satisfait, elle fonctionne bien avec ma config
* Moyen, il reste du travail pour la version final
* j'ai pas encore testé
* bof, j'attendrai la version finale pour voir
Amarok est un logiciel pour gérer et écouter sa bibliothèque musical, Un des problèmes lors de l’utilisation est la lenteur des requêtes sur la base de donnée SQLite.
Pour cela voila un petit tutoriel pour passer à une base de donnée mysql qui peut être même sur une machine distante.
Il faut commencer par se connecter en mode root
Crée la base de donnée qu’on va utiliser
Crée un utilisateur (amarok), mot de passe (mon_motpasse) et lui donnée les droits nécessaire pour exploiter la base :
Recharger les privileges pour prendre en compte les modification effectué
il reste maintenant la configuration au niveau logicel: configuration > configurer amarok > Collection et le tour est joué.
Vous pouvez retrouver ce tutoriel (en anglais) avec possibilité d’importer vos anciennes valeurs sur ce lien
[www.linuxjournal.com]
Diese Jahr geht alles ein bisschen geordneter als letztes Jahr für den LinuxTag. Die Pressemitteilung ist so gut wie veröffentlicht und Ryan Lerch hat Entwürfe für diverse Banner erzeugt. Ich persönlich denke, dass er sehr gute Arbeit geleistet hat und und diese Banner nur noch geringfügige Anpassungen brauchen.
I moved my old blog (what little there was of it) to juhp2007 and started a fresh one here.
Visando o intercâmbio de conhecimentos e a difusão do Fedora, o Projeto Fedora Brasil premiará os membros mais participativos do fórum.
Se você tem dúvidas, problemas ou soluções, poste-as no fórum e concorra a brindes!!
Participe !!
Hier était pour moi un jour particulier puisqu'il s'agissait de mon dernier jour au sein de la société Kaliop. Une société et des collaborateurs avec qui j'ai pris plaisir à travailler pendant près de 2 ans & demi, et où je pense avoir beaucoup appris.
Lundi commencera pour moi un nouveau défi puisque j'intègre la société Logica, la 7e société de conseil, de services informatiques et outsourcing en Europe (sources Wikipédia) qui est plus connu en France sous son ancien nom : Unilog (Mais où est passé Unilog). Mon titre y est décrit comme "Ingénieur en technologies de l'information" et j'y ferais principalement du php5/MySQL/eZ Publish; bref, je m'aventure en terrain connu ;-).
Autre changement en prévision : un nouveau déménagement ! Ce coup si je n'emménage pas seul vu que je déménage pour habiter avec ma copine ;-).
Petit message à mes anciens collaborateurs : Vengeance
: Dark Tyranus | Kakia la coquine | Touche les tétous 
I liked this comment from a uk journal:
Instead of driving miles to the supermarket to load up on food just in case the shelves are cleared, or whingeing about strikers’ ability to cripple the country, we would be better advised to start looking at alternative ways of doing things, based on human energy, ingenuity and appropriate technology. Put simply, our default programmes need to be reset. We need to relocalise our lives.
It means more adjustment than merely declining the offer of yet another oil-derived plastic bag. Affluent middle classes in urban areas have to get over their hang-ups and use public transport, not just during the dispute, but thereafter.
Unless we want an ever more monstrous chunk of our budgets to be gobbled up in spiralling fuel bills, then it’s time to think about selling the second, even your only car.
If we can’t walk, bus or train it to work, then employers must start developing schemes that liberate us from environmentally-ruinous commutes, and allow more people to work from home, exploiting all the benefits of email and telephone conferencing.
Businesses need to understand that it is no longer acceptable to fly staff up and down the UK to attend meetings when they could perfectly well take the train.
I’ve had two interesting conversations this week. One with some neighbors about the cost of commuting 60 miles each way for work. Another with a co worker who commutes 37 miles each way for work. Both of them are concerned about the spike in the prices of everything. I’ve tried to help them find alternative routes/transportation to get to work. Both of them saving a good deal of money (and energy). Something I forgot to mention to them is what is said above: We need to get used to things being like this. It is not going away.
Since starting the daily dose of rawhide I am gradually becoming more acquainted with the ins and outs of rawhide. A particular day or release of rawhide only exists for a twenty-four hour period–longer if something goes wrong with the compose process.
Rawhide is composed in Fedora’s infrastructure and made available at [download.fedora.redhat.com]. It is also made available and synchronized by the Fedora mirrors to improve download speed for users and reduce the burden on Red Hat’s infrastructure. To the uninitiated, compose is a special term which refers to creating or building an installable Linux distribution, in this case Fedora or Red Hat Enterprise Linux. See the Fedora Mirroring Page to learn more about becoming a mirror or understanding how the process works.
Because of the time it takes the mirrors to synchronize with Fedora’s infrastructure, combined with the current state of an individual mirror, sometimes it is difficult to tell which day of rawhide you are getting. In addition sometimes a tree cannot be installed if files are missing from the images directory. Snake provides a simple way to find out.
$ su -c 'yum install snake'
$ snake-rawhide-status http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os
checking http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os
Fedora development i386 (20080429): ok
snake-tree info provides additional details
$ /usr/sbin/snake-tree info http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os
No data source used
Name : Fedora development i386 (20080429)
Arch : i386
Id : 1209473593.37
Version : development
Family : Fedora
Variant :
Time : 2008-04-29 05:53 PDT
URI's :
Images : i386 (kernel, family, timestamp, variant, boot.iso, initrd, version, arch),
xen (kernel, family, timestamp, variant, initrd, version, arch)
Each of these commands translates some of the less readable information from the .treeinfo which is created when a tree is composed. For example
http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/.treeinfo
[general]
family = Fedora
timestamp = 1209473593.37
variant =
totaldiscs = 1
version = development
discnum = 1
packagedir =
arch = i386
[images-i386]
kernel = images/pxeboot/vmlinuz
initrd = images/pxeboot/initrd.img
boot.iso = images/boot.iso
[images-xen]
kernel = images/xen/vmlinuz
initrd = images/xen/initrd.img
[stage2]
instimage = images/minstg2.img
mainimage = images/stage2.img
Note: the .treeinfo file is a hidden file and thus not normally presented in a directory listing unless specified.
Even if you’ve verified date of a tree and that the images are present, there are still no guarantees that the tree itself is internally consistent–in other words there is no simple way to know whether a particular mirror has completely sync’d all of the latest packages. And if there is, please post a comment and tell me how ![]()
I read about it in yesterday's morning newspaper. Made me proud and happy.
A faculdade Simonsen, em Padre Miguel RJ, retornou às aulas com um laboratório todo novo e 32 máquinas rodando Fedora (que é a base de todos os cursos sobre Linux) administrados pela instituição. Cuido de duas turmas, somando 64 alunos e todos têm fedora em suas casas.
O Coordenador do curso, Professor Leonardo Cioti, está muito contente com o resultado e empolgado com o Fedora. Administra também alguns
cursos na FEUC (uma outra faculdade em Campo Grande RJ) e pretende montar lá mais um laboratório com 32 estações usando Fedora.
[1] A turma: [picasaweb.google.com.br]
[2] - (parte d)O laboratório:
[picasaweb.google.com.br]
Henrique “LonelySpooky” Junior
É com grande satisfação que informo a todos que um brasileiro está compondo o grupo do FLSCo. O FLSCo é o comite gestor do projeto de tradução do Fedora, fazendo a tradução e internacionalização da distribuição.
O eleito é o Diego Búrigo Zacarão, nosso amigo Catarinense, Embaixador do Projeto Fedora Brasil.
A todos, parabéns, e Diego, que sua presença posso ajudar cada vez mais o Fedora a se disseminar no Brasil.
Segue a lista dos integrantes do grupo:
The First FLSCo:
# Dimitris Glezos
# Diego Búrigo Zacarão
# Bart Couvreur
# Noriko Mizumoto
# Marek Mahut
# Fabian Affolter
# Piotr Drag
I previously mentioned Easy GIT, which greatly improves git, in large part by hiding man pages and command line options packed with unimportant implementation detail, while adding examples and options that relate to workflow.
Since then I've been using Easy GIT with other people and a central repository, and moving up the learning curve a bit, and started to find some stuff that still doesn't work for me.
(I guess I'll say eg and git interchangeably, since in many cases enhancements could go in either project.)
Should be a way to globally see what is outstandingFor my workflow, with a central repository and a small team (which is all my projects ever, whether D-Bus or Metacity or LiTL), any local-only changes or local-only branches are temporary.
In fact my standard procedure on a branch that will last a few days is to push to the server pretty much every hour or so, so I have a backup. Easy GIT (or git) makes this easier in some ways, since it's easy to create my own branch on the server.
No way I'm keeping a few days or weeks of work only on my local drive. I've watched a few too many other people do that and regret it.
Here's what happens, though. As the day goes on I end up with a half-dozen branches, and some commits on master too, in various stages of patch review, some approved for merge to master and some not. For most of these branches I probably intended to push them to the server, but for some really small quick-fixes, perhaps not.
Now say I want to power down, or go to bed for the night, or switch from my home computer to my work computer; what I want to do is say "sync to server" - just back it all up! I don't want stuff only on my local drive. If I go from home to work or vice versa, I want everything available on the server so I have it.
Two ideas:
This morning I set out to push all my patches that had not been pushed. Problem one: I couldn't figure out what these patches were.
Remote tracking branches: implementation detailRemote tracking branches are confusing, and I think could simply be an implementation detail. I care about remote repositories ("remotes"); I care about branches that are on remotes; I care about having an offline cache of branches that are on remotes; but I do not care that the offline cache happens to be implemented as a branch. And I do not ever, ever, ever want to write to the remote tracking branch.
How does one write to a remote tracking branch? I'm not sure to be honest. But today, for a second time, I discovered I had a remote tracking branch that was somehow not the same as the branch on the server it was supposed to be tracking. My only guess is that this results from typing "push origin/master" instead of "push origin", or the like. But I have no idea, really, how this could happen, or why I would want it to happen. Worse, I haven't been able to figure out how to fix it, short of a fresh clone.
This is only a small symptom of the problem, though. I think the big picture is that for purposes of command line syntax, "origin/master" should mean "branch master on the origin remote." If an operation should be done offline (as everything except writes and fetches should be), then behind the scenes it would use the remote tracking branch. If an operation is a write, then it should go to the remote branch instead of the tracking branch.
I don't need to know that "origin/master" and "branch master on origin" are different. I think it's clear in all contexts which one I mean, because git already separates network operations from local-only operations, and because it is never correct to modify the remote tracking branch (except to pull in new stuff from the remote branch, of course).
On every pull, the system should verify that the remote tracking branch (aka the offline cache) is exactly the same as the remote branch, and make it be the same if it isn't. And "push --branch master origin" simply should not be different from "push origin/master" - that's crazy.
Whether and where to push/pull: property of the branch, not of the push/pull operationGetting back to the idea of "eg sync": at any given time, I'm planning to either never push a branch, or always push a branch, or not push it for a while and then only push it when I explicitly decide to; but whatever the plan, it's not something that changes every hour. I want to say "keep this branch in sync with server"; or "don't send this to the server ever"; or "don't sync this for now, I'll re-enable sync later."
If branches were tagged with whether to push them or not, and to which server branch, I could globally "eg sync" the entire repository.
I guess git lets you push a branch to multiple different remote branches. Seems like an obscure feature that I can't imagine using. For me it would be fine if, for each remote branch I want changes on, I had to create a local branch, attach it to that remote branch, make the changes on this dedicated local branch, and push. In the normal case, I would have a local branch for all remote branches already anyway.
But, if there are people who love pushing to lots of remote branches from one local branch, they can just set all branches as "never sync" and then they can push individual branches by hand. The rest of us should be able to sync all shared branches at once, while still having local-only branches if we want.
Easy GIT has --all-branches and --matching-branches, but these are IMO wrong workarounds. --all-branches forces you to push stuff that may be a throwaway local branch or "on hold" temporarily. --matching-branches doesn't push new branches and may also push a branch you wanted to keep on hold. What's needed is that branches know where they go; I shouldn't have to push with a special "wildcard" option to do the normal thing, which is to sync all branches marked shared, and do not sync any branches I intend to be local-only.
Feedback: tell me what's going on!Now that Easy GIT fixed the docs, I think the number-one UI deficiency in git is that it has no feedback; it does not explain what it's doing when it's doing it. Sometimes it's totally silent; sometimes it has a bunch of babble about "objects" and "packs" that means nothing to me; neither of those is good.
This steepens the learning curve, since you can't watch what commands do.
Maybe worse, it makes the source control system "feel bad." For me, the purpose of a source control system is to make it so I can never lose any history or data; when every command feels like it did something mysterious I'm not sure I understand, I don't have a sense of security.
Commands should output things like: "downloading changes from remote server 'origin' on remote branch 'master'"; "merging branch origin/master onto branch master"; "3 new changes applied to master". For each command, I should get feedback on any network transfers; all branches that were involved; and all commits that were created or merged.
"eg branch" should show more than only branch names to help orient me. I would like to know if the branch is synced and if so to which remote branch, for example.
ChangeLog workflow is wrongFor a detailed ChangeLog, I want to write the ChangeLog entry as I develop the code, using 'C-x 4 a' in Emacs, ideally.
The problem is that when I go to commit, that's not when I want to write the log. I prefer to write it either as I go, or just before commit as part of self-reviewing the patch - I read the patch while doing 'C-x 4 a' to document each part. That's the value of having a ChangeLog file that exists always, and isn't just an open editor at commit time.
However, if you have a ChangeLog file git barfs all over every merge. git should be smarter. Merging ChangeLog conflicts is not exactly a computationally intractable problem. But there's an even better solution maybe.
Every time I switch to a branch, git could create an empty file called ChangeLog; then when I commit, it could pre-fill the editor with the contents of that file and reset the file to empty. Magic!
The problem is not that ChangeLog disrupts git merges. The problem is that git does not support the nice format and workflow of ChangeLog.
Use EMAIL and GECOSA minor thing, but if you just start using git, it puts garbage in the Author field. Every other program uses the EMAIL environment variable and your UNIX account information. That is a good default. If people want to override it via config option, then let them, but don't require configuration to get started.
Easier way to see what a branch doesIf you want to review a branch to see if it should be merged, the syntax is the magic triple dots: git diff master...mybranch
This is weird, arcane, hard to discover... and something I need to do all the time.
I'm not sure what the right solution is. Maybe just docs, or maybe it should be an option to diff instead of the funky triple-dots.
Deleting a remote branchI think to delete a remote branch you have to do eg push :branchname, another strange and surprising syntax.
eg branch -d remotename/branchname should work, IMO. (Again, writes to a remote branch should modify the server-side branch, not the remote tracking branch.)
Can the central repository be "messed up"?With subversion, I think it's basically impossible for someone with access to the central repo to accidentally make a change that can't be reverted. Sure they can log on to the server and delete stuff from the shell, but with Subversion commands, I can't do anything that won't show up in the history.
I can't tell whether this is true with git. Throughout the docs there are options like "--force" and "--hard" and warnings about how using the command can screw you. I don't know how many of these warnings apply to central, remote repositories, but I worry about it. Remember, I don't understand the git docs, and hope I never have to try.
An example from man git-push:
--force
Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. This flag disables the check. This can cause the remote repository to lose commits; use it with care.
Wait - can cause the remote repository to lose commits???!!! This is not what I'm looking for in a source control system. It's the main thing a source control system is supposed to be preventing!
Accidents worry me a lot more than malicious people or mysterious cosmic rays. Especially when something as absurdly hard to use as git is involved!
It also bugs me that I can accidentally do things that while theoretically recoverable, are still very hard to recover from. For example, somehow having changes on remote tracking branches that are not on the server. (To beat that dead horse a bit more.)
Overview of branch relationshipsIf you want to understand the branch structure of a project, your best bet is gitk, and gitk is not a good bet. I do not understand the gitk display at all.
There's probably some simple info the command line could report that would be very helpful, such as which branches have changes that are not on master, which branches were ever merged into a given branch, or which branch a branch was originally branched from. Perhaps some of this should be in the "git branch" output by default.
ConclusionSo much work to do.
So while I know there aren't many nmh users around, I figure I'll make some noise about it anyway. nmh-1.3-RC1 is out. I've updated the packages in Fedora 8 and 9, they should go live with the next package update.
You can see a mention of Cobbler in this post by Red Hat’s CIO.
Cobbler has a lot of interesting ways it can be going, and I am thankful to be inundated with patches from others at this point helping it go there. It’s going to be getting a lot better at low-level datacenter rollout tasks, from recent patches to support BIND, OMAPI, and so forth… and I may venture into the system imaging territory (finding good OSS projects to integrate) and doing a bit more about installing that other OS as well. It’s growing up, and I need to clone myself.
The past focus has been around supporting very large install bases — authn, authz, multiple servers, etc — in a sense, a depth first dive into “enterpriseyness”, without all the complexity. The future is really about breadth-first feature add and fleshing out all the nice stuff, while also making it easy to understand and deploy all the nice stuff without it feeling like a front panel full of DIP switches. There are a lot of corner cases in datacenter rollouts and we want to cover all the things you’re going to want and make that all easy to understand (which is reason for me to go explore Publican in a bit and do some more writing). So, please share what you are doing with it, if you are using it already, and all of the clever little hacks you’ve figured out.
If anyone is interested in doing stuff around the system imaging area (or even helping Windows rollouts), please do ping me. We have a huge list of ideas to expand upon. Some where in this, I also need to steal some more time for Func again — I’m looking forward to the GSOC guys piling on as well. It’s a good time to join up with either project and start following them if you haven’t already.
On 20th March 2008, the LITD15 committee of the Bureau of Indian Standards voted against Microsoft's proposed OOXML standard. 29th March 2008 was the last date for participating countries to vote on OOXML. In the interval between these two dates, Microsoft went to the Prime Minister of India and alleged that this committee acted against the national interest. Fortunately, the Indian bureaucrats who met the PM did a good job of defending the committee's vote against OOXML.Dear Prof. Phatak and my fellow committee members in LITD15,
It is a sad day for all of us when standards are created not on technical merits but through political bulldozing. In this hour of darkness, we look up to a respected teacher like you to show us the way out.
Open Standards are the foundation upon which we can build a just and inclusive information society and therefore these issues are critical for India's digital future. Today, thanks to the growth of the open source movement, users in developing countries like India have the choice of software programs that they can freely modify and deploy. This can go a long way in bridging the digital divide in India. However, proprietary standards end up nullifying these advantages.
For example, I can download and implement a Linux desktop on my PC, but to legally acquire the rights to use proprietary multimedia codecs, I will have to pay a royalty of 28 Euros (Rs 1,680) [1]. This payment adds no value to the local economy, increases costs for the end users and widens the digital divide, especially in developing countries like India. Such proprietary standards also violate the principle that standards should belong to all of humanity and should not be the monopoly of an individual or a corporation or a group of organizations acting in concert.
What I have observed is that clever organizations are trapping people into using their proprietary standards by:
1) Driving global adoption of *their* "standards"
2) Filing a thicket of patents around these "standards"
3) Collecting royalties for usage of these "standards" or threatening lawsuits against those who do not comply
How this scenario plays out in real life can be seen from the Joint Photographic Experts Group (JPEG) patent case. JPEG, as most users of digital photographs know, is a popular format for photographic images that has been widely adopted by makers of digital cameras, camcorders, PDA, cellphones and other devices. In 2002, Forgent, a company that owned Patent No. 4,698,672 in the US, ambushed the industry by suing 31 major hardware and software vendors, including Dell and Apple Computers. The company alleged that these companies infringed on its claim to an algorithm used in the popular JPEG picture file format. It is reported that Forgent's legal assault earned it $150 million. Forgent was finally brought to its heels by the Public Patent Foundation that challenged and overturned Forgent's claims on the basis of prior-art.
Dan Ravicher of the Public Patent Foundation who fought the JPEG patent case points out that, in the US, where most of these battles are fought, it costs only 39 cents to send a postcard with a cease and desist notice to an alleged patent infringer, the defendant would have to spend $40,000 to get a lawyer's opinion and anywhere from $2-4 million to defend a case. I do not have comparative numbers for India, but I am sure that no one on this committee relishes seeing the insides of a courtroom.
Therefore, I hope my fellow committee members will agree with me that our first responsibility as professionals who represent India at ISO is to ensure that we do not support such proprietary standards. At this point, it is also important to point out that all ISO standards are not necessarily open standards that empower users with the freedom to encode and decode their data. India has one vote at ISO but it is an important vote and we must exercise it to ensure the creation of genuine open standards at this global forum.
I therefore propose to my fellow committee members that the first bar that any standard must pass before it gets India's approval is that standards should be completely free of any IPR issues, royalties, patent encumberances, trade secrets etc. The proposed standard should give unfettered freedom to users to encode and decode their data in that format. If, and only if, it clears this bar should it be allowed to reach the next stage where it is evaluated on technical merits.
On the OOXML Issue
==================
I am given to understand that on 27th March 2008, the honorable Prime Minister of India held a review of this committee's "Disapprove" vote on OOXML. I am given to understand that Microsoft's submission to the Prime Minister's Office was that the committee's vote is against the national interest.
As someone who has worked over the last ten years to localize Linux to Indian languages and take IT to the 95 percent of Indians who do not speak English, I find such a comment deeply disappointing. Due to my involvement in Indian language computing, I was introduced to the transformative power of open source software and open standards like HTML. To me, the vision of building an inclusive information society is paramount and open standards are the foundation of this dream.
As a committee member, I would like to place on record my deep disappointment at the fact that Microsoft chose to question the decision of this committee at the highest office of our country. For over a year, we have reviewed the proposed standard with a fine tooth comb. Every opportunity was given to Microsoft to put their points across. At every meeting they brought a disproportionate number of participants along; some of these participants were not even Indian nationals. I think the committee as a whole was very courteous in accommodating all this but drew the line when this began to detract from the functioning of the committee. The only words that came to my mind when I heard that Microsoft's complaint had prompted the Prime Minister of my country to review this committee's decision was "stabbed-in-the-back." This was a great disservice to this committee and the country and I hope this never happens again.
It is to the credit of our policy makers, the Department of IT, the Ministry of Consumer Affairs and the Bureau of Indian Standards that the sanctity of this committee's decision was upheld. Therefore, I wish to second Point # 3 made by Prof. Phatak and would like to place on record Red Hat's appreciation for the exemplary transparency with which the proceedings of the committee were conducted. This is in sharp contrast to other countries where the decisions of the technical committees were overruled due to political considerations. In the context of what has happened globally, the conduct of Indian policy makers is all the more admirable and has done our country proud. We would therefore like to than our oft-criticized policy makers from the bottom of our hearts.
Standards cannot (and should not) be created in a technical vaccum. Without a moral and ethical framework, we cannot create standards that benefit humanity. Mahatma Gandhi summed it up best when he said that, “Real swaraj will come not by the acquisition of authority by a few but by the acquisition of capacity by all.” I believe that this committee should be focused solely on the user's swaraj (freedom) to encode and decode their data.
At times like these we look up to our teachers to provide us with a strong ethical and moral framework and be a guiding light. I therefore look forward to your mail and to your constructive suggestions on the way forward.
Regards,
Venky
PS: I have expressed some deeply held personal beliefs in this e-mail and it is entirely possible that I may be wrong in many places. However, I hope that we can start a dialogue around creating genuine open standards and India's role in creating standards that benefit the world.
[1] See http://tinyurl.com/2n4aox and https://shop.fluendo.com/
Cela fait trop longtemps que tootella.org n'est plus.... tootella, tu me manques, tu me donnes un signe de vie ?
Some time back somebody talked to me about how illogical the schedule of fedora is, why do you have the translations deadline before the final development freeze. There is no point in freezing the translations when your development is still going on. Why don't you do it gnome's way? they don't freeze their translations before development!
changelog:
I was looking for this for a long time. It is small and simple to handle
It keeps my daily earnings and expenditures properly, best of all it works in konsole
You can download it from this page.
I also created a RPM package for it, the review request is in the queue
So , if you are a Fedora package reviewer please look into this small package ![]()
I have been meddling around with Free and Open Source Electronic CAD Tools for quite some time now by means of contributing upstream, packaging a few and evangelizing the use of these tools by Students. Sometime last year, I stumbled upon this “Fedora Electronics Laboratory” spin maintained by Chitlesh Goorah and began to like it a lot. It had almost all tools needed to learn and enjoy Microprocessor coursework, Microelectronic studies and basic Electronics too. On seeing the vast availability of these tools in Fedora and not in my favorite Distros (Debian/Ubuntu), I decided to make some of these tools available to the Debian world as well (partly successful and partly not).
Last week I was offered to help the fedora electronics laboratory project and I gladly accepted. Now, I have the official Fedora packager status and have already made couple of commits to the project. Thanks to Chitlesh and the fedora team and I am sure I will continue to contribute to the best of my abilities!
Similar to last time, the fedora KDE-SIG will be importing qt-4.4 and kde-4.1 (alpha1) into cvs (devel, aka F-10 branch) soonish, so expect the ride to bumpy for a bit while we work out the kinks and broken dependencies.
Just as the novelty of the eeepc was beginning to wear off, today I got a model 2 OQO in the mail. It's a pretty nifty little device. First impression on opening the box and pulling it out was that it was a little 'chunkier' than I was expecting. It's pretty heavy at 3lbs. A whole pound heavier than the Eee. Similar slide-out keyboard to the n810. Much bigger screen.