Is the project abandoned? Time to fork?

[Griffon26]

It doesn't look like anyone with commit access or access to the app in google play is active anymore. I've not received any reply on direct e-mails to gggard and timoberger either.

What do you guys think? Is it time to fork and upload a new version of the app to google play under a different name?

I would prefer not having to maintain this app myself though, so if anyone else feels inclined to do so please say so.

[LudovicRousseau]

The latest commit is https://github.com/gggard/AndroidCaldavSyncAdapater/commit/27e8a0f8495c92e0780d450bdf0c7cec77a03a55 from 20 Nov 2013.

Either the project is perfect and finished :-), or is it dead and unmaintained :-(

[gggard]

Dear all,

Sorry for this too long silence. I have no time anymore for this project unfortunately.

If someone want to take over I add him/her to the dev list in github and on Google play.

Gerald

[Griffon26]

If noone else steps up, then please add me. My e-mail address is in my profile. Will I also be able to pass it on to someone else later?

[gggard]

I will, thanks !

[eloo]

hey guys, i'm currently working on a fork of this app. You can download the latest version as binary from my github repository Eloo

[ervee]

Hi, looks like this project is forked A LOT :)

To my best knowledge the fork of @wildgarden and @ennswi (which is a fork of wildgarden's fork) have some commits and look active, but I don't see any releases on their Github pages...

@Eloo does have a binary release (YAY!), but doesn't look that active?

@Griffon26 stopped development in April 2014? And has no binary release :-/

But I think the main question here is:

• Who IS really active in taking this App to the future?
• Where (to which fork) should anyone go for a bug report (if there is ever a binary version we can test).
• The same for pull requests...
• If we find "the active" fork. Are all other forkees so kind to modify their readme's to point lost souls to that fork?

Ralf.

[gggard]

Dear all, I have on more tome for this project unfortunately, but I would like it continue to evolve as I believe it is very useful (I use it daily on several mobile clients).

I am open to promote on github and google play anyone who volonter as admin for both in order to accept github request and push new binaries on the play store.

Let me know who want to take over, I will more than happy that this project is alive again and I will help the transition as much as I can

Gerald

Le 17 février 2015 17:02:29 GMT+01:00, Ralf notifications@github.com a écrit :

Hi, looks like this project is forked A LOT :)

To my best knowledge the fork of @wildgarden and @ennswi (which is a fork of wildgarden's fork) have some commits and look active, but I don't see any releases on their Github pages...

@Eloo does have a binary release (YAY!), but doesn't look that active?

@Griffon26 stopped development in April 2014? And has no binary release :-/

But I think the main question here is:

• Who IS really active in taking this App to the future?
• Where (to which fork) should anyone go for a bug report (if there is ever a binary version we can test).
• The same for pull requests...
• If we find "the active" fork. Are all other forkees so kind to modify their readme's to point lost souls to that fork?

Ralf.

---

Reply to this email directly or view it on GitHub: https://github.com/gggard/AndroidCaldavSyncAdapater/issues/222#issuecomment-74692215

Envoyé de mon téléphone. Excusez la brièveté.

[ennswi]

Hi,

I want to continue this project. I also try to fix the issues, but in the Next 2 months i don't reale have so much time. If i find free time for fixing some issues, i'll do this. I'm trying this weekend to deploy a beta release in f-droid.

[ervee]

Hi @gggard , thank you for replying and willing to support a continuation of your fine project!

@ennswi, your fork looks promising, you have my support! If you want, I can test the App in a number of virtual x86 Android versions against an OwnCloud calendar or another CalDav server if needed. I could possibly even give you access to these VM's if needed and I find a way to do that securely. Edit: Are you also willing to share a plain binary via Github and (if mature enough) work with @gggard to update on Play store? If you want to stay away from Google, perhaps I can do this.

I hope more people will help with the bugs that will be logged. And with coding feature requests.

[ennswi]

Hi @ervee,

thanks for your help. It would be create if you can test the APP in other caldav Server.

I already have Owncloud Server and use the Server for all my events and other things. I post the github URL already in the f-droid forum, that they include the APP.

[wildgarden]

Dear all, I would still like to contribute to this project. However, during the next 3-4months I won't have much spare time. I'm fine with the decision that ennswi fork will stay the main active one. I will update my readme to reflect this. I use the app to sync to owncloud server, too. I think the code is mature enough and worth being published to other stores. @gggard Thank you for this fine piece of code!

[ervee]

Thank you @wildgarden for willing to change you readme. Makes other people's search for the most curren/active fork a bit less hard.

[ennswi]

hi, good news. the app is ready for testing. https://f-droid.org/repository/browse/?fdfilter=caldav&fdid=de.we.acaldavj

[eloo]

Nice to hear. But your link seems to be wrong. https://f-droid.org/repository/browse/?fdid=de.we.acaldav

So the project is now developed under your domain? Maybe i will contribute some more code if I got the time ;)

