[Compcomm] Forum Decision

[Mike Dransfield]

Danny Baumann wrote:
> Hi,
>
>   
>>> We all appreciate your hard work there, but it's hard to see the effort
>>> needed for it if you do all work silently. Why on earth do you not use
>>> one of the two publically available repos? If you really do not like
>>> using git.opencompositing.org (getting commit access to it is a matter
>>> of sending your SSH pubkey to Guillaume and time of way less than a day)
>>> although e.g. Cedric already joined us there, please use at least
>>> git.compiz.org. 
>>>   
>>>       
>> You must stop sounding like a cult.  'Cedric has already joined us' can 
>> sound
>> scary ;)
>>     
>
> Bah, you know what I mean ;-)
> Rephrased: Cedric now also uses git.opencompositing.org, so you and RYX
> are the only active developers not using it.
> Better?
>   

Not really, the 'everyone else is doing it so you should too' argument
never really held any weight for me anyway.

>   
>>> And wanting to set up a git repo _after_ release doesn't really make
>>> sense to me - noone can reproduce how it evolved and what's maybe left.
>>> This does not only apply to the python plugins and the loader, but also
>>> to all the other plugins of Mike - maybe some of us would already have
>>> fixed those for latest git in this case ;-)
>>>   
>>>       
>> I set up a git repo ages ago but its only on my local hard drive, I dont
>> see any real pressing reason to put it in a public repo yet, but I am sure
>> I will one day.
>>
>> For people interested I have just uploaded the recent version here
>>
>> http://www.anykeysoftware.co.uk/compiz/plugins/python.tar.gz
>>
>> I have included a log in that tarball so you can see all commits.
>>
>> For people who want to contribute or branch it then there is an
>> up to date git archive here.
>>
>> http://www.anykeysoftware.co.uk/compiz/plugins/python-git.tar.gz
>>
>> I do not want the extra support hassle of people checking out
>> broken commits so I like to test things for a few days and then
>> release a tarball which I know will be good.  The releases are every
>> few days (sometimes more than once a day) and I normally bump
>> the python thread when I have done anything major.
>>     
>
> You sure can do anything you like, but the support argument isn't that
> strong to me. You always can tell people "using git versions ===
> unsupported".
>   

Thanks for the laugh, but they still report it and telling them
to sod off because they are using git makes them unhappy, me
running around fixing known problems on the users timescale
makes me unhappy.

Producing stable frequent releases keeps everyone happy :)

> What I'd like to see is just that we can release as many plugins as
> possible as a common tarball to reduce clutter and user confusion. 
>   

I don't think I have ever disagreed with that, the only thing
matching that description is here and I compiled it.

http://www.anykeysoftware.co.uk/compiz/plugins/extra-plugins-0.5.0.2.tar.gz

The only thing which I do not agree with is changing the name
of that to something 'neutral' and creating an entire forum around
it, deleting everything in the process.  THEN, repeating every 6
months along with the mood of the majority.  I want to build stability
and that cannot happen by changing everything all the time.

This has nothing to do with everyone using the same git repo, the
compiz-extra tarball will always comprise of plugins taken from
different locations and it should be built to accommodate that.


> Regards,
>
> Danny
>
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>