Martin Bähr
2014-12-27 18:05:02 UTC
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/
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+***@googlegroups.com.
To post to this group, send email to ***@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.
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+***@googlegroups.com.
To post to this group, send email to ***@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.