Jeremy Huntwork wrote:
At this point we have basically three directions we could take, and I
would like to get your feedback, please.
1) Use Trac for our entire online presence, including our website.
I'm not so sure about implementing the whole lfs website in it. I guess
it could be incorporated into it so it is just like before? I guess I
could get used to the idea and it would simplify making changes. Even
project leaders could do their updates. What about things that are
automaticed, like the hints list (which has a bash script IIRC) and
other such things? I guess the scripts could be modified, and
copy/pasted in if needed.
Replacing bugzilla will take some getting used to. We all have used
bugzilla for so long we are very used to it. A few comments on it: I
didn't see a URL field like in the current bugzilla, Platform (which
probably isn't even used for LFS and BLFS) is missing, priority is words
instead of P1-P5 but I guess we can get used to it and the type field
calling bugs "defects" seems kinda harsh, even though that is what they
are. In other words, it will probably do just as well, just need to get
used to it and have it auto-email the right list.
The svn browser, roadmap, etc are all very good. I like it! :)
Justin
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
