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
