[PD-dev] cvs admin question ...

[=?X-UNKNOWN?Q?g=FCnter_geiger?=]

Hi,

I think there is no reason for thomas to fear (man cvs). The CVS is a
place for collaboration, not a marketplace for externals. If Thomas
doesn't want to collaborate, then why does he want to put his externals
there ?
Did you talk him into that, or is it his own decision ?
There is also no reason for his paranoia, obviously he did not
understand what the purpose of the devel version of pd is.

Since the existance of CVS there has not been a single case where we
had problems.

Anyhow, I think giving Tim the administrative rights is a good idea.

Guenter



On Wed, 2 Mar 2005, IOhannes m zmoelnig wrote:

> Hans-Christoph Steiner wrote:
> >
> > First off, you should _always_ post to the pd-dev list before making
> > any changes to that file.  Period.  That goes for any of the files in
> > CVSROOT.  Its too easy to seriously break things by editing those
> > files.  And you should have confirmation from all those involved that
> > its ok.
>
> true
>
> >
> > Second, "tmusil" is not an existing user.  If Thomas wants to maintain
> wrong, we just created that user (on sf) yesterday; i told tim to add
> "tmusil" _after_ the user was created.
> since tim was not able to add him to the devs, i added him to pd-gem in
> the meantime, which worked like a charm (about 14h ago) (to all
> gem-devs: this is just temporary so i could help him to set up his ssh-keys)
>
> > iemlib in the sourceforge CVS, that would be great.  But just locking
> yes
>
> > everyone out of the iemlib directory is not helpful to anyone.
>
> of course i cannot speak for thomas, but: he prefers to be the sole
> maintainer of his sources.
> i agree that this is not very like "community based development", but
> this is how things are.
> there are other people with the same policy (e.g. like tom who is just
> mirroring his own cvs into pure-data)
>
> therefore i asked tim on the irc (because he was the only admin online)
> to make the iemlib's readonly (except for thomas who should have
> write-perms of course)
>
>
> >
> > For iemlib, I imported the IEM sources so that they could be part of
> > the build system.  This was discussed on this list.  I put on access
> > restrictions so that people wouldn't mistakenly commit to iemlib there
> > since its maintained elsewhere.  If someone wants to work on iemlib in
> > the SourceForge CVS, they can make a branch, then submit patches.
>
> which is perfectly ok.
>
> it is just to ensure that no one fu**s up tom's sources, or at least
> _his_ MAIN branch (either by accident or evil purpose (i do know that
> this sounds paranoid, but there is no arguing about that; tom's reason
> to _not_ use the puredata-CVS for so long has been born from this fear -
> after he had his first look at the CVS-version of pd itself and what
> people had done to it))
>
> please do accept other people's attitudes.
>
>
> mfg.ad.r
> IOhannes
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
>