Anybody interested? Begin forwarded message:
> From: Jesse Noller <jnol...@gmail.com> > Date: November 28, 2011 8:54:38 AM CST > To: PSF-Members <psf-memb...@python.org>, pydotorg <pydot...@python.org> > Subject: [PSF-Members] Python.org redesign RFP: Request for Comments > > Dear Members/Pydotorg staff: > > Attached to this email, and below this message (.rst format) you will find a > draft of a RFP (request for proposals) for the redesign/overhaul of the > Python.org website and properties. This has been in the works/being discussed > on the board level for some time, with input from a variety of parties. > > The intention is to issue this RFP to the community/public after a two week > request for comments, starting today (November 28th, 2011) and ending Monday, > December 5th 2011. > > Comments can be sent to: psf-redes...@python.org > > Notes on comments: > > - Comments are collected by the committee/team, and will not be openly > discussed. The committee and team will not reply to any comments prior to the > deadline for comments. > > - Once the RFC is completed, the board and committee will take into account > comments and modify the RFP as required. Once this draft is completed, the > PSF board will vote on the final version of the RFP, again taking comments > into account. > > I look forward to hearing from all of the volunteers and members we have - > I'm very excited about this project, and I am looking forward to what it will > bring. > > Thank you. > > Jesse Noller > Directory, Python Software Foundation > jnol...@python.org > > ============= RFP Follows ============= > > > > Request for Proposal > ******************** > > > Summary > ======= > > The Python Software Foundation (PSF) is accepting proposals for > architecture, design and development of the primary web site for the > Python programming language, python.org. > > The existing Python web site was originally discussed at PyCon 2003. > The site was then designed, developed and deployed in Spring 2006. The > site is currently maintained by a team of community volunteers using a > custom suite of tools. To get a better understanding of the current > system, you can review the redesign proposal, slideshow and system > usage guide by checking out the following code through subversion: > > svn co https://svn.python.org/www/trunk/beta.python.org/resources/docs/ > beta-python-docs > > Python has grown significantly in the last few years, both in terms of > audience and the amount of topical information about it. This > (welcome) abundance of information has outgrown the current website's > taxonomy. The key goal of this project is to update Python's official > web presence with an eye to better organizing the information we have > today (and expect to add in the future). The end result should aid the > various audience roles in locating the information relevant to their > needs. > > > Proposal guidelines > =================== > > Proposals should be submitted by XX:XXpm EST, XX/XX/XXXX via email to > psf-redesign in PDF format. Proposals received after this date and > time will not be considered. Proposals should be comprehensive, > covering all aspects of this RFP. > > Note: Bids submitted by a collaborative team of professionals are > acceptable as long as there is a single signatory to the contract. We > encourage teams and individuals to collaborate on this project as we > feel it will enrich the final product and reflects the Python > community's ethos. > > Proposals should include: > > * An overview of your company's recommended process for the project > > * A draft timeline with staggered deliverables for the project > > * Sketches of potential layouts which express the team's vision for > ``python.org`` are extremely helpful in proposal selection, but are > not required for submission. > > * Your suggestions for each of the points identified in *purpose* > > * Your qualifications for the areas identified in *scope* > > Proposals must contain the following information about the proposer: > > * Company name, contact information and website URL > > * Background, including company history, team members, services > > * Which company resources would be dedicated to the project > > * Samples and designer portfolios of work similar in size and scope > > * Contact information for referrals: > > > Purpose > ======= > > Although the current implementation of the Python web site has served > a key purpose over the years, the time has come for the site to > progress and become a compliment to the growth and maturity of the > language itself as well as the vibrancy of the community. > > This project represents an opportunity to revamp the Python web site > from the ground up. > > The next implementation of the site should: > > * Boast a modern design and experience > > * Provide concise and intuitive navigation > > * Showcase the simplicity and elegance of the language > > * Attract and convert potential Python users and Python Software > Foundation sponsors > > * Represent the vibrant, active community > > * Make it easy for a wide range of contributors to add content > > * Enhance the visibility of the PSF and its sponsors > > * Provide examples of success stories > > * Enhance the visibility of alternate implementations (Jython, > IronPython, PyPy...) > > * Exist atop stable and scalable infrastructure > > > Scope > ===== > > The scope of the project work will encompass the primary web site, > ``python.org``. There are five main areas that should be focused on: > > * Information architecture > > * Visual design and user experience > > * Front- and back-end development > > * System architecture and monitoring > > * Post-launch support and maintenance > > Examples of URLs that will be included in this project are: > > * http://python.org/ > > * http://python.org/community/ > > * http://python.org/download/ > > * http://python.org/news/ > > * http://python.org/psf/ > > The scope does not include sub-domains (such as ``pypi.python.org`` or > ``dev.python.org``) for ``python.org``. However, the work performed > should be done in such a way that the brand can be applied to other > PSF properties (e.g. ``pypi.python.org``) at a later date. > > > Requirements > ============ > > Note: These requirements are hard requirements, and are non-negotiable in > any proposal. > > * Detailed plan for importing all existing site content > > * Monitoring of critical systems using modern monitoring tools, such > as Munin, etc. Coordinate with the PSF Infrastructure team on tool > selection. > > * Allow for easy internationalization of content > > * Fast page speed/aggressive caching > > * Ability to quickly spin-up sub-sites (e.g. ``edu.python.org``) > > * Ability to quickly spin-up blogs (e.g. ``python.org/blogs/psf``) > > * Aggregate content from various sources (e.g. ``blip.tv``, blogs, > news feeds, etc.) > > * Section 508 compliance (WAI-ARIA potential compliance) > > * A well-documented API for retrieval and creation of content, with > preference given to APIs supported by existing client-side tools. > > * Open and standards-based accessible APIs that can be used from any > language to integrate new tools and features in Python and other > languages. > > * Retain current URLs or provide 301 redirects for those that change > > * Multiple versions of content must be saved as edits are made, with a > facility for reverting an individual document to an older version > > > Migration of Existing Data > -------------------------- > > All content from the existing site must be migrated to the new system > so that it is available on the launch date. Content of historical > pages must not be modified, although they should be restyled to fit > the new appearance. > > > Licensing > --------- > > All content, code, visual design, imagery and other related work for > the site must be done with a licensing scheme that allows for the > Python Software Foundation to redistribute, relicense and otherwise > dissemenate. > > The Foundation requires that all code involved in the construction of > the system follow Python's own permissive licensing scheme, and be > open source software. > > > Audience > ======== > > > Potential users > --------------- > > These users are new to Python or investigating it for potential use. > Questions they may have include: > > * What is Python? > > * What does it look like (e.g. syntax)? > > * Why would I want to use Python? > > * How do I get started with Python? > > * Who uses Python (success stories)? > > * What are some ways Python is being used today? > > * Who is using Python for XYZ industry? > > > Existing users > -------------- > > These users already use and/or contribute to Python. Examples of > information they are trying to gather include: > > * How do I do XYZ with Python? > > * Where are the closest Python user groups? > > * Which developers in my area are using Python? > > * Is our company's version of Python current? > > * What sources of information are there on XYZ in Python? > > * What is the roadmap for Python? > > * How do I donate or contribute? > > * How do I download the current release of Python? > > * How do I download an older release of Python? > > > Users of other languages > ------------------------ > > These users primarily use other programming languages. Examples of > what these users may be asking include: > > * Why should I switch to Python? > > * Can I use Python in tandem with the language(s) I'm using today? > > * How does Python compare to language XYZ? > > * Does Python have an implementation of a tool that does not exist in > my language? > > > Managers > -------- > > These users may be technical or non-technical. Examples of what these > users may be looking for include: > > * Who uses Python? Why? > > * What are some ways others are using Python? > > * Why does my staff insist on moving to Python? > > * How high is the quality of the software? > > * Python is popular. Should we be using it? > > > Contributors > ------------ > > These users are heavily vested in Python and contribute to the > language. They may be asking: > > * Who is working on which features for the next release? > > * When is build XYZ due? > > * What show-stopper bugs should I focus on? > > * How do I contribute [code|bug reports] > > > Sponsors > -------- > > These are potential contributors / sponsor members for the Python > software foundation, the information they would be looking for > includes: > > * All information in the "Managers" section > > * Information about the Python Software Foundation including what it > currently does, what it is has done > > * What benefits sponsorship includes. > > > Current Issues > ============== > > > Architecture and Maintenance > ---------------------------- > > Currently the site uses a custom-built content build system - this > system requires developer-level knowledge to contribute as much as a > news item to the system. We need the ability for individuals with > limited coding experience to contribute and maintain content on the > main site and sub-properties. > > > Information Architecture > ------------------------ > > If you examine the current home page, you will note the amount of > information first presented to the user is overwhelming, and the > navigation on the left hand side is as well. The latter - either > through lack of organization or "informational spread" of information > (the site has grown organically over time) means that navigation is > confusing/disjointed. > > > Visual Design > ------------- > > The current visual design is felt to be very dated, and lacking much > of the new UX and UI attributes (cleanliness, color, etc) that > represents the modern web. The site does present a massive amount of > information - in an overwhelming and unorganized fashion. The visual > elements and cues used are inconsistent and disorganized. > > > Project Management > ================== > > Contact information for primary and secondary contacts for the > proposing team should be be provided. Proposals should include > descriptions of the project management processes and tools typically > used by the proposal organization. After a proposal is accepted, the > PSF will expect weekly status reports. > > > Cost/Price Estimates > ==================== > > We understand that the design and architecture (UI/UX) part is likely > to be a number of rounds of back and forth between the > designer/architect person and the PSF. We understand that it is > impossible to put a fixed budget on a design process since by its very > nature it should be iterative and back-and-forth. > > Therefore, quotes should be broken down to reflect appropriate rates. > Instead of a single fixed price estimate, in the following format: > > * Back-end work: $(fixed amount) > > * UI/UX: $(amount per iteration/hour) up to $(max) > > * Ongoing stuff: $(amount)/month > > > Selection process > ================= > > Proposals will be evaluated based on the following criteria: > > * Proposal timeliness. > > * Did the submitter follow the submission instructions? > > * Was the proposal comprehensive? > > * Did the proposal cover the five main points mentioned in *scope*? > > * Are the resources, experience and technical expertise of the company > adequate? > > * Is there a clear plan for follow-up and further requirements > discussions and refinement? > > Final selection will be made by the Python Software Foundation board > of directors. The primary point of contact for all inquiries should be > psf-redesign. > > Additionally, if needed you can contact: > > * Jesse Noller, PSF Board member: jnol...@python.org > > * Python Software Foundation board: p...@python.org > > _______________________________________________ > PSF-Members mailing list > psf-memb...@python.org > http://mail.python.org/mailman/listinfo/psf-members
|
index.rst
Description: Binary data
