Hi! How can I contribute to Compose? Is there a pu...
# composev
voddan
06/11/2019, 10:44 AMHi! How can I contribute to Compose? Is there a public issue tracker where I could take some tasks from?
f
Fudge
06/11/2019, 10:50 AMTopic
Project page: https://developer.android.com/jetpack/compose, Issue tracker: https://issuetracker.google.com/issues?q=componentid:612128
v
voddan
06/11/2019, 11:10 AM@Fudge so those are external bugs, I suppose. But to contribute I would have to have a task and a general understanding of where the project is going. Can this be made publicly accessible?
b
Blundell
06/11/2019, 11:54 AMno, from my understanding: for that you would need to join Google đ
g
Gil Goldzweig
06/11/2019, 12:23 PM@Blundell Sure, sign me in
đ 1
l
Leland Richardson [G]
06/11/2019, 2:31 PM@voddan we donât have a great set of âgood first taskâ issues for contributors to hop in on yet. Compiling such a list is something weâve discussed but we havenât been able to do this yet.
One way to start (just spitballing here) could be to look at some of the tests weâve written for some components and add more covering more use cases.
Iâve done this in the past for one or two other projects, and sometimes in stages this early, you can find some bugs just doing that (that might not even have an issue created yet) and you can fix them while youâre at it! (Though depending on the bug it might be wise to reach out to the author and make sure itâs not intentional).
This is obviously sub-par to having a ready to go list of beginner tasks, which I very much want us to do, but this can also be very helpful and doesnât require all the context. Can really help improve the long term health of the project as well!
Leland Richardson [G]
06/11/2019, 2:31 PMAlso, weâve talked about compiling a roadmap or something but still discussing that. Not sure how soon something like that will happen
v
voddan
06/11/2019, 2:55 PM@Leland Richardson [G] awesome, thank you! A roadmap would be greatly appreciated, but even without it what you described is a very good suggestion.
l
Leland Richardson [G]
06/11/2019, 3:07 PMđ
r
Ryan Mentley
06/11/2019, 10:59 PMit's probably also a good idea in some cases to check if design changes are expected (semantics, for instance, is currently being restructured)
v
voddan
06/12/2019, 1:19 PMIs there a quick way to know what is going to change besides asking in this Slack?
l
Leland Richardson [G]
06/12/2019, 2:54 PMnot really - we donât even know what is going to change! đ These types of things are evolving daily
Leland Richardson [G]
06/12/2019, 2:54 PMonce we know, we could perhaps put that information somewhere - but afaik no attempt to do that has been made