On Mon, Apr 25, 2011 at 12:49 PM, Mark Brontein <[email protected]>wrote:
> Hi, I have been lurking on this list waiting till the new site is up so I > can give tg 2.1 a try. (I have tried downloading it fromthe old site but ran > into too many problems trying to load and use the tutorials. > The tutorials are one of the many items we're going to be working on in the docs. Unfortunately, they're probably going to remain problematic for much of the next few months while we iron out the other issues that are at higher priority right now. I know the tutorials are a major item, but completing the current move and getting our next immediate bug fix releases out the door are more important. We've already taken longer on the move than we should have, and I'm afraid that's mostly my fault for letting things happen the way they did. Even still, we're completing the major portion of the move this week, and dealing with cleanup after that's done. Once we've got that done, and 2.0.4 and 2.1.1 out the door, I'll be working in a mixed mode, working on docs and code as time and needs dictate. Completely cleaning things up, though, will take time. I'm sorry, I can't prevent that. > What would the best way to convey feedback and suggestions on documentation > and website content (from the perspective of a newbie). Trouble tickets? > comments here? Is the site content and documentation files in Git so that > one could create a fork and make suggested changes there? (not that I know > how to that). > Broadly speaking, we have three different kinds of content on the site. CMS managed (which is done by way of tgext.pages, and is not really accessible except via a specialized web interface), static documentation files, and static downloadable files. The downloadable files are in a git repository, and likely should be made publicly accessible, but this is not the case at this time. The last, the docs, are in a git repository that is publicly accessible. If you are looking for the 2.x docs, look here: https://sourceforge.net/p/turbogears2/tg2docs/ Now, to provide feedback? Any of the methods will work. You can fork a repository on sf.net, and send in pull requests. You can open tickets. You can send email to the ML. The best choice, though, is to open tickets. This provides us with a working memory that we can use while we try to answer things. If you're just asking for help, the ML is great. We will answer, and I am personally trying to answer everything (well, unless I see it's already answered entirely by someone else). If you're sending in patches, the best choice will be to go to sf.net, fork a repository, and send in a pull request. We'll go from there then. -- 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.
