All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Evgeny Novikov <novikov@ispras.ru>,
	Alexey Khoroshilov <khoroshilov@ispras.ru>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"lsb-discuss@lists.linux-foundation.org"
	<lsb-discuss@lists.linux-foundation.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [lsb-discuss] Google Summer of Code 2016 - Many new applications
Date: Fri, 25 Mar 2016 16:46:51 -0700	[thread overview]
Message-ID: <20160325234651.GA27689@kroah.com> (raw)
In-Reply-To: <56F5C2A7.3060400@gmail.com>

On Fri, Mar 25, 2016 at 07:58:47PM -0300, Till Kamppeter wrote:
> On 03/25/2016 02:23 PM, Greg KH wrote:
> >I didn't see anywhere to "star" an application,
> >why do some have that mark and others do not?
> 
> You can click the start in the list of applications or click the "STAR"
> option on the proposal page.

I don't see that option on the proposal page, nor can I click on it on
the list.  Maybe that's something that you need admin rights for :)

> This is to mark if you really want this student/project. Note that it is
> only for our internal use, Google does not see/use the star settings.

Ok, then I'm not going to worry about it.

Now that the application process is closed, what's our next step here?
How do we rank/sort/evaluate them?  I don't see the "put a number here"
option like we have had in previous years.

thanks,

greg k-h

  reply	other threads:[~2016-03-25 23:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 17:39 Google Summer of Code 2016 - Many new applications Till Kamppeter
2016-03-24 17:39 ` [Printing-architecture] " Till Kamppeter
2016-03-24 18:08 ` Greg KH
     [not found] ` <1943931458892174@web3o.yandex.ru>
2016-03-25 17:23   ` [lsb-discuss] " Greg KH
2016-03-25 22:58     ` Till Kamppeter
2016-03-25 22:58       ` [Printing-architecture] " Till Kamppeter
2016-03-25 23:46       ` Greg KH [this message]
2016-03-25 23:56   ` Till Kamppeter
2016-03-25 23:56     ` [Printing-architecture] " Till Kamppeter
2016-03-26  0:00     ` Till Kamppeter
2016-03-26  0:00       ` [Printing-architecture] " Till Kamppeter
2016-03-26  0:18       ` Greg KH
2016-03-26  0:39         ` Till Kamppeter
2016-03-26  0:39           ` [Printing-architecture] " Till Kamppeter
2016-03-26 14:15           ` Greg KH
2016-03-26 14:25             ` Till Kamppeter
2016-03-26 14:25               ` [Printing-architecture] " Till Kamppeter
2016-03-26 16:46               ` Greg KH
2016-03-26 17:04               ` Greg KH
2016-03-26 18:07                 ` Till Kamppeter
2016-03-26 18:07                   ` [Printing-architecture] " Till Kamppeter
2016-03-28 14:42                   ` Greg KH
2016-03-30 18:33                     ` Till Kamppeter
2016-03-30 18:33                       ` [Printing-architecture] " Till Kamppeter
2016-03-26 19:28       ` Denis Silakov
2016-03-26 19:43       ` Alexey Khoroshilov
2016-03-26 19:49         ` Luis R. Rodriguez
2016-03-26 19:49           ` Luis R. Rodriguez
2016-03-26 20:00           ` Till Kamppeter
2016-03-26 20:00             ` [Printing-architecture] " Till Kamppeter
2016-03-26 20:00             ` Till Kamppeter
2016-03-26 19:59         ` Till Kamppeter
2016-03-26 19:59           ` [Printing-architecture] " Till Kamppeter
2016-03-26  0:17     ` Greg KH
2016-03-26  0:36       ` Till Kamppeter
2016-03-26  0:36         ` [Printing-architecture] " Till Kamppeter

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=20160325234651.GA27689@kroah.com \
    --to=greg@kroah.com \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --cc=mcgrof@gmail.com \
    --cc=novikov@ispras.ru \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.