Expand awesome issue templates to other publiclab repositories

[Uzay-G]

In plots2, we have an amazing set of github issue templates for bug reports, ftos and feature requests. I think we should export these to other repositories, like mapknitter, image-sequencer, spectral-workbench and all the others where it would be useful. That way there would be more first timer issues on other repositories and this would simplify things for contributors.

Currently, there are templates in some other repositories. The problem is that they are not used because they are not suggested to contributors when they make an issue. unlike inside plots2. These repos use the old model for creating templates in Github and not the new one.

I am working on implementing this for Mapknitter but would love your help on accomplishing this on the other repositories! Do you think this is a good idea? @publiclab/community-reps I'd love to implement the changes! :+1:

[jywarren]

That'd be awesome!!!

On Tue, Jan 7, 2020 at 2:51 PM Uzay-G notifications@github.com wrote:

In plots2, we have an amazing set of github issue templates for bug reports, ftos and feature requests. I think we should export these to other repositories, like mapknitter, image-sequencer, spectral-workbench and all the others where it would be useful. That way there would be more first timer issues on other repositories and this would simplify things for contributors.

Do you think this is a good idea? I'd love to implement the changes! 👍

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/publiclab/plots2/issues/7141?email_source=notifications&email_token=AAAF6J6EQQF732JROTQ5O6DQ4TMM3A5CNFSM4KD6GYKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IESRRHQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAF6J35OJKFEQLQJ4NJUNTQ4TMM3ANCNFSM4KD6GYKA .

[Uzay-G]

I opened a pull request to begin this on image-sequencer.

[sashadev-sky]

@jywarren @Uzay-G i think what would be really awesome is if we could look into the option to open a PL repository containing just reusable template files that will pull into every repo. It will make things a lot easier. For ex., if we have a code of conduct change we just update the 1 file instead of 10 or so times across the organization’s repos.

I think Github provides documentation on doing this (sorry for not linking to it - on my phone).

Maybe I can create a GCI task especially for doing this? @jywarren Can be yours if I do @Uzay-G

[Uzay-G]

I'll look into this @sashadev-sky! Nice catch. :+1:

[Uzay-G]

Hey! I figured out how to do what @sashadev-sky suggested using https://help.github.com/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project. I made a repository with the default files we can use. Someone with permissions for Publiclab just needs to clone my repo through the organization and it should work.

I could also make/add a default SUPPORT.md file if that would be useful :+1:

[SidharthBansal]

There are multiple PRs here. May I know how many points you expect for each pr? Which task I should upload? If there are stale pr then kindly close them

[SidharthBansal]

I think 2 points for 2 prs. Please do similar changes to other repos too. We will give you points for this plots2/7141 at once

[Uzay-G]

This repo has all the templates. If the publiclab org clones it, then those templates will be expanded to every single PL repo. Could we do this?

[Uzay-G]

@jywarren @Uzay-G i think what would be really awesome is if we could look into the option to open a PL repository containing just reusable template files that will pull into every repo. It will make things a lot easier. For ex., if we have a code of conduct change we just update the 1 file instead of 10 or so times across the organization’s repos.

I think Github provides documentation on doing this (sorry for not linking to it - on my phone).

Maybe I can create a GCI task especially for doing this? @jywarren Can be yours if I do @Uzay-G

If we do it the way I mentioned above, we will only need to changes the templates in one place.