[ewiki] Re: Bugs and Patches

> van: Mario Salzer <mario@xxxxxxxxxxxxx>
> datum: 2005/12/05 ma PM 06:18:02 MET
> aan: ewiki@xxxxxxxxxxxxx
> onderwerp: [ewiki] Re: Bugs and Patches
> 
> I'm sorry for writing back that late once more, but lack of internet
> connectivity served me as perfect excuse before ;-P
> 
> hj.boerboom@xxxxxxxxx wrote:
> > Q1: I think that the homepage is working faster, because of the MySql 
> > upgrade ?
> 
> Possible, but I think the sourceforge team also upgraded the servers
> and they are partitioned among all sf.net projects differently now (we
> for example use the mysql-e.sf.net database server).
> 
> > Q2: Are Bryan Watters and Rob Buurman still project members ?
> 
> No idea about Bryan, but Rob is (though he has little time as well)
> and he lately contributed an initial Dutch translation. It was
> unavailable from CVS because I uploaded it in a hurry I think; but
> looks ok now.
I´ll take a look.
> 
> > Q3: The bugs are in BugReports, but where can we see who is doing what and 
> > where the patches are ?
> 
> I'm not working on anything currently. For the in-Wiki BugReports the
> patches should be pasted onto the individual pages as usual.
> 
> The issue has been brought up before, and I think it's time to
> reconsider using a real bugtracker. My grief with them is that they
> complicate the process even further (forcing user accounts onto
> people completely eliminates my will to report bugs for example).
> But if the current bug list and pages are far too useless, it's no
> question that everything has to be transfered into a real bug
> tracker.
There was a time you used the SF bugtracker !?!
I think the BugReports can be used by 'everyone'. But a few people should 
decide if they are really bugs ! So the BugReports get filtered. I think Real 
bugs should have real bugnumbers which can be seen when solved in releases en 
patches ! So: for the average user the simplicity of the wiki and for tracking 
real numbers.
> 
> > Q4: Version ewiki.php 1.301: Is this a patch for bug OnesSubpagesBroken ?
> 
> No, I don't think it adressed that at all.
> 
> > Q5: Where can I get a feel for the near future plans ?
> 
> Because there are a lot of bugs, those are going to have priority.
> After that the core script must be transtioned to use gettext/emu
> and finally use Unicode internally.
> 
> :: That there has been so little happening the last time does not mean
> I've given up ewiki. - On the contrary, it's still my favourite pet
> project and am running it on half a dozen sites. I'm just lacking time
> and a solid inet connection ATM.
> 
> > Q6: Is there a way to see in the source, which CVS-Revision I am using ?
> 
> There are no CVS revision tags in the source, because I thought it's
> usually tracked in the CVS/ control dir and that would suffice mostly.
> (??)
Only ewiki.php says of which release it is ! But you put it there yourself, not 
?
If I have a problem with a particular source and want to look in CVS if there 
is a newer version, then I have a problem, I have no reference, I have to 
download and diff to see which version I have. 
Doesn't CVS allow for the revision to be in the source, or can you generate a 
revision list to go with the release ?
> 
> > Q7: I want to deliver some 'improved' dutch /init-pages. How to do that !
> 
> If you want to help out, just tell me your sourceforge.net user name
> and I'll give you CVS permissions. This is always the BEST option,
BobRomeo like in the homepageWiki.
> because it omits the huge round trip and delay (me) when adding bugfixes
> and/or new features.
> The major advantage of CVS is that any patch could be easily reverted
> or changed if it later turned out to break something else or so. From
> a management perspective it's easier to give out a thousand CVS rw
> accounts than to look through likewise many submitted patches.
This is a bit like teh wiki-concept.
> 
> > Q8: {Shell/BP/Total}  How to help with /lang/nl ? Copy spanish version and 
> > make 
> > it dutch ? Or must one dive into gettext etc...
> 
> There is no english gettext .po file yet, because you can mostly
> generate it with gettext tools - but it needs additional (short) text
> snippets to serve as base for new translations.
> 
> > Q9: Why is not the adding of spaces in the pageTitle (and in PageIndex) 
> > also 
> > done with the WikiWords in the page content ? (I have a lot of people not 
> > using 
> > WikiWords, because of this.)
> 
> This is an exisiting feature and can be enabled with EWIKI_SPLIT_TITLES.
> If it doesn't work anymore (only used it with one site), then that's a
> bug.
I'll look into that, I thought that was just for the Titles ! (like in Split 
Titles
> 
> > Q0: Was it intended for the files in the /doc to become WikiPages ? Or in 
> > the 
> > future ?
> 
> Not at all. It just looked interesting to have documentation pages named
> with WikiWords. They don't need to be WikiPages at all.
> The overall plan for the doc/ directory was to split up the monster
> READMEs into smaller and more easily consumeable chunks, ordered by
> task. I hope that there'll be more step-by-step guides too.
> 
> Best,
> mario
> 
> 
> -- 
> http://www.freelists.org/list/ewiki
> 
>

Other related posts: