Friends,
I promised to write something up about how owncloud could/should
be integrated in the openSUSE distro. Would you mind looking into
it and give feedback?
Thanks a lot,
Klaas
Hi, as concluded in yesterdays project meeting, we want to shut down
users.o.o and redirect the subdomain to connect.o.o
However, there is still a part missing to get rid of users.o.o, that's
according to darix a maildump output for the @opensuse.org redirects.
Probably we can integrate this into the connect api, but also the client
(an is&t script, contact is mhoppe) has to be adopted.
It expects an output like:
-miska-(a)opensuse.org michal(a)hrusecky.net
Michal.Hrusecky(a)opensuse.org michal(a)hrusecky.net
69_rs_ss(a)opensuse.org 69_rs_ss(a)opensuse-forums.org
...
Has someone already worked on this?
Greetings
--
Thomas Schmidt (tschmidt [at] suse.de)
SUSE Linux Products GmbH :: Research & Development :: Tools
"Don't Panic", Douglas Adams (1952 - 11.05.2001)
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org
Hi Boosters,
You guys worked on a milestone trying to find out why people didn't
contribute as much to Factory despite building and maintaining packages
in their home:* or other places. As someone suggested a discussion about
that at oSC, I wonder if this is a 'done deal', did you guys solve that,
or is it worth discussing at oSC?
If so, who can lead it?
Cheers,
Jos
Good News Everyone!
(the following text applies only to the Membership Approval Team)
As a part of our Boosters sprint we decided to make our Membership
Approval Process much easier and thus effective. You don't need to use
Retro.o.o anymore, everything happens directly inside of the Connect \o/.
The whole process is now concentrated to the one webpage - which is
accessible from this short URL:
http://is.gd/newmembers
You see several rows, one for each applicant. On the left there is an
avatar, Accept and Decline buttons and validations link button. First
two buttons accept or decline the request, the last one shows popup with
all handy validation links to bugzilla, wiki and so on.
The middle part of each row is dedicated to contributions descriptions
that user filled in when applying through the membership widget. If
there were none given it says "No given contributions."
Right area is voting area. You can put your reason into the reason field
and press Thumb up or Thumb down button. When you click on the +N/-N
number you can see already given comments (and you can also delete
yours). After you voted you no longer see Thumbs buttons so you can't
vote again. If you want to change your vote, just delete your comment
and give another one.
Hope this will help to optimise the process which was stalled mainly
because of its complexity.
Suggestions welcome, patches even more so[1] :-)
[1] http://gitorious.org/opensuse/connect
--
Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o
openSUSE Boosters Team Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9
prusnak[at]opensuse.org Czech Republic
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org
Hi,
sending summary of investigation of possibility to collaborate with
universities...
How can we collaborate:
- universities have many students that needs to do some semesters
works, write bachelors thesis, master thesis, phd thesis and such.
- it's hard for teachers to come up with topics for students
- we've got many interesting stuff to do, but we don't have enough manpower
- so we can join our efforts:
- universities will provide students
- we will provide idea and mentor
- some teacher/person on the university side will take care
administrative part and thesis writing
- our mentor will take care of technical part
What would be needed to start it in large scope:
- have a list of topics and mentors universities and students can
choose from
- show requirements
- how hard it is
- detailed description
- whether somebody already tried that
- whether the topic is taken
- relevant references
- mentor, co-mentor
- have a list of mentors
- finished/unfinished/wip topics
- history of mentorship
- some possible evaluation from students/universities
Universities needs mentors they can rely on that wouldn't disappear
faster then a student and mentors that can take care of the student.
Workflow I can imagine...
Student needs to write thesis. Teacher needs a topic for him. One of
them will take a look at our topics list. He will search for a topic
according to the students skills. They will take a look at mentors
references, contact him and pick the topic. Teacher will take care of
administrative side of things - registration at university and help with
formal aspects. Our mentor will help with all technical aspects and will
guide the student. At the end students work will be actually used and
good for something. We would get new cool thing done and possibly
another open source enthusiast. Student would get interesting thesis
topic that is actually good for something. Teacher will have less work
with making the student graduate. Everybody wins.
<sidenote>
I know that RedHat is already providing mentors for the thesis and they
are giving talks and helping to teach students stuff. And if they find
somebody skilled among the students, they hire him.
</sidenote>
Apart from that, this might be a good idea for cross-distro
collaboration if we would get such a site running, something similar to
the Junior Jobs site Jos was sending here some time ago. Obviously the
main idea would be to have mentors from community as well. To make it
work and to have reliable mentors, we would probably need some filtering
and not let anybody be the mentor. Something like invitation only
mentors or that new mentor need to finish at least X thesis with some
full fledged mentor as co-mentor, so there would be some backup in case
of disappearance. I think that mentorship shouldn't be much harder then
GSoC mentorship and we have plenty of GSoC projects this year. So this
is the idea of what could be our sprint and why it might be a good idea.
But sure, we can start without infrastructure and without sprint, just
encourage people to prepare projects and topics and contact
universities.
Feedback, opinions welcome. Obviously it is just an idea, I haven't
tried to look for some existing solution that will help with that, might
do so in the future.
--
Michal HRUSECKY SUSE LINUX, s.r.o
openSUSE Boosters Team Lihovarska 1060/12
PGP 0xFED656F6 19000 Praha 9
mhrusecky[at]suse.cz Czech Republic
http://michal.hrusecky.nethttp://www.suse.cz
=======
General
=======
* Register for the summer event dummys!
=======
Standup
=======
name
** What did I do in the last week for the milestone?
** What am I planing to do in the next week for the milestone?
** What was/is blocking me from doing things for the milestone
last/this week?
cwh
** nothing
** nothing
** started to learn hermes. pushing the wiki/wordpress servers to nbg.
vacation/public holiday
ismail
** nothing
** nothing
** KDE 4.7 release. vacation/public holiday
tom
** nothing
** learn about the connect changes. work on the maildump app. fix some
minor nitpicks.
** vacation
coolo
** nothing
** nothing
** milestone 2/public holiday
vuntz
** nothing
** nothing
** vacation
michal
** nothing
** nothing
** GSoC students. MySQL bugs. Czech University Collab.
pavol
** extracted all the group plugin modifications to our own plugin.
core changes to the connect_inout plugin.
** work on the automatic emails for accepted/rejected members
** nothing
henne
** updated connect on gitorious to 1.7.10.
investigated 1.8 changes.
separated all the minor changes to patches.
** blog about the milestone
** vacation/public holiday. HR training on tuesday/monday.
=========
Milestone
=========
We will work further on this milestone. Goals and stories are in retro
http://retro.opensuse.org/projects/boosters-work/milestones/17/goals
We will kick-off another milestone on the 4th of July about attracting
one mid-sized FOSS project to release their binaries in OBS and use this
"pilot-customer" to improve the OBS documentation, tools and processes
for upstreams.
Henne
--
Henne Vogelsang, openSUSE.
Everybody has a plan, until they get hit.
- Mike Tyson
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org
What I did last week:
* fixed UnixODBC
* searching for solution for MySQL bug
* helping my GSoC students
What I did last week during my free time:
* attended OpenMobility Conference
- spoke with few guys from VUT University about possible cooperation
* managed to get osc into Gentoo [1], will blog about it later
* had a fun during online conference of SOZA (Slovak RIAA)
What I plan to do:
* follow up with how can we engage various students
* take a look at Connect patches
* continue with GSoC mentoring
* continue with bugs processing
[1] https://bugs.gentoo.org/show_bug.cgi?id=350599
--
Michal HRUSECKY SUSE LINUX, s.r.o
openSUSE Boosters Team Lihovarska 1060/12
PGP 0xFED656F6 19000 Praha 9
mhrusecky[at]suse.cz Czech Republic
http://michal.hrusecky.nethttp://www.suse.cz
guys, we just discovered that the poll here http://bit.ly/lfiaFz (don't
advertise, it is not official yet) allows anyone to edit and/or delete it...
At least, Bryen could do that. What went wrong?
As this poll is meant to be official, this is a bit of an issue :D
I hope someone can fix this up before it's 15:00 UTC on Tuesday!
Jos
Montag, 30. Mai 2011 sent Stephan Kulow:
> Am Montag, 14. März 2011 schrieb Vincent Untz:
> > For build failures: some people might have noticed, I'm a big fan of
> > automatic reminders, since it pushes the information to people. We can
> > start with a weekly automatic mail to opensuse-factory listing the
> > build failures (or a summary). I can write a cron job for that, and we
> > then see if it helps. (I won't be able to do it before next week,
> > though)
>
> Any success? I think it's fair to say it's past "next week" :)
>
This would be my favorite "next sprint". As said during the meeting,
I don't think this requires the full team for a long time as most of the infos
are already there, but I won't be able to do it myself alone.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-boosters+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-boosters+help(a)opensuse.org
What I did:
- dealing with old MySQL bugs
- fixing MySQL update in Factory
- GSoC students started to work, guiding them
What I plan to do:
- still got some pilled up bugs to cleanup
- need to watch my GSoC students more closely
- some MySQL related features I discussed on LinuxTag and didn't have
time to follow
--
Michal HRUSECKY SUSE LINUX, s.r.o
openSUSE Boosters Team Lihovarska 1060/12
PGP 0xFED656F6 19000 Praha 9
mhrusecky[at]suse.cz Czech Republic
http://michal.hrusecky.nethttp://www.suse.cz
