Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
GitHub migration planning
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  Messages 26 - 27 of 27 - Collapse all  -  Translate all to Translated (View all originals) < Older 
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Aaron C. de Bruyn  
View profile  
 More options Apr 24 2012, 11:52 am
From: "Aaron C. de Bruyn" <aa...@heyaaron.com>
Date: Tue, 24 Apr 2012 08:52:07 -0700
Local: Tues, Apr 24 2012 11:52 am
Subject: Re: GitHub migration planning

On Mon, Apr 23, 2012 at 22:30, Tai Lee <real.hu...@mrmachine.net> wrote:
> This seems odd to me. Django is generally a very open and community oriented
> project, which strives to consult with the community and achieve a
> consensus, resorting to a BDFL decision when necessary, after all sides have
> put their case.

You're right.  Speaking as a 'developer' who has contributed something
like 14 lines of code to Django ever, evar, I think everyone should
listen to me tell you why Microsoft's Visual Source Save 5.0* is the
best.

* It's not 'distributed' like all those new-fangled systems.  Too many
people working on a project at the same time introduces bugs.
* Single point of control.  Someone needs to review and test
everything.  If they go on vacation for a week, development should
stop and everyone else should go on vacation too.
* Harder to fork.  We don't need 50,000 forks of Django floating
around.  It'd be confusing.
* Backed by a company with billions of dollars.  This will ensure
innovation, and prompt bug fixing.
* Paid support.  If something goes wrong with the database that stores
the code, we can hold a Django bakesale to raise money to pay for them
to recover it.

Any arguments to my points will be taken as a personal attack because
you're attacking my personal choice of RCS after all. ;)

Hopefully everyone realizes that was a joke by this point.

But seriously, getting a bunch of geeks to decide on 'the best' RCS
will go over as well as deciding on the best text editor, the best IDE
to use for developing with Django, the best desktop environment, the
best distro, the best religion, or any number of other unresolved
discussions raging on millions of forums around the internets.

I personally have invested myself in developing with Django as a
framework.  As an 'end user' of the framework, I trust the core
developers to make sound decisions about its future--including which
RCS to use.  They are the ones who will be most impacted by the change
after all.

-A

* (No, I really don't want Microsoft's Visual Source Safe.  Nobody wants that.)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mohamad Efazati  
View profile  
 More options Apr 24 2012, 12:39 pm
From: Mohamad Efazati <my.karat...@gmail.com>
Date: Tue, 24 Apr 2012 21:09:52 +0430
Local: Tues, Apr 24 2012 12:39 pm
Subject: Re: GitHub migration planning

if trac maintain is paiful
maybe this link can be helpful
CommercialServices – The Trac Project ->
http://trac.edgewall.org/wiki/CommercialServices

در ۲۴ آوریل ۲۰۱۲، ساعت ۲۰:۲۲، Aaron C. de Bruyn <aa...@heyaaron.com> نوشته:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages < Older 
« Back to Discussions « Newer topic     Older topic »