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

Clojure support #572

Closed
greysteil opened this issue Jul 4, 2018 · 19 comments
Closed

Clojure support #572

greysteil opened this issue Jul 4, 2018 · 19 comments
Labels
Stale T: new-ecosystem Requests for new ecosystems/languages

Comments

@greysteil
Copy link
Contributor

Originally suggested in dependabot/feedback#76.

@camdez
Copy link

camdez commented Oct 22, 2019

What's the latest here? Just looking for someone to do the work, or is something in flight? Happy to help!

@feelepxyz feelepxyz added the T: feature-request Requests for new features label Oct 23, 2019
@devn
Copy link

devn commented Jul 1, 2020

Same, I'm new to dependabot, but I am happy to help in any way I can.

@infin8x infin8x added T: new-ecosystem Requests for new ecosystems/languages and removed T: feature-request Requests for new features labels Jul 2, 2020
@alexisvincent
Copy link

What is the process to get support for Clojure?

@steffan-westcott
Copy link

Congratulations to @0tza for getting some funding from Clojurists Together 😀 I hope the situation outlined in the post above improves and community contributions for Clojure support will be accepted in the near future.

@greysteil
Copy link
Contributor Author

Cc @asciimike @hmarr ☝️

@asciimike
Copy link
Contributor

Congrats on the funding, and thanks to the folks who picked Dependabot as an area of investment. We're glad to see the community invest in security!

As for the above, as stated, the main issue has been that we lack the domain expertise to support the full breadth of contributed ecosystems. We have been working with another popular ecosystem on a closer partnership experience where they can provide that level of support, and would consider a similar relationship with the Clojure community. At a minimum, we are asking for two folks who will commit to being active in this repo if/when Clojure questions come up (we will likely tag you); otherwise, we don't think we can provide an acceptable level of support for devs when they have questions.

@danielcompton
Copy link

Hi @asciimike! I’m a recent ex-Hubber, admin for the Clojure community Maven repo Clojars, and the secretary of Clojurists Together which funded @0tza for this work. I’m happy to help on providing a close relationship with GitHub here 😀

@asciimike
Copy link
Contributor

@danielcompton @0tza I see that the project is listed as starting 1 Nov 2021; how firm is that date? We're starting to do quarterly planning and I want to get a rough idea of when we should start talking about this in more depth.

@tobias
Copy link

tobias commented Sep 9, 2021

Hello @asciimike. I also am an admin for Clojars, the Clojure community Maven repository. I would be happy to provide a second set of eyes on any Clojure (& Clojure dependency ecosystem) questions.

@danielcompton
Copy link

I see that the project is listed as starting 1 Nov 2021; how firm is that date? We're starting to do quarterly planning and I want to get a rough idea of when we should start talking about this in more depth.

What kind of timing works best for you? The paid work was planned to be started in November, but we can also do development/prep work/coordination/etc. before then?

@asciimike
Copy link
Contributor

@danielcompton I think Nov 1 is actually pretty good as we should be wrapping up one of our larger currently-in-flight projects by then and can focus on new ecosystems. I'll set myself a reminder to ping this thread in mid-October to pick this up again.

@RutledgePaulV
Copy link

RutledgePaulV commented Oct 27, 2021

Hey all, is November still in the cards for this? I'm trying to balance timing of this feature versus rolling our own solution(s). Thanks and let us know if there's something we can do to assist.

@0tza
Copy link

0tza commented Oct 28, 2021

Hi! Seems like my schedule is clearing out and this is starting 1st Nov as expected. Happy to see all the interest and assist offers, I'll try to include everyone in the conversations.

@gphilipp
Copy link

Hi @0tza, sounds like you should have started the work by now 🤞. If there are conversations happening, where can we find them and contribute?

@0tza
Copy link

0tza commented Dec 6, 2021

I have started to move all the conversations to https://clojurians.slack.com/archives/C02PZRZPC4R
See you all there 👋🏽

@exvuma
Copy link

exvuma commented Feb 2, 2022

@0tza if we don't have access to that workspace how should we request access?

@0tza
Copy link

0tza commented Feb 3, 2022

@0tza if we don't have access to that workspace how should we request access?

That's a public channel on clojurians slack. it should be open to anyone.

Copy link
Contributor

👋 This issue has been marked as stale because it has been open for 2 years with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the Keep label to hold stale off permanently, or do nothing. If you do nothing, this issue will be closed eventually by the stale bot. Please see CONTRIBUTING.md for more policy details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale T: new-ecosystem Requests for new ecosystems/languages
Projects
Status: Done
Development

No branches or pull requests