Skip to content
This repository has been archived by the owner on Nov 22, 2019. It is now read-only.

trac configuration available? #1

Open
ArkosX opened this issue Feb 8, 2013 · 4 comments
Open

trac configuration available? #1

ArkosX opened this issue Feb 8, 2013 · 4 comments

Comments

@ArkosX
Copy link

ArkosX commented Feb 8, 2013

Hi, I didn't get it working... it seems there are more assumptions about the configuration.
Would it be possible to have the configuration?

(there were also some bugs "The "<? " vs. "<?php " already reported by someone, but I found it in several files).

However this seems a perfect tool for providing a board to trac.
I love the fact that is completely independent and can be installed in a local desktop (with wamp or something like that) without need to mess up with the server.

This could something big! Congrats for the job!

BTW. I have no idea of PHP.

@willmeyer
Copy link
Contributor

As regards the configuration, the easiest thing would be to look at the traclib interface (in lib) and use that as a guide. The system is built on a few assumptions about the trac configuration but not overly so, and its pretty clear within that interface what those are (for anything you didn't get from the README).

To be honest it'd be necessary to have some level of PHP though to add to or modify tracboard...

@ArkosX
Copy link
Author

ArkosX commented Feb 12, 2013

Thanks for the hint. I will take a look at the lib.
I understand that to change the code it is advisable to know at least a lil bit of PHP ;) It would be great that for the installation it wouldn't be though.
I hope I will learn enough at least to browse it freely.

PS. Did I do that of highlighting the last two sentences! I don't know how :P

@ArkosX
Copy link
Author

ArkosX commented Feb 12, 2013

Hi, I find interface info quite clear, thanks!
However what is "scope" field? How is it used by tracboard, is it necessary? how do you use it in trac?
Same doubts come regarding "blocking" and "blockedBy". In the end what is important is to know which ones are strictly necessary for the tool to work -and why, so that flexibility could be incorporated if possible-
Sorry for asking many questions but I hope that in the end that can be helpful to be used by more and more people. Consider me a usability tester :P and maybe even I can help on the code as well :)

Regards

@cburroughs
Copy link
Contributor

Scope is a custom field:

scope = select
scope.label = Scope
scope.options = n/a|large|medium|small
scope.order = 2
scope.show_when_type = feature|task|story|defect
scope.value = 0

It's just "how much work is this" measurement

blockedby = text
blockedby.label = Blocked By
blockedby.order = 1
blocking = text
blocking.label = Blocking
blocking.order = 1

It comes along with the master ticket plugin http://trac-hacks.org/wiki/MasterTicketsPlugin

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants