Hey guys,
and different teams of people working on things got me thinking: what is
the H5BP organization itself? It's changing quite a lot from just the home
of HTML5 Boilerplate.
It seems to make sense to invite more members and to expand the teams.
There are starting to be a few projects that need more expert people
helping out with the code but also the direction.
So if we emphasised more the H5BP organization and that it represented
collaborative development on projects primarily for (front-end?) developers,
hopefully we could get more people contributing and feeling that they can
influence the direction of projects.
Stuff like the mobile boilerplate, build scripts, etc., really need external
expertise and collaboration on the direction...especially if we want them to
be the go-to projects of their kind. At the moment, we don't have enough
people working on them and we're all a bit short on time.
Part of that approach would mean that people working in a team know
they have control over the direction of a project. They should know that if
they contribute a lot to improving a project, we're going to ask them to join
it's team. When they're part of a team it isn't just token commit access
but an invitation (and expectation) to help shape the project going forward.
It's also great when projects get moved into H5BP because it shows that
there are times when people want their project to be supported and promoted
by the H5BP members. We could make much more noise about that and
make it clear that we're open to more projects being built under the
organization. We could even make a "requests" repo where people can vote
on whether a project should be transferred to H5BP or started there, to
ensure we always know people would work on something (and think its good)
before adding it.
Curious what everyone else thinks.
Thanks,
Nicolas