January 2017 - Hubs-devel - Fedora mailing-lists

More blog posts!
by Suzanne Hillman 31 Jan '17

31 Jan '17

I evidently forgot to tell you all about one from 11 days ago. So, that one first: https://medium.com/@suzannehillman/locations-are-hard-8965a6ff0ea1#.4sqsr5i… Locations, they are hard! I also posted a general sense of what I've been up to: https://medium.com/@suzannehillman/sometimes-its-good-to-stop-worrying-abou… And trying to work on CSS gets it own post because the previous and this would make a very very long post: https://medium.com/@suzannehillman/css-and-mockups-2bf6fb160fa2#.sdf5meh72 Hope everyone is doing fabulous! Sz

2 1

Summary of today's meeting (31 Jan 2017)
by Máirín Duffy 31 Jan '17

31 Jan '17

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-01… 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-ta… 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

1 0

The "Stream" page
by Aurelien Bompard 27 Jan '17

27 Jan '17

Hey people! I'm wondering what the difference is between the "live feed" on a hub's front page and the "My Stream" page (which is not deployed on hubs-dev). Both pages seem to share a lot of the structure, and maybe I'll do some refactoring, but first I'd like to understand what are the differences. Thanks! Aurélien

2 4

Long convo on geo-location
by Máirín Duffy 25 Jan '17

25 Jan '17

Last week Suzanne and I had a long convo about geolocation data. Meetbot minutes are here: https://meetbot.fedoraproject.org/teams/hubs-devel/hubs-devel.2017-01-19-19… Noting here because I forgot to send it after the meeting. ~m

1 0

Meeting on feasibility of regional hubs mockups
by Suzanne Hillman 23 Jan '17

23 Jan '17

Sayan and I met to discuss the mockups I have so far, and identify places where there may be feasibility problems. We discussed the following: -Master List of Events: https://pagure.io/fedora-hubs/issue/281 -Master List of People: https://pagure.io/fedora-hubs/issue/280 -Getting location information: https://pagure.io/fedora-hubs/issue/286 -Event notifications: https://pagure.io/fedora-hubs/issue/282 -Joining a regional hub: https://pagure.io/fedora-hubs/issue/287 We decided: -event creation needs to happen in Hubs, with only name date and location being required upfront. -Sayan needs to look into 'event in x miles', and probably this will also relate to 'people within x miles' -Sayan needs to look into showing who is online within the search terms, and how to keep it lightweight and fast. -I need to create an issue relating to Hubs suggesting regional hubs to people, and discussion needs to happen around that. Minutes: https://meetbot.fedoraproject.org/fedora-hubs/2017-01-23/hubs-devel.2017-01… Sz

1 0

Quick meeting on regional hubs
by Máirín Duffy 17 Jan '17

17 Jan '17

Hi, Suzanne and I had a quick meeting today to discuss her work on regional hubs. Topics covered: - Format of feedback I'm giving her on her mockups - Social media research she has been doing to see what platforms Fedorans are using to share information / photos / reports about Fedora events - Prototype testing plan for her mockups thus far What we decided: - I'm going to make smaller mockup feedback files - Suzanne will update mockups based on feedback and to prep them for prototype testing - Current social media research is based on consultations with previous hand-picked regional interviewees; for more aggregate data Suzanne will put together a Fedora-wide survey - Suzanne will prep for prototype testing by coming up with tasks for the tests Meeting minutes: https://meetbot.fedoraproject.org/fedora-hubs/2017-01-17/hubs-devel.2017-01… Cheers, ~m

1 0

Summary of today's meeting + Another special meeting tomorrow, 1500 UTC
by Máirín Duffy 17 Jan '17

17 Jan '17

