need a /reload command for plugins

[anon]

need a /reload command for plugins

[anonymous]

There is a /reload command :) only works in chatrooms I believe, not in personal chats

[anon]

Nice try. However, "Command /reload is not recognized" in the latest svn.

[Talivan]

Sep16Sage LaTorra? Hey Pete, thanks for the cmonemt.Ideally it would be wholly separated, but I haven't been able to get that to work while still making the layout work without a lot of manual intervention. It's an ongoing process, but improving it (both by making the text less bound to the layout and making the layout more automated) is definitely a goal.Licensing is another interesting issue. Vincent's license on the original text is kind of vague, basically do what you want as long as you don't copy text directly, and even that might be okay if you ask. I need to ask vincent directly what that means for what licenses we can apply. I've had at least a couple of people ask about it, so it needs to be made clear somehow. My current leaning is Creative Commons, just so I don't have to mess with finding a different license.Other style sheets should be possible, especially with a little hacking. I can easily imagine automated python scripts to convert the xml to LaTex? or html (with hand crafted css), and I imagine there are probably even better ways.Anyway, thanks for your wall of text, I've attempted to reply with my own wall of text.

[Antonio]

Havading worked on some large prejcots at Canonadiadcal, I’m not offended by your post Here are a few points from my experiences:1. Use branches. Comadmitadting changes is a great way of doing work, but don’t put paradtially comadplete code on mainline.2. Do pre-merge reviews. Once you’re using branches, the review quesadtion becomes “pre-merge” or “post-merge”. As you’re doing your work on branches there isn’t the same urgency to get things merged, so pre-merge reviews don’t blocka0you. 3. Keep branches small and focused. Review time does not scale linadearly with the size of the change, so you’ll get betadter reviews with smaller changes. If a change really is large, it can be broadken down into smaller increadmenadtal branches that can be reviewed separately.4. Keep the trunk prisadtine. As menadtioned, havading the trunk fail to build is lame. At a minadiadmum, force a test build for each merge/commit to the mainadline and preferadably a test suite run. This is tedious but easy to autoadmate, so that is exactly what we do with PQM () — no need for the develadoper to wait around for the tests to run. Ideadally any mainadline comadmit can be a canaddiaddate for release.5. Budadget code review into the cycle. if you are writading more code than you can review then you’re doing it wrong. Find ways to get more of the team reviewading code, and give credit to the reviewaders when merging.We do use DVCS for all this, but it is not a preadreqaduiadsite. For a globadally disadtribaduted team it is ceradtainly very helpadful though …