On Sat, Dec 10, 2011 at 8:19 PM, Jeffrey Van Voorst
<[email protected]> wrote:
> Hi,
>
> I have opened issue 666 to track my edits to the pyjs website + a
> branch as per DEVELOPER.RULES.  As mentioned in the issue, should I
> request a pull when I have substantial changes

 you should always be doing regular "git pulls", which will either
fast-forward or merge, as appropriate

> or just push them
> myself to master and revert when issues arise?

 git doesn't work that way.  if there's a conflict, it will tell you
to do a "git pull" before allowing you to "push".  other peoples'
changes will then get merged or fast-forwarded locally, and you will
have to do any conflict-resolution locally.

> One item, that was probably mentioned before, is in the FAQ, the pyjs
> wiki link for section "Ok - what's the <i>best</i> server-side web
> framework I should use?" points to the google page.

 tsk, tsk, that needs sorting.

>  This should point
> to the pyjs wiki if that is the one of choice.
>
> A second item, is I cannot use the pyjs mail application

 i'm happy to give you free rein to fix it.

> access to the mail from their client.  On the other hand, I am not
> sure what would be the problem (besides server speed) for using the
> standard ancient method (e.g. GNU Mailman) that many Linux systems
> projects use to list mail archives by thread, date, etc as just links
> (I know--ugly, boring, etc. but it actually works).

 well the main reason why i like lamson is because it stores archive
data in JSON format.  it was therefore pretty trivial to write a
jsonrpc service to read the archives.  any other mail system i would
have had to have written more code.

 l.

Reply via email to