[Compcomm] The Next Step

[Sam Spilsbury]

On 4/17/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
>
> RYX wrote:
> > The WEB-team focuses on the website-discussion and -improvement, the
> > COREDEV-team focuses on improving the core (they even have their own
> > list already and I think this works well), the PLUGDEV-team focuses on
> > porting/improving/inventing old/new plugins, the APPDEV-team creates a
> > settingsTool/pluginIfaceForDecorator/startupManager, the DOC-team gets
> > its ass up and writes down good developer/user-documentation ...
> >
> >
>
> Just a note about these.  I do not think its a good idea to
> categorize devs like that.  Really most people will have little
> to do with core development.  Its only really needed when we
> need extra features for plugins or there is a bug.
>
> I think these teams would be good
>
> DEV - Should have actually written something substantial, not
> just people who would like to do something one day (sorry, no
> offense anyone), could be anything.



David, Maniac, roico etc


WEB -  Wiki, forum design etc.  These people may also be responsible
> for sysop stuff like restarting server or this could be another team.



Imnotpc,RYX,mikedee etc


RELEASE - We BADLY need people to write about new releases and
> publicise them.  We need at least one person who is mildly technical
> to translate the git logs into something people can understand.  This
> then needs to be put on a nice html page and linked on the usual
> sites.  There should also be someone mildly technical who can actually
> prepare a tarball for release along with each compiz release.



I volunteer for publicizing the releases. I'll also do a "This week in
Compiz" weekly blog about what has happened this week in the code. I know
how compiz works kinda so I should be able to do the job. If I don't know
the name of a term I'll bug the devs on IRC ;-) I cant prepare tarballs
though. Not enoguh time. Also there should be a way for developers to have
blogs, Ie planet.ubuntulinux.org to tell users whats going on. I'll make a
screenshot and video tour too.


DOC - Sounds good, should clarify what is being documented though,
> I assume the same people documenting the source code will be different
> from those documenting how to install a deb.



I'l do Intel setup on AIGLX


TEST - These people should routinely and systematically test new
> releases for new bugs and confirm old bugs are fixed.  People could
> choose 1 or 2 plugins each and then design a test with the developer
> which they can then repeat.



Compiz is alpha software. We're ALL beta testers. Users go onto the forums
and post stuff saying XYZ doesnt work! Team test = users. So when we are
older, we can tell our grandkids "I helped developed Compiz (Which would
have taken over the world by then ;-) )


_______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.RiverGorgeSolutions.net/pipermail/compcomm/attachments/20070417/f3d3490c/attachment-0002.htm>