Great, sounds good. I can take care of it, will probably get a new release out yet today.
Neil On 3/13/2010 12:33 PM, Hampus Wessman wrote: > Hi Neil, > > No problem. I appreciate your willingness to help. I've personally not > had much time for it lately (been too busy working and thinking about > the rewrite). > > I think we need to update the About dialog and the README. What you are > saying sounds good. We can change to "Originally created by Hampus > Wessman" and add you as the current maintainer. Then you'll get proper > credits for your work too. I could fix that tomorrow. > > I'll add a bug report for that bug I found. Would be nice if we could > have a new release out soon. I can spend a couple of hours on it too, > tomorrow. > > As the current maintainer of 1.x, feel free to make new releases > whenever you think it's time ;) > > Hampus > > > Neil M. skrev 2010-03-13 21:06: >> Hi everyone, especially Hampus. >> >> Sorry about the whole credit thing, it was something that I just >> overlooked. My goal has always been just to update Metalink Editor >> enough to keep it relevant and useful until your rewrite is done. I >> liked what you had come up with and have a continued need for it. The >> GUI is all still very much your code, I didn't want to presume credit >> for that, but if thats OK with you then thats what I'll do. >> >> So I propose that I'll update the About dialog (this is the first time >> I've really looked at it). I'll add my name as the maintainer/current >> developer and change the website to the sourceforge project. I'd like >> to keep your name in there somehow to make sure you get credit for doing >> the work of starting it. Maybe have you listed as a "created by" credit? >> >> And as for bugs/features everyone just go ahead and put them in the >> sourceforge tracker and I'll get to them for the next release. >> >> I think that addresses everything. >> >> Neil >> >> On 3/13/2010 2:58 AM, Hampus Wessman wrote: >> >>> I just removed the Metalink Editor 1.3.0 release from sourceforge.net. >>> It has at least one severe bug and states me as the only developer. Not >>> good. No hard feelings, but it's important for me that software with my >>> name on it works flawlessly (or contains bugs created by me). I think >>> this is the best solution for now. >>> >>> If we want to create a new release (e.g. 1.3.1) of the python metalink >>> editor, I think we should change all information about the authorship so >>> that it's clear that I'm not responsible for all of the current source >>> code (and to give credit to everyone involved). We should also fix all >>> bugs of course. Right now it fails to save meta4-files (complains about >>> a comparison between an integer and a string). Some prior testing would >>> probably be good (like a release candidate). >>> >>> I'm currently working on my new C++ Metalink Editor (finally have some >>> time for that!). Expect to hear more about that soon, once I've gotten >>> somewhere with it. >>> >>> / Hampus >>> >>> >>> Neil M. skrev 2010-02-28 01:12: >>> >>>> I just made releases of the following software that should be up to >>>> date >>>> with the v28 approved RFC draft. Ant already included the URL for web >>>> conversion service, the other two products can be downloaded from the >>>> sourceforge website: >>>> >>>> - Web Conversion Service >>>> - Metalink Checker >>>> - Metalink Editor >>>> >>>> https://sourceforge.net/projects/metalinks/files/ >>>> >>>> Neil >>>> >>>> On 2/27/2010 12:00 PM, Anthony Bryan wrote: >>>> >>>> >>>>> our Internet Draft/RFC appears to be done. now comes the fun part :) >>>>> there is quite a lot of software out there that supports metalink3. >>>>> >>>>> here's what supports metalink4: >>>>> >>>>> http://groups.google.com/group/metalink-discussion/web/internetdraft >>>>> >>>>> aria2 (patch, ready for 1.9.0) >>>>> KGet? >>>>> metalink checker (used by GGet, which Neil has ported to Windows) >>>>> metalink editor >>>>> Neil's web converter ( >>>>> http://www.nabber.org/projects/metalink/webconvert/ ) >>>>> >>>>> (note that all these probably need to be updated to the latest -28 >>>>> draft, we changed a few names like<metaurl mediatype=""> (from >>>>> <metaurl type="">)& maybe something else since these were >>>>> implemented) >>>>> >>>>> Peter is working on it for MirrorBrain. it'll nice to be test it out >>>>> with aria2/checker. >>>>> >>>>> what other metalink enabled apps should we focus on short/mid term? >>>>> probably the generating apps, so people have a way to make the new >>>>> metalinks... >>>>> >>>>> Bram's metalink tools? >>>>> libmetalink? >>>>> metalink-library? >>>>> >>>>> >>>>> >>>> >>>> >>> >> > -- You received this message because you are subscribed to the Google Groups "Metalink Discussion" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en.
