Questions

[moderakh]

The functionalities provided by this library seems to be very interesting.

Could you please kindly answer to my following questions?

1. I feel some of the functionalities of this library are really helpful and are missing from rxJava, (e.g., transformersorderedmergewith) I wonder if there is any plan for merging the features to rxJava? Is there any reason this hasn't been merged yet?
2. Do you have any track of who is currently using this library?
3. Is there a plan to move this from personal github scope to an apache project?

[davidmoten]

Thanks for your interest, here are some answers:

1. No plans for merge with RxJava simply because the API surface is already so huge. You'll find that the main committer David Karnok is pretty resistant to new stuff these days just to keep the review/testing/maintenance/documentation load down.
2. Sonatype stats indicate ~3000 downloads a month from Maven Central
3. Haven't considered that really. What do you think are the advantages?

Another note is that much of this repo's functionality has been migrated to http://github.com/davidmoten/rxjava2-extras for RxJava 2.x support .

[moderakh]

@davidmoten we are still on RxJava 1.x so I am more interested in rxjava-extras.

Where can I see the sonatype stats? is this available to public or only to the project owner?

I was thinking a non personal artifact group id (which right now is com.github.davidmoten) may make selling the idea of taking dependency on this library easier. (There are processes for reviewing and approving taking new dependencies.)

Thanks again

[davidmoten]

I viewed sonatype stats in my account. I don't think it's publicly visible.

I was thinking a non personal artifact group id (which right now is com.github.davidmoten) may make selling the idea of taking dependency on this library easier. (There are processes for reviewing and approving taking new dependencies.)

Perhaps. I've found that the groupId and artifactId are insignificant in importance compared to indicators like:

• recent activity on issues (discussion, fixes)
• recent commits
• recent releases
• static analysis like code coverage
• continuous integration
• decent documentation
• release to maven central (for jvm langs)

For example, after much stuffing around it turned out that a Microsoft owned Exchange Web Services java SDK was essentially dead despite media fanfare and claims of ongoing support. The big company name was worthless. Apache is a different matter of course but thought I'd mention it to contrast it with the personal repo.