From: Ashton Kemerling <ashtonkemerling@gmail.com>
To: David Wagle <david.wagle@gmail.com>
Cc: David Masterson <dsmasterson@gmail.com>,
emacs-orgmode@gnu.org,
Ashton Kemerling <ashtonkemerling@gmail.com>
Subject: Re: Some thoughts on MobileOrg and its development ....
Date: Tue, 12 Aug 2014 20:23:44 -0600 [thread overview]
Message-ID: <53eacc31.8649320a.5dd1.084d@mx.google.com> (raw)
In-Reply-To: <CAJdTJyMhJ1AxMnN9tAPM-eZMj6vCCG66Bvo8hP+WsxzGXRYxHA@mail.gmail.com> (David Wagle's message of "Tue, 12 Aug 2014 20:47:37 -0500")
David Wagle <david.wagle@gmail.com> writes:
> What's involved in 'rebooting' the project? Are the various owners of
> the iPhone and Android packages on this list?
>
> I'm not a coder at all, but I've administratively managed software
> projects before. I'm more than happy to do what I know how to do --
> which is mostly send out emails asking people if they can help do stuff?
>
> On Tue, Aug 12, 2014 at 8:07 PM, Ashton Kemerling
> <ashtonkemerling@gmail.com> wrote:
>
> I did some digging into that a few months ago. While I'm not an
> experienced iOS dev, I flailed about for a few weeks trying to add
> deadline parsing and failed miserably.
>
> I'm fairly convinced that most of the code is either super platform
> specific or in need of replacing with easier to maintain & test
> components.
>
>
> --
> Ashton Kemerling
>
>
>
Honestly, I don't know exactly what would be involved, I'm not
experienced in mobile and I don't have anywhere near the spare bandwidth
to be anything other than a secondary contributor. I do suspect that a
lot of existing code would be thrown away in a combined approach due to
the massive semantic and structural differences between native code and
HTML/JS/CSS.
I can say for certain that we would have to figure out the handoff of
various credentials from the old maintainers (who I am assuming would
not like to continue being maintainers) for the respective app-stores
and Dropbox tokens.
--
Ashton Kemerling
next prev parent reply other threads:[~2014-08-13 2:24 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 [this message]
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
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=53eacc31.8649320a.5dd1.084d@mx.google.com \
--to=ashtonkemerling@gmail.com \
--cc=david.wagle@gmail.com \
--cc=dsmasterson@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).