Re: Plans for Midnight Commander development
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Yury, Having this said, I'd hope to get on track as I'm back, unless again some natural and not so natural disasters are going to strike on me... The top priority is to fix the situation with man page transformations, and cut a release from current master, while documenting this whole process for it to be reproducible without access to Slava :-) Hey, I'm accessible :) I'll glad to help to release new version. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlXMZKwACgkQb3oGR6aVLprbUwCeMusHsBjVHi3SdtVnQbygQaTU 2WoAn3Gl1MrCe16SblWmdtKP9TJTUK9M =5zBG -END PGP SIGNATURE- ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
On Wed, 2015-08-12 at 23:15 +0300, Pavel Tsekov wrote: Well, you know, the usual stuff - tracking and fixing bugs, reviewing patches, etc. I'll start with learning the new code, getting used to it. I've created my own fork on github so that should be enough for starters. Excellent, this will do for now, indeed. If there is anything I can help you with, just ask on the list. Sadly, I haven't followed up on many important mails in the last couple of months, but if it's short, I'll try to do my best to answer... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
Hello Yury, Wednesday, August 12, 2015, 9:35:38 PM, you wrote: On Wed, 2015-08-12 at 15:28 +0300, Pavel Tsekov wrote: So, it is this time again? :) I'd be happy to help with any development related efforts. I'd certainly welcome any help from sane people, of which I'm convinced you are one. Let me know what you are up to, and if you need me to grant you any rights that you might need to proceed... Well, you know, the usual stuff - tracking and fixing bugs, reviewing patches, etc. I'll start with learning the new code, getting used to it. I've created my own fork on github so that should be enough for starters. Best regards, Pavel Tsekov ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
I think the top priority right now should be to fix the regex crash issue and release a 4.8.15. Then figure out what to do :) Unfortunately I won't be able to work on it any time soon. e. On Wed, Aug 12, 2015 at 2:28 PM, Pavel Tsekov ptse...@gmx.net wrote: Hello Yury, Sunday, May 31, 2015, 9:30:49 PM, you wrote: It seems that I'm the only member of the current team left who still wants to go on with the project, so here is my current plan. So, it is this time again? :) I'd be happy to help with any development related efforts. Best regards, Pavel Tsekov ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
Hello Yury, Sunday, May 31, 2015, 9:30:49 PM, you wrote: It seems that I'm the only member of the current team left who still wants to go on with the project, so here is my current plan. So, it is this time again? :) I'd be happy to help with any development related efforts. Best regards, Pavel Tsekov ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
Am 12.08.2015 um 15:09 schrieb Egmont Koblinger: I think the top priority right now should be to fix the regex crash issue and release a 4.8.15. Then figure out what to do :) Unfortunately I won't be able to work on it any time soon. Well i'm just glad that mc exists at all, otherwise i'd probably go and commit suicide or some such. :D Take it easy... given mc's popularity, there will always be someone around who wants/needs further improvements, and simply take it on (it's just gonna move on a little more slowly then). Fine with me.. -- MfG, Oliver Lange. This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do not consent to the retrieving or storing of this communication and any related metadata, as well as printing, copying, re-transmitting, disseminating, or otherwise using it. If you believe you have received this communication in error, please delete it immediately. ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
On Wed, 2015-08-12 at 15:28 +0300, Pavel Tsekov wrote: So, it is this time again? :) I'd be happy to help with any development related efforts. Hi Pavel, Great to hear from you... yes, it's Spring, Summer, Fall, Winter... and Spring again (hopefully! one day). In what concerns my personal situation, in the last month I have been completely swamped by totally unexpected and very unpleasant series of events, and thus didn't manage to pursue the plan as I posted it, beyond what I have actually done and reported on the list. Next week I'm leaving for offline holidays till mid-September, so the likelihood of me getting much done until I'm back is vanishing. Having this said, I'd hope to get on track as I'm back, unless again some natural and not so natural disasters are going to strike on me... The top priority is to fix the situation with man page transformations, and cut a release from current master, while documenting this whole process for it to be reproducible without access to Slava :-) I'd certainly welcome any help from sane people, of which I'm convinced you are one. Let me know what you are up to, and if you need me to grant you any rights that you might need to proceed... -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
On Wed, 2015-08-12 at 16:01 +0200, Oliver Lange wrote: Well i'm just glad that mc exists at all, otherwise i'd probably go and commit suicide or some such. :D Hopefully there won't be any need for such drastic measures; I'm still managing to at least keep the servers afloat, and even if something happens such that everything burns down... it's open source! There is a repo on github with full development history, source releases are spread all over the distro archives, so no worries... P.S. Do you happen to know esc? Just curious because of the domain name ;-) -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
On Tue, 2015-06-02 at 21:47 +0200, Yury V. Zaytsev wrote: Just FYI, massive firmware / os / software maintenance on the builders has been completed, I'll be looking into the mailing list traffic, Trac server and Travis next up as time permits. FYI, I did some important upgrades on the Trac server this week, but I didn't have time to look into what causes the ticket creation delay yet. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Re: Plans for Midnight Commander development
On Sun, 2015-05-31 at 20:30 +0200, Yury V. Zaytsev wrote: * I'm doing important and long overdue firmware / os maintenance on the builders right now, which will allow them to function for quite some time. After that, I want to migrate to Travis and integrate it with Github as a priority. Just FYI, massive firmware / os / software maintenance on the builders has been completed, I'll be looking into the mailing list traffic, Trac server and Travis next up as time permits. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
Plans for Midnight Commander development
Hi there, It seems that I'm the only member of the current team left who still wants to go on with the project, so here is my current plan. * Ilia's private post on a Russian blog site stating that Andrew decided to resign as a maintainer caused a lot of drama, but in reality, not much has actually changed since the last half a year; the situation that has been slowly deteriorating for quite awhile. * Midnight Commander is not going away; even if commits completely cease, I'm still up to maintaining the website and all thirds-party services, as we've been doing for the last 5-6 years for as long as I can; if this changes, a proper public announcement will be made as early as possible. * I want to make a new 4.8.15 release in the coming months (actually, as soon as possible) from what has accumulated in the current master. It's stupid to let it rot, and besides, I can check that all the knowledge required to make a release is documented, and someone other than Slava can do it as well. * I want to use the release announcement to call for volunteers to join the team as maintainers to contribute to bug triaging and code review. Hopefully, this helps attract the attention of distro maintainers / packagers and downstream users that do not follow the mailing lists. * After 4.8.15 release, I want to go through the current tickets and try to commit as much of trivial and/or uncontroversial patches as possible; this might form the basis for a new 4.8.16 release. * I'll be giving FTBFS bugs and fixes a priority, so as to at least keep mc build-able with current kernels, libraries and compilers. * Regarding mc^2 fork, I would like to review the code and get it merged. After that, we can make a major 5.0.0 release, which may take some time to stabilize. I would need help with code review to make this happen in finite time though. * I'm doing important and long overdue firmware / os maintenance on the builders right now, which will allow them to function for quite some time. After that, I want to migrate to Travis and integrate it with Github as a priority. * Similarly, I want to service the Trac server; I hope that I can find out what's the problem with ticket posting delays. * Whomever wants to help, or to join the team as a new maintainer, please familiarize yourself with current state of the art by exploring the repository and documentation on wiki. The least hand-holding you require, the more convincing you look. * You can pick tickets that need a review, rebase the patches, do a proper review, and after you've done quite some of them, I'll be happy to commit it for you. After demonstrating sanity and perseverance for some time, we can talk about the commit bit. I think these requirements are reasonable, and not much different from any other project. * If you want to invest a large amount of work into something to prove yourself, but are unsure about it, ask on the list. If you want to tell me (or anyone) what and how we should do, but aren't ready to invest large amounts of work yourself, then please don't. * Regarding the infrastructure the development process that we have set up and followed while still being active: nothing is set in stone. I'd like to believe that I'm not crazy and can be convinced by reasonable arguments. However, keep in mind that the best way to convince me is to actually do the work, e.g. if someone has been triaging Trac for some time, and can explain why it's been painful, and how a proper migration to service X that he is ready to prepare will solve all the problems and make him über productive, I'm likely to fall for this argument. In the same vein, I'm unlikely to fall for the argument that all hipsters are on Github, so if we ditch Trac immediately and move to Github issues, then suddenly there will appear a bunch of dedicated maintainers out of nowhere and start reviewing patches like crazy. * On the subject of arguments: replying to emails, while actually _thinking_ of what you are writing takes a huge amount of time. I have very little time. This email took me more than an hour to write. Think of how these three facts interact. * Regarding time, I can consistently make about 1 hour per week, up to 5 hours in bursts, but that's quite a bit of stress. I'll see whether I can figure something out, but in any case expect delays in communication. I will try to answer as much other emails that need to be answered from the recent threads, but I have now about 2 hours left. I hope that these points cover the most important issues though. -- Sincerely yours, Yury V. Zaytsev ___ mc-devel mailing list https://mail.gnome.org/mailman/listinfo/mc-devel
