> But don't be dismayed if no one responds. I'm not at all dismayed, and knew it was a shot in the dark, but might as well try for somebody who likes to discuss Django refactoring, or might be interested in the stuff we are building. And thanks again for the responses to my question about why no responses.
On Monday, March 6, 2017 at 10:10:53 AM UTC-6, mark wrote: > > I echo Vijay's comment. Lists like this are really great for very specific > questions and short code segments or error message that a more experienced > person can answer off the top of their head. Your question is very broad > and requires a large time commitment from the reader to respond. With that > said, there is nothing wrong with posting your question as you may get > someone who has some free time to dive in and try to help. Or someone who > has done a lot of refactoring and can give you some pointers. But don't be > dismayed if no one responds. > > You could also rephrase your question to be more like "I am in the process > of refactoring a large project. What recommendations would you make as far > as how to tackle this project? We built the project using Django x.x.x, so > where would you recommend we start with this project." More along the lines > of best practices for refactoring django projects, or what has the reader > learned after refactoring django projects. This question does not require > the reader to dive into your code, but to relate what they know about the > topic. Easier and much less time consuming for the reader. > > You could also offer to pay someone to help kick start your project, and > then if someone responds, take the discussion offline. > > As you refactor the project and run into issues, be sure to post those > very specific questions and short code segments/error message to the list. > The folks here are very friendly, extremely knowledgeable, and very willing > to help as long as you make it super easy for them to help you figure out > the answer to a specific question. > > God luck! > > Mark. > > On Mon, Mar 6, 2017 at 5:13 AM, Vijay Khemlani <vkhe...@gmail.com > <javascript:>> wrote: > >> Also, this type mailing lists are usually for specific questions about >> the framework >> >> "How do I make this particular query with the ORM" >> "Why isn't this variable getting rendered in the template" >> >> etc >> >> Your question is kinda broad >> >> On 3/6/17, Bob Haugen <bob.h...@gmail.com <javascript:>> wrote: >> > Antonis, thank you very much for the feedback! You are absolutely >> > correct! I apologize to you and the list, and will strive to follow >> > your suggestions in the future. >> > >> > I suspect, however, that the very long explanation that would have >> > been required to avoid the links would have been offputting, too. This >> > might be a request that was just inappropriate for this list. >> > >> > As for now, we're charging happily ahead. >> > >> > On Mon, Mar 6, 2017 at 5:45 AM, Antonis Christofides >> > <ant...@djangodeployment.com <javascript:>> wrote: >> >> Hi, >> >> >> >> I, like many people, am busy. I will generally not spend too much time >> on >> >> the messages of this list. I delete most of them after only reading the >> >> subject line. If I do choose to read the body, I expect to understand >> >> what >> >> it is about after a few seconds of reading. But all I can see in your >> >> original message is that you have a big Django project that needs >> >> refactoring, and several links with the code and your discussions about >> >> them. Essentially the message I'm getting is "I can't tell you what I >> >> want >> >> in this email message, but if you click on these links and study them >> for >> >> about half an hour, you'll get it". >> >> >> >> Likewise, it would have been way better to include your original >> message >> >> in >> >> the reply. In order to find your original message I had to dig in my >> >> Trash >> >> folder. I would normally not do that, and I would have ignored your >> reply >> >> as >> >> well. It just happens that I'm travelling and I'm quite relaxed. >> >> >> >> Bottom line: you need to make it very easy for me to help you, and I >> >> believe >> >> the same goes for other people as well. >> >> >> >> Regards, >> >> >> >> Antonis >> >> >> >> Antonis Christofides >> >> http://djangodeployment.com >> >> >> >> On 03/06/2017 12:36 PM, bobhaugen wrote: >> >> >> >> I was disappointed to get no response on this topic, and would be >> >> grateful >> >> for any feedback on why that might have been. >> >> >> >> Too big? Big ball of mud? Stupid project? ____? (I have very little >> >> touchiness...) >> >> >> >> I hope people did not think we wanted to get them to do all or even >> very >> >> much work for us. We are charging ahead here: >> >> https://github.com/django-rea >> >> >> >> We did find, and are using, some delicious advice from Marty Alchin: >> >> http://martyalchin.com/2008/jan/10/simple-plugin-framework/ >> >> And upgrading to the latest version of django, changing to class-based >> >> views, and breaking up both models and views into several files. >> >> >> >> Next: a bunch of abstract base classes. >> >> >> >> After that: more API work and a mobile app to use it. >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "Django users" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an >> >> email to django-users...@googlegroups.com <javascript:>. >> >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> >> Visit this group at https://groups.google.com/group/django-users. >> >> To view this discussion on the web visit >> >> >> https://groups.google.com/d/msgid/django-users/a3e12fd2-fc27-447a-a5f5-e394c3d67cff%40googlegroups.com >> . >> >> For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> >> -- >> >> You received this message because you are subscribed to a topic in the >> >> Google Groups "Django users" group. >> >> To unsubscribe from this topic, visit >> >> https://groups.google.com/d/topic/django-users/9OU0TfwcmTQ/unsubscribe >> . >> >> To unsubscribe from this group and all its topics, send an email to >> >> django-users...@googlegroups.com <javascript:>. >> >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> >> Visit this group at https://groups.google.com/group/django-users. >> >> To view this discussion on the web visit >> >> >> https://groups.google.com/d/msgid/django-users/4d7559f1-e3a2-64f0-d6b3-60c902e17921%40djangodeployment.com >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "Django users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to django-users...@googlegroups.com <javascript:>. >> > To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> > Visit this group at https://groups.google.com/group/django-users. >> > To view this discussion on the web visit >> > >> https://groups.google.com/d/msgid/django-users/CA%2BSvw0WRHpTUUV1RceS8MWuRjGQ3JyJqZ%3DCKdKGSLYV8%2BQma2g%40mail.gmail.com >> . >> > For more options, visit https://groups.google.com/d/optout. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CALn3ei1ebA9c7dZJ7EeVeQ39pSza90PhVz-7tv7MqJchDVM-6w%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5e8f17a9-a997-49a5-acb4-430221e48f5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
