Hi David, What do you mean full control? As far as it remains GPL and GI agrees, I am fine with that. :)
I started mrxvt project based on rxvt 2.7. After it was in a reasonably shape, GI took active development and added a lot of new features. I do not know much about the mrxvt05utf8 branch. My development was mainly in mrxvt05b branch. Feel free to ask questions about the design, I will try my best knowledge to answer - though my memory about it is fading. Later, I thought about code cleanup. Most notably: . Re-organize the code to make it more object-oriented. When I wrote it, I did not have much experience on object-oriented design. So it was kinda messy. But I did not want to use C++. Anyway, it’s just a personal taste. Feel free to try if you have a strong opinion towards C++. . Cleanup input handling. There are several input source in mrxvt: X event, and file descriptor of tty devices. The current code is very messy, and I always have a feeling that something is probably wrong in handling tty input - meaning input from one tty can possibly leaks into another tty. About library, I’d like to keep it as simple as possible. That said, I do not want to introduce dependency on additional libraries without a careful consideration. My philosophy towards mrxvt is to make it as much self-contained as possible. I do not have an opinion on hosting. As far as there is an official place to host the project, I am fine. Best regards, Jingmin On May 30, 2015, at 14:40, David Morris <otha...@othalan.com> wrote: > On Sat, May 30, 2015 at 12:42 PM, <gi1...@gmail.com> wrote: >> On Sat, May 30, 2015 at 10:32:23AM -0400, David Morris wrote: >> >>> Does anyone have an overview of the changes needed to complete utf8 >>> support? I've been considering a new software project and I might be >>> interested finishing it up, or perhaps even taking over all active >>> development. If I do either, I'd also migrate the code to a different >>> source control platform. >> >> Jehan's the guy who wrote an alpha UTF-8 branch! I've tried it -- it >> works, but crashes often. (And sometimes the display is borked.) >> >> I don't know the specifics about displaying UTF-8 though. Hopefully >> Jehan will write back soon with a good clear outline that will sell you >> on it. I'd love it if you finished the UTF-8 support and or took over >> development. > > I took a quick look around just to evaluate the scope of the project > if I were to take over. First, some questions: > > If I did take over active development, would complete control be > relinquished to me? I would only do this if I have full control of > the project. I would of course be happy to get any input, advice and > coding help. > > What is the history of mrxvt? Did the code originate from rxvt? Or > was it developed separately? If I have questions about the design > decisions, is there someone to ask? > > What is the relationship between code in the branch mrxvt05b (the main > development branch) and mrxvt05utf8? How much code was pulled in from > the utf8 branch? I can analyze each, but it'd be easier to get an > overview if anyone still remembers. > > The code looks generally reasonably clean and well commented, but were > any major changes considered? Such as code cleanup, porting to C++, > changing to different GUI libraries, etc.? > > Source code hosting: I looked at all of the alternatives and the one > that stands out to me is GitLab. If I move the repository, that would > be my first choice. > > SVN to GIT: I did a quick test using svn2git and it is quick & easy. > > Sourceforge Bugs, etc which need to be reviewed & transferred if the > hosting is changed. These would eventually have to be moved over to > the new system, but because of the lack of active development for a > long time now I don't see any rush to go through these. Patches > should probably be evaluated first. > 33 open bugs > 6 open support requests > 17 open feature requests > 6 open patch submissions > > The wiki would need to be ported over. This should be done before a > new release but is probably not necessary before then. > > David > > ------------------------------------------------------------------------------ > _______________________________________________ > Materm-devel mailing list > Materm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/materm-devel > mrxvt home page: http://materm.sourceforge.net
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
_______________________________________________ Materm-devel mailing list Materm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/materm-devel mrxvt home page: http://materm.sourceforge.net
