RS needs a community of maintainers

[Stéphane NICOLAS]

It's been over 2 years now that RS is out, freely on github.

It started with a very good idea of a couple of colleagues at OCTO : Maxence Walbrou, Jerome Van Der Linden, Mathieu Hausherr. When I joined their team, I took the development of "ze content provider" in charge, created a lib and redesigned it, opened it, named it RoboSpice and industrialized it with the assistance and guidance of Jerome.

Then we have all been pushing it even further, far further. It is today a powerful, feature rich, widely used (25+ millions devices) and well known open source lib. I honestly think it rivals Google Volley and its design is better, Ricardo Ciovatti played a major role in that, he contributed from the very beginning with me and Jerome. Then other devs contributed more than 300 issues and PRs, we have more than 250 tests, continuous builds, frequent releases and a fulfilling relation with the community of RS users.

Nevertheless, personally, I feel like I appreciate a more important degree of freedom, and maintaining RS is a good job, taking some good energy that I also like to deploy in other areas. I feel like it's not the role of the 3 of us to maintain RS alone.

In some extent, if this lib belongs to everyone of us, then we can share the responsibilities that it brings within.

So, I would like to invite the RS community to take more place in the maintenance of RS. This essentially means volunteering for coding, managing github issues, reviewing and merging PRs, taking in charge the CI, answering questions on the Google group or stack over flow RS section, keeping up the wiki effort and constantly targeting quality of software craftsmanship.

I dream of a more collective adventure where others can take the lead, and enjoy creating the future of RS.

Thanks in advance and for all we did up to now,
Stéphane

[Nikola Keskinov]

Hi Stephane,

I believe this is the proper place for "thank you" messages, and I would like to express my gratitude of having such a fine product open sourced and maintained.

Although I try to be just an API user and have not investigated the code too much, I am interested in volunteering as a maintainer. However, some details and guidance on that would of course be needed by the current team. I am relatively new both to Android development and active participation to open source, but I feel like this is the minimum effort that you still need to do, as the core developers that led the project this far:

• Define a roadmap for future development
• Create a "Want to contribute?" introduction page, including way of working for contributors (where to commit, how/when to update tests and documentation...).
• Create some technical in-depth documentation, at least basically explaining the tooling and plumbing that the project uses.

I believe that this would help RoboSpice users to feel more like part of the team, instead of bug-reporters and quick-fixers :)

Thanks,

Nikola

[Stéphane NICOLAS]

Can I have your github account ?

Thanks for these ideas, I am prefectly fine with all this. If some other devs see a NO-GO somewhere, please say it quickly.

S.

--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "RoboSpice".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse robospice+...@googlegroups.com.
Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.

[Adam Stroud]

I agree with Nikola. I am willing to help, I just need some guidance on where to help.

Adam

[Stéphane NICOLAS]

Hi Adam,

thx for offering. Maybe the simplest way would be to synchronize with Nikola about the things he mentionned on this thread.

There is also an open issue on which Nikola and Riccardo wanted to contribute, sync with them to collaborate : 

https://github.com/stephanenicolas/robospice/issues/265

Stéphane

--

[Colin Lee]

Hi Stephane,

I appreciate the fine work that has been done so far on Robospice and would like to see it integrated with the latest reactive programming concepts. I won't pretend to be a seasoned API vet. I jumped from DevOps automation to Android development not that long ago.

I'd be interested in a volunteer role helping with the RxJava integration for Robospice and Retrofit. I believe reactive programming will become the new best practice. This will remain the case even if Android development begins to migrate to a newer language like Kotlin or Scala.

Colin

[Adam Stroud]

Is RxJava support on the roadmap for RS? If so, I would also be interested in helping out here. I am still new to RxJava, but often get frustrated with the "callback hell" I find myself in when using RS. My reason for looking into RxJava was to help alleviate that pain when using RS with dependent requests.

Adam

Colin Lee wrote:

--
Vous recevez ce message, car vous êtes abonné à un sujet dans le

groupe Google Groupes "RoboSpice".

Pour vous désabonner de ce sujet, visitez le site
https://groups.google.com/d/topic/robospice/bM0B10zWS5k/unsubscribe.
Pour vous désabonner de ce groupe et de tous ses sujets, envoyez un

e-mail à l'adresse robospice+...@googlegroups.com

<mailto:robospice+...@googlegroups.com>.

[Stéphane NICOLAS]

Hi Adam and Colin,

there is an open ticket on GH waiting for volunteers to take it : 

https://github.com/stephanenicolas/robospice/issues/323

Please, please, don't wait for anyone else and create this module the way you would like to use it. :)

Go ahead, that would be a very nice feature. I tried to get into RxJava but didn't really have time till now to use it, so, really go ahead and submit a nice PR.

Stéphane

--

Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "RoboSpice".

Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse robospice+...@googlegroups.com.

[Julián Suárez]

Hi everyone, 

Again I would like to thank you for all the work you have done with this library, it has a great design and it fits the best practices for networking on android strictly which is a very good thing.

I used DataDroid before which uses a very similar concept but sadly DataDroid was deprecated, so I had to switch to RoboSpice and I really want to help it grow.

I would like to help on porting the library to gradle which is going to be the standard going forward. I've already sent a PR to use the samples with gradle. I would also like to help on the orm-lite-content-provider extension.

[Stéphane NICOLAS]

You are more than welcome inside the team Julian.

Ormlite content provider extension needs a maintainer and the switch to gradle would interest too. Do you wanna submit a PR for this, then we review it in team and then I will add you to RS contributors and will met you merge it in.

Wdyt ?

Stéphane

[Julián Suárez]

That sounds great, I'll start with the gradle stuff and send PR when I'm done, very glad to help

[Stéphane NICOLAS]

Fine Julian, but I think it will be hard to get all the stuff we have with maven turned into gradle. Let's see. Thx 

[Mykolaj]

Hello, Stephane!
Thank you and your team and all the community for RoboSpice. It is awesome as they say. And i use it in every project i have.
Recently a Retrofit library was updated to 2.0 as you may know already. And me myself and some of others on Stackoverflow were looking for a way to use RoboSpice with this new Retrofit version. So, i've made a new module called Robospice-retrofit2, and have it tested. Now i'd like to integrate it into the main code base, and make a snapshot. How can i do that?

The module's code can be founded here: https://github.com/mykolaj/robospice
Also there is a sample app: https://github.com/mykolaj/Robospice-Retrofi2-sample