« Return to Thread: Proposal for a new website

Re: Proposal for a new website

by Chris Kelly-2 :: Rate this Message:

Reply to Author | View in Thread

These are all great points, but it's a lot of information to
discuss and all of it may not be of direct interest to the
majority of people on this list. Could you create a new page
on our wiki, perhaps http://codex.gallery2.org/New_Website
with everything below so that we can track things we've
agreed on and more easily share progress updates? I'm not
saying that things can't be discussed here, but having all
of the information in one place will lead to shorter, more
digestible, emails and email threads.

I like that you separate the user docs/etc  from the dev
docs/etc. I feel like thats a separation we don't really
have now.

Some resources that we have that you may not be aware of:

1. I run a hosting company and have piles of equipment
(http://www.ithought.org) and do operations in my fulltime
job so I'm well versed in that area

2. Gallery has a handful of servers that we own and have
full use of. 3 or 4 of em, in two different colos (some
hosted with me)

3. We have two UI/UX/WebDesign people (Chad and Jakob) that
have done and awesome on Gallery 3 and will have some time
to spend on our website once G3 is out the door

-Chris


Romain LE DISEZ wrote:

> Hi all,
>
> a very bad person has hijacked the thread of Bharat about Git. To take
> him in the right way, I start a new thread here ;-)
>
> It seems that some people agree that the "web presence" of the project
> must be re-worked for a better consistency and visibility. As a starting
> point for the discussion, I present the way I imagine it.
>
>
> ==== WHAT ====
> A public website : www.galleryproject.org
>     It is a "store" for the project. There should be :
>      - news
>      - forum
>      - documentation for the user (installation, how to use, FAQ)
>      - download
>      - access to demo
>
> A development website : dev.galleryproject.org
>     This is the place that concentrate everything about development. The
>     intented audience is the core team, the plugins developers, the
>     themes developers, and people just interested to look at the code.
>     There should be :
>       - a wiki (No user info here, only API, roadmap, ...)
>       - a bug tracker
>       - a code browser
>
> A VCS : git.galleryproject.org
>
> A demo : demo.galleryproject.org
>     A clean installation of the lastest version. It must be resetted
>     each hour to avoid squatting. (some of the more popular themes could
>     be added to the demo ?)
>
> A forge : forge.galleryproject.org
>     The goal is to group projects that turn around Gallery :
>      - parallels branches (Windows, PgSQL, ...)
>      - popular plugins and themes ?
>
>     The projects in the forge have their own wiki/bug tracker (it is
>     important that bugs introduced by theses projects are not in the
>     main bug tracker, it's up to the maintainer to follow up the ticket
>     to the core team)
>
>
> ==== WHO ====
> There is a need for some skills :
>  - Web design : create an identity for the project and adapt it for the
>    differents websites
>
>  - Web development : integrate the differents applications, may be some
>    specific development
>
>  - System administration : manage the server, DNS, and backups, install
>    the applications
>
>
> ==== HOW ====
> Depending of the resources of the project :
>  - a dedicated server : it will handle all the services, everything
>    needed could be installed
>
>  - take the services where there are : there is no cost but it will be
>    difficult to do good integration
>
>
> ==== MY POINT OF VIEW ====
> It is probably clear that I'm in favor of a server that can be totally
> managed, it will help to have something consistant.
>
> The homepage must be clear and efficient : a quick presentation, the
> last news and two big button "Try" (-> demo) and "Download". It should
> not be longest than a screen (no scrollbar)
>
> There must be no bridge between the public website and the two others
> except ONE link in the menu (eg: "Development | Forge"). This way, the
> end-user won't be lost in the dev except if he wanted it.
>
> The sites must have the same design but must be clearly distinguable.
> For example : three colors themes, and three logo (the main logo and two
> adapted for dev and forge)
>
> A shared authentication system would be great. This way, the same login
> is valid for the forum, the bugtracker, and git (with a validation for
> git, of course)
>
>
> Waiting for feedback and candidatures...
>
>
> Greetings.
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
> __[ g a l l e r y - d e v e l ]_________________________
>
> [ list info/archive --> http://gallery.sf.net/lists.php ]
> [ gallery info/FAQ/download --> http://gallery.sf.net ]


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
__[ g a l l e r y - d e v e l ]_________________________

[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]

 « Return to Thread: Proposal for a new website