Re: @Meebo - 2 Django Contractors Needed!

[Joshua Partogi]

I've noticed that the mailing list name 'django-developers' always
creates confusion for first time users.

Kind regards,
Joshua

--
http://twitter.com/scrum8

On Apr 28, 9:51 am, Alex Gaynor  wrote:
> On Tue, Apr 27, 2010 at 7:14 PM, Kiko Griffin  wrote:
> > Hello All,
>
> > Thanks for reviewing and sharing with your network.  We are actively hiring
> > 2 Django Developers on a contract basis (3-6 months) with an opportunity to
> > convert full-time if interested.  I am hoping to fill the two openings by
> > the end of the week, so if interested please reply directly to
> > k...@meebo-inc.com immediately!
>
> > In case we're not on your radar, Meebo is a web based instant messaging
> > client that serves over 95 million users and allows you to chat with your
> > friends no matter what chat service they call home. We're now starting to
> > show up on top content sites, such as Mashable and Justin.tv, as an embedded
> > universal chat and sharing feature called Community IM. We are also known
> > for the innovative rich media and interactive ads we've developed for some
> > of the top brands in the world for display on our site and on partner sites
> > through Community IM. These activities have all led to quite an upswing in
> > media buzz about meebo making now a great time to consider joining our team.
>
> > Job Description:
>
> > Django Development Contractor
>
> > Meebo's Django Development Contractor will join the UX team and work
> > directly on developing the core site pages. Our ideal candidate will have a
> > passion for developing clean content-driven user interfaces, an eye for
> > off-by-one pixel issues, and a ninja at the art of Django. This is a
> > fantastic opportunity to apply your talents in a fun, fast paced startup
> > environment. Members of our team tend to be nice, humble, genuine, and fun!
>
> > Responsibilities include:
>
> >    * Work towards weekly and bi-weekly deadlines on the creation and
> > development of high-visibility, high-quality content-driven user interfaces
> >    * Work collaboratively with developers and visual designers to ensure a
> > clean product
> >    * Assist in testing regularly scheduled releases
> >    * Willingness to have fun and be part of an exciting growing team! Did we
> > mention fun?
>
> > Our ideal candidate will have:
>
> >    * 2+ years solid experience in building sites with Django
> >    * 2+ years of experience in HTML, visual/Web design
> >    * Degree in Human Computer Interaction, Computer Science (or equivalent)
> >    * Excellent communication and collaboration skills
> >    * A fastidious attention to detail (you noticed the double space in the
> > intro paragraph)
> >    * Previous experience with DHTML, CGI, CSS, JavaScript, AJAX, Python and
> > other Web applications a plus
> >    * An appreciation for visual design (e.g. color schemes, typography, and
> > layouts)
> >    * An obsession with delivering the best user experience possible
> >    * A passion for visual design and Web technologies and the desire to work
> > in a fast-paced, collaborative, and fun environment!
>
> > Look forward to connecting with you!
>
> > Regards,
>
> > Kiko
> > k...@meebo-inc.com
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To post to this group, send email to django-develop...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-developers+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/django-developers?hl=en.
>
> The django-developers list is for discussion about the development of
> django itself, and as such this message is inapprorpiate.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Porting Django to Python 3

[Joshua Partogi]

On Jan 9, 1:02 pm, Russell Keith-Magee  wrote:
> On Sat, Jan 9, 2010 at 2:25 AM, Dave  wrote:
> > Hello everyone,
>
> > My name is Dave Weber, and I'm a student at the University of Toronto,
> > studying Computer Science. For one of our undergraduate courses led by
> > Greg Wilson (http://www.cs.utoronto.ca/~gvwilson/), myself and a group
> > of 10 other computer science students will be trying to port Django to
> > Python 3.
>
> > Until the end of January, we'll be studying the existing Django code
> > in order to gain an understanding of how the program works. We'll be
> > doing this primarily through architecture documentation and
> > performance profiling. In early February we plan on beginning work on
> > the port.
>
> > A few of us have experience working with Django, and by the end of
> > January we should have a much better understanding of it. I've been in
> > touch with Jacob Kaplan-Moss, who pointed me to this group, and he
> > also provided me with links about contributing to the Django project
> > and Martin van Lowis' port.
>
> > We don't really have any specific questions right now as we're pretty
> > unfamiliar with most of the project at this point in time. However, we
> > are very eager to learn as much as we can, so if you have any advice,
> > warnings, or anything at all to say to us, please feel free! We'd like
> > to hear from all of you as much as possible.
>
> Hi Dave,
>
> Sounds like an interesting project!
>
> My best piece of advice would be to learn to love the test suite.
> Django's test suite may take a long time to run, but it is quite
> comprehensive, and has enabled us to complete several large internal
> refactoring projects with a minimum of impact on the general user
> community.
>
> My other advice would be to get involved in the community. Don't just
> treat your Python 3 port as "your CS project", independent of the rest
> of the world. For example, if your porting efforts discovers a section
> of code that isn't tested (or tested well), or you discover a simple
> fix that will boost performance, don't be a stranger - submit a patch
> and help us make Django better.
>
> This even extends to documentation - if your porting efforts generate
> architecture documentation that might be useful to the general
> community, we'd love to have that contributed back to the community.
>
> Best of luck with your project. I can't wait to see what you come up with :-)
>
> Yours,
> Russ Magee %-)

