Date: Fri, 13 Dec 2019 19:15:56 +0000
No, that repo only contains official SG20 work. For something to become
official, it will need to first appear as a proposal and be approved by
SG20.
On Fri, 13 Dec 2019 at 18:17, Tupaschoal <tupaschoal_at_[hidden]> wrote:
> Ah ok, I'll watch it closely and wait for the sample guidelines, I'm
> assuming every work will be on the SG20 repo, right?
>
>
> Túlio P. Leão
>
>
> On Fri, Dec 13, 2019 at 2:59 PM Christopher Di Bella via SG20 <
> sg20_at_[hidden]> wrote:
>
>>
>>
>> On Fri, 13 Dec 2019 at 17:55, Neil Horlock via SG20 <
>> sg20_at_[hidden]> wrote:
>>
>>> How to proceed from there? Do we have to wait for proper issue
>>>> description or can I just seize a topic and write about it?
>>>
>>>
>>> The intention is (I believe) for people to take topics and write the
>>> Outcomes and Objectives for each. Or what JC calls ASSBATs (A student
>>> should be able to). In Belfast, given the intention of this is to inform
>>> educators rather than students, that was semi-jokingly twisted into ATSBATS
>>> (A Teacher Should Be Able To). With this in mind, each of those topics will
>>> be defined by the key learning to be derived from that topic at various
>>> "levels".
>>>
>>> The "levels" at which each topic could be taught were discussed in the
>>> context of using the "audience" guidelines example that Gor Nishanov had
>>> used with his Co-Routines papers (Chris or someone may be able to help me
>>> out here with a direct reference as I cannot find it right now). In
>>> essence, those tables highlighted aspects of a topic that "Everyone should
>>> know" (fundamentals) down to "<100 need to know" (expert).
>>>
>>> IIRC, SG20 designated certain people to write the sample guidelines in
>>>> Belfast.
>>>>
>>>
>>> I would have to check the minutes, we definitely chose to have an
>>> initial topic (or two) set out as guidance. I do not recall if any
>>> individuals took that on.
>>>
>>
>> The minutes don't record it, but I know I did.
>> I think there's a photo on my phone that has the other names.
>>
>>
>>>
>>> Neil
>>>
>>> On Fri, 13 Dec 2019 at 17:41, Tupaschoal via SG20 <sg20_at_[hidden]>
>>> wrote:
>>>
>>>> How to proceed from there? Do we have to wait for proper issue
>>>> description or can I just seize a topic and write about it?
>>>>
>>>> Túlio P. Leão
>>>>
>>>>
>>>> On Fri, Dec 13, 2019 at 2:34 PM Christopher Di Bella via SG20 <
>>>> sg20_at_[hidden]> wrote:
>>>>
>>>>> As promised, the functions module is now tracked on GitHub
>>>>> <https://github.com/cplusplus/SG20/issues>, and so we could make that
>>>>> our designated demo module.
>>>>>
>>>>> Contenders for a sample module:
>>>>>
>>>>> - meta-error handling
>>>>> - I/O
>>>>> - functions
>>>>>
>>>>> If you're unsure about what is being tracked, or why, please ask it on
>>>>> the mailing list instead of GitHub, since those issues need to remain
>>>>> topic-relevant.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Chris
>>>>> --
>>>>> SG20 mailing list
>>>>> SG20_at_[hidden]
>>>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>>>
>>>> --
>>>> SG20 mailing list
>>>> SG20_at_[hidden]
>>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>>
>>> --
>>> SG20 mailing list
>>> SG20_at_[hidden]
>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>
>> --
>> SG20 mailing list
>> SG20_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>
>
official, it will need to first appear as a proposal and be approved by
SG20.
On Fri, 13 Dec 2019 at 18:17, Tupaschoal <tupaschoal_at_[hidden]> wrote:
> Ah ok, I'll watch it closely and wait for the sample guidelines, I'm
> assuming every work will be on the SG20 repo, right?
>
>
> Túlio P. Leão
>
>
> On Fri, Dec 13, 2019 at 2:59 PM Christopher Di Bella via SG20 <
> sg20_at_[hidden]> wrote:
>
>>
>>
>> On Fri, 13 Dec 2019 at 17:55, Neil Horlock via SG20 <
>> sg20_at_[hidden]> wrote:
>>
>>> How to proceed from there? Do we have to wait for proper issue
>>>> description or can I just seize a topic and write about it?
>>>
>>>
>>> The intention is (I believe) for people to take topics and write the
>>> Outcomes and Objectives for each. Or what JC calls ASSBATs (A student
>>> should be able to). In Belfast, given the intention of this is to inform
>>> educators rather than students, that was semi-jokingly twisted into ATSBATS
>>> (A Teacher Should Be Able To). With this in mind, each of those topics will
>>> be defined by the key learning to be derived from that topic at various
>>> "levels".
>>>
>>> The "levels" at which each topic could be taught were discussed in the
>>> context of using the "audience" guidelines example that Gor Nishanov had
>>> used with his Co-Routines papers (Chris or someone may be able to help me
>>> out here with a direct reference as I cannot find it right now). In
>>> essence, those tables highlighted aspects of a topic that "Everyone should
>>> know" (fundamentals) down to "<100 need to know" (expert).
>>>
>>> IIRC, SG20 designated certain people to write the sample guidelines in
>>>> Belfast.
>>>>
>>>
>>> I would have to check the minutes, we definitely chose to have an
>>> initial topic (or two) set out as guidance. I do not recall if any
>>> individuals took that on.
>>>
>>
>> The minutes don't record it, but I know I did.
>> I think there's a photo on my phone that has the other names.
>>
>>
>>>
>>> Neil
>>>
>>> On Fri, 13 Dec 2019 at 17:41, Tupaschoal via SG20 <sg20_at_[hidden]>
>>> wrote:
>>>
>>>> How to proceed from there? Do we have to wait for proper issue
>>>> description or can I just seize a topic and write about it?
>>>>
>>>> Túlio P. Leão
>>>>
>>>>
>>>> On Fri, Dec 13, 2019 at 2:34 PM Christopher Di Bella via SG20 <
>>>> sg20_at_[hidden]> wrote:
>>>>
>>>>> As promised, the functions module is now tracked on GitHub
>>>>> <https://github.com/cplusplus/SG20/issues>, and so we could make that
>>>>> our designated demo module.
>>>>>
>>>>> Contenders for a sample module:
>>>>>
>>>>> - meta-error handling
>>>>> - I/O
>>>>> - functions
>>>>>
>>>>> If you're unsure about what is being tracked, or why, please ask it on
>>>>> the mailing list instead of GitHub, since those issues need to remain
>>>>> topic-relevant.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Chris
>>>>> --
>>>>> SG20 mailing list
>>>>> SG20_at_[hidden]
>>>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>>>
>>>> --
>>>> SG20 mailing list
>>>> SG20_at_[hidden]
>>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>>
>>> --
>>> SG20 mailing list
>>> SG20_at_[hidden]
>>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>>
>> --
>> SG20 mailing list
>> SG20_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg20
>>
>
Received on 2019-12-13 13:18:35