Hi everybody, Today we concluded our meeting by deciding to meet again tomorrow from 1500 - 1600 UTC (with ahard stop at 1600 UTC): - Thursday Jan 12 - 1500-1600 UTC (10-11 AM EST) - #fedora-hubs Here's a summary of what we discussed today with a link at the bottom to full logs: Target Audience / Milestone Goal Discussion ===================================== - We'll focus just on the design team for our milestone 1. - This means the main development focus will be on IRC. - Rationale for this decision includes: (1) the main external dependency to design's hub is waartaa, which sayan is upstream for (2) getting an initial cut of IRC benefits all hubs; zanatasupport, while critical, isn't as widely applicable - we are leaving the current milestone tag aloneas a tag to be used for any tickets that relate to our 3 key target audiences; we are creating a new milestone tag "milestone1" for our first milestone: https://pagure.io/fedora-hubs/issues?status=Open&tags=milestone1 - ACTION NEEDED: taggingIRC tickets and other essential tickets with 'milestone1' tag. IRCFeature Deep Dive Discussion ============================ We came up with a list of atomic tasks that need to be done in the codebase to get IRC implementedto get the IRC widget working. This was all in the context of getting the IRC widget ticket completed: https://pagure.io/fedora-hubs/issue/2 1) add setting of whether or not IRC is enabled to the User database model and switch it on and off via the UI 2) add switch in UI to turn off a given channel in the irc widget so users aren't idling in it if they dont want to 3) upon clicking on button to enable IRC feature, log user on 4) for users who do not have an IRC nick configed in FAS, we need to direct them to set one up 5) mock up tool for helping new users set up their freenode nick and register it. should save out to FAS afterwards 6) figure out how to handle when user doesn't confirm email acct with freenode after 24 hrs of nick reg (reference: http://freenode.net/kb/answer/registration) 7) (some future point) add a config option to allow for the user to connect to a proxy they control rather than thru ircb (eg if they have some external log store they want to make sure their logs save out to) Note the narrative for this feature here - IRC is very integrated with Hubs. Some points: - By default, IRC is not enabled for a given user in hubs. Any IRC widgets on hubs will be greyed out and have a little promo to encourage the user to opt-in with a widget / button / switch for them to enable it. This should also have the caveat they should be logged out of any proxies / etc before they do it (otherwise we'll knock their proxy out. - FAS accounts have a field for storing IRC nick. They do not have a field for freenode credentials. We probably should have such a field? - Upon activation (which is from a single hub IRC widget), we will create an ircb user for them, log the user on to their given freenode nick in FAS, and have them join the channel corresponding to the hub they are on. If they would like to join additional channels, they'll need to enable them from each respective hub page's IRC widget. - If a user does not have a nick in FAS, we will prompt them to either provide their registered freenode nick (maybe don't accept unregistered nicks in the dialog?) and guide them through nick selection and registration. We need mockups for this. - Each IRC widget has a 1:1 mapping with an IRC channel. You cant switch channels from inside the widget. The hubs admin determines, when adding the IRC widget to their hub, what channel the widget is going to display. If a hub wants more than one channel displayed (likely a very rare case) they will need one widget channel. - We have some architectural issues in terms of passing info between FAS <=> hubs <=> wartaa <=> ircb. One basic example is having a hover/rollover to display the Real Name of a user's IRC nick in the channel log. Another is the IRC mention feature integration with the hubs stream / messaging area. Sayan needs to do some more research on this but believes we may not be able to use the iframe implementation of waartaa as a result. The state of what we have now: - right now someone could start on updating the the user model and adding a UI element to update the irc on/off setting. Nothing is blocking that work and it needs to be done. - we need a login mechanism - to log into freenode and triggered by enabling IRC in the UI (logs in via waartaa to generate cookies.) - the login page is made (provided by waartaa), sayan is currently working on redux integration of the data sent back from the server. waartaa is powered by aiohttp and react+redux Full logs: https://meetbot.fedoraproject.org/fedora-hubs/2017-01-11/hubs-devel.2017-01… Cheers, ~m

3 5

Holy long blog post, Batman!
by Suzanne Hillman 10 Jan '17

10 Jan '17

Another blog post! https://medium.com/@suzannehillman/affinity-mapping-and-brainstorming-5555c… - so many mockups... Sz

1 0

Where we stand, where we're going
by Máirín Duffy 10 Jan '17

10 Jan '17

Hi everybody, We had originally seta loose milestone of mid October 2016 with the 10 issues tagged 'milestone' from this list: https://pagure.io/fedora-hubs/issues?status=Open&tags=milestone We've definitely made progress, but we're a couple of months past our milestone and are stuck and/or blocked on the majority of our milestone issues. So I think we are overdue to reassess where we are at and what we're going to do toget Hubs up and making our fellow Fedorans more productive. We need to figure out how much time werealistically need to complete these and figure out a new realistic date for making a release so we don't lose momentum and stall out. If needed, we can pass issues over to others if anybody doesn't realistically have time to work on their issues; we can reassign issues and/or try to recruit morefolks to help too. I think at this point we'll need to focus on recruiting experienced developers to help us. Let'shash through this at our next regular meeting. ~m

1 1

Intro and links to blog
by Suzanne Hillman 06 Jan '17

06 Jan '17

Hi all, Some of you have already 'met' me during the hubs-devel weekly meetings. For those who have not, I'm Suzanne Hillman, Mo's Outreachy intern for the winter session. I'm working on the UX for the Regional Hubs feature in Hubs (https://pagure.io/fedora-hubs/issue/47 and https://pagure.io/fedora-hubs/issue/279 for more information). I've been blogging about it on Medium, with the posts also showing up in the Outreachy and Fedora planets. I'm also going to start posting the links here. The ones that have happened since I started a couple of weeks ago are at: https://medium.com/@suzannehillman/outreachy-starts-today-f990c2788c25#.aqk… (outreachy starts today), https://medium.com/@suzannehillman/analysis-is-confusing-cf623c66c25#.fg577… (analysis is confusing), and https://medium.com/@suzannehillman/initial-analysis-session-3a527dc9ea78#.l… (initial analysis session). Nice to meet you all! Sz

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

Hubs-devel January 2017