Russ,

Would it be possible if the django core developers to create a python3
branch in the django svn repository?

Kind regards,

--
http://jobs.scrum8.com | http://twitter.com/scrum8
-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Posting to the wrong list (was: Re: Need Django Developer urgent)

[Joshua Partogi]

I agree. In programming world, a 'user' is actually someone that
develops something with that framework or programming language. This
is quite contrast compared to OS world. The term 'Linux user' would
imply someone that actually use Linux, while Linux developers would
imply someone that is developing Linux.

Regards,

On May 12, 7:12 am, Glenn Maynard  wrote:
> Better names for django-users and django-developer would have been
> django-developer and django-core, respectively.  Calling this list
> "developer" wasn't such a great idea--the users of Django *are*
> developers; they're developing with Django.  No amount of tweaking the
> list description is going to fix the unintuitive naming.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Posting to the wrong list (was: Re: Need Django Developer urgent)

[Joshua Partogi]

Hi Jacob,

I really doubt that the people from HR would really read the
description of the group. I've been dealing with HR people. :-D All
they care about is posting the job based on the specs their end user
told them. And to them, the name django developers would imply that
the group is the place where you can get good django developers. While
django users seems to be more like a group of people that maintain
(use) django apps, the people in the IT department.

Cheers,

On May 8, 9:05 pm, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com>
wrote:
> On Fri, May 8, 2009 at 12:59 PM, Joshua Partogi <joshua.j...@gmail.com> wrote:
> > Some people get confused and thought that this list is for people that
> > develop apps with django :-D
>
> Those people might want to take the time to read the list description
> (http://groups.google.com/group/django-developers) that they see when
> signing up, which reads:
>
> """
> Discussion group for Django developers. This group is used for
> discussion of developing Django itself, not user questions; Please use
> django-users for issues regarding using the framework, questions for
> the Django user community, outreach, etc.
> """

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Need Django Developer urgent

[Joshua Partogi]

Some people get confused and thought that this list is for people that
develop apps with django :-D

On May 6, 11:32 pm, Alex Gaynor  wrote:
> 2009/5/6 Yeh, Kenzou K.F. 
>
>
>
>
>
> > Hello there,
>
> > Actually i come from Taiwan, and i' m a software engineer.
>
> > i am programmer, used to coding with c/c++, java, python, ruby. So
> > nice to meet you.   : )
>
> > 在 2009/5/6 下午 12:08000 時， haur 寫到：
>
> > > hello , i'am in china
>
> > > i'am  a  pythoner ~~
>
> > > uses python, django, nginx and so on.
>
> As I've said, this is not the right place for any of these discussions.
> Please take them to the appropriate forum.
>
> Alex
>
> --
> "I disapprove of what you say, but I will defend to the death your right to
> say it." --Voltaire
> "The people's good is the highest law."--Cicero
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Schema Evolution

[Joshua Partogi]

+1 with South. It's really comprehensive.

On Apr 18, 12:01 am, JL  wrote:
> Just to through in my 2c (since I'm acutally in the US).  I'd second
> South as being the most complete and flexible migration project.  I've
> used it on almost every Django project I've done.  I'd love to see it
> rolled in such that every dev working on evolution could focus on one
> platform.
>
> On Apr 16, 3:15 am, Andreas  wrote:
>
> > I know everyone is fed up with discussions about schema evolution and
> > multi db support but when it comes to schema evolution I think it's
> > time to have a discussion about it again.
>
> > I think we all can agree that picking a schema evolution app for a
> > django project isnt one of those things everybody wants to do when
> > they begin developing with django. And if im not mistaken, it has been
> > said on conferences and google talks that django is about not making
> > the developer to do decisions like "which auth framework or template
> > engine do i need" when they start out. I think schema evolution is one
> > of those pieces aswell. Of course one shouldnt have to use a django
> > shipped one.
>
> > My suggestion...
>
> > I've seen more and more people involved in django core development
> > either as core developer or submitting patches recommending south
> > (http://south.aeracode.org/) on twitter and people talking about it
> > on irc. My suggestion is simply to just through south in. Of course I
> > can see developers of other schema evolution frameworks could become
> > disappointed with this but Ill think it's in their interrest aswell
> > getting something shipped with django, and they can help contribute to
> > make it fit their needs aswell which would make the "default choice"
> > even better for more people. And if it totaly doesnt fit their needs,
> > they already have their own stuff to continue with.
>
> > I hope the core developers can make a decision that doent include
> > stepping on a sore toe and I hope they are not afraid and have what it
> > takes to pick something already built and branded, there's no need to
> > build a schema evolutotion framework for django.contrib form scratch.
>
> > Of course the 1.1 release is to soon for something like this but give
> > it some thought and a decision could be made before the summer for the
> > 1.2.
>
> > My 5 swedish ören because I dont have any cents.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---