public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly report 07/30
Date: Sun, 29 Jul 2018 08:36:14 -0700	[thread overview]
Message-ID: <20180729083614.242a40c9@professor-x> (raw)
In-Reply-To: <20180729082001.3a3f3c4e@professor-x>

[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]

On Sun, 29 Jul 2018 08:20:01 -0700
Brian Dolbec <dolsen@gentoo.org> wrote:

> On Sun, 29 Jul 2018 21:40:30 +0800
> Pengcheng Xu <i@jsteward.moe> wrote:
> 
> > Hi all,
> > 
> > Last week's report is available now.  Link:
> > 
> > https://jsteward.moe/weekly-report-0730.html
> > 
> > Thanks!
> >   
> 
> While I am not directly involved with gsoc this year... I can't help
> but to respond here.
> 
> Reports like this were not acceptable in past years.
> 
> Just showing a link to a report is not enough.
> 
> A PROPER report here should include enough info to give the reader an
> idea if they want to follow the link and get all the details.
> 
> While I don't expect a 3 page essay, you should summarize what was
> done in brief, but clear writing.  The link to the full detailed
> report at the end.

I should have followed the link before responding...

The link contents is no more than a brief summary.  I didn't do a word
count, but, I think my previous reply was about the same size...  So
how hard would it have been to copy/paste that text into an email...

But I still find that report lacking for a detailed report.  You should
have included some details of what was done for the automatic setup.

Also, why are your user guides just in a blog? Shouldn't the user guides
be added to the Gentoo wiki?  Blog guide info I would think would only
be for brief preliminary help info for mentors and other actively
interested persons.  So as the project progressed, they could keep up
to date with the code.  But the real documentation should in my
opinion be put somewhere central like our Gentoo wiki.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2018-07-29 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 13:40 [gentoo-soc] Weekly report 07/30 Pengcheng Xu
2018-07-29 15:20 ` Brian Dolbec
2018-07-29 15:36   ` Brian Dolbec [this message]
2018-07-29 18:30     ` Andrew Savchenko
2018-07-30  2:18     ` Pengcheng Xu
2018-07-29 18:10 ` Andrew Savchenko
2018-07-30  2:00   ` Pengcheng Xu

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=20180729083614.242a40c9@professor-x \
    --to=dolsen@gentoo.org \
    --cc=gentoo-soc@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