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

Are mature Java projects concurrent? #24

Open
fernandocastor opened this issue May 3, 2013 · 0 comments
Open

Are mature Java projects concurrent? #24

fernandocastor opened this issue May 3, 2013 · 0 comments
Assignees

Comments

@fernandocastor
Copy link
Member

This is the first issue specifically related to source code that must account for the actual language in which the project is implemented. To determine whether mature Java projects are concurrent, first we must define what is means to be concurrent and then we have to define what is a mature project. The first issue is easy: any project that employs at least one construct, either from the language or from a library (e.g., one synchronized block, one AtomicInteger, etc.) is considered to be concurrent.

As for maturity. we have to establish a proxy or a group of proxies for project maturity. Followers? # of commits? # of commits/day? # of forks? # of watchers? Activity of the contributors? Frequency of pull requests? # of lines of code?Age? Minimum thresholds for a number of criteria?

A related question that we must answer is what concurrent programming constructs do these projects use? How intensively?

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

1 participant