Hi everybody,
So today we hit this topic (Where we stand, where we're going) in our
regularly scheduled meeting. We are meeting again tomorrow to keep
hashing this out:
- Wednesday Jan 11
- 1500 UTC (10 AM ET)
- #fedora-hubs
Here's a summary of what we discussed today with a link at the bottom to
full logs:
- We've passed our milestone deadline and need to figure out where to go
from here.
- We have 6 major chunks of work -
(1) zanata
(2) waartaa / irc
(3) badges
(4) release cycle widget
(5) bookmarks bar
(6) help widget / err bot
- sayan and I had walked through how someone would be able to contribute
to the zanata feature from the ground up. Here are those notes:
https://meetbot.fedoraproject.org/fedora-hubs/2017-01-10/hubs-devel.2017-...
- we talked about pushing the code into devel/staging as our devel
instance is sorely out of date.
- we decided that we would hone down our milestones to one target
audience (i proposed design team) and deploy when that target audience's
milestone features were complete and get their feedback.
- our three target audiences and the external blockers we have for each:
- l10n/g10n (zanata)
- commops (errbot, waartaa)
- designteam (waartaa)
- we focused then on talking about waartaa and how we could make
progress there since it affects 2 of the 3 target audience groups pretty
critically.
- currently waartaa has a trello board that organizes tasks at a high
level:
https://trello.com/b/RetFEvn2/waartaa
- waartaa's code is in github:
https://github.com/waartaa/waartaa/
- waartaa is an upstream web irc client that we intend to use as the irc
client in hubs. it relies on something called ircb as its bouncer
component. the two projects are closely linked together and share a
kanban board. rtnpro and sayan are the upstream devs.
- sayan proposed (and we agreed) to go through the IRC related tickets
in pagure and replacing the links to the main trello board to the
specific trello card related to that issue. e.g.,
https://trello.com/c/FGSWyW89/28-chat-page-rooms - The hubs pagure issue
tracker should describe in detail work needing to be done in waartaa, it
should point to a waartaa issue/card that does that - the hubs project
pagure tracker is great for mockups etc. and references to those
upstream issues.
full logs:
https://meetbot.fedoraproject.org/fedora-hubs/2017-01-10/hubs-devel.2017-...
~m