On Tue, May 3, 2011 at 12:18 AM, Pavel Strashkin <[email protected]>wrote:
> I think you should put a links to main releases (2.x, 1.1.x, ...) on > the home page as it was done for an old site. These links could have 3 > sub-links under it: direct download link (Download), link to > documentation (Documentation) and link to changelog (ChangeLog). I > believe it will look very well. > I'll try to change this around, but am already looking towards the next revision of the site. We need to add some more information there to include stuff like feeds from the ML, possibly code commit feeds, etc. So adding those links is likely to occur then, rather than right away. Problem for now is the lack of space on the menu bar. We have to be careful there, but the next major update will be a good time to look at that. On Tue, May 3, 2011 at 12:27 AM, Pavel Strashkin <[email protected]>wrote: > I'm sorry that i'm asking here, but why do we need 2 google groups? > turbogears and tg-trunk. Let's keep only one (turbogears) so people > will not be confused like me and so on. I haven't knew about second > group (tg-trunk) and i missed a lot of (or few) interesting questions > and discussions. > First off: Don't be sorry for asking a question, whether it be here, the other ML, or even some other forum. As long as you make sure we can see it and try to answer it, that's all I can ask for. As to why there are two lists: This is a fairly common dividing line that occurs in OSS projects. The -trunk list is for people who want to keep up with the latest and greatest development version. For instance, keeping track of what's going on with Alessandro as he plows through tickets, or keeping up with my notes about the buildbot and the like. The regular list is meant more for people to use to discuss how to use the framework, as opposed to how to maintain the framework. Right now, I think the traffic is pretty much not paying attention to that dividing line, so we should look at whether or not we should continue having two groups. I'm going to hold off on that until we get things more back to normal. Once we have that, and the traffic can be more properly split, I think we'll see a stronger value in the two lists, and I would hate to have to close and re-open a list for something that small. On Tue, May 3, 2011 at 3:22 AM, Diez B. Roggisch <[email protected]> wrote: > We don't use buildbot, so I don't know much about it. But we wrote our own > deployment-system, and use that inside our also homegrown continuous > intergration system. I'm happy to share code & work effort to make it run > for more general scenario. It shouldn't be hard actually, as it's pretty > modular and simple already. So, give me a holler if you think it helps or > need more info. > Actually, I got buildbot working. It'll do all of the steps that are required. I just can't get lxml to install properly into a virtualenv for some reason, despite having done so in the past. Just spent the past hour or so working on hat, in fact, and my frustration level has gotten too high. I'll try again tomorrow night. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen -- 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.
