Re: [Gimp-developer] web site move
On Mon, 6 Oct 2003 11:43:28 +0200, Branko Collin [EMAIL PROTECTED] wrote: On 5 Oct 2003, at 13:46, Sven Neumann wrote: David Neary [EMAIL PROTECTED] writes: [...] There is no reason why mmmaybe shouldn't have become www a couple of weeks ago. If you would have read gimp-web list (where this topic should actually be discussed), you would know that there were good reasons for not doing the move immidiately. I do read the gimp-web list, and I have no idea what you are talking about. The last blocker was resolved last Monday or the Monday before, IIRC. I suppose that Sven was refering to the comments made on the Thursday the 18th in bug #121299. Some of these comments and the related issues were relayed to the gimp-web list by scizzo in the thread with the subject Moving of site proposal. Moving the web site on the 18th was not a good idea because there were still too many broken pages that could not be fixed immediately, so instead it was proposed to move it on Sunday 21th. This did not happen (Yosh said on the following Monday that he had been too busy) and a few additional improvements were done in the meantime, so the site was officially declared ready with the message Status of the new web site that I posted on Tuesday the 23rd. I believe that most or evenall of these points have been addressed in the meantime but we should leave it up to the web team to decide when they want to move the site. Could you please tell us which part of the web team has to say the word? I don't think that there are any official rules for that (and I doubt that there should be any). However, if there is a consensus among the active members of the web team and/or if the web coordinator (yours truly) says that it is OK, then we can say that the decision has been taken. Both of them happened two weeks ago. So the official decision is that the web site should move as soon as possible. There is no need to wait for any additional decisions. As far as I know, the last blocker is that Yosh should find some spare time for moving the site and all user accounts from the old machine to the new one. There are still some things that should be done with the new web site, such as updating the news on the home page or adding links to some files from the gimp and gimp-1-2 CVS modules (INSTALL, Wilber construction kit and others) but this will be much easier to do once the user accounts are moved so that I can set up the corresponding links and scripts on the new box. -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: mailing list problems (was: Re: [Gimp-developer] web site move)
Hi, Sven Neumann wrote: I eventually found a way to make it work. I don't remember exactly how but there are several ways (web or e-mail) to subscribe and to confirm the subscription and at least one of them works. Please try subscribing again, because any discussion about the web site should take place on the gimp-web list. Raphael, how can one subscribe by mail? I'm only aware of the mailman web interface. Problems subscribing to the gimp-user list were also reported today on the cinepaint-developers list. Someone should look into this since we really need these lists working. If you or someone else remembers how to work around the problem, please let us know. For information, there is the entirity of the page when I try to subscribe to gimp-web: Bug in Mailman version 2.1b4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/lists/mailman/scripts/driver, line 87, in run_main main() File /usr/lists/mailman/Mailman/Cgi/subscribe.py, line 94, in main process_form(mlist, doc, cgidata, language) File /usr/lists/mailman/Mailman/Cgi/subscribe.py, line 176, in process_form mlist.AddMember(userdesc, remote) File /usr/lists/mailman/Mailman/MailList.py, line 807, in AddMember cookie = Pending.new(Pending.SUBSCRIPTION, userdesc) File /usr/lists/mailman/Mailman/Pending.py, line 64, in new db = _load() File /usr/lists/mailman/Mailman/Pending.py, line 121, in _load return cPickle.load(fp) TypeError: dict objects are unhashable Python information: VariableValue sys.version 2.2.1 (#1, Oct 5 2002, 11:19:44) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path/usr/local sys.platformfreebsd4 Environment variables: VariableValue PATH_INFO /gimp-web HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 CONTENT_TYPEapplication/x-www-form-urlencoded HTTP_REFERER https://lists.xcf.berkeley.edu/mailman/listinfo/gimp-web SERVER_SOFTWARE Apache/1.3.27 (Unix) mod_ssl/2.8.11 OpenSSL/0.9.6g PYTHONPATH /usr/lists/mailman SCRIPT_FILENAME /usr/lists/mailman/cgi-bin/subscribe SERVER_ADMIN[EMAIL PROTECTED] SCRIPT_NAME /mailman/subscribe SERVER_SIGNATURE Apache/1.3.27 Server at lists.XCF.Berkeley.EDU Port 443 REQUEST_METHOD POST HTTP_HOST lists.xcf.berkeley.edu HTTP_KEEP_ALIVE 300 HTTPS on SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /usr/local/www/data/gimp-web REQUEST_URI /mailman/subscribe/gimp-web CONTENT_LENGTH 105 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 HTTP_CONNECTION keep-alive SERVER_NAME lists.XCF.Berkeley.EDU REMOTE_ADDR 194.206.161.214 REMOTE_PORT 21927 HTTP_ACCEPT_LANGUAGEen-us,en;q=0.5 UNIQUE_ID P4KKz4AgcPIAAFGVafA SERVER_PORT 443 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODINGgzip,deflate SERVER_ADDR 128.32.112.242 DOCUMENT_ROOT /usr/local/www/data Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: mailing list problems (was: Re: [Gimp-developer] web site move)
On 06 Oct 2003 18:44:08 +0200, Sven Neumann [EMAIL PROTECTED] wrote: Raphaël Quinet [EMAIL PROTECTED] writes: P.S.: Dave, you mentioned that you had problems subscribing to the gimp-web list. I remember having had some problems as well, but I eventually found a way to make it work. [...] Problems subscribing to the gimp-user list were also reported today on the cinepaint-developers list. Someone should look into this since we really need these lists working. If you or someone else remembers how to work around the problem, please let us know. Well, it looks like the mailing lists are completely broken now. When I tried last month, it was still possible to get around the mailman bug that was triggered during the confirmation step. But now the crash occurs during the first step of the subscription, so there is no way to avoid it. I just tried to subscribe a new address to the gimp-web and gimp-developer mailing lists and I immediately got the following error message: -- Bug in Mailman version 2.1b4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/lists/mailman/scripts/driver, line 87, in run_main main() File /usr/lists/mailman/Mailman/Cgi/subscribe.py, line 94, in main process_form(mlist, doc, cgidata, language) File /usr/lists/mailman/Mailman/Cgi/subscribe.py, line 176, in process_form mlist.AddMember(userdesc, remote) File /usr/lists/mailman/Mailman/MailList.py, line 807, in AddMember cookie = Pending.new(Pending.SUBSCRIPTION, userdesc) File /usr/lists/mailman/Mailman/Pending.py, line 64, in new db = _load() File /usr/lists/mailman/Mailman/Pending.py, line 121, in _load return cPickle.load(fp) TypeError: dict objects are unhashable -- [...more info snipped ...] So after the archives, now it is the subscription mechanism that is broken. If I am not mistaken, nobody can subscribe to any of the gimp mailing lists (user, developer or web) until this problem is fixed. -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: mailing list problems (was: Re: [Gimp-developer] web site move)
On Tue, 7 Oct 2003 11:31:45 +0200, David Neary [EMAIL PROTECTED] wrote: I eventually found a way to make it work. I don't remember exactly how but there are several ways (web or e-mail) to subscribe and to confirm the subscription and at least one of them works. Please try subscribing again, because any discussion about the web site should take place on the gimp-web list. Raphael, how can one subscribe by mail? I'm only aware of the mailman web interface. As I wrote at the same minute (but 24 seconds before your message ;-)), the problem that I observed a few weeks ago was only in the confirmation process, not in the first step of the subscription. But now the problem is even more severe: the first step is already broken, so it is not possible to subscribe to any of the GIMP mailing lists. :-( -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] GIMP 1.3 Reference Manuals
Hi, I've updated the online version of the GIMP 1.3 API reference at http://developer.gimp.org/api/1.3/ Thanks to the help of Mitch and DinDinX, the documentation has improved since version 1.3.20. However there is still a lot of work to do. We'd like to concentrate on documentation of the libraries for now since the core API hasn't really settled enough yet. If someone wants to contribute, there are several things you could work on: - Completion of the libgimp* API references This basically means adding gtk-doc style comments to undocumented functions as well as improving the introductory parts that are found in the tmpl directories. - Proof-reading the existing docs More or less the same workflow as above. Please note that the comments for the libgimp PDB wrappers are generated from the PDB documentation that is found in tools/pdbgen/pdb. - Addition of some introductory chapters This could be for example Compiling a GIMP Plug-In or Porting a GIMP Plug-In to the 2.0 API (Jeff Trefftzs expressed interest to do the latter). There is a README in the devel-docs directory that should get you started with gtk-doc and DocBook XML. If you are interested or if you have any questions please let the list know. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: GIMP 1.3 Reference Manuals
Hi, here are some stats on the current state of the documentation of our libraries: libgimp 77% symbol docs coverage. 365 symbols documented. 110 not documented. libgimpbase 21% symbol docs coverage. 27 symbols documented. 104 not documented. libgimpcolor 3% symbol docs coverage. 2 symbols documented. 66 not documented. libgimpmath 81% symbol docs coverage. 60 symbols documented. 14 not documented. libgimpmodule 100% symbol docs coverage. 20 symbols documented. 0 not documented. libgimpwidgets 84% symbol docs coverage. 261 symbols documented. 49 not documented. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] 1.3.21 made it to slashdot.
Thanks to the native SVG support! :-) Surelly, it would be a nice time to have the new site in place already. JS -- http://slashdot.org/article.pl?sid=03/10/07/130202 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Gimp 1.3.21 is on slashdot
That means that over the next hours, tens of thousands of people will point there browsers to www.gimp.org. Some people in the foruns, including me, have provided links to mmmaybe.gimp.org. However, the latest release on mmmaybe is 1.3.17. Could 1.3.21 be announced there in the next minutes? Also, it would be fine if someone could get a 1.3.21 Windows build soon. Regards, JS -- PS. I am not a subscriber to gimp-web . ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: mailing list problems (was: Re: web site move)
[EMAIL PROTECTED] (2003-10-07 at 1131.45 +0200): Raphael, how can one subscribe by mail? I'm only aware of the mailman web interface. When it works and for example for gimp-developer list just send a mail to [EMAIL PROTECTED] with subject subscribe (replace list name and domain as necessary). It comes in the headers, but I guess most mailers hide them and do not offer a way to extract the info in a useful way (if you are not faking the user agent field try pressing h). GSR ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 1.3.21 made it to slashdot.
Joao S. O. Bueno ([EMAIL PROTECTED]) wrote: Thanks to the native SVG support! :-) I'd just like to point out, that most comments at slashdot are too exaggerated (as usual). Let me get some facts straight: 1) The GIMP is not a SVG editing tool. We can just render SVG files to images, the vector information are lost, with the notable exception of Paths, which also lose some information, since the SVG paths irreversibly get converted to bezier paths. 2) The GIMP can not save complete images as SVG. Only Bezier paths can be exported in an SVG with non-fancy default options. 3) The GIMP does not really try to compete with Sodipodi. Naturally there are points where the scope of the GIMP and Sodipodi overlap, but right now we are only talking about a reimplementation of a tool that has been in the GIMP for ages. IMHO it would be feasible to have some features of Sodipodi in the GIMP also, but it will be a long way. 4) The GIMP uses librsvg in the SVG-plugin for rendering the SVG. In fact the Plugin originally was part of librsvg and got adopted by Sven into the Gimp after talking with the librsvg maintainer. I hope that this can clean up some confusion from the comments. Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 1.3.21 is on slashdot
Hi, Joao S. O. Bueno [EMAIL PROTECTED] writes: That means that over the next hours, tens of thousands of people will point there browsers to www.gimp.org. Some people in the foruns, including me, have provided links to mmmaybe.gimp.org. However, the latest release on mmmaybe is 1.3.17. Could 1.3.21 be announced there in the next minutes? The 1.3.21 announce has been submitted yesterday already. It seems the news engine is broken which keeps it from showing up. Now who can fix this? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 1.3.21 is on slashdot
On Tue, Oct 07, 2003 at 07:01:32PM +0200, Sven Neumann wrote: Hi, Joao S. O. Bueno [EMAIL PROTECTED] writes: That means that over the next hours, tens of thousands of people will point there browsers to www.gimp.org. Some people in the foruns, including me, have provided links to mmmaybe.gimp.org. However, the latest release on mmmaybe is 1.3.17. Could 1.3.21 be announced there in the next minutes? The 1.3.21 announce has been submitted yesterday already. It seems the news engine is broken which keeps it from showing up. Now who can fix this? Fixed now. Unfortunately, the current situation requires news updates to be regenned by hand. -Yosh ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 1.3.21 made it to slashdot.
Hi, Simon Budig [EMAIL PROTECTED] writes: 3) The GIMP does not really try to compete with Sodipodi. Naturally there are points where the scope of the GIMP and Sodipodi overlap, but right now we are only talking about a reimplementation of a tool that has been in the GIMP for ages. IMHO it would be feasible to have some features of Sodipodi in the GIMP also, but it will be a long way. The main ppoint about adding SVG path import/export was to allow for better integration with Sodipodi and other vector applications. The new functionality allows you for example to create a graphics in an vector application, export it as SVG, import it into GIMP and do some pixel-manipulation to fine-tune the result. The fact that you get the paths imported into GIMP should make this task easier since you can for example use them to create selections. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 1.3.21 is on slashdot
On Tue, 07 Oct 2003 11:15:40 -0300, Joao S. O. Bueno [EMAIL PROTECTED] wrote: That means that over the next hours, tens of thousands of people will point there browsers to www.gimp.org. Some people in the foruns, including me, have provided links to mmmaybe.gimp.org. However, the latest release on mmmaybe is 1.3.17. Could 1.3.21 be announced there in the next minutes? Unfortunately, this is difficult to do before the move. That's why I wanted the web site to move as soon as possible, so that I can play directly with the files (using my account on the new box, once it is set up) and replace the temporary news that have been put on mmmaybe as a test by the real news that have been posted over the years on news.gimp.org and more recently on www.gimp.org. Adding a single news item for 1.3.21 would be a quick hack, but would not solve the problem of migrating the news archive to the new site. I prepared some of the work by extracting all individual news items that have been posted on the old web site out of its private CVS repository, but now I need the web site to be moved before I can import all these articles with correct dates and authors into the new system. In summary, this premature announcement on Slashdot coupled with the delayed move of the web site is just causing a big mess. :-( -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp 1.3.21 is on slashdot
Raphaël Quinet wrote: Adding a single news item for 1.3.21 would be a quick hack, but would not solve the problem of migrating the news archive to the new site. I prepared some of the work by extracting all individual news items that have been posted on the old web site out of its private CVS repository, but now I need the web site to be moved before I can import all these articles with correct dates and authors into the new system. Put back the web site that was right and worked. I am considering the options. This mmmaybe web site is not a gimp dot org anymore as far as I am concerned. Put the old site back. no more hacks no more quick hacks put the old site back carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
