Hi,
We had a weekly status meeting today. Here are the meetbot minutes:
https://meetbot.fedoraproject.org/fedora-hubs/2017-01-31/hubs-devel.2017-...
Here's a summary:
IRC Widget
=========
- jcline has a PR open against FAS3 (
https://github.com/fedora-infra/fas/pull/255) to add
the necessary IRC fields. he will ping today to see if it can be reviewed soon.
Widgets
=======
- jcline explored how widgets work in hubs and wrote up his findings as documentation in
https://pagure.io/fedora-hubs/pull-request/302
- jcline spent time implementing the db change in hubs and then changing his mind
- abompard and jcline talked about modules vs classes for widgets and agreed classes would
be better. classes are a bit more work because it requires defining an interface, but
classes are more flexible and can be implemented anywhere that is python-accessible and
allow us to provide default implementations thru inheritance.
- abompard has some widget-related stuff written, jcline will review abompard's open
PRs today to unblock him
Docs
====
- jcline got the API autodocs going for Hubs, I just haven't made a PR yet because it
depends on my first docs PR
Halp widget
==========
- nothing back from openstack so we're going to assume we're on our own wrt
meeting bots
- abompard thinks he can implement a change in the hubs config that will give him the
necessary info to implement the widget without needing to change meetbot. hubs users would
need to list the channels they are working on, this info would be used by the halp widget
to filter the halp requests but it could be used by other widgets too. that's why I
think it's more a hub-level config (I'm thinking of the IRC widget, but maybe also
a meetings widget, etc)
- We talked about it being nice if it was shared - e.g., it would be nice to have
notifications of the data go to the stream as well as the halp widget.
- the main use case for the halp widget is the comm ops folks altho other people could use
it too. the comm ops folks aren't necessarily members of the teams that are looking
for help but they try to identify which teams need help at a higher level and route
helpers as needed.
- (1) If a given user doesn't have IRC activated, they still would be interested in
halp requests that have to do with teams they are a member of (2) we may at some point
want to make it possible to monitor other info (beyond IRC) to create halp items in the
widget. (3) we may at some point want to make it possible to manually enter in a halp
request to the halp widget
- For (1) abompard needs a list of IRC chans used for each hub, and (2) and (3) don't
change the decision. He will just make sure the table can hold more info than just a list
of IRC chans
- we talked about
http://blog.linuxgrrl.com/2016/11/15/fedora-hubs-and-meetbot-a-recursive-... and how
some teams meet in #fedora-meeting-* channels and how some meet in a team channel. That is
still a complication but doesn't block this implementation plan. Simple idea for
getting team minutes out of #fedora-meeting-* channels - use the meeting name from
meetbot: each hub's admin could have a configuration for the hub that they could add
their meetbot meetingname tags to, then you wouldn't have to upgrade meetbot
Regional Hubs UX
===============
- shillman setting up times to have people try to use prototypes. she had her first
sessions with a2batic last night
- shillman touching up the social media/photo sharing survey. It's meant to try to get
an idea of what sorts of social media/photo sharing tools people are using, with the
intent to have some conversation between Hubs and those tools available.
- blogged html/css convo part one, need to continue part 2 since we got mired in python
& JSON details and didn't get to html/css so much:
https://medium.com/@suzannehillman/css-and-mockups-2bf6fb160fa2#.tlw423lrt
Cheers,
~m