Hello Mates,
I would like to inform you that the Etherpad for the openSUSE Medical
IRC Meeting (July) is now available at :
http://ietherpad.com/Mo5jljnvcd
Feel free to express your opinion , or add your topic.
Recommendation : PLEASE ADD YOUR TOPICS UNTIL FRIDAY 22/07/2011 17:00
UTC/GMT + 3 hours , SO AS THE MEETING TOPICS BE PUBLISHED IN THE NEXT
WEEKLY NEWS ISSUE (185) !!!!
Regards ,
Rousinopoulos Athanasios-Ilias
openSUSE Medical Project Leader
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi everyone,
The weekly report is much later this week as I'd been focused on getting the Mid Term report completed. The ToDo List is finally nearing completion (well it's finished but I want to tweak it a lot more).
You can as always find the report at [0] and the text is below. I recommend reading the blog post as it has screenshots showing off the ToDo List :).
---- Report Text ----
In addition to the Midterm report that I've previously posted I'd like to update everyone on what I've been getting up to since.
The ToDo Lists feature has all of the basic functionality I wanted it to have, which includes setting individual dates for bugs and setting the completion state. I've also spent time going through my code and cleaning up so I can move on and work on merging this work with the New Comments Dialog work and hopefully getting that work merged into master. Once all of that is completed I will move on to working on the Cloud Sync features and researching QML. The ToDo List represents the last real planned addition to Entomologist but it doesn't mean I'm going to slow down or stop doing work now. I want to see the Cloud Sync integrated and I think adding QML support for adding new tracker types would be awesome.
The primary concern for me at the minute is testing the current iteration of the ToDo list across all 3 platforms and making sure that any major problems are resolved.
Plan for the next week (Which is 3 days now!): Finish the ToDo list and then merge it with the New Comments branch and work out all of the inconsistencies between these two branches.
[0] - http://wp.me/pjdJf-5a
thanks,
David Williams
Entomologist UI Changes.--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
[snip]
>>> There also has been some
>>> extensive discussion on openFATE, see for example
>>> https://features.opensuse.org/query/tag?tag=scientific
>>
[snip]
>>
>>> Best regards!
>>> Vojtch
>
> Hi
>
> I am doing research in digital communications and embedded systems. I have the
> same feeling that some packages need to be added to openSUSE (e.g. aigaion
> (bibliography management) or IT++ (signal processing)). Maybe a wiki page
> would be a start in order to list and vote software that could be added to
> openSUSE. This could be a good way of advertising less known software useful
> for scientists.
Yes, that sounds like a good idea, and I guess the openfate page Vojtěch
pointed is a good starting point, especially
https://features.opensuse.org/309007
where some people have already listed a bunch of desired packages.
The page already contains a growing list for popular scientific
software. I just added there packages I would like to see in openSUSE.
Maybe you would like to add your wishes there as well?
The question is how to proceed with the voting for packages question,
since it is probably unreasonable to vote for "Yes, I want to have the
150 packages in opensuse" since some people has to do some work then,
concerning especially those package which have not been packaged yet at
all in OBS. Lots of things to discuss :)
Kind regards
Andre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOJIctAAoJEA79ggnbq9dmUTMH/34GFN+BDtqtTbqzTzYHynrZ
CavEs0033/NHkqO23JqXPWZ0ks2x8O0cn5gWsQdkK+Nouomg/agvHtQU0rXt5tcr
1s/Jc/4JH4QJbGBh/YZu/I6S+NP4zL9BFGdkIrbhEYABZyEJ7nNxUsG5xcEuZRNo
nBMcF8iB1AULH3cl7uWqcuxaCdPqxlTYVfxUfxvPM6cPxQFAfrnf61Hvs56XErBi
+6nj1fx9PGxPqwOFcquhsQNLthtWpGceoIbTXGn5wTapxAv3M9stJrrC4ewAca/S
Xo5K9cR4jZOxmoYotT7hKpqfnbpBwSTYTBMb3DDtXNvwBfDXmA7LVaMsKCUik64=
=RzqY
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/18/2011 06:02 PM, Vojtěch Zeisek wrote:
> Hi
>
> Dne 18.7.2011 17:34, Andre Massing napsal(a):
>> Hi there!
>
>> I just want to quickly check whether there is a general interest for a
>> get together at the oSC of people working with scientific computing (SC)
>> software and openSUSE.
>> A motivation behind this is to discuss how to improve opensuse as
>> platform for scientific computing. I am in general very satisfied with
>> my shortterm experience of openSUSE, including tumbleweed, but I after
>> my recent switch to this distribution I discovered that quite some
>> packages which are interested in my SC corner are either outdated or
>> not available in the *official* repos.
>> Some of these are:
>
>> openmpi outdated (1.2.8)
>> libatlas (none)
>> mayavi and enthought related packages (none)
>> python-scipy (none)
>> paraview
>> petsc,trilinos, armadillo (none)
>> netgen, tetgen, triangle (none)
>> bullet (none)
>> cgal, gts (none)
>> scientific python (none)
>> suitesparse?
>
>> Some of these are spread over different projects like Science and
>> Education, which results in a significant overlap of packages with
>> different version numbers, possible incompatibilities etc.
>
>> So an idea might be to talk about how to improve the situation, software
>> which might be interesting to package (maybe even trying to start a
>> unifying SC project) or about what else comes into your mind!
>
>> As I said that are some first thoughts and I am looking forward to
>> hearing any comment, suggestion etc.
>
>> Cheers,
>> Andre
>
> I'm biologist, so I'm also highly interested in this question, although
> I'm not developer (I help with translations and bug reporting). Just to
> remind, there are two important mailing lists for those topics:
> http://lists.opensuse.org/opensuse-medical/ and
> http://lists.opensuse.org/opensuse-edu/
Thanks for the pointers. I subscribed to them as well and will forward
the message to those. I recognized a very low traffic on the Education
ml, is that project still active? And what about the science project?
> There also has been some
> extensive discussion on openFATE, see for example
> https://features.opensuse.org/query/tag?tag=scientific
Oh, great, I was thinking about opening such a feature request, thanks
for pointing that out, I will add a list of missing interesting software
there.
> I personally use R (incl. Rkward and so on), a lot of software written
> in Java (hehe, is there real need to package it?;-)
> and easy C binaries.
> Also software like KBibTeX and so on. Some software is in repos like
> Science, Education, devel:/languages:/R:/ (not so much there at all), ...
> So I'm interested in such activity, but I'm not sure how much I can
> help. :-)
Well, that it would be one purpose of a BoF :) Are you planning to
attend the conference?
Cheers,
Andre
> Best regards!
> Vojtch
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOJGwAAAoJEA79ggnbq9dmAmoH+wXcwD886ZVwcsw/S5ki17IN
VyTyU6q1X48OdKT4IC3ANOrilDoRGVdhkg947N1pYncn+mWThgU9ft5M1VfFfBSw
oRGE9mPMdPYhHUUH+mW24B0OFO2DHYwb4Eqd2RObAnRdEWwPSZUwWSnypBXtKkqC
qJiAxwYkPnCg7exJt28BnCjpuq1HzFAor+j1yjj/WjyRKmJ804eH3pUN2ay56YU0
LxrIXsAPrRFq/C5qY+0xlyKRi3Ta+DWmGjwCrQl8bx0YIk8dn+Nfyi8F6GYjiEpy
VVEJsoD5bHMFhOtxmyQQSbfsVbZZZo6N5Bj3RWF8E1m8Zww2S7pzXu+RLb8xeW8=
=chuN
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there!
I just want to quickly check whether there is a general interest for a
get together at the oSC of people working with scientific computing (SC)
software and openSUSE.
A motivation behind this is to discuss how to improve opensuse as
platform for scientific computing. I am in general very satisfied with
my shortterm experience of openSUSE, including tumbleweed, but I after
my recent switch to this distribution I discovered that quite some
packages which are interested in my SC corner are either outdated or
not available in the *official* repos.
Some of these are:
openmpi outdated (1.2.8)
libatlas (none)
mayavi and enthought related packages (none)
python-scipy (none)
paraview
petsc,trilinos, armadillo (none)
netgen, tetgen, triangle (none)
bullet (none)
cgal, gts (none)
scientific python (none)
suitesparse?
Some of these are spread over different projects like Science and
Education, which results in a significant overlap of packages with
different version numbers, possible incompatibilities etc.
So an idea might be to talk about how to improve the situation, software
which might be interesting to package (maybe even trying to start a
unifying SC project) or about what else comes into your mind!
As I said that are some first thoughts and I am looking forward to
hearing any comment, suggestion etc.
Cheers,
Andre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOJFJuAAoJEA79ggnbq9dmZvAH/RnGBzM1Gxjhyo7fJJo2+gGC
CJDzdg0T7OHcQUl588lQiVJrayFrUbs9mSddm0DG6XVrBIndJc2OTEuRZhBeBbka
BtQbzdDKPLDyRSZ301OS4KCkDzdzEDuGunwtQ5svA5tOgEx7EDfjuwMSV9UmdQR/
4qoTNG/du88YcKM3dk2odFBwOpm5lU6wEqA06Aw/CaR2TB8mIszilvNZdx/9Ic5y
CYkz/TMXWvqGglQoy+y+12poJ9olZj0B3wAStfB78/9aLeNUT5YMWfW5ogo9cehW
T7lAJZlJeITh7eico12BJNq5wBNzHmb6BE8NewGjbfCtaT/NieLJH7FnTvyqk2Y=
=Y7Gq
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi all,
Let me start with the important part:
===========
We want you to THINK MORE ABOUT YOURSELF AND YOUR WORK for this openSUSE
conference. What do YOU want to accomplish? What does YOUR team need to talk
about? What features should be finished? What decisions should be made? Use
the conference for that!
PLEASE SEND IN BoF PROPOSALS for oSC! They take no preparation and barely any
work as 'leader' - it's just an informal get-together. Yes, you can do that
over dinner too, but - nobody takes notes, lots of beer... A BoF is NOT any
more formal than a dinner meet but it does ensure the participants are
focussed on the discussion, not the food, and sober ;-)
Sending in a BoF proposal ensures you get a room for 40 minutes with no
strings attached. And you never know who suddenly shows up and happens to be
willing and able to take on some work!
Aside from BoF's, we love more workshops and hack sessions. How about a hack
session to fix up one or two modules in YaST. Or fix some kernel bugs. Or get
a bunch of perl updates packaged. Or, to get more people working on your
stuff, a workshop "hacking on YaST". A workshop "porting your app from sysv to
systemd"...
Register your session here: http://bit.ly/nsycEP
============
About the oSC deadline:
Last monday the deadline for the oSC CfP was extended. We had a fair number of
submissions already but the "interactive" proportion of sessions wasn't what
we hoped.
I'm sure that's partially due to lack of clarity about what we want, so let me
try to explain a bit here too.
We want to get more 'work done' at oSC. And focus more strongly on openSUSE.
The last conference had many non-openSUSE people and the results were great -
but for openSUSE it wasn't what it could've been.
Now many of us get together only once a year at the conf and we could do more
than listen to talks, have dinner and drink beer. That's why we want more BoF
sessions (essentially team meetings), workshops (eg teach to package better,
or test, or ...) and hack sessions (get together and do work).
Each of these sessions we'll try to explain more. The BoF was explained a few
weeks ago [1] and today the workshop will get some attention [2]. Next week I
hope to get something out on how to efficiently do a hack session.
Be sure to read http://news.opensuse.org regularly and send in your proposals
here: http://bit.ly/nsycEP
Cheers,
the CfP committee and the Conference team
[1] http://bit.ly/lIzf5E
[2] on http://news.opensuse.org around 17:00 EU time
Hi all,
The following is the mid-term report for the SSC (Suse Studio
Comandline Client) Project
Tasks completed;
* Framework for the command line client including argument parser and
handlers for the various accessible "objects"(repos, packages, files,
templates) in Suse Studio.
* Directory management utilities: The app requires the creation and
management of an appliance directory for local caching of changes
until ready to be pushed to Studio.
* Test suite for those actions that are independent of the web API
Tasks to be completed:
* The update, status and commit commands: These would be the commands
that make use of the locally cached information from the appliance
directory. This is the last remaining feature in the app.
* Integration tests: Tests that include requests to the web API.
Without tests of this nature it is not possible to affectively test
large portions of the app.
* Documentation: code level and sample use cases.
Please do checkout the code [1] and do a '$ rake install' to install
the gem. You can then try '$ ssc help' to see the usage instructions.
Thank you.
[1] http://gitourious.org/ssc/ssc
--
Ratan Sebastian
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi all:
I've finished my term exams last week, and here is the link to my
third project report:
http://verybin.tumblr.com/post/7754467930/weekly-report-5
if you have any suggestion or comment, please do not hesitate to send me:)
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi,
here's a small summary of the 8th (coding) week. This week I spent
most of my time with rewriting the working copy code.
Done:
- added support to add and delete packages
- added some "abstractions" for the tracking file format:
currently packages and files are tracked in a xml file
- thought about the package update algorithm. Basically
it'll work like this (simplified version):
- perform update in a tmpdir (phase 1)
- if the tmp update finished, copy/rename all files to
the wc (phase 2)
Advantage:
If the update is interrupted in phase 1 the wc wasn't touched
at all and nothing should be broken.
If the update is interrupted in phase 2 the wc is _inconsistent_
but a subsequent "update" call can resume the update and everything
should be consistent again (in this case only files are
copied/renamed (no remote access is needed))
TODO:
- implement update + commit algorithm
If everything works as expected most parts of working copy code
cleanup should be finished after this week.
Marcus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi all,
A bit of a reminder as well as a thank you for the page about upcoming
features for openSUSE 12.1. I saw some people have added some features, which
is great! If you want to talk about openSUSE 12.1 and what is coming, use it:
http://en.opensuse.org/openSUSE:Upcoming_features
If you KNOW what might come or are working on something, OR can fix something
- please do!
Cheers,
Jos