On 28/12/2005, "Ondra Kudlik" <[EMAIL PROTECTED]> wrote: >Wed, Dec 28, 2005 ve 04:22:34PM +0100, Martin Waschbüsch napsal: >> Am 28.12.2005 schrieb "Ondra Kudlik" <[EMAIL PROTECTED]>: >> >Hi boys,
Evening, lads! >> >I'm now in process of setting up Trac for our documentation, bug >> >reports, wiki and others. I think, as Martin said, that Iloha needs >> >all of us not only one :) and we need some place for users and also >> >for developers... Agreed, but if Trac is successful, I'd be inclined to drop the forum, the new wiki, Sourceforge bug reports, etc.. Two points of contact (the mailing lists and Trac) is plenty. >> >If you agree, I will set up trac system and we need to: >> > >> >1/ find all reported bugs and add them to one place >> >2/ build a road map to new release >> >3/ we have many developers so all of them can tak bugs and work on >> >resolving them Sounds good! >> >I like to get all infos from current web pages, source forge web and >> > others and fill them into new pages (I'm volunteer to do this) with >> >current information about iloha status and documentation. >> > >> >I'm watting for replies... >> >> I think this is a good idea. You have a thumps up from me and thanks for >> doing this! >> What about the Wiki that (I think) Andrew set up for us? I liked it! The wiki hasn't been touched for over a month. Perhaps part of the reason is that there are so many other reporting mechanisms that the wiki has been overlooked... or maybe after the initial flurry of activity, nobody is updating it because nobody is updating it. If Trac is deployed we will need to make sure that it suffers a similar fate. >So, I'm not sure. I also like this wiki, but do not know how to >integrate it with Trac because it has it's own wiki engine. > >I can see two ways: > > 1/ to have independent wiki on wiki.ilohamail.org and trac and >other things on ilohamail.org (in future...) > > 2/ to have everything on one address in one engine > >I personally think that one place for everything is better but it's >up to all of us... Andrew, what do you think about it? You read my mind :-). >> >PS: As I said, I volunteer to set up "new" pages but I need some >> >native speaker corrector :) My english writing is really not good. But on >> >other side, I only want to collect information and centralize >> >them... >> >> Oh, don't worry. I am sure Dean or Andrew or another native speaker will >> help you out. Certainly! That's no problem at all. As far as information exchange is concerned, it doesn't need to be perfect anyway. I'll be happy to proofread any release announcements or other formal communiqués. :-) I'd like to make a point, if I may: there does seem to be a patching problem. Reporting bugs is obviously a critical task when improving Ilohamail, but it needs to be followed up by a swift patching process. The wiki contains ten or so suggested patches from earlier in the year. I assume that none of these haven't been committed, otherwise the wiki should have been updated. However, some of these patches are still relevant and need to be attended to. Similarly, on the mailing lists we've had several users ask about 0.8.14-rc3 which claims that it's -rc2 on the login screen. This bug is very trivial to fix yet hasn't been dealt with. (I suppose that the -rc3 Release Candidate, minus that typo, is ready for a proper release by now and can be simply called 0.8.14.) We also need to draw more attention to the unstable releases. The last unstable release was in April, and several new features are available in CVS. The last thing I want to see is an ordinary user inquire about AJAX or something, and to be told "it's in CVS." Things break in CVS - in fact, if a program's CVS is fault-free than something is very wrong! Seriously though, users require a more high-quality, stable program than what is directly available in the versioning system. One of the highest priority tasks for the unstable branch is to produce a new semi-stable snapshot. I'd be happy to download and use it (which is not the case for CVS) and drill out any prominent bugs. I'd love to take on more responsibility than that, but the PhD is too demanding :-(. Sorry to level these criticisms when there's little I can do to help, but I'd love to see someone turn this around into something positive! Cheers Andy ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Ilohamail-devel mailing list Ilohamail-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ilohamail-devel
