Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by JuergenRagaller: http://wiki.apache.org/lenya/DocuPublicationRedesignContestDraft ------------------------------------------------------------------------------ = Docu Publication Redesign (Lenya Website) (Draft) = - This is a draft. + '''This is a draft''' + + '''Lenya Website Redesign Contest''' + + '''A special welcome to all interested and skilled in web design!''' + '''It's good to have you here. It would be great if you would join our community and provide your expertise to give the Lenya Homepage a shiny new look.''' + Some ideas about the contest were taken from the Solr logo redesign page (http://wiki.apache.org/solr/LogoContest) - thanks to the Solr community for inspiration! @@ -43, +49 @@ * Compatibility: IE 6 and higher, Firefox 3, Safari 2 == How To Enter == - Everything will be attached to the following Bugzilla entry: TODO - You will need to create a new Bugzilla account to do that. + You can attach your screenshots and other design assets to the following Bugzilla entry: TODO + You will need to create a new Bugzilla account to do that. With the creation of a ASF-Bugzilla account you agree to the license terms of the Apache Software Foundation. Please note that by logging in/creating a Bugzilla account, you certify that any object code, source code, patch, documentation, etc. that you may supply to an Apache project can be redistributed under the same [http://www.apache.org/licenses/LICENSE-2.0 Apache License version 2.0 license terms and conditions] as + the project itself. - * Attach one ore more images of the redesign. Include 330x220 GIF, JPEG, or PNG samples -- one each of homepage and interior page -â allows three samples per 1024x768 screen. Also need full screen versions â HTML and associated files? + * Attach images of the redesign, interior page and the homepage + possibly more pages. Size: 1024 x 768 PNG or JPEG. + * If you chose to do the redesign by writing css (using the zip-archive of the docu publication) make screenshots of the result. * Optionally attach additional resources (CSS, Photoshop or Fireworks files). Multiple entries may be submitted by a single person. (Bear in mind: voting will be for an entry, not the person who submitted them so multiple entries will compete against each other. This may be improved by voting for every entry before vote for best entry.) - TODO: As for as I can tell, there is no built-in mechanism to let users agree on the ASF license in Bugzilla (in Jira this seems possible) â any suggestions on how we can do this correctly? - - Ask legal if placing a notice in the introduction to the Bugzilla is enough. Ask for the best phrases, i.e. mix and match: - * Attachments | Submittals | The winning entry - * to this bugzilla | to this contest - * are automatically | become - * under the ASF license. | the property of the ASF. - Or must every entry contain a phrase like "This submission may be used under the Apache license." (Again, ask legal for phrasing.) - Do we need submitters to sign paper with the ASF? ASAP or only before use (after the contest ends)? - == Voting == - * WRITEME Community-Voting - * WRITEME Commiter-Voting + The voting will take place on the user mailing list. So please make shure you subscribe there. + People involved or interested in the Lenya project have stars they can give to on ore more entries: + Number of stars to give: - The SOLR contest's voting will be on the User ML. Each person has up to 15 votes with the first entry receiving 5 votes, and up to four additional entries receiving 4, 3, 2, and 1 votes. The number of entries does not affect the process; the final count is 28 with at least one "family" of five entries only varying font and color. Voters may not specify other distribution of the votes. + *10*: Lenya commiters + * 8*: regular user/dev mailing-list-posters (definition of ml posters as described by solprovider) + * 6*: persons with an apache.org email + * 4*: everybody else - We should use a Lenya application for a better voting process. Display a page of entries vertically with images of each entry's homepage and interior page horizontally. Clicking opens the full screen entry in new window. Designers should include sample graphics -- recommend 330x210 images to fit three samples per 1024x768 screen. + The entry with the highest number of stars wins the contest. + Unless: That entry receives more than two vetoes from Lenya committers or there is a consensus among the committers about a lack of quality of the entries overall. + == Cancellation == + The contest can be cancelled when there are less than 3 entries; or when there is obvious misuse. - ---- - - AndreasHartmann: I think voting on the user mailing list is sufficient. We can prepare a page displaying the contestants' submissions like you described and assign a number or textual ID to each entry. The vote can just refer to the IDs. - - ---- - - The first round of voting should be for all entries to offset similar entries being damaged by splitting the vote. Each person votes for every entry: - Veto (only Committers) - No Vote - Acceptable - Fantastic - * Limit Fantastic votes so each five entries allows one Fantastic vote per person. A Fantastic vote counts as three Acceptable votes. - * Two Lenya Committers' Vetoes removes an entry from the ballot because if two Committers agree an entry is unacceptable, the entry would not survive the final vote. - * Per ASF rules for project changes, final selection requires a Lenya Committer-only vote. The rules allow a justified Veto. This phase should ratify the most popular entry and only need additional rounds if the entry is vetoed or does not receive the required votes. - * How can non-Committers vote be verified one per person? People can have many email addresses. Accepting only apache.org addresses limits to Apache Committers. Lenya Committers' votes count double or more? - - - ---- - - AndreasHartmann: Another option would be that each user has e.g. 5 "stars" which she can distribute over the entries (e.g., three stars for entry A, one star for B and one star for C). That would avoid the negative psychological impact caused by "Hate" votes :) - - ---- == Time Line == @@ -103, +89 @@ ---- - AndreasHartmann: Should we really use JPEG as preferred file format? With small file sizes, it is prone to artifacts. Wouldn't PNG be the better option? - Solprovider: JPEG does not add artifacts at high quality. Contest submissions should be high quality; file size of samples is not a concern. - - ---- - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
