Hi all,

I've been following the discussion of how to improve on the list, and I'd
very much like to help. At the PSPS, the talk that inspired
http://dev.plone.org/plone/ticket/7816 that I heard was partially about
helping the community understand the Framework Team. It's also clear though
that the team itself also needs a little bit of organizational overhaul, as
the discussion on the list has documented (and which Martin wonderfully
summarized on the ticket).

I'm hoping that both these goals can complement one another. It sounds like
a lot of what is needed internally is documentation and formalization, both
of which can help the rest of the community understand the team better and
see where they can fit in. To move this along, I'd like to, with some help,
play journalist. At the PSPS, someone suggested a Framework Team blog, and
I'm happy to set that up and write up what I learn about how the team
currently works and what's being proposed to improve it. Wherever we keep
the blog could also house a schedule and maybe some static documents about
the agreed upon process for the team. The goal, to me, is to simplify things
for team members and to clarify things for newcomers to the community who
want to participate. Having some centralized sources of information about
how things work and what's going on should help, I hope.

To me, this team in particular is one of the really bright spots of Plone,
and so I'd like to do whatever I can to help it run more smoothly and help
the rest of the world know how cool it is that we have things like peer
review and a real process (even if it could use some tightening up) for
improving Plone. I also know that the participants have a great deal of
knowledge and consistently good judgment (otherwise they wouldn't be here),
so I greatly appreciate any suggestions and ideas that I can help

Thanks and I look forward to feedback and more ideas.

Framework-Team mailing list

Reply via email to