Re: [Midnight Commander] #271: Updated Dutch translation
#271: Updated Dutch translation -+-- Reporter: mpol| Owner: Type: defect | Status: new Priority: major | Milestone: 4.7 Component: locale | Version: 4.6.2 Resolution: |Keywords: review Blocking: | Blockedby: -+-- Comment(by winnie): just update it. :) -- Ticket URL: www.midnight-commander.org/ticket/271#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Further Midnight Commander development
On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote: You might not be aware but I am (still) one of the two official MC maintainers. De jure, maybe you are. De facto, the project is an orphan. How many more times do I need to submit my patches to get your attention? How many millennia do we need to wait to get UTF-8 support? Slava, how can I start committing fixes to devel branch of your effort? Basically, I need a mini-HOWTO: 1. What source control system is in use? (In case reader is not familiar with one, giove an URL to the doc, and also mention three most needed commands how to check out the tree?, How to update checked-out tree? and how to commit local changes to the tree? 2. What mailing list do I need to use for posting patches prior to applying them to the tree? 3. Do I need to get approval from someone (as a reply on that list?), and can I apply the patch after that (IOW: do I have write access?), or do I need to hand the patch to someone else? Regarding (3). MC project is in such sorry state now, it can't possibly become worse if someone will start working on it. At worst, the effort can be just dropped, if the set of people with write access will prove incapable of going decent work, and we will be back at 4.6.2 (IIRC). So let's not get busy erecting overly restrictive rules regarding development, WE BADLY NEED DEVELOPMENT TO HAPPEN. Regarding stable and devel branches, yes, this is a usual practice for projects of moderate size. Let's do it that way. Say, stable will have 4.7.0, 4.7.1, 4.7.2 releases planned with moderately simple fixes only, and devel will evolve for some time to create new stable 4.8.x branch sometime in the future. We need to stop talking about great plans and start coding. Give me a devel branch to play with! :) :) :) -- vda ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re[2]: Further Midnight Commander development
Hello Denys, Monday, February 16, 2009, 3:15:45 PM, you wrote: On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote: You might not be aware but I am (still) one of the two official MC maintainers. De jure, maybe you are. De facto, the project is an orphan. How many more times do I need to submit my patches to get your attention? If I am not mistaken most of your patches were incomplete and you wouldn't bother to fix them. I see how comfortable is to be on the right side at the right time for people like yourself. You just hope to get your patch inside the codebase without caring about its quality. How many millennia do we need to wait to get UTF-8 support? As much as it is needed do be done properly. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Re[2]: Further Midnight Commander development
On Mon, Feb 16, 2009 at 3:02 PM, Pavel Tsekov ptse...@gmx.net wrote: Hello Denys, Monday, February 16, 2009, 3:15:45 PM, you wrote: On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote: You might not be aware but I am (still) one of the two official MC maintainers. De jure, maybe you are. De facto, the project is an orphan. How many more times do I need to submit my patches to get your attention? If I am not mistaken most of your patches were incomplete and you wouldn't bother to fix them. Oh really. I just checked. http://mlblog.osdir.com/gnome.apps.mc.general/2004-10/index.shtml http://www.mail-archive.com/mc-devel@gnome.org/msg05103.html 24/10/2004 - I posted the patch for the 1st time sometime later - I added it to bug database as well 07/11/2005 - patch was rediscovered and an active discussion started (which means there was more than one reply per year) 12/08/2006 - patch got applied By this time, of course, I didn't track the fate of the patch. THREE YEARS for a teensy patch like this???!! http://mlblog.osdir.com/gnome.apps.mc.general/2004-10/txt4mW4MB9qlO.txt You are glacial. Another patch, which I posted more than once, and this one is not applied: http://www.mail-archive.com/mc-devel@gnome.org/msg05526.html You didn't even have any objections. You just dropped the ball. You know, I have more interesting things to do in this life than spending three more years getting it applied. Especially that it is a bit bigger, who knows, maybe I'm being optimistic about three years here... -- vda ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Re[2]: Further Midnight Commander development
Hi Denys, Would you please cool down a little bit? Don't you think we can resolve this peacefully w/o further mutual accusations, don't we? I think that both parties will benefit from this... It's crystal clear that current development model desperately needs a change. But Pavel has some valid points too. Let's cooperate. When I saw Pavel Roskin gone it made me sad. We owe him a lot. Behaving like Enrico won't help to get the problems solved but rather make them unsolvable. OK? Thank you for your understanding. -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Further Midnight Commander development
Hello, It is very common in every project I participate to use different mailing list for these different goals: users, developer discussion, bug tracking and commits. It makes it easier to filter, and it allows for people that care about one particular area to focus on that area. If you want all the mail mixed up, you have the choice of doing that in your email program, but there is no need to force other people into your development model. Having multiple lists, one per task makes it so that people can opt-in into what they want instead of having to opt-out with complicated rules that they have to updated every once in a while. Miguel. On Feb 14, 2009, at 11:53 AM, Oswald Buddenhagen wrote: On Sat, Feb 14, 2009 at 05:43:55PM +0100, Patrick Winnertz wrote: Well.. I would like to have some place to discuss everything. of course. If this is too much it would be worth to move this to a separate mailinglist. yes - *if*. but that's not going to be the case. i cannot imagine that the additional effort resulting from fragmenting the communication channels even more would be in any way justified. but that's not my decision anyway ... ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Re[2]: Further Midnight Commander development
Hello, I am not really unavailable. In fact if someone bothered to ping me personally I would have noticed immediately. The list traffic was stalled for quite some time and I haven't been reading it on a regular basis for a while so I missed the interesting part. I agree with Pavel here. mc-dev has been for the most part dormant, and some terrible decisions (like that whole mhl fiasco) could have been avoided. Anyway, I am making making my way trough the mailing list volume for the last two months. I would not like to comment before I have gone trough all threads but some threads caught my attention already - search for mhl Does it feel familiar, is it what MC really needs ? Is this someone's excercise ? Luckily that mhl thing got nuked. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Disable cvs/savannah
Hello, 2.) cvs is in my eyes not very optimal for working together. git is better for such an task in my eyes. Probably the most interesting feature of using GIT is that everyone can have a full check out of the code, and it would be easier to maintain branches and maintain changes that are not officially blessed until that time comes. I am lame enough that I still have trouble using GIT myself, but progress requires learning, and it is worth taking this step. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Further Midnight Commander development
On Monday 16 February 2009 20:17, Pavel Tsekov wrote: So you want to bitch... I really cannot help you with that. How much did I bitch in these years while the patch was lying around? URL please. In case you did not notice, I want to code. I want to help MC to improve and sligtly more than glacial pace. If enough people complained that you patch wasn't included in the tree I guess it would have been included. Look at the stats of the list. They are pitiful. 2008-November: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 28226 bytes ] 2008-October: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 22216 bytes ] 2008-September:[ Thread ] [ Date ] [ Author ] [ Gzip'd Text 19325 bytes ] 2008-August: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 32094 bytes ] 2008-July: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 35622 bytes ] 2008-June: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 95316 bytes ] 2008-May: [ Thread ] [ Date ] [ Author ] [ Gzip'd Text 6232 bytes ] 2008-April:[ Thread ] [ Date ] [ Author ] [ Gzip'd Text 8738 bytes ] 2008-March:[ Thread ] [ Date ] [ Author ] [ Gzip'd Text 62349 bytes ] April 2008. Whole SIX mails during a month? October. Twelve mails. Yeah. That's the spark of activity. Most people *ignored your list* as nothing was happening here. Me included. Another patch, which I posted more than once, and this one is not applied: http://www.mail-archive.com/mc-devel@gnome.org/msg05526.html You didn't even have any objections. You just dropped the ball. I made an observation and you failed to follow up. I wonder how many users of my project I would piss off with attitudes like that. Obviously I must have red the patch and the code since I made that observation. I spent some of my time on it but you wouldn't care to explain why the patch is necessary. Read my mail again. I did explain how to see the bug in action, it's quite trivial. Sorry - it doesn't work like that. We'll see. -- vda ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
