[CHAOSS] [wg-di] Working Group Team Discussions on Github

Emma Irwin eirwin at mozilla.com
Fri Oct 5 16:37:13 UTC 2018


"*public* posts are visible to all members of the organization."

*sigh* that is not the right word for limited  org level access.
Nevermind then...

On Fri, Oct 5, 2018 at 9:25 AM Tobie Langel <tobie at codespeaks.com> wrote:

> My understanding is “public” means org members only and “private” means
> team members only.
>
> —tobie
>
> On Fri, Oct 5, 2018 at 18:23 Emma Irwin <eirwin at mozilla.com> wrote:
>
>> It is actually, in the functionality to post publicly, or for just team.
>> However, the only options we have are for 'private or CHAOSS org'.   From
>> reading the documentation, it seems that this setting to allow 'public
>> posts',  is Github org-level.  Can someone help me?  (wiling to hop on a
>> call with me to figure it out perhaps).
>>
>> Thanks
>>
>>
>>
>> On Fri, Oct 5, 2018 at 8:24 AM Emma Irwin <eirwin at mozilla.com> wrote:
>>
>>> Thank for feedback.   It was not the intention to  'not be open' , I'll
>>> see if I can configure it differently.
>>> Discourse is definitely better than mailing lists - at Mozilla we've
>>> moved to this as our primary community tool.  We can always use those
>>> <https://discourse.mozilla.org/> for the interim as well (I can setup a
>>> chaoss category).
>>>
>>> On Fri, Oct 5, 2018 at 2:44 AM Jose Manrique Lopez de la Fuente <
>>> jsmanrique at bitergia.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I think GitHub Team Discussions is set to GitHub organization members.
>>>> I am agree with Tobie's concerns, and also with Emma's reasons for
>>>> requesting something different to a mailing list for discussions.
>>>>
>>>> I would vote for something like Discourse (https://www.discourse.org/),
>>>> a free open source software forum. There could be a set of groups
>>>> pre-defined (for example, each CHAOSS WG), open for anyone to join and
>>>> discuss, without requiring to be GitHub user and also member of CHAOSS
>>>> organization.
>>>>
>>>> Just my 2 cents
>>>>
>>>> ---
>>>> Manrique
>>>>
>>>>
>>>>
>>>>
>>>> El vie., 5 oct. 2018 a las 9:03, Tobie Langel (<tobie at codespeaks.com>)
>>>> escribió:
>>>>
>>>>> It seems that the content of these threads are not publicly visible.
>>>>> Unless that’s setable somewhere, it’s an important step back from openness,
>>>>> and as such, a real blocker.
>>>>>
>>>>> —tobie
>>>>>
>>>>> On Fri, Oct 5, 2018 at 08:33 Dawn Foster <dawn at dawnfoster.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 5, 2018 at 3:48 AM, Emma Irwin <eirwin at mozilla.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> As per Issue in our task tracker,
>>>>>>> <https://github.com/chaoss/wg-diversity-inclusion/issues/73> we are
>>>>>>> experimenting with Github Team Chat.  We are doing this for a number of
>>>>>>> reasons:
>>>>>>>
>>>>>>>
>>>>>>>    1. To better capture threads of conversation outside of email.
>>>>>>>    2. To be a more visible source of conversation for newcomers.
>>>>>>>    3. To better accommodate proposals, that are early/half-baked or
>>>>>>>    exploratory without triggering bigger discussions on the list.
>>>>>>>    4. To experiment beyond mailing lists.
>>>>>>>
>>>>>>> I might also add : to better inform monthly updates, which not
>>>>>>> everyone can make.
>>>>>>>
>>>>>>
>>>>>> Sounds like a great idea!
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> For reasons I cannot yet describe, only Dawn, George, Daniel and I
>>>>>>> are members
>>>>>>> <https://github.com/orgs/chaoss/teams/di-working-group/members>.
>>>>>>> Please help me debug, he process for being 'added' to this team.   This is
>>>>>>> ultimately the potential (team forum
>>>>>>> <https://github.com/orgs/chaoss/teams/di-working-group/discussions>
>>>>>>> ).
>>>>>>>
>>>>>>
>>>>>> We ran into something similar earlier this week when Daniel couldn't
>>>>>> assign a GitHub issue to me. I suspect that you need to add the other
>>>>>> people to the CHAOSS Organization:
>>>>>> https://github.com/orgs/chaoss/people before adding them to a team.
>>>>>> When you add someone to an organization, they need to go through the
>>>>>> process of accepting being added, which may or may not also need to be done
>>>>>> before you add them to a team. After Daniel added me to the organization,
>>>>>> and I accepted it, he was able to assign me to issues. I'm guessing this
>>>>>> might solve your issue?
>>>>>>
>>>>>> Cheers,
>>>>>> Dawn
>>>>>>
>>>>>> _______________________________________________
>>>>>> CHAOSS mailing list
>>>>>> CHAOSS at lists.linuxfoundation.org
>>>>>> https://lists.linuxfoundation.org/mailman/listinfo/chaoss
>>>>>>
>>>>> _______________________________________________
>>>>> CHAOSS mailing list
>>>>> CHAOSS at lists.linuxfoundation.org
>>>>> https://lists.linuxfoundation.org/mailman/listinfo/chaoss
>>>>>
>>>> _______________________________________________
>>>> CHAOSS mailing list
>>>> CHAOSS at lists.linuxfoundation.org
>>>> https://lists.linuxfoundation.org/mailman/listinfo/chaoss
>>>>
>>>
>>>
>>> --
>>> Emma Irwin (she/her)
>>> Community Development
>>> Open Innovation Team
>>>
>>
>>
>> --
>> Emma Irwin (she/her)
>> Community Development
>> Open Innovation Team
>>
>

-- 
Emma Irwin (she/her)
Community Development
Open Innovation Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/chaoss/attachments/20181005/f08ff0d5/attachment-0001.html>


More information about the CHAOSS mailing list