1 |
> On 5 Oct 2021, at 21:29, Alec Warner <antarus@g.o> wrote: |
2 |
> |
3 |
> I thought we were going to go with the github-pages type route |
4 |
> (markdown, rendered online or locally.) |
5 |
> |
6 |
|
7 |
So, the thinking was, we could allow somewhat shorthand |
8 |
notes or for the people who want to invest more time, allow |
9 |
the GitHub-pages type route. |
10 |
|
11 |
But I'm open to the idea of just recommending people |
12 |
use that if there's no appetite for mixed types. |
13 |
|
14 |
> -A |
15 |
> |
16 |
> On Tue, Oct 5, 2021 at 11:28 AM Sam James <sam@g.o> wrote: |
17 |
>> |
18 |
>> This is a preliminary version/draft of a proposed change to |
19 |
>> GLEP 68. |
20 |
>> |
21 |
>> I'd like to introduce a method for developers to signal anything |
22 |
>> special about a package and how to correctly maintain it. |
23 |
>> |
24 |
>> Sam James (1): |
25 |
>> glep-0068: Add notes element for package maintenance instructions |
26 |
>> |
27 |
>> glep-0068.rst | 26 +++++++++++++++++++++++--- |
28 |
>> 1 file changed, 23 insertions(+), 3 deletions(-) |
29 |
>> |
30 |
>> -- |
31 |
>> 2.33.0 |
32 |
>> |
33 |
>> |
34 |
> |