Re: Django Development Model

[Lachlan Musicman]

On Mon, Oct 29, 2012 at 9:39 AM, Smriti Patodi <smriti...@gmail.com> wrote:
> Hi Everyone,
> I am a MSIS student at Santa Clara University, CA. My team has chosen Django
> to work on for our Software Project Management course.
> I was wondering if there is some place where I can find documentation
> related to Django's Software Development process/model.
> Or if any of the community members can give some insight on the topic.
> Thanks in advance.

Spend time with the tutorial, then just keep reading the docs - it
doesn't really get any easier. The tutorial is fantastic.

It is well marked on the front page:
http://www.djangoproject.com/

https://docs.djangoproject.com/en/1.4/intro/tutorial01/

If you don't know webservers, you will need to read up on one - Apache
or Nginx are well supported.
If you don't know DBs, sqlite doesn't need any study, but MYSQL and
PostgreSQL are the other two most popular options. MySQL has a lot of
docs floating about and is easy to pick up


Cheers
L.

>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/YTgUf90fZxkJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.



--
...we look at the present day through a rear-view mirror. This is
something Marshall McLuhan said back in the Sixties, when the world
was in the grip of authentic-seeming future narratives. He said, “We
look at the present through a rear-view mirror. We march backwards
into the future.”

http://www.warrenellis.com/?p=14314

[Lachlan Musicman]

On Mon, Oct 29, 2012 at 2:00 PM, Lachlan Musicman <dat...@gmail.com> wrote:
> On Mon, Oct 29, 2012 at 9:39 AM, Smriti Patodi <smriti...@gmail.com> wrote:
>> I was wondering if there is some place where I can find documentation
>> related to Django's Software Development process/model.
>

> Spend time with the tutorial, then just keep reading the docs - it
> doesn't really get any easier. The tutorial is fantastic.
>
> It is well marked on the front page:
> http://www.djangoproject.com/
>
> https://docs.djangoproject.com/en/1.4/intro/tutorial01/
>
> If you don't know webservers, you will need to read up on one - Apache
> or Nginx are well supported.
> If you don't know DBs, sqlite doesn't need any study, but MYSQL and
> PostgreSQL are the other two most popular options. MySQL has a lot of
> docs floating about and is easy to pick up

These will also make your life easier:

*nix:
bash and vim/emacs
pip (python installer)
virtualenv
virtualenvwrapper

django:
South (for when you make small changes in the model structure)
django-extensions (for when you need extras like "what does a map of
my models look like)

Cheers
L.

[Kurtis Mullins]

Hey,

I'm not sure there is a specific Project Management (which to me implies Software Engineering) style that people use with Django. In my experience, using agile methodologies work great; You can quickly prototype your idea and enhance your product as needed.

The tutorial, as others have mentioned, is a great starting point to learn about the Django Framework. For the purpose of a university course, I would keep the technologies as simple as possible: Use SQLite for the database (this comes with Django), use Django's built-in 'runserver' for development purposes until you need to push the web application to a production (read: live) environment. I would focus on things such as building Models, using Forms and Views to get and display any related data, and maybe some semi-complex Templates related functionality such as Template Inheritance.

Depending on the depth of the course, it would be very great knowledge for the students to know how to use a traditional DBMS with Django. It would also be very beneficiary for the students to learn how to configure an HTTP Server to communicate with a Django Application. However, these are only details related to the deployment of Django and can easily set the students on a wide tangent from the objective of teaching students how to manage and implement a web application project using the Django framework.

Hopefully that helps answer your question a bit. Good luck!

On Sun, Oct 28, 2012 at 4:39 PM, Smriti Patodi <smriti...@gmail.com> wrote:

Hi Everyone,
I am a MSIS student at Santa Clara University, CA. My team has chosen Django to work on for our Software Project Management course.

I was wondering if there is some place where I can find documentation related to Django's Software Development process/model.

Or if any of the community members can give some insight on the topic.
Thanks in advance.

--

[Smriti Patodi]

Hello Dennis,

