[opensuse-project] Geeko wants you! idea
Hi, as anticipated elsewhere I'm putting together a wiki page to collect information on where help and contributions are needed in openSUSE. The basic idea is to create a SINGLE page on the wiki where: * users can find information on where their help is more needed, and links to other pages where they can find more details on how to start working on a certain task. * developers and long term contributors can insert their needs in terms of people necessary to do something. In other words it is a sort of page to recruit volunteers, so that they don't get lost in the wiki and on mailing-lists. Ideally, when this page is ready, it should be linked in very visible places, like news.o.o and in some part of the wiki home page (a blinking neon light on it would help ;)), so that it can be easily found. Of course all suggestions to improve the idea, and all comments are welcome. Currently the page is here: http://en.opensuse.org/Geeko_wants_you! and it looks quite desert, because I just started to put it together. I will add more stuff soon, but for the areas where help is needed, I need your help! Regards, Alberto -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hi, on 03/05/2009 05:13 PM Alberto Passalacqua wrote:
as anticipated elsewhere I'm putting together a wiki page to collect
Why don't you improve http://en.opensuse.org/Tasks Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Thursday 05 March 2009 17:43:40 Henne Vogelsang wrote:
Hi,
on 03/05/2009 05:13 PM Alberto Passalacqua wrote:
as anticipated elsewhere I'm putting together a wiki page to collect
Why don't you improve
We can abandon it in the end or migrate stuff from there - or merge the two. But you bringing up the page points out the problem that Alberto has: It's difficult to navigate the wiki... Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, Mar 6, 2009 at 7:53 PM, Andreas Jaeger
On Thursday 05 March 2009 17:43:40 Henne Vogelsang wrote:
Hi,
on 03/05/2009 05:13 PM Alberto Passalacqua wrote:
as anticipated elsewhere I'm putting together a wiki page to collect
Why don't you improve
We can abandon it in the end or migrate stuff from there - or merge the two.
But you bringing up the page points out the problem that Alberto has: It's difficult to navigate the wiki...
Hi, I've merged the pages. Currently improving the layout.. and yes, we definitively need to put forward this page for more visibility. R. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hi,
I've merged the pages. Currently improving the layout.. and yes, we definitively need to put forward this page for more visibility.
Thanks. We agreed with Henne I'll work on it. The merging imho should go in the opposited direction, to keep the page name. I'll do that in the weekend and clean it up :-) Regards, A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hi,
I've merged the pages. Currently improving the layout.. and yes, we definitively need to put forward this page for more visibility.
R.
I like the graphics additions a lot btw. Thanks for the work! But the content is not what I have in mind. I don't want to create a page with messages like "talk to these guys for this", "read there for that", as Task is currently structured. I want a sort of "work search page" to match demand and offer, with as specific as possible tasks, so that users can find it immediately what it is needed without waiting for someone to answer them, well...in most of the cases ;-) For example the "documentation" section is well done, while the build service section is the exact opposite of what I'm thinking to. :-) Regards, A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
I've merged the pages. Currently improving the layout.. and yes, we definitively need to put forward this page for more visibility.
R.
Hi, I unlinked the pages again. First of all, next time, before deleting content, please _ask_. In second place, my original idea of "Geeko wants you!" is not reflected in the current Task page, and I have no idea of what other people that worked on that page wants to keep and what can be removed, as a consequence, for now I don't see any urge to proceed with the merging. In my opinion the Task page is of very limited use as it is, because, as I already said, it contains too vague information, and before launching the idea to the public, we should first collect a certain number of activities (specific!) where help is needed, so that we can provide useful information from the beginning. So, if any part of the distribution needs help, let's answer to this thread and write where the need is, and in what the activity consists, and what "level of experience" is required, if possible. Thanks, A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
I extracted some content from Task, and created an example of how I think the page should look like. http://en.opensuse.org/Geeko_wants_you! Of course I hope the contact information will become more precise, and the descriptions too, when the page starts to be used. What do you think? :-) Regards, A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Sat, Mar 7, 2009 at 1:08 PM, Alberto Passalacqua
I've merged the pages. Currently improving the layout.. and yes, we definitively need to put forward this page for more visibility.
R.
Hi,
I unlinked the pages again. First of all, next time, before deleting content, please _ask_.
Sorry about that. I'm not really "shy" to do somtehing on the wiki, because I know there is always a way to go back, as every change is tracked in the history :)
In second place, my original idea of "Geeko wants you!" is not reflected in the current Task page, and I have no idea of what other people that worked on that page wants to keep and what can be removed, as a consequence, for now I don't see any urge to proceed with the merging.
In my opinion the Task page is of very limited use as it is, because, as I already said, it contains too vague information, and before launching the idea to the public, we should first collect a certain number of activities (specific!) where help is needed, so that we can provide useful information from the beginning.
It's my opinion too. The "Tasks" page is unseless if the task described are not enough focused and too vague. For the "merge", I have done only formatting work + copy/paste of former existing available information (I just added some zypper task, as i knew there were some work required in this area).
So, if any part of the distribution needs help, let's answer to this thread and write where the need is, and in what the activity consists, and what "level of experience" is required, if possible.
I extracted some content from Task, and created an example of how I think the page should look like.
http://en.opensuse.org/Geeko_wants_you!
Of course I hope the contact information will become more precise, and the descriptions too, when the page starts to be used.
What do you think? :-)
It's much better. But I still think that both page need to be merged ;) We just need a complete description (task, who to contact, experirence required, etc.) for each task, as showed in your exemple :) R. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
It's much better. But I still think that both page need to be merged ;) We just need a complete description (task, who to contact, experirence required, etc.) for each task, as showed in your exemple :)
If you agree, we could work on the "new page" and then merge, so that we don't throw something "in progress" out too early. My idea of plan of action is: - Poke teams to give us some task where they need some help. - Add the task in the format we like. - Write a short presentation of the initiative on news.o.o and add the link in a visible place. Do you agree? A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-03-07 at 12:00 -0600, Alberto Passalacqua wrote:
If you agree, we could work on the "new page" and then merge, so that we don't throw something "in progress" out too early.
You could have both pages. The "Geeko wants you!" one could be for "proselytism", and the "task" page the place where you can find actual tasks to do. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmy5qUACgkQtTMYHG2NR9VnngCfXBUcnhK7FjFQAYS9ldvzvmpt OhoAnRLqJhBHqv07PEp0QkAOvHFdhLt9 =N7H2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
If you agree, we could work on the "new page" and then merge, so that we don't throw something "in progress" out too early.
You could have both pages. The "Geeko wants you!" one could be for "proselytism", and the "task" page the place where you can find actual tasks to do.
We have also the generic "How to participate" wiki page for generic prosyletism, so we can use it. No need to confuse the potential contributor even more imho. R. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
If you agree, we could work on the "new page" and then merge, so that we don't throw something "in progress" out too early.
My idea of plan of action is:
- Poke teams to give us some task where they need some help. - Add the task in the format we like. - Write a short presentation of the initiative on news.o.o and add the link in a visible place.
Do you agree?
I agree totally, and 'm ready to help! Some of the teams have already written some specific tasks to complete (ie, zypper tasks, that I added to the current "Tasks" page), but on their own specific project page.. and therefore not very visible in the inner wiki. We need to : - check every teams page, and merge their actual tasks to complete in the Task/Geeko wants you wiki page, - be sure that they will add their community help request on this centralized page in the future. We can also add a "tracking page" (ie. /Geeko wants you's subpage) that help us to do the migration/actual poking status. R. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Sun, 2009-03-08 at 12:31 +1100, Rémy Marquis wrote:
If you agree, we could work on the "new page" and then merge, so that we don't throw something "in progress" out too early.
My idea of plan of action is:
- Poke teams to give us some task where they need some help. - Add the task in the format we like. - Write a short presentation of the initiative on news.o.o and add the link in a visible place.
Do you agree?
I agree totally, and 'm ready to help!
Some of the teams have already written some specific tasks to complete (ie, zypper tasks, that I added to the current "Tasks" page), but on their own specific project page.. and therefore not very visible in the inner wiki.
We need to : - check every teams page, and merge their actual tasks to complete in the Task/Geeko wants you wiki page, - be sure that they will add their community help request on this centralized page in the future.
We can also add a "tracking page" (ie. /Geeko wants you's subpage) that help us to do the migration/actual poking status.
R.
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;) -- Michael Fox Developer and user of Blender3d www.blender.org mfoxdogg@gmail.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Saturday 07 March 2009 10:30:25 pm Michael Fox wrote: ...
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org . -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Sat, 2009-03-07 at 23:18 -0600, Rajko M. wrote:
On Saturday 07 March 2009 10:30:25 pm Michael Fox wrote:
...
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
true but passing fancies, or minor fixes, for example a little tweak to say a KDE4 widget (i know it not OpenSuSE) they can just put it in the tracker incase someone wants it, also with a tracker a patch that may not be needewd now would still be found when it is needed avoiding alot of hassle. and as such keps proposals and fixes from the community all organised and in one spot not scattered all over the web only being found by scouring the mailing lists.
-- Regards, Rajko
-- Michael Fox Developer and user of Blender3d www.blender.org mfoxdogg@gmail.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Saturday 07 March 2009 11:53:50 pm Michael Fox wrote:
On Sat, 2009-03-07 at 23:18 -0600, Rajko M. wrote:
On Saturday 07 March 2009 10:30:25 pm Michael Fox wrote:
...
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
true but passing fancies, or minor fixes, for example a little tweak to say a KDE4 widget (i know it not OpenSuSE) they can just put it in the tracker incase someone wants it, also with a tracker a patch that may not be needewd now would still be found when it is needed avoiding alot of hassle. and as such keps proposals and fixes from the community all organised and in one spot not scattered all over the web only being found by scouring the mailing lists.
We have bugzilla, as Christian said. The problem is only proper selection of options when you file (upload) an improvement patch, and later when you are looking for it. Bugzilla has everything in the URL, so for some functions there are already links on the openSUSE wiki. OK, here is example: http://en.opensuse.org/Bugs That kind of links can be prepared for any project. It is much easier than to setup another bugzilla, and at the end we would have to create such "Easy Links" anyway. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
We have bugzilla, as Christian said. The problem is only proper selection of options when you file (upload) an improvement patch, and later when you are looking for it.
Actually bugzilla is pretty bad and confused, and it became worse with the new version. Searching on bugzilla is not exactly a friendly experience. I think one of the point Michael was proposing is to have a separate tracker for opensuse patches only, so that they are all in the same place without any need to be mixed with bugs. I am not sure, but something similar might be already in use internally at SUSE (swampid stuff? can anyone clarify?). Regards, A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Sunday 08 March 2009 05:52:56 pm Alberto Passalacqua wrote:
We have bugzilla, as Christian said. The problem is only proper selection of options when you file (upload) an improvement patch, and later when you are looking for it.
Actually bugzilla is pretty bad and confused, and it became worse with the new version. Searching on bugzilla is not exactly a friendly experience.
I know that bugzilla is not friendly, its a user interface is somewhat old, created for geeks that adjust fine on almost anything that you throw on them. Basic problem is how to access information, and that is exactly the same with any information system/medium. I spent time thinking how to use wiki, categories, special pages, and what not. The only conclusion is that it is linear, unstructured space that anyone can shape the way he wants. You can make article index, or use category as an index. Each has good sides, bad sides, and workarounds.
I think one of the point Michael was proposing is to have a separate tracker for opensuse patches only, so that they are all in the same place without any need to be mixed with bugs. I am not sure, but something similar might be already in use internally at SUSE (swampid stuff? can anyone clarify?).
It's to me unclear just what should go in that tracker. YaST, zypper, some scripts, what else is openSUSE specific? Maybe sample configurations (templates) that are applicable only for openSUSE? Applications should live upstream, and, unless there is a decision to branch development, like OpenOffice vs. Go Office, having openSUSE specific patches will not help maintenance. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Rajko M. a écrit :
I know that bugzilla is not friendly,
I think one of the point Michael was proposing is to have a separate tracker for opensuse patches only
bugzilla is not friendly is not a reason to make an other system that is not necessarily more friendly, but to enhance bugzilla. The main problem with bugzilla is probably the fact that the search results don't have any visible link with the words given! jdd -- http://www.dodin.net http://valerie.dodin.org http://www.youtube.com/watch?v=t-eic8MSSfM http://www.facebook.com/profile.php?id=1412160445 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Alberto Passalacqua wrote:
We have bugzilla, as Christian said. The problem is only proper selection of options when you file (upload) an improvement patch, and later when you are looking for it.
Actually bugzilla is pretty bad and confused, and it became worse with the new version. Searching on bugzilla is not exactly a friendly experience.
I think one of the point Michael was proposing is to have a separate tracker for opensuse patches only, so that they are all in the same place without any need to be mixed with bugs. I am not sure, but something similar might be already in use internally at SUSE (swampid stuff? can anyone clarify?).
Hi, swamp (http://swamp.sf.net) is used to track the process of maintenance updates, but does not handle patches. Those are only stored in the build system. I think the best way to create a patch is to branch the package, apply the patch, and send a submit request after successful testing. (http://en.opensuse.org/Build_Service/Collaboration) Greetings -- "A strange game. The only winning move is not to play.", Wargames -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Nedeľa 08 March 2009 06:18:34 Rajko M. wrote:
On Saturday 07 March 2009 10:30:25 pm Michael Fox wrote:
...
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
Why do you think so? Stano -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Monday 09 March 2009 07:22:18 am Stanislav Visnovsky wrote:
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
Why do you think so?
Because svn is not writable by anyone, so contributor has to submit patch that someone will check/approve before it will be included. Though, I had in mind regular packages provided trough oss, non-oss, update and factory repositories. Someone experimenting in his oBS home directory can provide unchecked packages even without intention to do so. Users can find them and install trough http://software.opensuse.org/search . I've just searched zypper for 11.1 and there is few. The only nick I can recognize is lrupp. The other can be zypper developers as well, but I can't recognize who's behind nick. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Pondelok 09 March 2009 15:34:04 Rajko M. wrote:
On Monday 09 March 2009 07:22:18 am Stanislav Visnovsky wrote:
Zypper and yast are special case. Nothing goes in without approval. Communication on developers lists. See http://lists.opensuse.org .
Why do you think so?
Because svn is not writable by anyone, so contributor has to submit patch that someone will check/approve before it will be included.
Well, that's same as with any other "upstream" project. If you are active contributor, you can get write access. I agree, the packages for YaST and zypp are submitted in a specific way - we submit a new version instead of a package with additional patch (see http://lizards.opensuse.org/2008/11/07/yast-releases-independent-of-opensuse... releases/ for some thoughts on the matter).
Though, I had in mind regular packages provided trough oss, non-oss, update and factory repositories. Someone experimenting in his oBS home directory can provide unchecked packages even without intention to do so. Users can find them and install trough http://software.opensuse.org/search . I've just searched zypper for 11.1 and there is few. The only nick I can recognize is lrupp. The other can be zypper developers as well, but I can't recognize who's behind nick.
Yes, that's a general problem of OBS. Stano -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code, as with the build service and contrib repo code cannot be reviewed you pretty much have to trust them, personally if someone contributes to zypper i want the code to be efficient and clean and readable and not contain little nasties like potential X crashers ;)
You told me Blender has a patch tracker, but I have never seen one. Could you describe what it does? What software is used for the purpose by Blender? :-) Thanks a lot for the answer. Alberto -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hello, on Sonntag, 8. März 2009, Michael Fox wrote:
Couldn't we develop a patch tracker for those who want to help have a place to put their work so relative teams can review their code,
There's no need to develop a patch tracker IMHO - we already have enough tools in place. Just use bugzilla and add the patch as attachment. Or subscribe to the mailinglist of the project you are coding for and post it there. Oh, and please use the time saved to write a separate patch tracker for some more useful programming ;-)) Regards, Christian Boltz -- Aber genauso können mir ja auch die Grünen leid tuen. Da bin ich doch lieber blau ... [Konrad Neitzel in suse-linux] -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Fri, 2009-03-06 at 09:53 +0100, Andreas Jaeger wrote:
On Thursday 05 March 2009 17:43:40 Henne Vogelsang wrote:
Hi,
on 03/05/2009 05:13 PM Alberto Passalacqua wrote:
as anticipated elsewhere I'm putting together a wiki page to collect
Why don't you improve
We can abandon it in the end or migrate stuff from there - or merge the two.
But you bringing up the page points out the problem that Alberto has: It's difficult to navigate the wiki...
Andreas
I also think we need to figure out a softer word to use than "task". When people are new and looking around, we want them to feel motivated and special to volunteer to perform a function. Seeing "task" as they walk in the door makes them walk in the opposite direction. I personally don't like going to pages called tasks unless I'm already part of the particular project. -- Bryen Yunashko openSUSE Board Member openSUSE-GNOME Team Member GNOME-A11y Team Member -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
I also think we need to figure out a softer word to use than "task". When people are new and looking around, we want them to feel motivated and special to volunteer to perform a function. Seeing "task" as they walk in the door makes them walk in the opposite direction. I personally don't like going to pages called tasks unless I'm already part of the particular project.
That's why I thought to "Geeko wants you!", which is something funnier and well, involves openSUSE mascotte...always nice ;-) A. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Friday 06 March 2009 09:36:35 am Alberto Passalacqua wrote:
I also think we need to figure out a softer word to use than "task". When people are new and looking around, we want them to feel motivated and special to volunteer to perform a function. Seeing "task" as they walk in the door makes them walk in the opposite direction. I personally don't like going to pages called tasks unless I'm already part of the particular project.
That's why I thought to "Geeko wants you!", which is something funnier and well, involves openSUSE mascotte...always nice ;-)
A.
Don't forget prominent link from "Tasks" to "Geeko wants you!". Someone looking what to do will most likely use "todo" or "task" as a search word. I just created redirect from "Todo" to "To do", so that users looking for "todo" land on existing page. Also we have http://en.opensuse.org/How_to_Participate linked from front page. That would be the first place where someone that is looking how to help would go. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (12)
-
Alberto Passalacqua -
Andreas Jaeger -
Bryen -
Carlos E. R. -
Christian Boltz -
Henne Vogelsang -
jdd -
Michael Fox -
Rajko M. -
Rémy Marquis -
Stanislav Visnovsky -
Thomas Schmidt