From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Screenshot contest 2009
Date: Sat, 27 Jun 2009 00:16:43 +0300 [thread overview]
Message-ID: <200906270016.57962.hwoarang@gentoo.org> (raw)
In-Reply-To: <200906221357.23648.hwoarang@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
> On Sunday 14 June 2009 18:55:59 Markos Chandras wrote:
> > > Markos Chandras wrote:
> > > > Hello fellow devs,
> > > >
> > > > Back in 2007 , a screenshot contest took place[1]. How about running
> > > > a second one this year?
> > > >
> > > > As a quick draft, the following rules may apply
> > > >
> > > > 1) Users can submit only one screenshot
> > > > 2) The deadline will be the 30th of July 2009
> > > > 3) Developers cannot take place
> > > >
> > > > An elected committee ( 2-3 devs but even more ) can vote and elect
> > > > the top 10 screenshots
> > > >
> > > > Optionally categories may exist
> > > >
> > > > KDE,Gnome, Openbox etc
> > > >
> > > > I'd like to hear your thoughts about this
> > > >
> > > >
> > > > [1]:http://www.gentoo.org/main/en/shots.xml
> > >
> > > gentoo-project please
> > >
> > > Regards,
> > > Petteri
> >
> > Ok I am moving this discussion on gentoo-project as Petteri suggested.
> >
> > Here[1] you can find a draft about the related page of the contest.
> > Every single screenshot , will be uploaded to a google picasa web gallery
> > so all of them
> > can be publicly accessible and viewable.
> >
> > Furthermore, I request permission from @infra to allow me do the
> > following
> >
> > 1) create a subfolder under xml/htdocs/main/en where the old shots.xml
> > will be putted in ( maybe with a different name like "contest-2007.xml"
> > 2) put my shots.xml under xml/htdocs/main/en/
> >
> > I would be grateful if infra could provide me an alias on woodpecker (
> > screenshots@gentoo.org or something ) for me and the rest of committee.
> > Users and developers will use this e-mail address to send their
> > screenshots.
> >
> > If somebody wants to be on the committee please let me know.
> >
> > Thanks
> >
> > [1] http://dev.gentoo.org/~hwoarang/files/shots.xml
> > [2]
> > http://picasaweb.google.com/Markos.Chandras/GentooScreenshotContest2009
>
> Hello again,
> A week has passed, so since nobody raised any objections about my
> modifications on xml/htmldocs/main I will proceed with my proposed changes.
> I plan to do it on Wednesday night.
>
> Thank you
Seems like I dont have access to touch xml/htdocs/main/en place on cvs server.
So consider this effort as "stalled" until somebody with access on that place
do the work on my behalf
Cheers
--
Markos Chandras (hwoarang)
Gentoo Linux Developer [KDE/Qt/Sunrise/Sound]
Web: http://hwoarang.silverarrow.org
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-06-26 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906131454.34321.hwoarang@gentoo.org>
[not found] ` <4A33CAED.2060606@gentoo.org>
2009-06-14 15:55 ` [gentoo-project] Re: [gentoo-dev] Screenshot contest 2009 Markos Chandras
2009-06-22 10:57 ` Markos Chandras
2009-06-26 21:16 ` Markos Chandras [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906270016.57962.hwoarang@gentoo.org \
--to=hwoarang@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox