Yasushi Masuda wrote:
> Ilias Lazaridis wrote:
>>> Kenneth Gonsalves wrote:
>>>>> On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
>>>>>
>>>>>>> ok, 2 roles, .
>>>>>>>
>>>>>>> So, is
[EMAIL PROTECTED] wrote:
> regarding how a developer would interact with any schema evolution
> implementation...would you prefer / see as more natural:
>
> 1) a commandline util only (via manage.py)
> 2) a web-based UI only (via the admin screens)
> 3) both
of course i would prefere
Kenneth Gonsalves wrote:
>
> On 02-Jun-06, at 5:59 AM, Ilias Lazaridis wrote:
>
>> ok, 2 roles, .
>>
>> So, is it possible to have an overview of the _active_ "core
>> developers"
>> and "other contributors&
Adrian Holovaty wrote:
> On 6/1/06, James Bennett <[EMAIL PROTECTED]> wrote:
>> It's a simple truth that you can't please all of the people all of the
>> time, so at some point in any development process you have to sit down
>> and mark out three groups:
>
> James, you really hit it on the head h
Luke Plant wrote:
>
>> b) create a permanent branch "patch" (or a seperate svn) where commit
>> access is granted essentially on request.
>>
>> c) the remaining patches can be applied by the contributers to the
>> "patch" branch.
>>
>> the patch committers can collaborate to keep the branch stabl
James Bennett wrote:
> On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Is is possible to have an overview of the currently _active_ team,
>> including roles? e.g. on a page on the project wiki?
>
> The Django project defines pretty much two roles: "core d
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Is such a document available, which lists e.g.
>>
>> * committers
>
> Not that I'm aware of.
>
>> * subsystem leads (or component leads)
>
> Except for
[EMAIL PROTECTED] wrote:
> You can try this EnergyKey
> http://www30.webSamba.com/SmartStudio
> This may be help you.
> Now I always use EnergyKey, it helps me so much in my work.
very intresting tool!
.
--
http://lazaridis.com
--~--~-~--~~~---~--~~
You receiv
Adrian Holovaty wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> I think you've missinterpreted the writings in the frot-page.
>
> OK, everybody, let's settle down... This is slowly turning into a
> really lame argument that's not m
I've been pointed to this document here:
http://www.djangoproject.com/documentation/faq/#who-s-behind-this
but I'm missing information about the further team member and their roles.
Is such a document available, which lists e.g.
* committers
* subsystem leads (or component leads)
* code
Kenneth Gonsalves wrote:
>
> On 01-Jun-06, at 12:28 AM, [EMAIL PROTECTED] wrote:
>
This is actually one of the accepted Summer of Code projects for
Django, so the best answer is perhaps to way until the end of the
summer to see what happens with it.
>>> I cannot wait so long and a
John Melesky wrote:
> Ilias Lazaridis wrote:
>> Comparing with other systems, this admin interface is one of the
>> strongest points of Django.
>>
>> Remember that not every user is able to take all the setup barriers.
>
> If Django were an application intende
Jay Parlar wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> And an efficient tool should assist a user to become productive immediately.
>>
>> http://case.lazaridis.com/multi/wiki/Product#Functionality
>>
>> There are webframeworks which p
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Please feel free to send me any concrete criticism about my website via
>> private email (your comments are very welcome).
>
> I seem to have screwed that up by forgetting that replies
James Bennett wrote:
> On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
>> * Replace command "django-admin.py" by "django-admin" or "django"
Thanks for your reply, but the discussion has evolved a little.
I had already replied to the reply of Mr. Joseph Kocherhans:
http://groups.google.com/
Jay Parlar wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Additionally: The fact that I have _not_ the full domain knowledge (=
>> background information) enables me to make those "sweeping suggestions"
>> from a newcomers point of v
Tom Tobin wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Jacob Kaplan-Moss wrote:
>>> On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
>>>
>>>> At this point, Django's persistency layer seems intresting, but the
>>&g
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Additionally: The fact that I have _not_ the full domain knowledge (=
>> background information) enables me to make those "sweeping suggestions"
>> from a newcomers point of v
[EMAIL PROTECTED] wrote:
>>> This is actually one of the accepted Summer of Code projects for
>>> Django, so the best answer is perhaps to way until the end of the
>>> summer to see what happens with it.
>> I cannot wait so long and additionally I sense several problems for the
>> SoC project:
>>
[EMAIL PROTECTED] wrote:
>> I assume "Adrian Holovaty" is the Django Project Lead?
>>
>> Is there a Team Overview available?
>
> Disclaimer: I don't intend this to be rude, so forgive me if it sounds
> that way...
>
> Is it possible, given you haven't read the very first link on the
> Django Sit
Adrian Holovaty wrote:
> On 5/31/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
>> Just wondering what the procedure is for getting a patch accepted? I
>> submitted a patch (http://code.djangoproject.com/ticket/1994) a week
>> ago, and have had no feedback on it so far.
>>
>> Is there some kind of mont
Jacob Kaplan-Moss wrote:
> On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
>
>> At this point, Django's persistency layer seems intresting, but the
>> evaluation uncovered a few weaknesses, most importantly the lack of
>> schema evolution support:
>
> This is actually one of the accepted Summ
Ilias Lazaridis wrote:
> After reviewing the relevant source code base a little, I have started
> with the implementation of the schema evolution skeleton (which will
> contain a functional "Add Field" support).
>
> http://case.lazaridis.com/multi/wiki/DjangoSchemaE
oggie rob wrote:
>> It would be nice if I could have an answer on this,
>> thus I can avoid redundant effort.
>
> Perhaps there would be more confidence in your efforts if it:
> a) Wasn't making someone else's work redundant
> b) Came from some detailed design
> c) Worked on all databases befor
Ilias Lazaridis wrote:
> After reviewing the relevant source code base a little, I have started
> with the implementation of the schema evolution skeleton (which will
> contain a functional "Add Field" support).
>
> http://case.lazaridis.com/multi/wiki/DjangoSchemaE
DavidA wrote:
>> I am wondering how to retrieve a collection of columns within a table,
>> whilst using the standard python dbapi2 functionality.
>
> Do you mean cursor.description?
>
> cursor = connection.cursor()
> cursor.execute('select * from blog_post where 1 = 0')
> for col in cursor.descr
James Bennett wrote:
> On 5/29/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> The "Add Field" functionality is nearly ready.
>
> You are aware that a full implementation of schema evolution for
> Django was accepted as a Google Summer of Code
Ilias Lazaridis wrote:
> After reviewing the relevant source code base a little, I have started
> with the implementation of the schema evolution skeleton (which will
> contain a functional "Add Field" support).
>
> http://case.lazaridis.com/multi/wiki/DjangoSchemaE
Derek Anderson wrote:
> jeroen, brant, ilias, etc:
>
> schema evolution was an idea suggested and specifically granted for the
> SoC project. i don't know who here was involved with ranking the
> proposals, but for better or worse mine was accepted. to a certain
> extent i expect this to come w
After reviewing the relevant source code base a little, I have started
with the implementation of the schema evolution skeleton (which will
contain a functional "Add Field" support).
http://case.lazaridis.com/multi/wiki/DjangoSchemaEvolution
With a very small assistance from the team (mostly s
Joseph Kocherhans wrote:
> On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
>> At this point, Django's persistency layer seems intresting, but the
>> evaluation uncovered a few weaknesses, most importantly the lack of
>> schema evolution support:
>>
>> http://case.lazaridis.com/multi/wiki/Djan
31 matches
Mail list logo
