Trac

Hi, as I did not realize how to use the Trac system, I am posting here (supposedly this ugly text would be replaced by some how-to-use-trac instructions by someone who has the knowledge).

( Actually, these hints often help better than any DON'T POST HERE ANY MORE. )

First of all, there is a gazillion of links and buttons on the bugtracker page, but I do not see a big red "Post A New Issue Here" button (or link), probably because I have missed it. But a hint on that would be nice.

Second, there is no "register here" page (all this "an e-mail to your address has been sent" stuff is already very boring – and this is one more reason why I liked hatta so much when I've found it, but anyway – ) – and when one goes to the login page, http://bugs.hatta-wiki.org/login, it also provides no hints on HOW one gets registered on this wonderful system.

As for the real issue that brought me here, I do not think that using the _find_repo_path(path) @ storage.py:45, that finds some Mercurial repository somewhere up the directory tree is the right thing to do – at least, by default.

I discovered it by accident from my very first attempt to use hatta – and was not completely happy with it. Making a brand new repository in the standard place – i.e. docs/.hg – or using the config – is quite enough, I think.

Except that, I have found hatta extremely well designed and accurately implemented. It is elegant, what I admire, and I am really very much impressed with the effort it took to implement it.

Ah, and a question to the author: how did you pack all the hatta/* modules into one flat hatta.py file ?

Looking at http://hg.hatta-wiki.org/hatta-dev/log/d0b4daab0fab/hatta/__init__.py, one could see that the single file was splitted into sub-modules at version 1.4.0dev (or may be 1.4.1dev the latest), but the Download page has version 1.4.3 as a single file. There is also a raw-file repository, as I can see – but it is probably a little bit difficult to maintain those two in parallel without a right tool. So how does the merging to a single file happen ?

Thank you for your feedback. The truth is that the move to Trac wasn't perfectly planned. Initially, I left it open for everyone without a need for any logins – that's what I would like to have the most. But then I got spammed heavily and discovered that there is no way to remove the tickets created by spammer (I found out how to do it later, but the process is manual and leaves traces). Because I didn't have time to develop some sort of spam protection plugin for Trac, I had to just enable logins and require them for posting. I hate this, but it was the only solution I had at the time. It didn't stop the spam: here were lots of users created automatically using the registration form. Then someone suggested to use an OpenID login, and I configured and enabled that, disabling he registration. People who registered previously can still login using "Login", others can use whatever OpenID account they have – it's very easy to get one. I would still like to open the bugtracker to general public without requiring any logins, but that requires me to write some code, and my time is rather limited. In the mean time, I have enabled registration (maybe the spammer got bored), if that is going to help you.

As for help, you can find Trac documentation at http://trac.edgewall.org/wiki/TracGuide, I will try to add a link to it to the bugs page, thanks for suggestion.

Lastly, the hatta-dev code, with 1.4.0dev version, is going to be released as 1.5.0. The 1.4.3 comes from the hatta repository, which is a stable branch (I had to release some bugfix versions). As you noticed, Hatta 1.5.0 is not going to be a single file anymore, it has grown too big and complicated for that. Splitting it into many modules allows not only for better code organization and structure, but also for reuse of parts of my code by other projects. I might decide to distribute it as a `hatta.zip.py` file, though (Python can run such files just fine). – ~Radomir Dopieralski