> has this not been decided? if it has been decided, then why the complete > rework of ideas?
can you point me to where the ideas were previously discussed? On Sun, Jan 24, 2010 at 5:38 AM, Greg Milby <[email protected]> wrote: > i thought Branko and Justin were doing this? (The rest of us were voting - > at best)>??? > has this not been decided? if it has been decided, then why the complete > rework of ideas? > > ----------------------- > Visit My Sites! > www.syrbot.com | My Site > www.attackr.com | Latest Blog Posts > > > > On Sun, Jan 24, 2010 at 8:32 AM, Branko Vukelic <[email protected]> wrote: >> >> On Sun, Jan 24, 2010 at 1:10 PM, Angelo Gladding <[email protected]> >> wrote: >> >> Although I will probably inevitably end up sounding like a fascist, I >> >> don't think a public vote should be the principal decision-making >> >> mechanism in projects like this. It's better that everyone simply >> >> takes a look at the work-in-progress stuff and contribute their ideas. >> > >> >> We've actually just started working on this the other day. >> > >> > http://webpy.org/deployment?m=history >> >> With all due respect, Angleo, I'm starting to get a feeling you are >> trying to prove something here, which is not necessarily a >> constructive approach, and certainly doesn't leave a good impression. >> >> And just in case my gut feeling is correct, I will tell you this. You >> could have simply said "I think you guys are slow and/or don't know >> what you're doing. Look at how complete a solution I can provide in >> time it took you to just experiment with a few color schemes and some >> shitty snake graphic." I would have appreciated such a response better >> than "Here's some stats so go figure." Very rude. >> >> Also, throwing at us your own templates that are completely different >> to ours is a good way to show how things can be done differently, but >> it's not part of the process. It does not allow us to simply call diff >> on two versions and pinpoint the differences (at least with whatever >> tools we happen to be using right now), let alone merge your changes >> to what we are working on. >> >> Justin and I are looking for constructive contributions, as usually is >> the case with open(-source) projects. Please follow Ken's example, and >> ask Justin to let you have a look at what is currently being >> implemented, and use that as a starting point for further discussion. >> You can ask Justin directly for a link to latest implementations. I >> myself have made all my work available, and freely commentable, so, >> again, use that opportunity to express your views. I will take any >> kind of remark, even the utterly useless "I don't like this" in many >> of its guises, as long as it's made with honesty, and open-mindedness. >> >> With that said, we will of course, take into consideration all your >> suggestions, and implement whatever we see fit. Then you can review >> what is being done in a hopefully less conflicting manner. >> >> Best regards. >> >> >> > I don't understand why your mockup is far less complete than mine... >> > >> >> ...we all have real lives, so we couldn't get our schedules synced. >> > >> > Ahh the asynchronicity of unreal life. >> > >> > - - - >> > >> > (min)imalism — for the community's consideration. >> > >> > http://i.imgur.com/Eq5kN.png >> > >> > CHANGES >> > >> > Site Template >> > >> > * one snake, please — I personally like this one best >> > * transparent favicon and snake logo >> > * SEARCH >> > * first tab-index >> > * support for OpenSearch (see upper right of *my view* above) >> > * Goog custom search across webpy.org, launchpad & github >> > * `universal edit button` (see tooltip in *my view* above) >> > * one, obvious home link (doubles as hCard for the web.py organization) >> > * breadcrumbs will logically fit between top `web.py` and `<h1>` >> > * if any URIs actually descend multiple levels of hierarchy [???] >> > * HTML5 (i.e. <header>, <article>, <nav>, <footer>) >> > * document structure places `article` content before `nav`igational >> > elements >> > * simplified navigation >> > * changelog has nothing to do with "Getting" which leaves only >> > `Download` >> > * hence change of heading from `Get` to `Use` >> > * merge `download` into `install` >> > * move deployment information from `install` to `deploy` >> > * break setup into parts and merge with `deploy` and elsewhere >> > * `learn` section is more focused >> > * quote moved to footer revealing whitespace and collapsing header >> > * Aaron and Anand's info provided as hCards (as `vcard.agent`s of >> > web.py) >> > * Anand presented with <address> to designate *main author* >> > * table of contents >> > * `rel-license`d page under a CC0 [critical change – comments?] >> > * designed to formalize the Public Domain dedication universally >> > * syntax highlighting >> > * jQuery auto-inserts `back to top ↑` before each h2 >> > >> > About >> > http://webpy.org/about?template_root=/min >> > >> > * <title> reads only "web.py" >> > * single hAtom status feed entry represents most recent version >> > semantically >> > * hAtom to Atom transliteration provides feed (see *my view* above) >> > * Anand's hCard used heuristically to imply hAtom feed author >> > * semantically: Anand is an author/agent of web.py who posted version >> > 0.33 >> > * split testimonials into `project that use web.py` and `people that use >> > web.py` >> > * each contains an hCard — `org`s for projects and `people` for people >> > * began sourcing each quote >> > * linking to author's identity where possible >> > * overall sanitization of section >> > >> > Installation >> > http://webpy.org/installation?template_root=/min >> > >> > * content restructure and merge with >> > * terminal snippets are copy/pasteable >> > * CSS used to insert shell indicator >> > * trailing newline to ensure sending of entire sequence of commands >> > >> > History of Installation >> > http://webpy.org/installation?m=history&template_root=/min >> > >> > * hAtom feed >> > >> > Deployment >> > http://webpy.org/installation?template_root=/min >> > >> > * untouched merge.. >> > >> > TODO >> > >> > * align vertical rhythm to a baseline grid >> > * semantically connect change log feed to full change log history >> > * deal with translation clutter >> > * standardize table headers (i18n [???]) >> > >> > - - - >> > >> > Comments/suggestions/changes/feedback welcome. >> > >> > Shortcuts to preview it, use it and revert back to the default >> > template are on my user page http://webpy.org/user/AngeloGladding or >> > manully set your template root >> > http://webpy.org/account/preferences/template_preferences to `/min`. >> > >> > On Sat, Jan 23, 2010 at 3:13 PM, Branko Vukelic <[email protected]> >> > wrote: >> >> On Sat, Jan 23, 2010 at 11:40 PM, Angelo Gladding >> >> <[email protected]> wrote: >> >>> So it looks like you're really focusing on color. I imagined the >> >>> redesign would incorporate more discussion in the areas of information >> >>> architecture and content — semantics, typography, accessibility, >> >>> usability. >> >> >> >> As it should. I have some ideas about that as well, but since this >> >> started out a bit chaotic, we'll try to get this thing going, and >> >> change stuff as we go. >> >> >> >>> That said, I don't understand why your mockup is far less complete >> >>> than mine (regardless of perceived quality) given I spent a couple of >> >>> hours one evening (content modifications included), had my hands tied >> >>> to the existing HTML structure, and your redesign has been in the >> >>> pipeline for.. longer. >> >> >> >> So far, Anand's the only guy working on webpy.org. And we all have >> >> real lives, so we couldn't get our schedules synced. We've actually >> >> just started working on this the other day. >> >> >> >>> Now that I know about this feature of Infogami I feel a strong urge to >> >>> take a stab at a lower-level design but the last thing I want to do is >> >>> step on toes. Can we discuss some of the finer points of the redesign >> >>> in the open? >> >> >> >> Sure thing. I don't think anyone would mind. :) >> >> >> >> >> >> >> >> -- >> >> Branko Vukelić >> >> >> >> http://foxbunny.tumblr.com/ >> >> http://www.flickr.com/photos/16889...@n04/ >> >> http://www.twitter.com/foxbunny >> >> http://github.com/foxbunny >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups "web.py" group. >> >> To post to this group, send email to [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]. >> >> For more options, visit this group at >> >> http://groups.google.com/group/webpy?hl=en. >> >> >> >> >> > >> > >> > >> > -- >> > Angelo Gladding >> > [email protected] >> > http://angelo.gladding.name/ >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "web.py" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/webpy?hl=en. >> > >> > >> >> >> >> -- >> Branko Vukelić >> >> http://foxbunny.tumblr.com/ >> http://www.flickr.com/photos/16889...@n04/ >> http://www.twitter.com/foxbunny >> http://github.com/foxbunny >> >> -- >> You received this message because you are subscribed to the Google Groups >> "web.py" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/webpy?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/webpy?hl=en. > -- Angelo Gladding [email protected] http://angelo.gladding.name/ -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
