>
> In addition to the wiki page mentioned above, I do recommend just
> having a look at how Airflow have their repository configured.
> https://github.com/apache/airflow
>
> They do have a simple PR template.  The issues layout / forms are
> great - try working through the Issues / New Issue process!
>

Still looking at that and it seems reasonable

If the DIscussion is added to Github (assume one of the repository admins
could enable that in some way), how would that work with existing mailing
lists?  Would it be like a new mailing list?  Would things get mirrored to
the existing lists?  Would posts on discussion get forwarded to emails?

Still raises the question, if the problem with current setup is mainly
driven by lack of integration between JIRA/Github - see autolink thread),
learning curve of JIRA (difficulty of using JIRA) -  possibly lack of
process/documentation, and change control/management/time to do so, will
this still result in potentially new/different learning curve of GItHub
Issues/Discussions, having to change process/documentation again, and how
to handle existing ticket (doall the tickets get duplicated from JIRA to
GIt?  Or maybe a subset [no need for closed ones unless some record of
these is preferred; try to avoid bringing duplicates, OBE tickets, etc.],
make JIRA read only after a time.

I've been following the openjdk side and they continue to have multiple
tracking systems which in that context is also burdensome but I believe
part of that is driven by the organization management side (have an
"official system of record for issues", have a secondary one on github
which still has to be linked up with each other).  However, I noticed in PR
discussion some "switches" that can be added to the discussions to trigger
automatic things like or set state like request reviews, set milestones,
etc.  How much of that is present in our current workflow?

Eric Bresie
[email protected]


On Thu, Nov 11, 2021 at 9:44 AM Eric Bresie <[email protected]> wrote:

>
> Eric Bresie
> [email protected]
>
>
> On Thu, Nov 11, 2021 at 9:08 AM Neil C Smith <[email protected]>
> wrote:
>
>> On Thu, 11 Nov 2021 at 14:55, Eric Bresie <[email protected]> wrote:
>>
>> >    -  Repository admins accept content reports
>>
>> Interesting. Maybe. What does the last one mean exactly?!
>>
>> Have to confess I don't know since I'm not an admin :-) but  I'm guessing
> it has to do with reporting abuse of some kind for the given repository
>
>
> https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository
>
>

Reply via email to