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