From: Alexis <flexibeast@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Some thoughts on MobileOrg and its development ....
Date: Thu, 14 Aug 2014 10:54:17 +1000 [thread overview]
Message-ID: <87a977yiio.fsf@gmail.com> (raw)
In-Reply-To: <878umsuiz1.fsf@gnusosa.net>
Carlos Sosa writes:
> There's a difference feature wise between MobileOrgNG[1] and
> MobileOrg-Android[2], which I believe should be merged into one project.
> For instance, I don't know of MobileOrgNG having a SSH synchronizer
> which many people make use of, including me, but with that said,
> MobileOrgNG has a far greater and friendlier interface.
>
> I would suggest merging both projects for the sake of a better user
> experience.
Well, again, the fundamental problem here is that none of these three
MobileOrg* projects are being actively worked on / maintained. The last
commit to MobileOrgNG was on 13 February last year (and is "149 commits
ahead, 863 commits behind" MobileOrg-Android). And despite
not-insignificant discussion here on the Org mailing list about the
MobileOrg* projects over the last few months, none of the lead devs for
any of these projects has chimed in, which suggests work on the Org
ecosystem is a very low priority for them right now. So it seems to me
that the likelihood of getting the two projects to work on a merge
process is similarly very low.
It's certainly true that someone could create a third Android-specific
version of MobileOrg that combines what they feel to be the best of both
Android apps. However, assuming that new app took off, we would still
have two different implementations on two different platforms where
fixes and improvements to code and documentation on one platform
wouldn't be immediately useful and/or appropriate for the other
platform. (Not to mention there'd still not be even theoretical support
for platforms other than iOS and Android.)
From a purely selfish point of view, as an Android user, a new Android
app combining MobileOrg-Android and MobileOrgNG would probably meet my
needs in the short term. In the medium to long term, however, i'm not
yet convinced that it would make the Org-on-mobile-devices situation
much more sustainably active than it is now.
Alexis.
next prev parent reply other threads:[~2014-08-14 1:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 0:56 Some thoughts on MobileOrg and its development Alexis
2014-08-09 4:13 ` Xebar Saram
2014-08-09 4:22 ` David Masterson
2014-08-13 1:07 ` Ashton Kemerling
2014-08-13 1:47 ` David Wagle
2014-08-13 2:23 ` Ashton Kemerling
2014-08-13 2:45 ` Alexis
2014-08-13 4:04 ` Ashton Kemerling
2014-08-13 8:10 ` Jacek Generowicz
2014-08-13 22:23 ` Carlos Sosa
2014-08-14 0:54 ` Alexis [this message]
2014-08-13 2:59 ` Alexis
2014-08-09 7:53 ` Jacek Generowicz
2014-08-14 1:47 ` Sean Escriva
2014-08-14 2:10 ` Ashton Kemerling
2014-08-14 10:17 ` Jacek Generowicz
2014-08-14 12:17 ` Henning Weiss
2014-08-14 13:07 ` Eric Abrahamsen
2014-08-14 13:36 ` Jorge A. Alfaro-Murillo
2014-08-14 15:29 ` Xebar Saram
2014-08-18 7:20 ` Samuel Loury
2014-09-10 19:39 ` Samuel Loury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a977yiio.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).