Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidelines for contributing #68

Open
Sciss opened this issue Dec 1, 2017 · 9 comments
Open

Guidelines for contributing #68

Sciss opened this issue Dec 1, 2017 · 9 comments

Comments

@Sciss
Copy link
Contributor

Sciss commented Dec 1, 2017

Should a CONTRIBUTING.md guide be added? What is the policy now that the project is "community maintained". Is there still a CLA that needs to be signed, etc.?

And what would be the forum to discuss; should there be dev gitter room or so?

@benhutchison
Copy link
Contributor

Some answers:

  • From a look at the CLA I think its intended to still apply, but scala community modules are a grey area not explicitly documented
  • I'd prefer not to add a gitter room, can we just use github issues for comms..?
  • I still see scala swing maintenance as a legacy support activity myself, so contributing guide is not my priority, but I welcome anything you might offer

@Sciss
Copy link
Contributor Author

Sciss commented Feb 15, 2018

Ok. I agree with not having a Gitter, nobody intends to do any 'support' of any sorts. I mainly wondered if there are legal hurdles to submitting pull requests, but if nobody objects, we can just handle it informally.

@ashawley
Copy link
Member

Slightly off-topic, but I wrote a a contributor guide on the scala-xml wiki. Feel free to steal any or all of it..

https://github.com/scala/scala-xml/wiki/Contributor-guide

@SethTisue
Copy link
Member

about the CLA, previously: #51 (comment) so I think the status quo is that contributors are supposed to sign the CLA but we don't have automation for it in the module repos

@benhutchison
Copy link
Contributor

Thanks @ashawley I'll try to copy-n-modify your guide as time permits

@Sciss
Copy link
Contributor Author

Sciss commented Aug 15, 2023

Just a heads up – I have been watching GitHub very critically since they were bought by Microsoft, and all the changes introduced since then. Their newest shtick is threatening me into loosing access if I do not install a smart phone application for 2FA. I have no intention to install any phone applications nor to give them my phone number. So I am currently undoing the entanglement of my GH account with other organisations, and will slowly be migrating the repositories I'm involved in to codeberg.org . I don't really know what that means for "maintaining scala-swing", a project I'm still using and I'm still interested in. So for now, FYI.

@SethTisue
Copy link
Member

Although they're now requiring 2FA, and although I personally use a phone app (Google Authenticator) for that, I'd be surprised if there were really only smartphone options? Can't you use the desktop version of e.g. 1Password or something?

@SethTisue
Copy link
Member

these look relevant: https://github.com/orgs/community/discussions/49715, https://github.com/orgs/community/discussions/23490

@Sciss
Copy link
Contributor Author

Sciss commented Aug 15, 2023

I managed with KeePassXC now. Nevertheless will minimise my GH presence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants