Nice work!
On Thursday, July 14, 2016 at 10:36:19 PM UTC-5, Andrew Godwin wrote:
>
> I am happy to report that the Official Projects DEP, number 0007, was
> approved by the Technical Board and is now adopted as final!
>
> Andrwe
> On 4 Jul 2016 11:39 am, "Andrew Godwin
I am happy to report that the Official Projects DEP, number 0007, was
approved by the Technical Board and is now adopted as final!
Andrwe
On 4 Jul 2016 11:39 am, "Andrew Godwin" wrote:
> I've revised the documentation section for clarity about external hosting,
> and give
I've revised the documentation section for clarity about external hosting,
and given the lack of further discussion or dissention, I'm now taking the
DEP to the technical board for a decision.
Andrew
On Sun, Jun 12, 2016 at 4:35 AM, Andrew Godwin
wrote:
>
> On 12 Jun 2016 2:00 a.m., "Tim Graham
On 12 Jun 2016 2:00 a.m., "Tim Graham" wrote:
>
> 1. It might be nice if projects had more than one shepherd so there's not
a single point of failure. Of course, if all members of the maintenance
team end up joining the team, then there's no issue.
It depends how the role of work is split betwee
Hi Andrew,
Here's my 2 cents:
1. It might be nice if projects had more than one shepherd so there's not a
single point of failure. Of course, if all members of the maintenance team
end up joining the team, then there's no issue.
2. Re: "The main project documentation does not have to be
Just to update on this, there was some good feedback on the draft for
writing and clarity, and it's now made it into an official draft, located
here:
https://github.com/django/deps/blob/master/draft/0007-official-projects.rst
If you'd like to read through the draft and raise discussion points or
o
Hi everyone,
I've started on an "official projects" process DEP as I discussed here a
while back, to formalise the process of adopting non-core packages as
repositories under the official Django organisation, with a view to taking
Channels on this route (and hopefully including the existing localf
