Well, if someone has Kevin's phone number they should call him, I have Mark's phone but he is away for the holidays, so I am not going to bother him. I have already suggested that whoever is in charge (Lee M. and Kevin) should have a reporting tool page them when the site is down. You are right, if the project maintainers can't keep a TG site up, it really does not look good at all. I don't know what to say other than it's unacceptable and a solution is long past due. I know people are complaining a lot and cursing over this issue. I have to admit myself, that django and RoR maybe where my focus goes. If it takes 2 days for someone to just put the site back up, what else is not being paid attention to?
IMO, this has the potential to be the downfall of TG. Some serious restructuring needs to be factored in.. the documentation has been improved greatly, but it is still very much in need of work, the book.. well sadly I feel it needs a complete rewrite and a better publishing company with different editors/reviewers. Pearson really missed the boat here. I give mark a lot of credit for his valiant effort in writing the book and being it his first book, well he did a phenomenal job. But that doesn't mean that errors in the book aren't enough to drive anyone mad. Especially those who are new to TG. In my opinion the book covers a lot and is very informative but the dots don't seem to be connected clearly.I would much rather have had the book come out in a few months later, than feel so rushed. PR has a lot to do with 'word of mouth' we all know that.. but how can you spread the word if you can't even show them a website.. bad bad bad! Enough of the problem... What's the solution? I am not quite certain at this point but I do have some fundamental ideals. - The site must remain up always .. mirror it and the main page should be static to show the mirrors list. - Documentation.. stop being lazy, me included.. write documentation that is clear and precise not something half-ass just for the sake of. - Screencasts are loved by all... not build this in minutes.. but more informative. One of the problems is that a lot of experienced developers forget... is that not everybody has their skill level. Writing documenation that they themselves can understand may not be what novices can understand, and for TG to be successful, novices NEED to understand. There are a lot of people that have done a great job helping this project and taking the time from their personal lives to do so, let's not assume because of my post everyone is a slacker. That is for sure not the case. I personally thank everyone that has contributed. I offered to help Sys Admin the site, but because of holding the key's to the kingdom is so sacred, It was declined. Even though I have commit access to python.org. If credibility was the issue, well there are such things as personal references. It's obvious that 2 people is not enough right now to maintain turbogears.org. Mike On 12/31/06, Nyenyec N <[EMAIL PROTECTED]> wrote:
Thanks Elvelind, it worked for me. -- nyenyec On 12/31/06, Elvelind Grandin <[EMAIL PROTECTED]> wrote: > > For those that are trying to install turbogears you should be able to use: > > easy_install -fhttp://dumbledore.turbogears.org/eggs/ turbogears > > > -- > cheers > elvelind grandin > > > > >
-- -mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
