[00:17:08] --- Russ has left: Disconnected [02:22:32] --- dev-zero@jabber.org has left [02:36:17] --- dev-zero@jabber.org has become available [02:46:54] --- deason has left [04:11:57] --- dev-zero@jabber.org has left [05:02:56] --- dev-zero@jabber.org has become available [05:29:32] --- Jeffrey Altman has left: Replaced by new connection [06:26:10] --- dev-zero@jabber.org has left [07:42:30] --- cclausen has left [10:03:28] --- deason has become available [11:17:51] --- edgester has become available [11:32:26] --- dev-zero@jabber.org has become available [11:36:55] Given my grand login doesn't seem to have been set up, is there anyone around who can give me a tar or zip'd copy of the OpenAFS CVSROOT ? [11:36:55] --- matt has left: Lost connection [11:37:37] gimme a moment [11:38:08] Providing what's in /afs/.grand.central.org is up to date, it's just the CVSROOT I need (or specifically, just val-tags) [11:39:54] i have no idea if that's up to date. i will give you everything you might need. [12:11:59] I think emailing the newsletter to all three lists is overkill. I think that most people subscribed to -devel are on all three lists and those on -info are on -announce as well. [12:14:25] Jeff H.: thanks for releasing the newsletter for -announce. I think a separate mailing list for the newsletter would really limit the exposure. I think sending it to one or more of the main three lists is the best approach [12:19:50] on git workflow, I think it will take some experimentation to figure out what's going to work best [12:21:53] I'm hoping that the newsletter will encourage people to be forthcoming with their projects, even if they're half-baked. I also think that the newsletter would be a good place to publish official and unofficial git repos. [12:23:15] At the risk of repeating myself ad naseum, I'm open to any and all suggestions on changes to the newsletter. [12:24:13] it strikes me as long [12:24:15] It's more effort than I expected, but I've had 4 people tell me that they like the newsletter and appreciate the effort, so that makes it worth it [12:24:24] yeah, it is a little long [12:24:27] but I haven't thought about it enough to give suggestions [12:24:33] I noticed that when editing it [12:25:17] Maybe I need to shorten the project summaries [12:26:35] I'll look at it either today or tomorrow, and see what I can come up with [12:27:32] thanks! [12:28:11] I do compromise on editing more vs timeliness [12:28:21] in favor of timeliness [12:30:00] * edgester thinks out loud. I wonder if moving the project contact info to the web site would be any better, but probably not. [12:30:26] summatusmentis: This newsletter had more stuff because of the workshop [12:30:38] granted, it happens [12:30:38] keep that in mind [12:30:47] ya [12:47:08] --- dev-zero@jabber.org has left [12:57:48] --- Russ has become available [17:09:13] --- Jeffrey Altman has become available [17:12:02] I think it only makes sense to report project updates when something has changed. [17:17:22] --- dev-zero@jabber.org has become available [19:57:49] in the case of no updates, I think it' useful to say "no updates" [19:58:14] unless there are no updates for a while, then just remove it [20:00:16] I'm not sure Harmut understood what I was asking for, but I just published it anyway to get it done. [21:08:52] --- edgester has left [21:38:14] --- Jeffrey Altman has left