Go to the FreeLists Home Page Home Signup Help Login
 



[haiku-web] || [Date Prev] [06-2006 Date Index] [Date Next] || [Thread Prev] [06-2006 Thread Index] [Thread Next]

[haiku-web] Re: Trac (reevaluated)

  • From: Waldemar Kornewald <wkornew@xxxxxxx>
  • To: haiku-web@xxxxxxxxxxxxx
  • Date: Thu, 08 Jun 2006 20:51:40 +0200
Mikael Jansson (mailing lists) wrote:
Tach!

Na? :)

Only developers and admins are allowed to create tasks. Users may
only create
"bug" and "wish" tickets (later, we might not allow for wishes,
anymore). This
probably requires permissions per ticket type.

There are numerous pluggable authentication systems, I'm using the
DBAuth plugin which uses a SQLite database instead of relying on the
web browser for authentication. Also handles groups nicely.  Otherwise,
there's also two special users, "anonymous" and "authenticated" which
perhaps would suffice?

It is important that we know the reporter's email address. I'd like to enforce
this by requiring to sign-up and login (same as with Bugzilla). I don't really
believe in this "open for anyone" ideal where we get spammed every day and
can't contact the reporter because he thought he should stay anonymous. I.e.:
* require authentication
* require valid email address
* only "Developers" group can create "task" tickets
* every authenticated user can create "bug" and "wish" tickets
* anonymous users get read-only access
We need real user management. The ticket assignment function ("reassign") should
have a drop-down list of all users in the "Developers" group. The normal
installations I've seen are far too "unrestricted" for my taste.


If Subversion access isn't directly needed, I could setup Trac instance
matching the requirements stated below. It'd live at http://bits.jansson.be/haiku
for the time being.

Yes, thank you. That would be a great testing possibility and finally show some
progress.


Which code base will you use? Do you have access to Charlie's implementation?
Actually, I'd prefer using a public and maintained code base. Charlie, did you
ask the Trac guys whether they want to take over RelationalTrac (simpler,
better, etc., what speaks against it?)?

Still the matter of hosting in the end.  Although, for a low-traffic
site (i.e., not providing Subversion access, missing out some of the
major points of Trac but good enough for a pilot test I guess), I'd
have no problems at all hosting it -- got some 2.5TB bandwidth to
spare.

Later, we will move it to our host. It supports Python, so Trac should work. Seriously, our main concern is bug+task management, the roadmap, and the timeline (history), not the SVN integration. That can wait until Trac officially supports remote repos integration.

Bye,
Waldemar Kornewald


----------------------------------------------------------------------- haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.