Yes you are right..I am looking for how the Django effort itself is managed by the developers and the Django community in general? 

I want to get more information on:

- how Django team gathers requirements for each release

- how does the planning go on for each enhancement/release

- how the team members communicate about their progress(are their any formal checkpoints within a release?)

-what is the process of code review and approval, who all are involved

- how about the test planning, are the test plans developed prior to the implementation or are they done simultaneously

- and about the estimate of time and resource for the release, do you use any estimation techniques or how is it done

If you could some insight on these area or you could let me know of any documents/websites where I can find this information.

Thanks

Smriti

On Sunday, October 28, 2012 8:26:33 PM UTC-7, Dennis Lee Bieber wrote:

On Sun, 28 Oct 2012 13:39:52 -0700 (PDT), Smriti Patodi
<smriti...@gmail.com> declaimed the following in
gmane.comp.python.django.user:

> I am a MSIS student at Santa Clara University, CA. My team has chosen
> Django to work on for our Software Project Management course.

        Your inquiry is slightly ambiguous.

        Are you intending to /implement/ some "software project management"
application /using/ Django?

> I was wondering if there is some place where I can find documentation
> related to Django's Software Development process/model.

        Or are you, instead, asking how the Django effort itself is managed
by the developers? Which is how I interpret the above statement.

        {I believe the other two responses currently extant interpreted your
request as the former -- you wish to implement a project management
application using Django. [I'd also hope that a candidate in a Master's
degree program in IS would have encountered relational databases by now
<G>]}
--
        Wulfraed                 Dennis Lee Bieber         AF6VN
        wlf...@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[Elena Williams]

Smriti, 

If you're really interested from the "horse's mouth" -- I'd suggest googling DjangoCon and DjangoCon EU recordings (they are often on blip.tv but the most recent ones were put up by youtube.com/jessenoller.

Most DjangoCon have a core-team sit-down and/or fireside chat with BDFL/s and this is really informative on how the Django internal design/decision making processes really work.

Also Russell Keith-Magee's "No, Bad Pony" talk which he re-gave recently at PyCon AU, but had previously given at DjangoCon would probably answer some of your questions also.

Regards.

 

---
Elena :)
@elequ

04022 90172

--
You received this message because you are subscribed to the Google Groups "Django users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/9rVD2a5r74QJ.

[Russell Keith-Magee]

On Sat, Nov 3, 2012 at 7:58 AM, Smriti Patodi <smriti...@gmail.com> wrote:

Hello Dennis,

Yes you are right..I am looking for how the Django effort itself is managed by the developers and the Django community in general? 

I want to get more information on:

- how Django team gathers requirements for each release

- how does the planning go on for each enhancement/release

- how the team members communicate about their progress(are their any formal checkpoints within a release?)

-what is the process of code review and approval, who all are involved

- how about the test planning, are the test plans developed prior to the implementation or are they done simultaneously

- and about the estimate of time and resource for the release, do you use any estimation techniques or how is it done

If you could some insight on these area or you could let me know of any documents/websites where I can find this information.

Hi Smriti,

For context: I'm a 6 year veteran of the Django core team, and President of the Django Software Foundation.

The short version -- everything you learned in your Software Project Management class is wrong :-)

The longer version -- Open source projects operate under a different set of criteria to textbook commercial projects. For the most part, this is due to the fact that in an open source project (at least, in a volunteer run project list Django), we don't have a known resourcing availability. There's no point making grand plans, because there's no guarantee that you'll have enough resources. 

As a result, we don't really have a formal requirements gathering process. The features that get added in any given release are those features that someone in the community is enthused enough to build, that can garner enough support from the core team.

Some of Django's development process has been documented:

https://docs.djangoproject.com/en/1.4/internals/contributing/

https://docs.djangoproject.com/en/1.4/internals/release-process/

However, some of these documents are "in principle" documents that don't necessarily always follow through to "in practice". 

If this is something you're doing as a research project and you've got specific questions, I'm happy to jump on Skype for an hour or two for an in-person discussion. Email me off-list if this is something you're interested in.

Yours,

Russ Magee %-)