Re: [libreplanet-discuss] [fossil-users] [OT] Who's interested in project management & collaboration tools? And...

[Thomas Harding]

On 07/08/2012 01:54, Miles Fidelman wrote:
> Hence the project :-)
>
> Seriously, this started with some work on distribution of military 
> operations orders - currently distributed largely as text and 
> attachments, by email - and asking if we could simplify handling of 
> follow-up messages by sending HTML+JavaScript messages that could 
> update themselves by pulling follow-up messages out of the mail stream 
> and applying changes.

Forces/NATO has ACP127 with an XML version of, and there is stuff to 
send such ACP127 format accross applications built on SGBD with large 
databases
Text/ACP127 attachments mainly distribute that orders in an (almost) 
human-readable form
having such a text/ACP127 plus XML/ACP127 as multipart allows to inject 
the last in any appliance

So, having such an xml+human readable ACP127-like format adapted to Free 
Software developpement project (through xslt) would do the drill, no 
matter the transport is (NNTP, SMTP, XMPP, SCP...). Adding multipart to 
e-g SLRN would be trivial, and you can authenticate too and/or use 
SSL+key pairs.

A good setup in case of SMTP would be use "submission" port (ISPs 
genarally blocks 25), thera are enough mailing-list possibilities to 
propagate :)

Also remember NNTP is perfect to propagate changes as you have "control" 
and "pairs" -- chained.

Ideally an automated NNTP client would pull a server as cron task (any 
number of persons in the project could host an INN), then push changes 
to a git through a middle-end (or integrated)

The "text editor" could be wsgi hosted (web) or standalone

> It looks like HTML5, the latest generation of browsers, and a few 
> work-arounds (use a proxy to work through cross-origin restrictions), 
> make it all feasible.  Seems like its now time to make a run at it.
>
> > So, are you thinking of this on laptops or on mobile devices
> > or both?
> Both.  Goal is to make everything run in a browser, with distribution 
> via email, and updates/synchronization via either XMPP or Atom.  
> Biggest stumbling blocks are saving files locally, particularly on iOS 
> where there's no direct access to the file system.  Seeing how much we 
> can do with browser storage. Alternative is to use a local server, 
> access files via both DAV and the file system (again, an issue on iOS).
who cares on iOS here ? a wsgi web host is enough for that piece of shit.

HTH,
TSFH