Re: [proaudio] Status of pro-audio overlay and small updates

[Tom <gimpel@xxxxxxxxxxxxxxxx>]

Am 23.08.2012 19:33, schrieb Dominique Michel:
> Le Thu, 23 Aug 2012 03:08:19 +0300,
> keenblade <keenblade@xxxxxxxxx> a écrit :
> 
>> On Sal 21 Ağu 2012 23:56:03 EEST, Dominique Michel wrote:
>>
>>> "svn ci -m 'some comment'" look very easy and fast to me.
>>
>> I agree, it is easy and fast. I don't think forking will make easier 
>> things with git. But I am not against migrating to the git. Git is
>> also easy and fast, too.
> 
> I know that, and I am not against migrating either. And tuxfamily do
> have git and mercurial too. But, I want to have a good raison to
> migrate. A migration imply work to do, that is time that will not be
> used to make something else. And in many cases, a migration imply
> also a loose of data like the historic.
> 
> And to have to manage send commits from other peoples is not what I
> call a good raison. Again, I don't have the time for that.
> 
> For peoples not sure of their ebuilds, it is far better to make bug
> reports with their ebuilds. That way, their ebuilds will be commented
> and they will hopefully learn to make better ebuilds.
> 
> For peoples reasonably sure of their ebuilds, the best is when they get
> commit access. And it will be the same problem in any case: for what
> I know, only evermind and gimpel can give this access right to the
> maintainers. But this is not so hard. When I begun as maintainer with
> this overlay, we was 4 or 5 guys including gimpel and evermind. Today,
> we are twenty with commit access to the svn. The last one is
> nwmatt (Matt Henley), the guy that started this subject.
> 
> Welcome on board Matt! And thanks for helping!
> 
>>
>>> Alternatively, he can send it to the list, but it will take more
>>> time to do that than the above svn command.
>>>
>>> Dominique
>>>
>> Also people can use our bugtracker which is a better place to send 
>> patches, works or bug reports: http://proaudio.tuxfamily.org/bugs
> 
> That's right, even if I don't use it ofen. That way, they are also sure
> they work will not be "lost" in the archive of this list.
>  
> 
> 

Hey guys,

I haven't been working on the overlay for ages, mostly because I ditched
gentoo a year ago when I became father and preferred to spend the time
it took me to maintain my gentoo install with my son instead.
But still available as project admin @ tuxfamily and responding to mails
etc.

Still, I'd like to add my 2ct.

SVN serves quite well for reasons Dominique already explained: very low
to zero maintainance effort for us project admins. New people create an
account at tuxfamily, we add them to the project and that's it. They can
commit. And commiting is all they have to do - SVN is fine for that.

GIT indeed has lots of benefits like forking, send merge requests,
branches etc - I'm hard pushing my work company to switching from SVN to
GIT for those reasons - but IMHO it can also complicate things up for
small projects like this one.

But this is a democratic project. If the majority of commiters and
potential contributors prefer to migrate to GIT - step up and do it.
But bear in mind that you also have to find a manager who takes care of
merge requests etc. I will not do it, my time's too spare. Dito for
Dominique. Not sure about evermind.

If it's only about GIT, we can also create a GIT repo on tuxfamily and
do a git-svn clone. Current users will have commit permissions
automagically - so that would be low effort. The SVN repo would have to
be killed afterwards to avoid doublemobble.

Regards,
Tom (gimpel)