Meeting Minutes: 26 April 2016

[Máirín Duffy]

Meetbot link:
https://meetbot.fedoraproject.org/fedora-hubs/2016-04-26/fedora-hubs.2016...

Summary:

New runserver script
=================

- ryanlerch added a runserver script to run the dev server

We've got fedora-bootstrap!
======================
- ryan lerch also splitted the templates, so that there is a master template that the hubs
are using
- ryan lerch ported hubs to fedora-bootstrap
- fedora-bootstrap made things look quite pretty but broke a few things as well, like the
ability to configure a widget, this has been restored today

Widget config/add/position work
==========================

- today, pingou has been adding the logic to add a widget
- so we should have all the bits and pieces in place to: add a widget, configure an
existing widget, remove a widget
- hub wide, we have the logic to re-order them
- note: each widget now has a position argument, required, to determine if the widget
should be only on the left column (for example feed), the right column (for example
pagure's tickets) or present in both
- (both means it could go in either right or left column.)
- Dimuthu added the ability for widgets to have a footer. An example is the 'request a
new meeting' button here https://pagure.io/fedora-hubs/issue/29#comment-599

ircb / waartaa
===========

- on ircb, slick666 has been working on logging (he is one of the contributors to ircb)
- sayan and rtnpro are spending time on reading reactjs

what javascript framework should we use
=================================

- looks like reactjs vs angular
- not sure how to make decision - there is a thread on infra list:
https://lists.fedoraproject.org/archives/list/[e-mail]...
- criteria: one that most people have experience with is most favorable, but it's
harder because we dont have experience with them so much, so there's not a preferred
one
- angular may be easier to learn
- rtnpro prefers react; details on the infra thread
- decision we'll have to make soon

apr 21 hack session with commops
============================

- background - mizmo looking into badges ui for hubs eg
http://pagure.io/fedora-hubs/issue/17
- big badges RFE for 'tracks' or groups of badges, would help bootstrap / on board
contributors onto project/team hubs
- could have prerequisitie badge tracks
- decause, ryanlerch, sayan, flory7, mizmo met thursday night to talk about badges and
hubs:
  - layer 1: simplest implementation. no changes to badges. display badges related to a
hub via tagging system already in place in hubs
  - layer 2: simple badge track system. multiple badges together constitute a track.
badges can have an order within the track or be orderless. ordered badge track might be
something like, "make 1 blog post," "make 5 blog posts," "make 10
blog posts." orderless track might be something like, "participate in IRC
meeting," "make 1 blog post," "post to team mailing list." Could
also have combos of ordered and unordered badges within the same track.
  - layer 3: badges sphere grid (example: http://glacoras.net16.net/Images/SSGOSG.gif)
different colored areas represent different skill sets. in an RPG - black mage vs healer
vs warrior. For Fedora badges, could be badge categories - content, development, testing,
events, etc. Each node on the grid is a badge. And we could do things like this, to allow
users to build out their skill sets, know what badges they need to earn to progress in a
given category, even make recommendations for the next badges/task they might want to
pursue or team/project hubs they might want to check out based on the badges they've
earned. Could enable radar chart widget for user profiles so you can understand a given
user's skillset: http://jsfiddle.net/fxs2n8s5/
  - re layer 3: talked about this old mockup:
https://fedoraproject.org/w/uploads/9/9a/FedoraRPG-mockup-startpage.png  - here tracks are
"missions," and when you complete a mission you get a "trophy." there
is also a notion of "campaigns" where you can do x number of tasks to complete
the campaign. 
- problem with layers 2 & 3 is that it'd require a data model change in badges
system, so when we make that change we should make it once for both to minimize impact.
- layer 1 is good enough for flock implementation.
- another idea from hyperkitty mockups:
http://blog.linuxgrrl.com/wp-content/uploads/2013/08/user-profile.2.png
- concerns: too much like linkedin, worried about recruiters using data to contact users /
harass
  - we talked a bit about privacy measures, using fas +1 or shared group membership maybe
as a requirement to view certain personal data on profile pages like the radar chart
  - talked about making the radar chart against projects instead of skillsets
  - talked about having a widget to list the projects someone's a member of
  - talked about widgets like the mission progress widgets here:   - talked about this old
mockup: https://fedoraproject.org/w/uploads/9/9a/FedoraRPG-mockup-startpage.png 
  - goal with user profiles: serve as the FAS front end to user profiles, show how to best
contact a person, help understand their skill set / if they are the right person to talk
to about a particular project. no creepy, no stalker-y
 - widgets can be configured by users, so they can always hide it if they are worried or
add it if they want it

interns
=====

- we have a number of interns coming on, we should make up some milestones / goals for
them so we can plan on what we'd like done in time for flock and help figure out tasks
to work on to get towards it. will meet tomorrow at the same time. 

- fedocal link for meeting:
https://apps.fedoraproject.org/calendar/infrastructure/2016/4/27/#m3879  email mizmo if
you want to be added to get a reminder

[Máirín Duffy]

Oh I forgot to link to the Thursday meeting IRC logs. Mostly the discussion was in jitsi
but there are some notes in the log:

https://meetbot.fedoraproject.org/teams/commops/commops.2016-04-21-22.23....

~m