Great to hear it.
I guess one way to minimise your risk would be to work with a select few on building the sync engine plugin api, and then allow people to build their own engine independently. That way you keep the rights to NR with the IP for the killer features you've developed, but others can contribute under whatever revenue model they feel happy with - like the Tasker/Locale model. That way everyone wins.
--
You received this message because you are subscribed to the Google Groups "NewsRob User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to newsrob+u...@googlegroups.com.
To post to this group, send email to new...@googlegroups.com.
Visit this group at http://groups.google.com/group/newsrob?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
So, for the trial period, the app would remain closed source with contributing developers involved, with a promise to roll back contributed changes if an OSS approach is not taken?
In the event of a rollback, I'm sure there will be some interest in going another route if you decide not to continue NR Mariano. I can certainly see not using any NR code in any other project, that's fair, but enforcing "If we rollback after 3 months you cannot use any of what you've gathered during that time. This includes what you learn from code or the messages, technical and commercial." could prove problematic.
Mark's suggestion of separating out new sync targets might be useful in such a case. The "internal" team would produce an interface, that would be published under an OSS license, just the interface class itself, not any implementing code. Then any work done on that side of the fence could remain OSS in the event of a rollback and allow another project to implement the other side of the interface should you decide NR will not continue under that plan.
--
Can I just say that this is a brave step, but I really appreciate it, Mariano, as losing Newsrob would massively diminish my smartphone experience. Thanks for doing it!
What I don't want is to find NewsRob code someplace else after the rollback. I probably not be able to enforce it anyway, but I'd like to have clear language so that there is no doubt what is meant. Having said that, I agree that this could be problematic.
So for the trial period and a possible rollback what I don't want is code or anything else from the repository to be used outside of NewsRob. I also may want to discuss commercials etc. on the mailing list and would like to keep that close to my chest.Lastly I don't want to go through each file in the repository and see if it can be exposed.So maybe (a) I shouldn't talk about commercials or anything else in that respect for the time being. (b) Give access to the repository just person by person, so that when something is uncovered which I have taken out, it may still be contained. (c) Change the following sentence from:"If we rollback after 3 months you cannot use any of what you've gathered during that time. This includes what you learn from code or the messages, technical and commercial."to:"If we rollback after 3 months you cannot use any of what has been in the repository before the trial."We should be good then, correct?
Hopefully we can get things going. We have just over a month. :) I know you're a busy guy Mariano, no complaints here
Hello Mariano. I'm a professional Android develop (I work for HTC on the backup application for the HTC One) and a very enthusiastic user of NewRob, and would love to contribute to its future. If you are still looking for people to participate in the pilot project, please let me know.-wilhelm
--
Btw, let me know when you have something you need testing. I won't join the Dev list, but happy to put in some QA hours as appropriate, to help shake out those int/long overflow errors. ;-)
Because I'm not an android developer and don't have any time to contribute code at the moment.... :-(
We will also be talking and exchanging ideas, discussing what backends to use etc. ;)
On Wed, May 29, 2013 at 9:05 AM, Mark Otway <ma...@otway.com> wrote:
Because I'm not an android developer and don't have any time to contribute code at the moment.... :-(
On 29 May 2013 07:55, "Mariano Kamp" <marian...@gmail.com> wrote:
Sounds good, but why don't you want to join the developer list?
On Wed, May 29, 2013 at 7:24 AM, Mark Otway <ma...@otway.com> wrote:
Btw, let me know when you have something you need testing. I won't join the Dev list, but happy to put in some QA hours as appropriate, to help shake out those int/long overflow errors. ;-)
On 29 May 2013 06:08, "Mariano Kamp" <marian...@gmail.com> wrote:
Yes, Wilhelm.That sounds great. We would be happy to have you.Could you please confirm that you are ok with the "rules" I outlined here? http://groups.google.com/group/newsrob/browse_thread/thread/4859ebe498040e53/3299a1db0115576d?hl=en_US#3299a1db0115576d
On Tuesday, May 28, 2013, Wilhelm Fitzpatrick wrote:
Hello Mariano. I'm a professional Android develop (I work for HTC on the backup application for the HTC One) and a very enthusiastic user of NewRob, and would love to contribute to its future. If you are still looking for people to participate in the pilot project, please let me know.-wilhelm--
You received this message because you are subscribed to the Google Groups "NewsRob User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to newsrob+unsubscribe@googlegroups.com.
Although I am not an Android dev, I am willing to assist with testing if there are any opportunities.
Andrew