Re: Subscriptions in Hubs
by Máirín Duffy
Hey Ryan!
Subscribe : follow :: member : friend
thats weird so.... subscribe basically means you follow the hub, but becoming a member means a FAS member of the team, listed in the roster, etc.
The idea came about bc of the cross functional nature of some of our teams... eg a lot of ppl mightbwant to follow fesco the council but arent on it.... website member might want yo follow design or marketing or vice versa...
subscribe = listen, member = do.
im cool w renaming subscribe to follow if its clearer.
cheersm
~m
Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Ryan Lerch <rlerch(a)redhat.com> Date: 11/20/17 4:52 AM (GMT-05:00) To: hubs-devel <hubs-devel(a)lists.fedoraproject.org> Subject: [Hubs-devel] Subscriptions in Hubs
Hi all, just going through hubs at the moment, and just wondering if anyone could shed some light on what subscriptions are.
Currently, it is possible to subscribe to a hub (both group or user) -- but what does a subscription do? The reason this is a little cloudy to me is that it is currently possible to subscribe to a hub even if i am a Admin or Member of the hub. Is there something different that a subscription gives the user that a member or admin doesnt get (i assume in the way of notifications).
cheers,
ryanlerch
6 years, 5 months
Subscriptions in Hubs
by Ryan Lerch
Hi all, just going through hubs at the moment, and just wondering if anyone
could shed some light on what subscriptions are.
Currently, it is possible to subscribe to a hub (both group or user) -- but
what does a subscription do? The reason this is a little cloudy to me is
that it is currently possible to subscribe to a hub even if i am a Admin or
Member of the hub. Is there something different that a subscription gives
the user that a member or admin doesnt get (i assume in the way of
notifications).
cheers,
ryanlerch
6 years, 5 months
Heading toward production
by Paul W. Frields
I talked to Ryan Lerch this morning -- he's been spending some time
surveying the state of Hubs and seeing how best to participate and
help get us toward a production deployment. With a fresh set of eyes
Ryan had mentioned he'd seen a few issues in the current state of Hubs
that could affect deployment. I suggested he take on a couple
additional challenges:
1. Turn the "MVP" (minimum viable product) idea into a written page
on the wiki. This doesn't need to be a full-on, novel-length
document. Rather, a few highlights:
* Problem statement
* Timetable
* Goals
* Scope / Use cases
Having a solid definition, as opposed to just tagged tickets, helps
judge whether Hubs is successfully letting users complete the required
tasks. Gaps can be turned into further tickets, of course. But it
helps to have an agreed-upon scope that doesn't change as a function
of ticketing.
2. Track progress according to the timetable, using the methods the
team's already selected (i.e. pagure issue tracking, weekly
meetings). It might be helpful given the current weekly meeting time
if it can adjust a bit to Ryan's availability -- i.e. move earlier in
the day so he can make it during nighttime hours.
Ryan said he was interested in helping this way -- would that work for
other participants?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
6 years, 5 months
mizmo outage-ish today
by Máirín Duffy
Hey,
I'm in Westford today and I'm going to be giving a talk at the local
high school as part of an outreach program we do with them; I'll need to
leave about halfway through today's meeting to make it there on time.
I'm in IRC and in #fedora-hubs now though so if you need to talk to me
about anything hubs I'm around :)
Cheers,
~m
6 years, 5 months