schedule chat in irc?
Daniel Chudnov
poke at it more lately. I have some tasks I'd like to use it to
accomplish, but I know that that's true of several other folks here,
too, and that our diverse tasks are, well, diverse. It concerns me a
bit that there isn't an explicit roadmap or plan, and that without one,
our goals and interests might tend to pull the project apart rather than
make it stronger.
Er, pep talk over, sorry.
Anyway - would folks be interested in scheduling an IRC chat to spell
out everybody's goals for fbo, to work on prioritizing that some, and to
carve up a few responsibilities? I don't see a need to impose strict
timetables, or push anybody harder than you all clearly already push
yourselves. Instead I'd just want to see a plan develop as to where
things are going, and how, so it's clear to all the developers and
potential users out there just what the whole thing is about and what to
expect from it. And so we can work out some details along the way like
"how are we going to manage tickets" and the like.
Let me know if you're interested, and if enough folks sign on, we'll
work out a time and channel.
Thanks! -Dan
Dan Scott
--
Dan Scott
Laurentian University
Mike Beccaria
Gabriel Farrell
> I've been a fan of this project since its inception and have started to
> poke at it more lately. I have some tasks I'd like to use it to
> accomplish, but I know that that's true of several other folks here,
> too, and that our diverse tasks are, well, diverse. It concerns me a
> bit that there isn't an explicit roadmap or plan, and that without one,
> our goals and interests might tend to pull the project apart rather than
> make it stronger.
>
to collaborate and overlap smoothly where necessary.
> Anyway - would folks be interested in scheduling an IRC chat to spell
> out everybody's goals for fbo, to work on prioritizing that some, and to
> carve up a few responsibilities? I don't see a need to impose strict
> timetables, or push anybody harder than you all clearly already push
> yourselves. Instead I'd just want to see a plan develop as to where
> things are going, and how, so it's clear to all the developers and
> potential users out there just what the whole thing is about and what to
> expect from it. And so we can work out some details along the way like
> "how are we going to manage tickets" and the like.
>
certainly be a place for roadmaps and the like. More on that in
another post.
> Let me know if you're interested, and if enough folks sign on, we'll
> work out a time and channel.
>
more realistic. And I don't see anything wrong with having the
conversation on #code4lib.
gsf
Dan Chudnov
> I believe I've just about got Trac working just right -- it could
> certainly be a place for roadmaps and the like.
Great!
>> Let me know if you're interested, and if enough folks sign on, we'll
>> work out a time and channel.
>
> We could try for tomorrow or Friday, but maybe some time next week is
> more realistic. And I don't see anything wrong with having the
> conversation on #code4lib.
My only concern with using #code4lib is that it tends to be pretty
trafficy during the (eastern time-ish) workday. So i'd bet that if we
meet between 9-6pm ET, we'd be better off in our own channel. If we
do it at night, #c4l would be fine, or if it's not, we can always
relocate.
That said, I'll propose two times and we'll see if we can line it up:
#1 - This Friday, 7 December, 3-4pm ET (in "#facbackopac" on freenode)
#2 - Next Tuesday, 11 December, 9-10pm ET (in #code4lib)
I haven't really spelled out the things I'd like to see fbo do in the
future yet, so I'll write up some of these thoughts separately to save
a few steps. I'd be really interested in hearing other folks'
thoughts (and hopes and dreams and nefarious intentions) too.
Looking forward to it! -Dan
Daniel Lovins
I don't know much I'd be able to contribute yet, but I'm definitely interested.
-- Daniel (Lovins)
Gabriel Farrell
> Dan,
>
> I don't know much I'd be able to contribute yet, but I'm definitely
> interested.
>
> -- Daniel (Lovins)
>
Friday afternoon is the better of the two dates for me. I like the
idea of having it in #code4lib because it's more out in the open, and
this kind of project talk in the channel lifts the general discussion
to a more, shall we say, respectable nature. But I could see there
being plenty of disruptions and distractions on a Friday afternoon, so
a separate channel is probably the right thing. I'm sure our
discussion will be mentioned, if not announced, in #code4lib anyway.
The one and only Gabriel
Dan Scott
Friday works for me, and I concur with Gabriel; announce it in
#code4lib, but we'll get a room. I mean, we don't want a repeat of the
rsinger/jrochkind U2 shows do we? :)
Daniel Chudnov
> Friday works for me, and I concur with Gabriel; announce it in
> #code4lib, but we'll get a room. I mean, we don't want a repeat of the
> rsinger/jrochkind U2 shows do we? :)
>
No, we really don't. And especially not on the same stage at the same
time. :)
So that's two Dans and a Gabe signing on for tomorrow (Friday) at 3pm
ET, with a Mike and a Daniel also interested but not yet confirmed on
the time. Let's roll ahead with Friday at 3pm ET in #facbackopac on
freenode, or to coordinate an alternate location in #code4lib if that
fails. I hope Mike and Daniel both can join us too - Daniel, have you
been to IRC-land before? Let me know if you need any info on signing in.
Maybe we could spend the hour doing something like this:
- 20min going "around the room" saying/brainstorming what we want from
fbo and associated tasks
- 20min talking about those tasks, prioritizing/sequencing, and naming
names of who's intending to do what and when to do it
- 20min talking about meta stuff like handling tickets,
copyright/license, etc.
We can fire up and share a google doc while the session's going to be
sure we track all of this too.
Does this work for everybody?
-Dan
Daniel Lovins
-- Daniel L.
Gabriel Farrell
> Does this work for everybody?
>
> -Dan
gsf
Jodi Schneider
-Jodi