random/unordered items for review/thought

[C Anthony Risinger]

i fell off the grid a bit this weekend ... moving all my junk to a new
home ~2 miles away. right now, i'm [legitimately :-] leeching off of
my neighbors/friends wifi, with my own fatty-mac-daddy pipe relinked
on Tuesday.

bigger, nicer, closer to work/school/*, and best of all ... *cheaper*!
most excellent.

i'm now responding to a couple things i starred along the way ... but
here are some others random/unordered items from my ongoing list
(start new thread if you want to discuss further!):

- rename to pyjs, drop pyjamas
done! yay that was easy

- autobuild website
probably not relevant anymore if using jekyll/github tools

- eventually drop pyjd, rename to pyjs-runtime-*/pyjs-native/pyjs-direct/???
this needs discussion, pyjd is confusing and awkward IMO ... "desktop?
don't all browsers run on the desktop?" this should be named something
more accurate. note: i am not suggeting pyjd be eliminated, quite the
opposite ... i want to promote it properly, and focus on the primaries
while ultimately seeking unification (the firebreath stuff?).

- donations are puiblic visible, used for major features
this could possible be done via bitcoin or similar, but i'd like
donations to be setup in a way that's transparent, and open to anyone.
ATM, thanks to github/google groups, my own server is mostly free,
and i don't think it's very fair (or even true at this point) to claim
"server costs" or the like ... i'd rather it be a like a chest 'o
booty, where any 'ol dog could have a slice.

- cut ie6 (stop devel)
for the most part this is effective immediately. no steps will be
taken to actively break it, but no steps will be taken to ensure it's
continued success. IE6 is dead ... http://www.ie6countdown.com/ ...
USA and others are less than 1%, Americas/Europe not more than 2%, and
worldwide is falling below 7%. if we cut out China there would almost
be no user's left at all. we do not -- and reasonably cannot --
special case other "niche" browsers; IE6 is no different. peace out!

- fix distribution (pypi, release, separate)
ensure the various ways pyjs is distributed works, and works well.
releases should be actual tarballs, not just git tags. much of this
will be addressed by "pjswaf" -- a pyjs+waf build tool tailored to our
needs -- as i will pick this back up and merge once some other issues
are resolved. in short, there are like 30 things in the top-level,
and that sickens me.

- buildsystem (remove constraints/hardcodings)
somewhat related to the above; to many places are hard-coded or
pointlessly generated. there is a good chance most of this will be
eliminated when i merge the waf tool. i'm a firm believer in
"portable apps", and pyjs will be capable of running standalone or
system installed, with no special provisions for either.

- newbification!
this is a giant black hole of issues, ideas, and the like. mostly
related to docs, presentation, highlect flow/conspet charts, etc etc
etc etc etc ... some other day ;-)

- fix devel rules
this was briefed elsewhere, but DEVELOPER.RULES must be either
cleaned/corrected, or dropped, with the expectations spelled out in
more well-known places (i've never seen that file until i came here,
and have never seen it elsewhere).

- migrate issues
repair any dangling this-and-thats

- remove crazy number of branches
this was sortof already done, but the original git repo had ~15-20
dead, temporary, or ??? branches (even some that were mine that i
explicitly removed, somehow reappeared?!?!). this won't happen moving
forward, and is easily avoidable.

- analytics account
pyjs.org is a real google apps account now, and creating an analytics
account is very simple from there -- should be ready within the next
week. while i can't open the doors to everyone, any information
contained is community knowledge, and all statistics/etc will be made
available upon request, interval, or through integrations (website,
etc).

- management roles/duties (apply/delegate?)
i briefed this in the past, but as pyjs.org expands into new avenues
of reach (twitter, et al) we'll need people or teams to "own" the
accounts and interactions thereto. ideas are welcome here. Peter
Bittner has mentioned styling the twitter account to me (i'll get you
those details shortly!), but there are others, particularly the
Google+ page, with more to come. a list is being aggregated ... more
on this in future.

- remove the "humor" from everything
uhm, this is pretty self-explanatory, but many of our docs, code, and
publicly visible information is chock-full of useless and often
long-winded tangents that contribute nothing. to-be-ZAPPED.

- follow the tools we use (uwsgi, github, linode, etc)
let the folks whose backs we stand on know we appreciate their work.

--

C Anthony