-
Notifications
You must be signed in to change notification settings - Fork 14
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
Kickstarting development in our team #48
Comments
Hi Alexander, That's an amazing offer, thanks! IMHO there'd be two super useful starting points:
Those two points are somewhat related because type checkers need proper modules to function. I have an aborted attempt for adding flow types and modules in the same branch [2]. I ran out of time. [1] [2] |
After the general fixing and making the code base ready for further development, our priorities would be: Can you maybe create a github project? |
How long did you work on that branch and how much work left do you see in it (roughly in hours) ? |
@amenk I spent maybe 3 days full time on that branch.
Not sure what you mean. Is it https://help.github.com/articles/about-project-boards/ ? Happy to set that up and make you contributors if that's what you have in mind. |
Yes I mean the project board. I think the type script thing might be also something for a junior developer? Just have to find out how it works ... So s/he might be able to do that - with the main goal to bring the Firefox plugin forward, which is currently a show stopper.... |
I think it would be nice if you make me us a contributor ... would set up a board / roadmap then and we can discuss about the priorities. |
Hi,
we would like to assign one of our developers for improvement of the extension.
Can we start with that a fork? What should we know? I think it would be mostly frontend - I would compile a list of features (mostly those I reported).
I think you wanted to restructure the frontend? Should we first help with that?
The text was updated successfully, but these errors were encountered: