Is DRF still considered alive? #8110
-
|
Hey. Let me start that I really appreciate all the work the encode is doing for python ecosystem, I am really grateful for that. However, I went through 2020 and 2021 reports and there isn't really much about DRF, as it's considered feature complete and stable. Reports where DRF is mentioned:
the main take-away is that even if it's the main source of income for Encode, it's not where the most focus goes. From my perspective, this is the image I get (and it might be unfair!):
I like DRF, used that in many projects, but I am starting to worry. This is not looking good. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hiya, Okay, so I ought treat this one as a prompt - I've been pretty clear in the reports lately about prioritizing other Encode projects, for quite a while, but yeah it's clearly out of balance. Even though I think the best us of my OSS time at the moment is elsewhere, there really does need to be more maintainance time on REST framework, and if not then it'd be time to start talking about transfering it elsewhere (eg. over to the DSF.) There will need to be some kind of transfer one of these days, but right now let me just treat this discussion as a prompt and get back to commiting at least some of my time back onto the project. Ensuring that at least one of my five working days a week was dedicated to REST framework would be a great plan. Here's the obvious things I can think of prioritising:
What priorities would you like to see, @hnykda? |
Beta Was this translation helpful? Give feedback.
-
|
DRF 3.13 is already few months delay so that would be great to focus on. there are some django related stuff, without whom I dont think its feature complete. django is 16 years old and still not feature complete, and as DRF is a django extension, unless django is feature complete, as the new features which are not supported in drf from django is not working properly. dedicating 1 working day per week would be great. you could consider adding some more collaborators who contributed to drf for few years. You can consider me for help in ongoing maintenance hand. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Tom!
I agree. I do think that you working on the other projects is actually better for the ecosystem. That's why I think you wouldn't have to necessarily do all the job by yourself, but rather invest your time in a plan to have long-term maintainers.
The ones you listed sound good to me. And honestly, I think you can tell better. I want to appreciate you taking this seriously and with a good-faith assumption. |
Beta Was this translation helpful? Give feedback.
-
|
If I could be a future collaborator of this project, I can manage monthly fund for my time spending on the project. |
Beta Was this translation helpful? Give feedback.
-
|
@auvipy That's an interesting proposition. Right now Encode is only just about break-even for my full-time salary so we're not able to take on a contractor right now, but it's feasible that could change. You're very welcome to email me privately and fill me in on what current OSS contracting you're taking on (I know you're a celery maintainer, and they have some funds managed via open collective, right?) and what your expectations would be from a contracted REST framework position. |
Beta Was this translation helpful? Give feedback.
-
|
thanks Tom for your kind reply, I will be reaching you soon as ASAP. tom@tomchristie.com is this the email to reach you? |
Beta Was this translation helpful? Give feedback.
Hiya,
Okay, so I ought treat this one as a prompt - I've been pretty clear in the reports lately about prioritizing other Encode projects, for quite a while, but yeah it's clearly out of balance. Even though I think the best us of my OSS time at the moment is elsewhere, there really does need to be more maintainance time on REST framework, and if not then it'd be time to start talking about transfering it elsewhere (eg. over to the DSF.)
There will need to be some kind of transfer one of these days, but right now let me just treat this discussion as a prompt and get back to commiting at least some of my time back onto the project. Ensuring that at least one of my five working days a week …