From: Gaute Hope <eg@gaute.vetsj.com>
To: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>,
supmua <supmua@googlegroups.com>
Subject: Re: [sup] papercuts and google code-in
Date: Sun, 28 Dec 2014 14:14:01 +0000 [thread overview]
Message-ID: <1419775872-astroid-4-gk0eja34lo-1194@strange> (raw)
In-Reply-To: <1419701714-sup-6215@email.archlab.tuwien.ac.at>
Hi,
I invited you to become a contributor to the sup organization on github
(embee right?). That way you can assign yourself to these issues and
handle them on the issue-tracker.
Thanks for doing this, I hope there is time to polish things up enough
to merge them.
regards, gaute
Excerpts from Martin Bähr's message of December 27, 2014 19:05:
> hi,
>
> while using sup i am taking notes whenever i notice some small issue or an idea
> for an improvement.
>
> some of these may be real bugs, some a matter of taste, and so i didn't take
> the time to write them all up as issues.
>
> i have put the list here http://pad.hackerspace.sg/p/sup-ideas
> (but that server is down now, so i put a backup here:
> https://factor.cc/pad/p/sup-ideas )
>
> now, i am a mentor for FOSSASIA at google code-in, and i put up that list as a
> source of tasks for students to work on.
>
> (a sample task is here
> https://www.google-melange.com/gci/task/view/google/gci2014/6127040658931712
> i have since updated the text a little bit advising students for the need for
> writing tests and testing against develop and use-mail branches)
>
> essentially that means that sup is able to participate at google code-in.
>
> so far only one student showed interest, but if well maintained he might become
> a sup contributor.
>
> if you are interested to take advantage of this you could help in the following ways:
> if you have suggestions for tasks, add them right on that etherpad page. (add
> your name and a description of the task)
>
> you could also add your name behind existing tasks if you are interested to
> help students with those.
>
> i don't think you need to sign up with google code-in to help. it is probably
> enough to communicate with the students through github issues and
> pull-requests. and you can help by reviewing and closing pull-requests.
>
> if a pull-request is closed i can immediately close the students task, though i
> may close their task if i am satisfied with the work, regardless of the
> pull-request status. (since the tasks are my wishlist, it doesn't necessarily
> follow that all my wishes should be accepted into sup)
>
> note that google code-in is a contest, and the number of tasks the students
> close carries some weight in winning a prize. this causes some students to show
> impatience with getting their tasks reviewed. i do hope that this impatience
> does not spill over into github discussions, but if it happens, please just
> ignore it (and let me know, so i can deal with it)
>
> greetings, martin.
>
> --
> eKita - the online platform for your entire academic life
> --
> chief engineer eKita.co
> pike programmer pike.lysator.liu.se caudium.net societyserver.org
> BLUG secretary beijinglug.org
> foresight developer foresightlinux.org realss.com
> unix sysadmin
> Martin Bähr working in china http://societyserver.org/mbaehr/
>
> --
> You received this message because you are subscribed to the Google Groups "The Sup email client" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to supmua+unsubscribe@googlegroups.com.
> To post to this group, send email to supmua@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/supmua/1419701714-sup-6215%40email.archlab.tuwien.ac.at.
> For more options, visit https://groups.google.com/d/optout.
>
next prev parent reply other threads:[~2014-12-28 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 18:05 Martin Bähr
2014-12-28 14:14 ` Gaute Hope [this message]
2014-12-28 16:12 ` [sup] " Martin Bähr
2014-12-28 17:06 ` Gaute Hope
2014-12-28 17:31 ` Martin Bähr
2014-12-28 18:00 ` Gaute Hope
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=1419775872-astroid-4-gk0eja34lo-1194@strange \
--to=eg@gaute.vetsj.com \
--cc=mbaehr@email.archlab.tuwien.ac.at \
--cc=supmua@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox