Re: Proposing development discussion forums

2019-08-10 Thread gaurav jain
This sounds good to me, plus this can be a all in one django spot for
django developer specially new developer


On Sat, 10 Aug, 2019, 8:33 AM Andrew Godwin,  wrote:

> Hi everyone,
>
> This might be slightly controversial, but I would like to propose that we
> have a forum for discussing Django development (and potentially user
> support), alongside the mailing list and maybe, eventually replacing it.
>
> My full reasoning is below, but in short, it would be more accessible for
> new users, have a better UI, give us the ability to moderate away
> problematic posts, be better for privacy, and still allow email-based
> interaction.
>
> At DjangoCon AU, the opening keynote was an invited speaker from the Rust
> community (E. Dunham, https://twitter.com/QEDunham). I invite you to
> watch the full talk if you are at all interested in how another language
> handles their community (https://www.youtube.com/watch?v=TW7PxyrCBR0),
> but the takeaway for me was their use of forums rather than mailing lists.
>
> The Django mailing lists were an excellent choice when Django began, but I
> feel they have aged out of the modern Web somewhat. The user interface for
> accessing them is particularly poor, which makes it particularly bad for
> new contributors.
>
> In addition, when looking at how to organise the effort to help bring
> async into Django, something more dynamic, and more segmented, than mailing
> lists would be incredibly useful. I don't want to drown out the list in
> specific discussions of how to port certain features, but we need to have
> those discussions somewhere permanent and asynchronous (so not IRC).
>
> The mutability of a forum is also not to be overlooked - as well as
> allowing things like pinned posts and post edits for small issues (or a
> living header on a long discussion topic), it also allows for permanent
> removal of things that break the Code of Conduct. On the people front, it
> also allows people to post without their email being public, allows for
> name changes, and provides for someone's right to be forgotten via
> anonymisation of prior content.
>
> Now, I'm not suggesting we kill the mailing list and switch over or
> anything like that; instead, I suggest we run an instance of Discourse as a
> test, and use it as the primary discussion area for async work, as well as
> anything else that people want to discuss - with the expectation that
> anything important still goes out to this mailing list.
>
> Why Discourse? Apart from being a mature, open source forum project, it's
> also very fully featured, and even supports subscribing and interacting
> with the forum over email, so it can still fit into an email-based
> workflow. There are also plenty of small niceties, like the option to have
> it hosted for us via a paid service, or the ability to use GitHub for login
> rather than requiring a separate username and password. It also helps that
> Rust seems quite happy with it.
>
> I'm mostly asking for the "temperature of the room" on this one - if we
> get some small objections, I think a trial period is still worthwhile. If
> there are major objections, then I'd like to ask people what their
> alternative suggestions are for solving this sort of communication.
>
> Do I think this would replace the mailing list? Not in the short term, but
> maybe if it takes off and we all like it better. I personally would
> interact with django-developers a whole lot more if I could just subscribe
> to certain topics (rather than trying to emulate that with an email filter
> as I do now!), and honestly the same thing for django-users. That said, I
> also recognise that diluting the support/discussion pool is not exactly an
> attractive idea, which is why I'm asking for input!
>
> Thanks,
> Andrew
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAFwN1urJmpwTYqXSF_L57hDLL5-9T4Bkvj9Sb9p8na_-_YWEgA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMiDnWACO%3D%2B%2B4b76c076z_ZTrDAwy9fObNByxmhzuf12iNrMaA%40mail.gmail.com.


GSoC-19 Project Ideas

2019-01-31 Thread gaurav jain
Hi Everyone,
I had some ideas for the upcoming GSoC.
1. To make a code coverter old clean flask monolithic code to be converted 
to simple Django Code. All we would need is to change the queries and shift 
rest of the code. 
2. I have personally been using a code generator for my 
APIs(https://github.com/GauravJain98/drf-generator). So similar to this i 
wanted something like create react app that would take the project name the 
number of apps and name of apps and make the whole this for us.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d1eb040a-5656-4889-b589-c504a9c9c13c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


GSoC Idea

2019-01-31 Thread gaurav jain
from django.db import models
from django.contrib.auth.models import User

class CommenInfo(models.Model):
archived = models.BooleanField(default=False)
created_at = models.DateTimeField(auto_now_add=True)
updated_at = models.DateTimeField(auto_now=True)

def delete(self):
self.archived = True
super().save()

class Meta:
abstract = True
class Team(CommenInfo):
pass


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/73471eba-70a9-416d-8877-1d3c94555fe4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google Summer of Code 2019

2019-01-31 Thread gaurav jain
One Idea i have a one command django project maker to instead having 1+n 
commands(n number of apps) and linking them in setting we can have command 
take the number of apps and app_names in ine do and then later we can add 
functionality for heroku ,docker etc

On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:
>
> Org applications for Google's Summer of Code are now open (deadline 
> February 6). Do you think the Django Software Foundation should participate?
>
> We haven't had any high quality student applications that we could accept 
> for the past two years.
>
> Perhaps it's partly a function of a poor ideas page (
> https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't 
> do a great job of publicizing our involvement and attracting high quality 
> students. Perhaps it's because the student payment isn't all that much 
> (+/-$6000 USD, depending on student's country)* for the amount of work 
> involved (also, students have to put in a lot of work up front in their 
> application, with no guarantee of being accepted into the program).
>
> If you have any ideas about mentoring or suggesting a project, or if 
> you're serious about being a student (you should start contributing to 
> Django now if you don't already), please share.
>
> * https://developers.google.com/open-source/gsoc/help/student-stipends
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/636bd240-4422-4864-aa96-76d8836fdeab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.