Hi Simon, Welcome to the list and happy hacking!
On Tue, Aug 5, 2008 at 2:00 PM, Simon Michael <[EMAIL PROTECTED]> wrote: > There seems to be quite a delay between sending a patch and seeing it > appear in the darcs-user list. I am reading it via gmane. My email listing shows that your patch arrived before this email. So, I think it may be a gmane issue or perhaps this email list just has a bigger turn around time than you're used to. Or perhaps I was slow to moderate, see below. > > Is there some human action involved ? What could we do to speed this up > ? It is one of those little things that will increase the instant > gratification factor that encourages contributors. I'm one of the list moderators, but I only moderate the list on weekday mornings. The moderation is just for people that have never sent to the list before, patches go through automatically if you're already signed up. We simply use the moderation as a way to remove spam, while keeping the list open. > On a related note, a bot in #darcs that announces patch/bug activity > would also help. I've been looking for one that works with darcs repos > for a while. The only working solution I found was ciabot, does anyone > know of another ? I know there is one good tool for watching a repo and > sending email notifications (name escapes me), I guess that could be > adapted. You might be interested in some of the following tools: http://wiki.darcs.net/DarcsWiki/DarcsPatchWatch http://wiki.darcs.net/DarcsWiki/DarcsMonitor http://darcswatch.nomeata.de/repo_http:__darcs.net_.html All of the above can be found here: http://wiki.darcs.net/DarcsWiki/RelatedSoftware Post-hooks can be used to implement just about any functionality you want when patches are applied to a repository. With that said, don't expect David to maintain the solution you want. He's made it quite clear in the past that we need to keep the main repository setup simple for maintainers. This in no way prevents clever solutions though, since the main repository and mailing list is still publicly accessible. I don't mean to discourage you, I just want to be clear that the best solutions will require little or no involvement from the maintainer. One thing you could do is periodically poll the main repo, and have a post-hook that does your annoucements. Or, better yet, you could volunteer to have a buildbot, and then you'd automatically get notified when new patches are pushed and perhaps customize your buildbot to notify you some way. Announcing patches that are sent to darcs-users does seem a bit silly to me since they are already sent here and announced implicity and David replies ASAP letting you know if the patch is applied or rejected. So I think what you want is that any patch applied to the repository at http://darcs.net is announced. The only patches that end up there without going through the mailing list are patches that David pushes himself. Since he's the original author and current maintainer he often doesn't submit patches for review, unless the changes need to be discussed with others. This isn't really a problem normally because the bug database picks up resolved issues from patch names now. Now that I've typed all that out, I'm left wonder what we would gain by having a bot tell #darcs that patches are applied. Thanks for your interest in hacking darcs! Jason
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
