19:33:44 <mizmo> #startmeeting hubs-devel
19:33:44 <zodbot> Meeting started Wed Jan  4 19:33:44 2017 UTC.  The chair is mizmo. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:33:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:33:44 <zodbot> The meeting name has been set to 'hubs-devel'
19:34:13 <mizmo> #topic Regional Hubs Feature Prioritization
19:35:35 <mizmo> #agreed while budget tracking features are important to many, we decided it's out of scope for this regional hubs but we'll design with budget concerns in mind (eg providing fields in events to store budgetary data - allocation, actual cost, investment returns (measurable outcomes) etc)
19:36:23 <mizmo> #agreed Making local resources (events, people, groups) visible, findable, and scalable is a primary goal for Regional hubs
19:37:13 <mizmo> From  shillman's notes: "There are a lot of different places that have information about Fedora-related events. This can make it difficult to know if you can’t find any  nearby because they don’t exist, or because you haven’t looked in the right place. This makes it difficult to prioritize event attendance. There are also many different places to find non-Fedora-related but relevant events, which  makes it difficult
19:37:13 <mizmo> prioritize Fedora sponsorship."
19:37:37 <mizmo> #action mock up a master list of regional hubs, filterable
19:37:53 <mizmo> #action mockup a master list of regional hubs members, filterable (shillman)
19:38:10 <mizmo> #action mock up a master list of regional hubs events, filterable (shillman)
19:38:20 <mizmo> #agreed our goal is that regional hubs provides a canonical list of local resources - events and people
19:38:25 <mizmo> ok
19:38:28 <mizmo> anythin else from this note?
19:39:08 <mizmo> i think generally if the system is attractive and inviting and we get people using it, the data wont be stale. thats a risk here i guess, if people don't use it, it won't be the canonical list to refer to and will be just yet another place that data is scattered to
19:39:08 <shillman> Not that I'm seeing?
19:39:39 <shillman> Yeah, that's a concern. and I don't expect to be useful for non-fedora event purposes.
19:39:57 <mizmo> #info Note #2: "It would be useful for us to tie Hubs into social media so that people can access the types of social media that is popular in their countries if they want to do so (not everyone uses IRC natively). Eg Twitter, facebook, telegram, Eventbrite, instagram"
19:40:12 <mizmo> so this is a good idea
19:40:18 <mizmo> i think it would involve the feed widget
19:40:22 <shillman> Do we want to provide support for grabbing Fedora event data from elsewhere? To encourag euse?
19:40:41 <mizmo> maybe. if there are other sources of event data.
19:41:01 <shillman> I think that there is, and that's part of the problem (there's multiple).
19:41:02 <mizmo> did any specific ones come up in your convos?
19:41:09 <mizmo> i usually find out about events from planet fedora
19:41:11 <mizmo> or mailing lists
19:41:31 <mizmo> for me blogs are the main way to find out
19:42:17 <shillman> Which may be hard to grab that data from...
19:42:23 <shillman> But things like: https://fedoraproject.org/wiki/Events
19:42:55 <mizmo> so i think we need to be the new /wiki/Events - we need to provide a new version of that
19:44:10 <shillman> Because blogs are hard to grab info from.
19:44:12 <shillman> OK.
19:44:25 <shillman> (and mailing lists ahve the same problem)
19:44:29 <mizmo> you can see how it ties into the budget concerns with estimated attendance and event report links
19:44:57 <shillman> (but maybe we can make it easier to do; when there are blog entries and mailing lists, do we have any chance of detecting thta there is an event and suggesting it get added to our events list?
19:45:02 <shillman> *nodnod* Yeah
19:45:40 <mizmo> so i guess another measure of success here -
19:45:57 <mizmo> #idea we'd like to provide a better replacement interface for what http://fedoraproject.org/wiki/Events does
19:47:29 <mizmo> that would be a good measure of success
19:47:35 <shillman> *nod*
19:47:41 <mizmo> yeh we could try to detect that its event related
19:47:49 <shillman> Yeah? That'd be huge, if so.
19:48:03 <shillman> Because those "add to calendar" buttons google has are really handy.
19:49:18 <mizmo> i have been thinking about some machine learning stuff. i wouldn't make it a priority though to try to do the detectoin but at some point we probabaly could
19:49:26 <shillman> *nod*
19:49:29 <shillman> k
19:49:32 <mizmo> soi think an action item here too, i want to come back to that wiki page but
19:49:39 <mizmo> #action compile a list of regions and their social media prefs
19:50:03 <mizmo> so we know what social media things we need hooks for. so we can provide facilities to hook a given regional hub up to twitter, telegram etc
19:50:24 <mizmo> okay so back to the Events wiki
19:50:30 <mizmo> are there other sources beyond this that folks you talked tomentioned?
19:50:48 <shillman> I think I have that list able to be compiled, but I'd want to check with my interviees to make sure I didn't miss anything.
19:51:02 <mizmo> okay great
19:51:43 <shillman> Um. What you've mentioned, I think: blogs, social networking, mailing lists, direct email... let me check if there's anything else. One sec.
19:52:29 <mizmo> we'd want specific apps to be in the list per region
19:53:14 <shillman> IRC... lwn.net, wiki pages...
19:54:07 <mizmo> okay cool
19:54:31 <shillman> telegram.. pro-linux.de/kalender
19:54:33 <mizmo> so honestly, the events wiki is probably the main canonical resource, but it doesn't get a lot of exposure because its a wiki, so its mostly used by people planning and not people looking for events nearby
19:54:46 <shillman> Yeah, it looks liek lots of different places.
19:56:09 <mizmo> so lets make this events list thats part of regional hubs the new wiki/Events
19:56:11 <mizmo> ok
19:56:13 <mizmo> next note
19:56:42 <mizmo> #info note #3: "Many ambassadors are local resources for their local Fedora community. It may be useful to make as many of those resources easily available without having to go through an overworked ambassador."
19:57:04 <mizmo> so did you get into details with any of the ambassadors about what kinds of resources they provided?
19:57:23 <mizmo> #chair shillman
19:57:23 <zodbot> Current chairs: mizmo shillman
19:57:37 <mizmo> ^ (so you can use tags too, sorry i forgot you have to be chair to do)
19:57:49 <shillman> :)
19:58:17 <mizmo> #idea a FAQ per each regional hub, where the local ambassadors can list the questions/answers they get asked over and over to point to (would it save them time / burnout?)
19:58:29 <shillman> Anything from helping with wiki pages to supplying graphics, forms, letters...
19:58:36 <shillman> Ah! That would likely be handy.
19:59:01 <mizmo> #idea each regional hub could have a library widget with commonly asked-for resources (forms, design assets, etc)
19:59:19 <mizmo> the library widget is already a thing but really needs a decent visual design
19:59:40 * mizmo tries to think of other ideas
19:59:41 <mizmo> i think sometimes theres per release resources that come out
19:59:49 <mizmo> like for F25, the media art, is a big thing the ambassadors ask the design team for
19:59:58 <shillman> website work, videos, docs, visa letters, invitation/sponsorship letters
19:59:59 <mizmo> so if there was a way to make release specific assets pop up too
20:00:01 <shillman> *nodnod*
20:00:29 <mizmo> #idea a widget that points to release-specific assets of interest to regional folks (release party posters, media art, etc)
20:00:33 <shillman> event creation... peopel managing...
20:00:38 <shillman> Lots of different things, really.
20:02:07 <mizmo> #idea event widget that creates an event on fedocal and also gets added to the master events list to enable regional people to create local events
20:02:17 <mizmo> shillman: what are you thinking in terms of people managing?
20:02:18 <mizmo> eg volunteer sign up?
20:03:31 <shillman> I think it's more that some ambassadors help their people learn how to manage other people. LIke, sponsors for events, venues, things like that.
20:03:52 <shillman> Probably also volunteer sign up and recruitment.
20:04:11 <mizmo> #idea volunteer recruitment / sign up / tracking built into local events
20:04:33 <mizmo> so it sounds like best practices / training almost
20:04:43 <shillman> Yeah, agreed.
20:05:00 <shillman> I think it's... how to best get things done in their local area.
20:05:18 <shillman> Which varies by country and region and even within countries, I'm sure.
20:05:48 <mizmo> #idea work with commops to develop general best practices / training for regional ambassadors, and enable local organizers to fork their own version of those guidelines with local details (?)
20:05:59 <shillman> Mmm!
20:06:50 <mizmo> any other ideas?
20:07:15 <mizmo> oh
20:07:33 <mizmo> #idea some kind of way to store a list of local external resources: local vendors + venues
20:08:27 <shillman> Maybe something to help make event organizing easier? I'm not sure if that counts as being a resource or not, but lots of ambassadors need to do it.
20:09:01 <shillman> (starting to have trouble focusing, FYI)
20:10:21 <shillman> Maybe move to new note?
20:10:31 <mizmo> sure
20:11:06 <mizmo> #info note #4: It is difficult to find Fedora members who are in a specific location, especially if they are not ambassadors.
20:11:20 <mizmo> so this one i think we have covered - we basically have a master list of regional hubs members that is easily filterable
20:11:28 <shillman> Yeah, I think so too.
20:11:38 <shillman> Question, though.
20:11:51 <shillman> Shoudl it show people who are in FAS, but have never logged into Hubs?
20:11:58 <mizmo> we also should have a suggestion system - hey this person is doing stuff and is nearby, want to invite them to your regional hub? and on the other side, hey this regional hub is near by, want to join it?
20:12:00 <mizmo> yes it should
20:12:25 <mizmo> beacuse whether or not they use hubs, they are still a member of that region and still a resource you can tap
20:12:26 <mizmo> does that make sense?
20:12:53 <mizmo> #agreed finding fedora members in a specific location is covered by the master filterable list of regional hubs members
20:13:05 <shillman> Yes. Is there any info in FAS to tell us how active people actually are? Otherwise those might turn out to be cobwebbed people
20:13:53 <shillman> Maybe it should include something saying that they haven't logged into Hubs, or something.
20:13:59 <shillman> At the least.
20:14:09 <shillman> (and if they have, something to indicate how long it's been?)
20:14:12 <mizmo> yeh you know we have cobwebbing hubs but not people
20:14:22 <mizmo> i think thats a great idea
20:14:26 <shillman> k. :)
20:14:27 <mizmo> #idea cobweb people who haven't been active in fedora
20:14:35 <shillman> cobweb the humans! ;P
20:14:39 <mizmo> maybe instead of cobweb, retire lol
20:14:43 <shillman> yeah. ;P
20:15:10 <mizmo> #agreed part of findability of people is also suggesting to them to join local regional hubs, and suggesting to the local regional hubs to invite them
20:15:30 <shillman> Yes, indeed.
20:15:35 <mizmo> #agreed ensure that the people you find are actually active by cobwebbing inactive people / moving to bottom of lists / etc
20:15:40 <shillman> (what does agreed do?)
20:15:50 <mizmo> agreed means we decided on it
20:15:52 <shillman> Gotcha
20:16:01 <mizmo> i think (hope) it gets called out to a separate bullet list in the autogenerated notes
20:16:06 <mizmo> i guess we'll find out when the meeting is closed :)
20:16:09 <mizmo> next note
20:16:16 <mizmo> #info note #5: It is not easy to identify events by proximity to one’s self in time or space. This makes attendance, and prioritization, difficult.
20:16:47 <mizmo> okay so for this one, we have the master event list. and certainly, I think perhaps off the bat, it should suggest say the upcoming events that are nearest to you
20:16:56 <mizmo> and you can filter to widen what it shows
20:17:07 <shillman> Both by time and space, I hope?
20:17:09 <mizmo> and maybe it could have a feature where you could say if you plan to go or not
20:17:10 <shillman> THe filtering
20:17:14 <shillman> Mmm! Yeah.
20:17:17 <shillman> y/n/maybe?
20:17:30 <mizmo> so then big events like flock that wouldn't be local but you might travel to, would should up
20:17:30 <mizmo> yes definitely
20:17:42 <mizmo> #idea for events, let users indicate yes / no / maybe if they plan to go or not
20:17:42 <shillman> Or perhaps helper/attender/etc
20:18:04 <mizmo> #idea allow people to sign up as volunteers or organizers for events
20:18:04 <shillman> So wait...
20:18:12 <mizmo> that kind of ties into volunteer mgmt too
20:18:27 <shillman> big events should show up no matter where you are? Perhaps separately from local ones?
20:18:49 <shillman> So that you will always know about them, even if your time/space filter isn't inclkuding those?
20:19:04 <shillman> (at least the ones for your region)
20:19:10 <shillman> Or only if you've said you want to go?
20:19:25 <mizmo> yeh i think so
20:19:39 <mizmo> maybe big events that are tagged global or global region wide in your region
20:19:40 <mizmo> so like
20:20:00 <mizmo> if i'm in tokyo, fudcon pune would show up for me. but if im in boston it wouldn't (unless i expliitly said i was going or maybe going or volunteer or org)
20:20:10 <shillman> k, that makes sense
20:20:17 <mizmo> if i'm in tokyo, or caracas, or london, or boston, flock will show up becaue it's region wide
20:20:46 <mizmo> #agreed global events like flock will show up for everybody by defualt
20:21:01 <mizmo> #agreed region wide events like a fudcon apac would show up for everybody in that region
20:21:41 <mizmo> and beyond that i think it's say the 20 closest to you in time order from most recent to furthest out?
20:22:09 <mizmo> brb going to grab a cup of tea
20:22:09 <shillman> By default, sure.
20:22:10 <shillman> k
20:23:27 <mizmo> ok cool
20:23:45 <shillman> Oh. And it should save your most recent settings for later uses.
20:24:03 <shillman> (because I know for sure that Ryan cares more about 'things in Australia' than 'soon'.
20:24:41 <mizmo> im not sure on that one just because the data is time bound, and the page isnt going to look the same as you left it as events scroll off when they happen
20:24:59 <mizmo> one way to get around that problem though
20:25:04 <shillman> Right, but the filtering settings should still stay? Or not?
20:25:06 <mizmo> people caring about immediacy vs location
20:25:17 <mizmo> is to have a time-sorted display on the left, and a map on the right
20:25:23 <shillman> Hmm!
20:25:41 <mizmo> i think generally filtering settings persisting per session makes sense but i think it'd be confusing if it wasn't reset
20:25:52 <mizmo> but maybe not, i dont know
20:25:57 <shillman> Hmm. k.
20:26:13 <mizmo> im just nervous because when you're using those filters - and you keep them applied - the data set is changing underneath
20:26:21 <shillman> You think a calendar for the time set?
20:26:24 <shillman> True. But...
20:26:39 <shillman> won't people tend to expect that to be the case for events?
20:26:45 <mizmo> whenever filters are applied it's got to be bonk you over the head obvious filters are applied. because when people dont realize the list is filtered they think oh theres only 5 items when there's really 100 and tehres a filter on top
20:26:56 <mizmo> i dont think people consciously think about the filter sticking around
20:26:57 <shillman> Ah! Yes, good point...
20:27:24 <mizmo> i think this isnt as hard a problem as we're making it to be - the main point is the visual design needs to make it super super obvious when filters are applied
20:27:38 <shillman> *nodnod*
20:27:54 <mizmo> #agreed when filters are applied to list, needs to be super obvious filters are at play
20:27:58 <shillman> And I think that's wise regardless, and would also mean saving the settings won't be a proble, in the situation youa re thinking
20:28:10 <mizmo> #idea map-based display of events + calendar-based display of events to showlocation vs time
20:28:45 <shillman> I like it. Not certain if necessarily calendar-based? Can't decide if list or calendar is better. Suppose it depends on numbers of events and the limit of the time range.
20:29:03 <shillman> (calendars can get hard to read if crowded)
20:29:10 <mizmo> i like lists, they're easier to scan, but having the calendar as a navigational element maybe or an option would be good
20:29:15 <mizmo> i think always showing the map would be helpful
20:29:19 <shillman> Yes, agreed.
20:29:24 <mizmo> its such a quick visual
20:29:29 <mizmo> to understand where things are
20:29:40 <mizmo> the other major component here
20:29:42 <shillman> (and maybe useful for finding people, also...)
20:29:43 <mizmo> is suggesting events to people
20:29:53 <mizmo> since the problem to solve is people don't know about events near them
20:30:00 <shillman> True!
20:30:20 <mizmo> when an event is coming up in a user's region - suggest it to them?
20:30:25 <shillman> Absolutely.
20:30:35 <shillman> If they haven't already said what they wanted to do with it.
20:30:42 <mizmo> when an event is coming up that people you are friends with / teammates with are going to - suggest it to them? "8 of your friends are going to this event"
20:30:49 <shillman> *nodnodnod*
20:31:07 <shillman> but that may be less useful if your friends/teammates aren't co-located?
20:31:08 <mizmo> what about after the event is over
20:31:10 <mizmo> youw erent able to go but you wanna find out what happened
20:31:22 <mizmo> can we collate the blog posts, IRC convos, metbot logs, video recordings, discsusion about it?
20:31:33 <mizmo> which means the master event list would need a 'past events' section too
20:31:37 <shillman> Hmm! I;d like to think so...
20:31:39 <shillman> True!
20:31:51 <mizmo> and maybe for people who said maybe or went, notify them with any follow up materials from the event. photos.
20:32:01 <mizmo> photos is a big post event thing
20:32:29 <mizmo> we need to be able to slurp in flickr groups, g+ albums, fb albums if we can
20:32:37 <shillman> Yes. Agreed.
20:33:17 <shillman> I need to ask one of the interviewees where he was storing his photos.
20:33:19 <shillman> It wasn't those...
20:33:27 <shillman> And slurp in tweets?
20:33:52 <mizmo> yes!
20:34:28 <mizmo> when ppl create the event we should set an official hash tag so we can slurp up stuff from it
20:34:42 <shillman> Yes!
20:34:57 <mizmo> #agreed we should store event generated materials post event - blogs, photos, social media posts
20:35:21 <mizmo> #agreed when event is created official hash tag should be set o we can grab materials from it later
20:35:43 <shillman> (tasty, tasty tweets)
20:35:56 <mizmo> #idea suggest to contrbutors events coming up they could go to nearby, events friends are going to
20:36:18 <shillman> Do we want to suggest events that friends are going to if they aren't nearby?
20:36:29 <shillman> Maybe... if they are larger events?
20:36:44 <shillman> Or team-based events, but those seem like they'd already know about them.
20:37:20 <mizmo> if they already knew about them and said yes no or maybe then we dont notify. only notify if they didnt rsvp?
20:37:28 <shillman> Indeed, re only if not RSVP
20:37:46 <mizmo> #agreed suggest events to people in notifications only if no RSVP on record
20:37:58 <shillman> I'm just less sure about friends attending being enough reason to suggest.
20:38:08 <shillman> Due to possible lack of proximity.
20:38:15 <mizmo> it might be neat to suggest events to attend if a lot of people from a given hub are going. eg design team hub has a notification to its feed, "10 design team members are going to __"
20:38:32 <mizmo> well
20:38:34 <shillman> And of course, 'proximity' varies wildly depending on where you live.
20:38:40 <mizmo> my thought isnt that oh they're my friends i'll travel to india to se ethm
20:38:56 <mizmo> it's more, hey, if 10 of us are goingt o be colocated, maybe we stay an extra day or carve out time for a meet up
20:39:37 <shillman> That sounds less like a 'hey, they are going, you shoudl go' and more like a 'you are all going to be nearby and maybe you should meet up'
20:39:54 <shillman> Agreed on events suggestions based on a lot of hub people going
20:40:13 <mizmo> yeh
20:40:34 <mizmo> #agreed notify hubs if a number of members are going to be colocated at an event together
20:40:58 <shillman> Hmm. Thought those were two different things
20:41:21 <shillman> a) tell hub people if a bunch of people in ahub are going to a thing and suggest that they go
20:41:40 <shillman> b) tell friends of yours when you and them are already going to be co-located, even if you aren't normally.
20:42:02 <mizmo> oh b is neat
20:42:30 <mizmo> #agreed notify friends who aren't located near each other normally (based on FAS location) when they will be colocated at an upcoming event (make sure doesn't spam during flock)
20:42:38 <mizmo> we have to make sure it doesn't get annoying for flock
20:42:41 <shillman> Yes!
20:43:23 <shillman> Maybe a) can include a useful tool for people to sign up for trying to meet up at said event.
20:44:09 <mizmo> #idea provide tooling to create impromptu meetup at event where team mates are colocated
20:44:26 <mizmo> okay anything else on this one?
20:44:31 <mizmo> i think we have one more note
20:44:40 <mizmo> i guess one more consideration
20:44:50 <mizmo> if youre going to an event and its a far way to travel you need to know way more in advance
20:44:55 <shillman> Yes.
20:44:57 <shillman> True.,
20:45:08 <mizmo> so i think the cross regional / global ones should be announced even before specific dates are locked in maybe
20:45:16 <mizmo> or before all the details are known
20:45:18 <mizmo> so ppl know its coming
20:45:19 <shillman> And of course, 'far' varies depending on your local idea of how far things are expected to be.
20:45:28 <shillman> Mmm! Yes, that seems wise.
20:45:43 <mizmo> i can go to an event in cambridge with a couple days notice. for india... i need a few months
20:45:51 <mizmo> (need a visa at the very least and that takes a couple months)
20:46:01 <shillman> Maybe once a bid has won?
20:46:04 <shillman> Yes, indeed.
20:46:10 <mizmo> yeh
20:46:22 <mizmo> once the bid has won then an initial sketchy detailed event should be created
20:46:30 <shillman> Yeah.
20:46:47 <mizmo> okay lets move on to the next note
20:47:02 <mizmo> https://matrix.org/_matrix/media/v1/download/matrix.org/MLKkhtsftBzPeXJMqvefdDKq - mizmo_2017-01-04_20:46:54.txt
20:47:09 <shillman> Do we want to have people get notified or have the option to be notified about such things?
20:47:18 <shillman> Because they probably won't be checking the events list constantly.
20:47:25 <mizmo> #idea need a 'fedora-specific" data field for events. some events are linux wide or open wide, some are fedora only
20:47:47 <mizmo> i think if you're a member of a regional hub connected to the event you should get the notifcation
20:47:57 <shillman> I think you meant to do this:
20:47:58 <shillman> #info note #6 It is difficult to learn
20:47:58 <shillman> about local meetups, whether
20:47:58 <shillman> or not they are Fedora-specific, and identify if they are active. This can
20:47:58 <shillman> make Fedora outreach (hackfest/workshop, table/booth, speaking/presenting)
20:47:58 <shillman> difficult to do.
20:48:01 <mizmo> but if youre not a member maybe youd want to get it anyway
20:48:03 <shillman> hmm.
20:48:15 <shillman> (you posted a link instead)
20:48:33 <mizmo> oh weird, i didnt in my client but my client may have link ified it for some reason
20:48:38 <shillman> ah
20:48:54 <mizmo> #info note #6 It is difficult to learn about local meetups, whether or not they are Fedora-specific, and identify if they are active. This can make Fedora outreach (hackfest/workshop, table/booth, speaking/presenting) difficult to do.
20:49:02 <shillman> better. :)
20:50:03 <mizmo> so we need to decide if we show notifications about local meetups to people based on their location data in their main feed by default
20:50:09 <mizmo> or we only show it to people who are members or regional hubs
20:50:11 <shillman> I'm not completely sure how we'd get info about non-fedora events in hubs.
20:50:17 <mizmo> i think maybe we show it by default to everyone?
20:50:20 <mizmo> oh the ambassadors would put it in
20:50:24 <shillman> Ah.
20:50:33 <shillman> Then agreed.
20:50:35 <mizmo> eg jflory7 went to hack mit, and represented fedora there. but it wasn't a fedora specific event. fudcon - that's a fedora specific event.
20:51:17 <shillman> I think we should show by default to people based on location data, and if all we have is a country, but they are in regional hubs, that will come into effect.
20:51:24 <mizmo> #agreed we show notifications about local meetups to everyone (regional hubs members or not) based on their location data in their main feed by default. they can opt out using notifcation contextual filters
20:51:27 <shillman> (or they are in a different country but are in a regional hub)
20:51:28 <mizmo> yeh
20:51:31 <mizmo> that makes sense
20:51:51 <mizmo> identifying if local meetups are active
20:51:56 <shillman> Also I agree on the data field for fedora-specificness.
20:52:03 <mizmo> so a meetup is different htan an event in that it's recurring
20:52:22 <mizmo> #agreed have data field for fedora-specificness for events (fedora specific event vs general technology event fedora is attending)
20:52:33 <mizmo> a meetup is sort of a regular thing, like a LG meeting - every month or so
20:52:43 <mizmo> so events should have an ability to be recurring
20:52:51 <shillman> Ah! Is _that_ the difference between meetups and events?
20:52:53 <mizmo> but we dont want a recurring event on the calendar that nobody shows up to
20:52:59 <mizmo> yeh
20:53:54 <mizmo> #idea need to differentiatebetween meetups (regular recurring events, eg monthly) vs events (happen on an annual basis or are one shot deals)
20:54:02 <shillman> So maybe one can make recurring events, but if no one actually says they are going, it goes away?
20:54:13 <mizmo> yeh
20:54:16 <shillman> That seems too harsh...
20:54:27 <shillman> Maybe that instance goes away. But how soon?
20:54:39 <mizmo> maybe - an instance of a recurring event doesn't get promoted to people outside of the group without someone stepping up to organize it
20:54:43 <shillman> Ah!
20:54:46 <shillman> Yeah, that sounds better.
20:54:47 <mizmo> so you can set up a recurring event
20:54:58 <mizmo> but it won't be active in the system until someone takes ownership for that individual instance
20:55:04 <shillman> I like that one.
20:55:11 <shillman> Is one person going enough, do you think?
20:55:15 <shillman> Probably?
20:55:31 <mizmo> one person organizing is enough, and the organizer can cancel it if not enough attendees
20:55:36 <shillman> Ah! Good thought.
20:55:47 * mizmo does event management for a non profit so has a good handle on how this shold work i think
20:55:52 <shillman> *nod* Gotcha. :)
20:56:16 <mizmo> we need a notification to remind the organizer a day or two before the event to check in and make a call if there are enough attendees, the weather will permit, etc
20:56:21 <shillman> True!
20:56:40 <mizmo> we need a notifcaiton to remind the last instance's organizer or maybe the regional hub assocaited with it that the next upcoming one neds an organizer
20:57:11 <shillman> And if cancelled, notification to the peopel who were signed up to attend (eg for cancelled for weather reasons).
20:57:19 <shillman> Or even both of those people.
20:57:20 <mizmo> yes
20:57:37 <mizmo> #agreed need series of notifications around event management - for cancellations, for organizers, etc
21:00:30 <mizmo> another persona here is the guest
21:00:36 <shillman> Very true.
21:00:38 <mizmo> if theres a guest presenter
21:00:53 <mizmo> oh god
21:00:59 <shillman> ...?
21:01:11 <mizmo> there was a big accident in westford
21:01:17 <mizmo> gimme a sec i want to make sure my familys ok
21:01:58 <mizmo> a schoolbus hit another car
21:02:21 <shillman> Oh no...
21:02:29 <mizmo> same color as the car my hubby drives but i dont think itd be him, its too early for him to pick up the kids
21:02:50 <shillman> Is the news on nearby?
21:02:55 <shillman> And yikes.
21:05:01 <mizmo> yeh i tend to keep the tv on mute - usually bc the kids are watching it in the morning and mute it for some quiet afterwards :)
21:05:09 <shillman> Aaah
21:05:12 <shillman> You're at home.
21:05:13 <shillman> Gotcha. :)
21:05:17 <mizmo> yeh
21:05:39 <mizmo> ok sorry for the interruption :) lets get back to it
21:05:39 <mizmo> and honestly this is the last note, there aren't any more
21:05:55 <shillman> :)
21:05:58 <mizmo> the only thing maybe is anything we'd want to provide for a guest rpesenter
21:05:58 <shillman> No worries.
21:06:12 <mizmo> maybe making them sign up for a hubs account is heavy? but i dont know if we need to solve that problem either
21:06:22 <mizmo> but they might want to know how many ppl are showing up etc. but they can just visit the link manually
21:06:24 <shillman> Well, some way to upload files; be notified of changes in event...
21:06:26 <shillman> Right.
21:06:49 <mizmo> anything else for this note?
21:06:54 <mizmo> i think we have a lot of ideas and actions right?
21:06:55 <shillman> Maybe event creation can include a place for putting in a guest's email address?
21:07:21 <shillman> That way they can be notified if needed and the organizer doesn't have to remember?
21:07:25 <mizmo> yeh that makes sense
21:07:28 <shillman> We do. We have a lot lot. :)
21:07:44 <mizmo> #idea provide a way for guest speakers toevents can be contacted in event details
21:08:43 <shillman> We actually don't have a huge number of actions, but they are pretty big actions. :)
21:08:52 <mizmo> yeh
21:09:04 <mizmo> does this give you a good direction of where to go from here / what to work on?
21:09:12 <mizmo> i think too
21:09:15 <shillman> Two mockups of _dooom_, social media by region, and where interviewees stored photos.
21:09:20 <shillman> I think so.
21:09:29 <mizmo> as you start building out mockups and stuff seems to congeal more, you should file a ticket for each
21:09:39 <mizmo> eg have a ticket for the master list of events, and post the mockups to the ticket
21:09:44 <shillman> I'm not sure if I should focus on the mockups I was already working on, or the ones we just came up with.
21:09:46 <mizmo> we use the tickets as the feature specs basically
21:09:56 <shillman> Huh.
21:10:16 <mizmo> i think the ones you were working on are getting to a good point that you'd want to start doing the vis design in inkscape for them
21:10:42 <shillman> And I probably need tickets for all those.
21:10:54 <shillman> I am _not_ strong on visual design, BTW.
21:10:57 <mizmo> yeh
21:11:21 <mizmo> thats ok, i think it still helps to have the experience
21:11:36 <shillman> Ok.
21:11:44 <mizmo> even if you just worked on vis design mockups for say the joining regional hubs stuff you already have done in balsamiq
21:11:53 <mizmo> youd have the experience of working with vis design mockups
21:12:00 <shillman> *nodnod* Ok.
21:12:45 <mizmo> i would use the bootstrap1.svg file as the assets for them
21:13:13 <mizmo> f you're in the groove with balsamiq it might make sense to start doing more balsamiq mockups for the new actions we came up with here
21:13:21 <mizmo> and work on the vis design of the mockups you already did later
21:13:23 <shillman> The design for the joinhub.svg file is the old structyre.
21:13:30 <shillman> BTW.
21:13:32 <mizmo> its kind of up to you what you want to tackle
21:13:45 <mizmo> yeh i wouldn't use the joinhub.svg as assets for vis design, just as a reference for how the join system used to work
21:14:02 <mizmo> the new system i sent you (subscribe => join) is in the bootstrap file
21:14:27 <shillman> Ah. You mentioned it for the joining a hub interaction thing. So I was confused. :)
21:14:32 <shillman> Oh, end meeting?
21:15:11 <mizmo> oh yes
21:15:13 <mizmo> #endmeeting