Hi folks, Those who have been watching me in the irc channels will note that I've been digging into the launchpad structures, team structures and community contribution areas.
One of the first areas I've been looking at is the Edubuntu documentation efforts. I've put some notes up on https://wiki.edubuntu.org/EdubuntuCommunity/Teams as well as a proposed hierarchy. Feedback on this would be great, either through the mailing list or inline on the wiki. My thinking around this is simply to reduce the differentiation between the teams and consolidate the efforts. If the teams can be represented in Launchpad effectively then team contributions, features, specifactions, support and bugs can be logged efficiently and accountably. You'll see that I have two suggestions as such: - One to create a proper relationship between teams: - This will serve to enable proper assignment of tasks, bugs, and specs between teams - The other is to reduce the number of teams and try and consolidate with the larger Ubuntu Doc team - This is essentially what Kubuntu do Please offer suggestions and feedback. I hope for this to be a healthy debate that we can extend to the artwork teams, marketing & advocacy teams and wherever else we want to focus attention. Best regards, Will van der Leij -- Canonical Ltd [EMAIL PROTECTED] +27 82 335 4834 http://www.ubuntu.com - http://www.edubuntu.org Ubuntu: Linux for Human Beings -- edubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
