On Monday 27 June 2011 17:05:33 Renato Araujo Oliveira Filho wrote:
> In my opinion if this is a Brazil problem with gitorius we prefer stay
> on gitorius, create a script to sync will be one more thing to care
> about.
> We will need keep this script up to date every time when a new project
> is create or remove, and  we will need to pay attention if the
> mainline was updated because the script will fail sometimes due
> gitorious problems.
> Then my suggestion is avoid this extra effort and continue on
> gitoriuos, with this  we will avoid confusions of have 2 repositories
> and the sync problems.
> And if somebody want to use github they can use that for personal
> repository.

To avoid an extra overhead on our side I agree with the all or nothing 
philosophy.

Regards
 
> On Mon, Jun 27, 2011 at 3:45 PM, Matti Airas <[email protected]> 
wrote:
> > Hi!
> > 
> > On 27.06.2011 19:54, ext Renato Araujo Oliveira Filho wrote:
> >> We have created scripts to keep the main projects (apiextractor,
> >> generatorrunner, shiboken, pyisde) up to data once a day (during the
> >> nightly build). But due the gitorious stability problems this script
> >> does not syc every day, some time this fail with a server hang up,
> >> then we are keeping this sync manually for now.
> >> 
> >> We do not intend to keep the other projects up to date on gitorious
> >> but we would like to listen your opinions about that first.
> > 
> > As mentioned before, I'm of course all for using tools that best suit the
> > job. However, I'd still like to have the repos mirrored to Gitorious
> > because many might still be pulling changes from there, either out of
> > habit or because of some older scripts or just because that's how their
> > clones are set up.
> > 
> > It really shouldn't be that difficult to implement mirroring to
> > Gitorious, even if the connection to Gitorious from Brazil would be
> > unreliable. Just run the mirror cron job every half hour and redirect
> > the output to /dev/null - you'll simultaneously provide a better service
> > and mitigate issues with pushes occasionally failing - it doesn't really
> > matter if the mirroring is delayed for half an hour. Then you can set
> > another mirroring on a daily basis, _without_ the /dev/null redirection,
> > that way you can catch issues if the mirroring breaks completely down.
> > 
> > ma.

-- 
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PySide mailing list
[email protected]
http://lists.pyside.org/listinfo/pyside

Reply via email to