[Jentsch]

Hi *, I would like to contibute some code. Where should I place the pull request?

[gggard]

Hi nodiscc,

You can contribute by pull request to the master of this original repo, knowing that I try to find a maintener for this repo to merge the forks that are ahead like the @ennswi one.

If you like to become contributor to the project to do it directly, do not hesitate to raise your hand ;-)

Gérald

Le 23/02/2015 00:50, Jentsch a écrit :

Hi *, I would like to contibute some code. Where should I place the pull request?

— Reply to this email directly or view it on GitHub https://github.com/gggard/AndroidCaldavSyncAdapater/issues/222#issuecomment-75472962.

[ervee]

@gggard , it though we were moving to @ennswi's repo as the active one as it is so far ahead? Clearly (see also #231) you think different. I can imagine it is hard to let go, but @ennswi is still active in development of this App. I can imagine it is easier to move to his repo since he is also (willing to) building binaries and pushing it to stores.

Are you willing to reference @ennswi's repo in the Readme and in the Play store and assist him (or her?) in pushing bin's to Google Play?

[gggard]

Dear @ervee,

The problem here is to decide what is best for the project.

The beauty of opensource and the only way to make a project evolve is to welcome external contributors, not only because we are stronger together, but also because there is a lot of turn-over in the project and that's fully natural (I started some time ago, @timmoberger continue the work for a while and now you are willing to continue the effort, that's the way things are working), this turn-over of contributors has to be managed intelligently.

Now just step back for a moment and imagine the project in 1 month, 6 months or one year, you, @ennswi and others will certainly have found something more motivating (in their personal life or in open source projects, that's natural and the advantage of doing open source project as a hobby instead of being payed for that) and will gradually slow down the effort for it. What will happen ? Exactly this kind of discussion again, will we have a other redirection of project ? and then in 3 years ?

What about the users that are not aware of the way github is working (i.e. 99.99% of the Google play users of this app) ? How can they find they way amons several projects, several issues trackers, ...)

I have proposed to let to a group or individual the key of the trunk several times (i.e. the github project and the google play account), if you or @ennswi want, I do this today but I strongly believe that a "hard" fork is not the best option for the project for the reasons above.

Hope you will understand and share my view, do not hesitate to disagree !

Gérald

[ervee]

@gggard , I'm willing to help where possible. I hate the fact that I can't program a single line, so in that aspect I'm not of much help. But I can compile, test, report bugs, translate, etc.

Giving me access to your repo (or whatever repo) is not of much use. I can't approve pull requests because I'm no good at coding so I won't know what I'm approving :)

I think it depends a bit more on @ennswi . Is he willing to push his repo changes to this repo and take the key to this repo so people can submit bugs and pull requests here again? Or can you pull his changes to your repo just like that? If not, and you (@gggard) are not changing your Readme and Play store links, we will never have "the one place to be" for this project and people who search for it will get lost forever.

[gsnerf]

Just to put in my 2 cents :)

When a project can't be maintained by it's creator anymore and it still aims to go on, it should be transformed into an team project. That means: an own repository group with repository that is not tied to a single person but rather to the project itself. The owner should be a maintainer (who doesn't necessarily need to develop on its own). If the owner needs to change later on this can happen by simply changing the settings and ownership status of the project group rather than actually moving the repository from here to there.

Developers can then contribute and the current maintainer simply merges the pull requests into the main tree and makes sure there are regular releases. This then can go hand in hand with the forks current developers are using. The point is: do current developers agree to such a move? Are they willing to work in such a way?

I'd hate to see this project go away, simply because there is no agreement about how to proceed. This seems to be the only open project that is actually working in some way or another.

EDIT: There seem to also be DAVDroid of course.

[pafcioooo]

Is there possibility to pin this issue, so people stopped using this version? I took me quite a lot of time to find this thread and switch to aCalDav to solve a an error "uknown error".

[ervee]

IMHO you should switch to DAVdroid. Very active project, installable trough F-Droid and 1 App for Calendar and Contact Sync.

[eloo]

yep can recommend DAVdroid too

[pafcioooo]

@ervee @Eloo thanks a lot for suggestion, which I have followed:-)