Dan Nicholson wrote:
Thanks, I like it. I made a ticket with some WikiFormatting:
http://wiki.linuxfromscratch.org/blfs/ticket/1774
Thanks for this. A nice example of Trac's power.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubs
On 1/23/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
>
> Both yourself and Alexander have been given editing permissions in the
> BLFS Trac env.
>
> Enjoy. ;) And please play around with it.
Thanks, I like it. I made a ticket with some WikiFormatting:
http://wiki.linuxfromscratch.org/blfs/tick
Dan Nicholson wrote:
On 1/23/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
I've only given permission out to current devs and editors (and Richard
as ex-editor, general xLFS historian, project mascot, everyone's
favorite Old Fellow. :) )
That's fine. You don't need to add me. I just thoug
On Mon, 23 Jan 2006 08:29:27 -0500
Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
> Richard A Downing wrote:
>
> > I have a login ([EMAIL PROTECTED]) for BLFS which I know
> > the password (and checked it with Bogzilla), but trac doesn't let
> > me log in. Or perhaps you're just picking on me! (:-)
Alexander E. Patrakov wrote:
I played with one LiveCD bug report, and had to add an extra newline
between commands in order for them to appear on separate lines.
Something that I would never have to do in Bugzilla.
Well, this is considered (by upstream) a feature and not a bug. Notice
that
On 1/23/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
>
> I've only given permission out to current devs and editors (and Richard
> as ex-editor, general xLFS historian, project mascot, everyone's
> favorite Old Fellow. :) )
That's fine. You don't need to add me. I just thought I'd give feedbac
Jeremy Huntwork wrote:
Dan Nicholson wrote:
A lot of newlines that were ignored, a couple chunks that are indented
for some reason. Not a show stopper, but something to think about.
Maybe some more tweaking is necessary in that Python conversion
script.
I'm pretty sure this won't exist f
Bruce Dubbs wrote:
> Please watch the trimming so who said what doesn't get mixed
> up. Jeremy did not say the above. I did.
Whoops! :) Sorry about that. :)
> No offense taken. However, I personally do not want to cater to an
> application that is notorious for not following standards.
> IE
On 1/22/06, Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
>
> Please log in and play around with the tickets, wiki, etc. If you don't
> have the necessary permissions to make a change (I tried to get all
> current devs all appropriate permissions for their project), email me
> and I'll fix it up.
>
>
Dan Nicholson wrote:
Well, I went to the blfs tickets and logged in and that worked. I
tried to add a comment to a random ticket and I couldn't find any way
to do it. Maybe I don't have enough permissions yet.
Same as above with the lfs tickets.
I've only given permission out to current dev
Richard A Downing wrote:
I have a login ([EMAIL PROTECTED]) for BLFS which I know the
password (and checked it with Bogzilla), but trac doesn't let me log in.
Or perhaps you're just picking on me! (:-)
R.
Were you trying the LFS Trac env. or the BLFS one? Either way, I'll add
you to both. Gi
On Sun, 22 Jan 2006 19:25:36 -0500
Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
> Matthew Burgess wrote:
> > immediately though, of course. I think another two weeks of
> > testing by *all* members of the community, be they developers or
> > our beloved users, is still necessary to ensure we can al
Bruce Dubbs wrote:
> No offense taken. However, I personally do not want to cater to an
> application that is notorious for not following standards. IE users are
> not our target audience.
Agreed. But I still wanted to see if I could fix that. A little
mis-alignment is one thing, having the main
David Fix wrote:
> Jeremy Huntwork wrote:
>
>>David Fix wrote:
>>>Just wanted to mention that the penguin still looks funny in IE. ;)
>>
>>And this matters...how?
>>
>> -- Bruce
Please watch the trimming so who said what doesn't get mixed up. Jeremy
did not say the above. I did.
> Just figu
Jeremy Huntwork wrote:
> David Fix wrote:
>> Jeremy Huntwork wrote:
>>
>>> Just pinging this.
>>
>>
>> Just wanted to mention that the penguin still looks funny in IE. ;)
>
> And this matters...how?
>
> -- Bruce
Just figured if you weren't aware of the issue (many of you are running
Mozill
David Fix wrote:
> Jeremy Huntwork wrote:
>
>>Just pinging this.
>
>
> Just wanted to mention that the penguin still looks funny in IE. ;)
And this matters...how?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the
Jeremy Huntwork wrote:
> Just pinging this.
Just wanted to mention that the penguin still looks funny in IE. ;)
Dave
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Matthew Burgess wrote:
> immediately though, of course. I think another two weeks of testing by
> *all* members of the community, be they developers or our beloved users,
> is still necessary to ensure we can all make the best use of this tool.
> If you could provide feedback about usability or l
Matthew Burgess wrote:
>
> 7) There is no "Read" link in the menu bar described above. How does
> putting the rendered version of the book on the wiki.l14h.org site get
> handled by Trac - is it just a couple of Rewrite rules or similar to
> request that Trac just passes handling of serving the s
Jeremy Huntwork wrote:
Well, the signal to noise ratio in this thread was probably the lowest
I've seen for a long time on this list. To say I'm disappointed in the
behaviour/attitude of certain contributors would be putting it very
mildly indeed.
That aside, here are my thoughts on Tra
Jeremy Huntwork wrote:
> Jeremy Huntwork wrote:
>
>>So, my plan is to manually add the 'Opened' time to the 'Last modified'
>>field in the bugs database. Any objections?
>
>
> I made this change on the backup database on anduin:
>
> 'update bugs set delta_ts=creation_ts where delta_ts="-00-
Jeremy Huntwork wrote:
> So, my plan is to manually add the 'Opened' time to the 'Last modified'
> field in the bugs database. Any objections?
I made this change on the backup database on anduin:
'update bugs set delta_ts=creation_ts where delta_ts="-00-00 00:00:00";'
It fixed the problem. S
Bruce Dubbs wrote:
>
> No. It just means that there was a glitch that needs to be worked out
> as a part of the conversion. We won't (can't) upgrade to the new system
> until all such problems are worked out.
I think I found the problem. (Btw, I was pinging the wrong bug in
blfs-bugs. I thought
El Jueves, 19 de Enero de 2006 12:41, Jeremy Huntwork escribió:
> In my experience only ViewCVS does it this way. Every other different
> piece of software I've used shows the file right off. Anyway, I wonder
> if there's a way to control this, and I can look into it...
Actually I see more logica
On Wed, Jan 18, 2006 at 11:07:41PM -0600, DJ Lucas wrote:
> Furthur, the default view in every webviewer of a repository that I've
> seen is to show the revision history and I don't really see a good
> reason for change. Not that it's such a problem, it is only one more
> click, but it is just
On Wed, Jan 18, 2006 at 09:08:49PM -0700, Archaic wrote:
> That implies that joe random shouldn't be able to file a bug. Do we want
> this? I personally don't mind as I think people should take their issue
> to -support or -dev before filing bogus bugs, but that may just be me.
Sorry if this wasn'
Jeremy Huntwork wrote:
DJ Lucas wrote:
The very first (and most annoying) thing I've noticed (that will affect
me) is that the default when clicking on a file in the source browser is
the current revision instead of revision history. That will just drive
me batty!
Heh, that's funny. I felt
On Wed, Jan 18, 2006 at 07:10:42AM -0500, Jeremy Huntwork wrote:
> DJ Lucas wrote:
>
> > The login button does not provide a link to create a new (unprivelaged)
> > account...may not be possible.
>
> There's a plugin to allow this, but I'm not sure we want to. I think
> it's a good thing to restr
On Tue, Jan 17, 2006 at 10:43:28PM -0600, Randy McMurchy wrote:
>
> Yes, this is true. And my apologies for my oversight in forgetting
> this. Can Trac be used for the Wiki and Bugzilla only, or must there
> be other baggage associated?
viewCVS is a hog and is ugly. Trac would fill this role beau
Randy McMurchy wrote:
> Sigh
>
> Obviously there was a difference in the search criteria. I have
> a very speedy broadband connection. There is no way that what you and
> I did was the same if it took me over a minute and you 10 seconds.
Fine. Don't beleive me, I don't care. You said you clic
DJ Lucas wrote:
> The very first (and most annoying) thing I've noticed (that will affect
> me) is that the default when clicking on a file in the source browser is
> the current revision instead of revision history. That will just drive
> me batty!
Heh, that's funny. I felt the opposite - I'm g
Randy McMurchy wrote:
>
> Jeez, Jeremy posted earlier that he will start tomorrow with the
> conversion, yet there's bugs preventing the system from even working
> correctly.
>
> Isn't there something wrong with this picture?
>
I said I'd start the conversion tomorrow, not that we have to start
Randy McMurchy wrote:
> You are trying to compare me asking you about some foreign package
> that I've never been exposed to, which has nothing to do with LFS,
> me, my situation, or anything I've ever been associated with, and
> because you are recommending the LFS community move to it... with
>
Randy McMurchy wrote:
> Justin R. Knierim wrote these words on 01/18/06 01:53 CST:
>
>
>>I read it differently as giving an example how fast the conversion could
>>be done. If he said "lets do it right now" and didn't say "if I start
>>tomorrow" I would agree with how you read into it.
>
>
>
Justin R. Knierim wrote these words on 01/18/06 01:53 CST:
> I read it differently as giving an example how fast the conversion could
> be done. If he said "lets do it right now" and didn't say "if I start
> tomorrow" I would agree with how you read into it.
Please, c'mon Justin, I'm just tryi
Randy McMurchy wrote:
What bothers me the most now, and what everyone should consider, is
that the guy that is pushing this whole deal said earlier this
evening that he would like to start tomorrow with the conversion to
put this crap in production...
Please re-read the post:
http://www.lin
Jeremy Huntwork wrote:
Randy McMurchy wrote:
What is on Anduin is not a test run. The BLFS stuff there is very
incomplete. It is not even close to being current with exiting
Bugzilla.
What am I missing here?
I didn't import all the bugs from the BLFS bugzilla database. One bug
was giving m
Tushar Teredesai wrote these words on 01/18/06 01:40 CST:
> I have only been skimming this thread but I *think* he is planning to
> upgrade subversion tomorrow, not move over everything to trac
> tomorrow. Also I believe he said if we run into problems with trac, we
> can hit the panic button and
On 1/18/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> What bothers me the most now, and what everyone should consider, is
> that the guy that is pushing this whole deal said earlier this
> evening that he would like to start tomorrow with the conversion to
> put this crap in production...
I ha
DJ Lucas wrote these words on 01/18/06 01:03 CST:
> Well, that changes things. It's definately not ready. Toss my last
> review right out the window for now.
What bothers me the most now, and what everyone should consider, is
that the guy that is pushing this whole deal said earlier this
eveni
Bruce Dubbs wrote these words on 01/18/06 00:48 CST:
> No. It just means that there was a glitch that needs to be worked out
> as a part of the conversion. We won't (can't) upgrade to the new system
> until all such problems are worked out.
And, the decision gets made before the "problems are w
Jeremy Huntwork wrote:
DJ Lucas wrote:
I trust this is for testing purposes...
This isn't to do with Trac, but Trac benefits by it. We are running
Subversion 1.1, IIRC. And 1.3.0 has been released and we feel it's a
good time to upgrade. If you have a concern with that, please voice it.
Jeremy Huntwork wrote these words on 01/18/06 00:15 CST:
> Finally, it wasn't a copout, it was unecessary work. Apply the same
> advice here that you hand out to newbies in lfs-support. If you can't be
> bothered to read, why should I answer the questions for you?
Absolutely ludricrous. Never min
Randy McMurchy wrote:
> Jeremy Huntwork wrote these words on 01/18/06 00:21 CST:
>>I didn't import all the bugs from the BLFS bugzilla database. One bug
>>was giving me trouble and I stopped after that. There is a python script
>>that converts them, it was hanging on one of the BLFS bugs.
> Does
Jeremy Huntwork wrote these words on 01/18/06 00:21 CST:
> I didn't import all the bugs from the BLFS bugzilla database. One bug
> was giving me trouble and I stopped after that. There is a python script
> that converts them, it was hanging on one of the BLFS bugs.
Does this mean the rest of them
Jeremy Huntwork wrote:
It took approximately 10 seconds here, just now. It started loading the
page immediately, and tickets appended into the list on the bottom
within the 10 seconds.
Yeah, that page with all bugs is 2.5MB in size, it just takes some time
to send it. Here on my lousy dsl c
Jeremy Huntwork wrote these words on 01/18/06 00:23 CST:
> Randy McMurchy wrote:
>>Yes, more than 60 seconds. Actually, worse than what we have. I
>
> It took approximately 10 seconds here, just now. It started loading the
> page immediately, and tickets appended into the list on the bottom
> with
Randy McMurchy wrote:
> Justin R. Knierim wrote these words on 01/18/06 00:08 CST:
>
>
>>It looks pretty complete to me. I see every bugzilla bug imported into
>>it. Click 'View Tickets' and then '{6}'. Caution, only an example,
>>takes a while to load all tickets.
>
>
> Yes, more than 60
Randy McMurchy wrote:
> What is on Anduin is not a test run. The BLFS stuff there is very
> incomplete. It is not even close to being current with exiting
> Bugzilla.
>
> What am I missing here?
>
I didn't import all the bugs from the BLFS bugzilla database. One bug
was giving me trouble and I s
Randy McMurchy wrote:
Yes, more than 60 seconds. Actually, worse than what we have. I
actually had to check my internet connection. But this is me being
stupid and naive on how to use the software.
What does the time compare for bugzilla to display a list of all 1000+
(or 2000+) bugs, for ea
Alexander E. Patrakov wrote:
> Looks good, but some functionality is not obvious. E.g., how to search
> all open LFS tickets for the word "udev" in their name (not in comments)?
I am sorry I never answered this.
You would click 'View Tickets' and then 'Custom Query' underneath it.
Or, and proba
Justin R. Knierim wrote these words on 01/18/06 00:08 CST:
> It looks pretty complete to me. I see every bugzilla bug imported into
> it. Click 'View Tickets' and then '{6}'. Caution, only an example,
> takes a while to load all tickets.
Yes, more than 60 seconds. Actually, worse than what w
Randy McMurchy wrote:
> Jeremy, I suppose you and I will never agree on this point, so let's
> just drop it. It was your job to do some research and relay to the
> community your findings. You failed in this. At least this is my
> opinion.
>
> "Go to the links provided" is a cop-out. The software
Randy McMurchy wrote:
What is on Anduin is not a test run. The BLFS stuff there is very
incomplete. It is not even close to being current with exiting
Bugzilla.
It looks pretty complete to me. I see every bugzilla bug imported into
it. Click 'View Tickets' and then '{6}'. Caution, only an
Jeremy Huntwork wrote these words on 01/17/06 23:52 CST:
> There already has been a test run.
What is on Anduin is not a test run. The BLFS stuff there is very
incomplete. It is not even close to being current with exiting
Bugzilla.
What am I missing here?
--
Randy
rmlscsi: [GNU ld version 2.
Jeremy Huntwork wrote these words on 01/17/06 23:39 CST:
> I don't see why I should be expected to spell out things that are
> spelled out via links provided.
A2D in a big way. And, thankfully to I'm sure everyone, my last
contribution to this thread.
But, Jeremy, you are dead wrong. More w
Jeremy Huntwork wrote these words on 01/17/06 23:11 CST:
> You said 'Let the community speak', I said they already have. That's the
> point.
I think perhaps you didn't understand what I was driving at. You've
probably contributed 20,000 words on the subject, most of them
reiterating what you had
DJ Lucas wrote:
> I trust this is for testing purposes...
This isn't to do with Trac, but Trac benefits by it. We are running
Subversion 1.1, IIRC. And 1.3.0 has been released and we feel it's a
good time to upgrade. If you have a concern with that, please voice it.
> I've been sitting back and
Jeremy Huntwork wrote:
I need to upgrade Subversion on Belgarath first (we should do that
regardless of Trac). Because it's a major upgrade, we need to svn dump
and load all our repos. I've dumped all of them already.
I trust this is for testing purposes...
Next step is building Subversion,
Randy McMurchy wrote:
> My comments tonight I suppose are because it is just now, tonight,
> after, what? a week or two of your proposal that we find out that
> you cannot divorce the different capabilities of Trac from one
> another? That you must more-or-less go all or nothing?
>
> This was not
Jeremy Huntwork wrote:
Then we install Trac and create an environment for each project. Lastly,
we import the bugzilla database for each one. (This might take some
time, a week, perhaps)
Sounds reasonable. I think it will be a good replacement, from playing
around with it. The 3 component
Bruce Dubbs wrote:
>
> Jeremy, what do you see for an implementation schedule?
I need to upgrade Subversion on Belgarath first (we should do that
regardless of Trac). Because it's a major upgrade, we need to svn dump
and load all our repos. I've dumped all of them already.
Next step is building
Randy McMurchy wrote:
> No, it cannot.
Yes, it can.
>From m-w.com
"2 : anxious concern : SOLICITUDE"
What's more, the phrase I used is well known and never, in my
experience, has it referred to terror.
> there. Some would say that is being too worrisome, I just think
> it is you being argument
Bruce Dubbs wrote these words on 01/17/06 22:37 CST:
> I don't agree with you on this, Randy. Jeremy's subjective feelings
> developed from installing and working with the system are relevant. He
> is also qualifying his statements as subjective which is good practice
> when data is incomplete.
Jeremy Huntwork wrote these words on 01/17/06 22:26 CST:
> I wasn't trying to be dramatic. 'Fear' can mean concern or caution, and
> is how I intended it.
No, it cannot. Fear to most English speakers is associated with
"afraid, danger, panic, alarm, fright, horror, terror" and many
others that I
Randy McMurchy wrote:
> Jeremy Huntwork wrote these words on 01/17/06 21:08 CST:
>
>>Apart from the fact that I
>>tested Trac on Anduin, which would have helped Trac's processing time,
>>Trac uses SQLite as a backend. I'm inclined to believe that is a mite
>>faster than Bugzilla's MySQL database,
Randy McMurchy wrote:
> Then please, restrict your comments (as they pertain to your suggestions)
> to material you have researched and know to be a fact. Quite frankly,
> your subjective guesses are meaningless.
Fine, in the future I will. But tell me why you are so venomous towards
me but would
Randy McMurchy wrote:
> There are no fears. Please don't use words that don't accurately
> describe what I've said. Drama isn't needed here, just the facts.
I wasn't trying to be dramatic. 'Fear' can mean concern or caution, and
is how I intended it. Why is there is a problem between us reading
th
Jeremy Huntwork wrote these words on 01/17/06 21:08 CST:
> Apart from the fact that I
> tested Trac on Anduin, which would have helped Trac's processing time,
> Trac uses SQLite as a backend. I'm inclined to believe that is a mite
> faster than Bugzilla's MySQL database, but I have no raw data to
Jeremy Huntwork wrote these words on 01/17/06 21:08 CST:
> Let me try to put some of your fears to rest.
There are no fears. Please don't use words that don't accurately
describe what I've said. Drama isn't needed here, just the facts.
>From the sounds of things, I am against the proposal. If th
Randy McMurchy wrote:
> Then, after Trac proves itself a success as a Bugzilla replacement,
> another component of our on-line presence can be migrated over, if it
> is deemed that we should go that route.
Let me try to put some of your fears to rest.
The source viewing capacity of Trac is so mu
Bruce Dubbs wrote these words on 01/17/06 18:38 CST:
> I think he means that we should benchmark both trac and bugzilla on the
> same hardware and under the same load to make a judgement about
> performance. IS that right, Randy?
Well, I simply *loathe* using Bugzilla on Belgarath right now. Shi
Jeremy Huntwork wrote:
> Randy McMurchy wrote:
>
>
>>I've often thought that the way Trac is being presented is less
>>than a "fair trial".
>
>
> Offer suggestions, please, on what you think would be a fair trial. I'm
> sorry that my excitement about it carries me along sometimes. :)
>
> FWIW
Jeremy Huntwork wrote:
>Offer suggestions, please, on what you think would be a fair trial. I'm
>sorry that my excitement about it carries me along sometimes. :)
>
>
>
Give it a run for its money, let the people that are going to use it,
use it, and see how it works under a load with people usi
Jeremy Huntwork wrote these words on 01/17/06 18:22 CST:
> FWIW, I believe all of the project leads have said that they'd like to
> use Trac. Also, the implementation of it won't be done overnight, so we
> should be able to hit a panic button if we need to.
I don't think anyone has argued that se
Randy McMurchy wrote:
> I've often thought that the way Trac is being presented is less
> than a "fair trial".
Offer suggestions, please, on what you think would be a fair trial. I'm
sorry that my excitement about it carries me along sometimes. :)
FWIW, I believe all of the project leads have s
Archaic wrote these words on 01/17/06 17:58 CST:
> Trac is on a faster computer than belg, so this may be a red herring.
> Bugzilla on anduin would be fast, too. I'm in favor of trac replacing
> BZ, though, so don't read it wrong. Just trying to be honest.
I've often thought that the way Trac is
Archaic wrote:
> On Mon, Jan 16, 2006 at 08:07:46AM -0500, Jeremy Huntwork wrote:
>
>>* Reading and searching through bugs/tickets is noticeably faster.
>
>
> Trac is on a faster computer than belg, so this may be a red herring.
> Bugzilla on anduin would be fast, too. I'm in favor of trac repla
On Mon, Jan 16, 2006 at 08:07:46AM -0500, Jeremy Huntwork wrote:
>
> * Reading and searching through bugs/tickets is noticeably faster.
Trac is on a faster computer than belg, so this may be a red herring.
Bugzilla on anduin would be fast, too. I'm in favor of trac replacing
BZ, though, so don't
Jeremy Huntwork wrote:
> At the least, we might very well be able to push out static content to
> the mirrors with Wiki or Trac links back to the main site.
It may not be clear what I meant here. I meant have dynamically
generated 'static HTML' pages based on what is currently published in
the Wik
Archaic wrote:
> So basically you are adding undue weight to your preference make option
> 2 require much more support that option 1? That seems jaded. First,
> let's throw out the facts.
I never really thoroughly responded to this, though I should have. I
don't know if this will change anyone's v
Jeremy Huntwork wrote:
> Did anyone get to look at this at all? Some benefits of Trac over
> Bugzilla that I've personally noticed:
[...]
> These are just some of the things that I appreciate about Trac. You
> might be able to find others. :)
My personal favourite:
* Everything is a Wiki and the
Jeremy Huntwork wrote:
> I will at my first opportunity. I'm still at work right now, and it's
> looking like it will be a long night. :( In the meantime, you are
> welcome to play around with the sample installation. Don't worry about
> adding sluff or junk tickets, etc. It's not a permanent insta
Randy McMurchy wrote:
I suppose I'm just not a big fan of changes, so I was hoping you
could summarize this. That way everyone could review it, and go use
it and know what to look for difference-wise. There's only been
about 6 people vote on this, I wouldn't really call it a 'community
decision'
Jeremy Huntwork wrote these words on 01/10/06 16:05 CST:
> So the weight has definitely shifted to number 2. Which is what I
> expected, and is fine. Unless there are any other objections then, I
> think we can safely say that we will be replacing Bugzilla and ViewCVS
> with a trac installation
Archaic wrote:
So basically you are adding undue weight to your preference make option
2 require much more support that option 1? That seems jaded.
No, I was just saying that we haven't gotten as much feedback as I would
have liked, and so far the votes seemed nearly even. I knew if I said
s
On Mon, 9 Jan 2006 12:11:07 +
Richard A Downing <[EMAIL PROTECTED]> wrote:
> On Sun, 08 Jan 2006 18:55:57 -0500
> Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
>
> > I would really like to get everyone's opinion.
> All things being equal I think this looks like a good candidate for a
> complete
On 1/10/06, Archaic <[EMAIL PROTECTED]> wrote:
>
> 1. The HTML as it stands is basically static.
> 2. The people who are allowed to edit the pages already have the
>ability.
> 3. The website is stable and works well.
> 4. The website includes some already scripted and automated dynamic
>con
On Mon, Jan 09, 2006 at 08:47:15PM -0500, Jeremy Huntwork wrote:
>
> Also, I'm still preferring that we choose option 1, IOW, that we use
> trac for as much as we can, including the main site. There have been a
> couple that have chosen that option, as well. So if we are going to go
> with 2, IOW,
Richard A Downing wrote:
> Does this increase the load on the server compared with a website +
> bugzilla or, perhaps, decrease it?
I think it distributes the load and is a "good thing". The wiki/bugs
are on anduin and svn is on belgarath. I think we could make a case for
a third server just for
BTW, I don't know if any of you happened to look at the sample site
using Internet Explorer. If so, something in IE's poor rendering of the
CSS is causing it to cut the logo in half. I haven't quite pinned that
bug down yet, but I'll look into it soon.
In the meantime, if you did happen to vie
On Sun, 08 Jan 2006 18:55:57 -0500
Jeremy Huntwork <[EMAIL PROTECTED]> wrote:
> I would really like to get everyone's opinion.
I like the look of this too. You've done a good job getting the
look-feel like the website.
I really like the SVN browser and the Changelog.
My only criticism is that t
Jeremy Huntwork wrote:
Here is a link to the sample site:
http://wiki.linuxfromscratch.org/lfs/
Looks good, but some functionality is not obvious. E.g., how to search
all open LFS tickets for the word "udev" in their name (not in comments)?
As for a replacement for ViewCVS, Trac is good.
Randy McMurchy wrote:
> Oh, wait a minute, now there is references to "intelligent viewers" in
> the statement directed to me. And in a negative way.
The statements weren't meant to be directed at you. And in hindsight the
words were poorly chosen.
Good day.
--
JH
--
http://linuxfromscratch.or
Jeremy Huntwork wrote these words on 01/08/06 21:02 CST:
> Not much of an artist are ya?
Oh, I don't know. Folks have always said I've created really nice
graphics on the web sites I've done.
And what is it with you anyway? I say I don't like your puzzle
piece and you have to insult me saying I'
Bruce Dubbs wrote:
>1. Replace Bugzilla
>2. Replace ViewCVS
>3. Be a target for multilib/i18n issues.
>
>I do not think is should replace the general website. I'd prefer to
>keep those pages static and archived in svn.
>
>
I would opt to keep everything entact until everyone has agreed that
Randy McMurchy wrote:
> The puzzle piece to me represents an incomplete project with not
> even a completed item for the puzzle piece to go into. To me it
> represents incompleteness. The improperly capitalized "linux", well,
> is improperly capitalized (in my opinion).
>
Not much of an artist ar
Jeremy Huntwork wrote these words on 01/08/06 17:55 CST:
> Note that if the community prefers items 2 or 3, I would still like to
> use the new logo on our exisiting sites, so comments on that are welcome
> as well.
I don't know what you mean by "new logo" but if it is that jigsaw
puzzle piece wi
Jeremy Huntwork wrote:
>2) Keep our existing website, but use Trac for a development wiki and to
>replace Bugzilla and ViewCVS. The wiki pages would only include
>development works in progress, not the main website pages, similar to
>how our previous wiki was set up.
>
>3) Keep everything as is, i
Jeremy Huntwork wrote:
Note that if the community prefers items 2 or 3, I would still like to
use the new logo on our exisiting sites, so comments on that are welcome
as well.
I very much like the way you can view the subversion tree, and the
bugzilla bugs now converted to tickets are much
1 - 100 of 101 matches
Mail list logo
