Hi Paolo, I do like the overall idea - a few thoughts below.
My first concern for this, which somewhat echoes James, is that trying to organise an additional in-person event that a large number of contributors are expected to go to is difficult. Funding considerations are one concern - we would need to make sure everyone whose companies did not cover them to go had their trip paid for - but time away from home is also something that we should be considerate of, be it for family or for anything else. That, too, brings an interesting challenge - who do you invite (and presumably help pay for)? We no longer have a core team, and I don't think it's worth singling the Technical Board out in this regard - the Fellows are an obvious requirement if they can make it, but past that, it's a hard metric to gauge. I do like your point about disconnecting it from needing to give a talk, though - conferences and sprints are certainly Different Moods for me, and it can be draining to be sociable for three days and *then* have to go into sprints and be even more so. I don't know if there's a useful resolution to this specific problem. My second concern is almost the opposite of that, ironically, which is that I do believe there are some things that benefit from synchronous, in-person communication. A single week at the most recent DjangoCon has done wonders for me in that regard, and while I do believe it should be a hybrid event, I also think it should *not* be a remote-only event. While it is a personal opinion, I find in-person sprinting significantly easier (due to the nature of the work as opposed to purely coding) and would probably find it hard to attend a remote-only sprint. The final question I would raise is that of location. There are two elements here - where in the world do you hold it, and what the actual venue is like. There is no single location in the world you will ever find where everyone can attend - even with very patient Australians who are far too willing to sit on planes for ages. It's likely you'd have to geolocate in either the Americas or in Europe, and if you additionally want to host it in a location that is safe for all attendees, that cuts down the number of US states and European countries even more. And then, the venue. In the modern world, I ideally want an *outdoors* sprint venue, so that we're not all stuck inside a room hoping the masks work well enough. That places limitations on climate and season and also availability of power - so many that it starts to look like an impossible task to satisfy this along with all the above. I don't write this as a means of discouragement - I think there's a lot to be said for your idea, and even though I've outlined a lot of potential flaws, I think a flawed event in this fashion would be better than nothing happening at all! I just want to highlight all the talking points we're going to need to really think about and have answers to if we take this forward. (I didn't even discuss how we might fund this, which is also a conversation to have, but waving our hands in the air and going "sponsorship" is enough for me to start with) Andrew On Wed, Oct 26, 2022, at 4:01 PM, Paolo Melchiorre wrote: > Hi everyone, > > Following Andrew Godwin's example, I too share with you a proposal > that I made during DjangoCon US 2022 and that I have already shared > with some of you. > > Inspired by an article by Will Vincent, I wrote my proposal for Django > Core Sprints, and its genesis, in an article and would also like to > have the opinions of the Django community members interested in the > idea: > https://www.paulox.net/2022/10/26/about-my-proposal-for-the-django-core-sprints/ > > Ciao, > Paolo > -- > Paolo Melchiorre > > https://www.paulox.net > > -- > 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 > <mailto:django-developers%2bunsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAKFO%2Bx6FAf-M14fKx5QS1K8rru2L3mOiR1R%3Dn6FzDk%3DrnaUq3A%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/ebd86080-6735-45f7-8dd7-3ddc23c4a44d%40app.fastmail.com.
