Hi,
This is my work during last week for the Upstream Tracker Project.
1. Simplified forms for user input.
2. Added Search feature to search for Results.
3. Disambiguation page for multiple records with same name.
4. Started working on paper trail for managing version history.
This week, I plan to
1. Create a view for looking at record history and undo any
modifications. (This will be restricted to people who have access -
Username & Pwd)
2. Integrate existing Python Script to work with the Rails server.
--
Regards,
N.B.Prashanth
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi!
This is my first report of the work I'm doing on AppStream and
PackageKit / the Software-Center.
It took a little longer to write it, university is giving me a hard
time, sorry for that!
Before the SoC development started, I already familiarized with the SC
code and learned a bit more Python, which will definitely help a lot
:-)
I ported the SC from using PkClient to PkTask, because PkTask is a
much more generic interface and the thing we want to use in the SC.
Unfortunately, the SC was still extremely slow, so I applied some
PackageKit-tricks to make it over 420% faster, I introduced some new
PK API for that.
Still this was not enough: If you install software, you are - due to
PK's design - unable to also query package details, which makes it
impossible to view application details while installing stuff. This
makes using the SC a pain and also has some problems when it comes to
searching stuff.
In the last two weeks, I discussed all these issues with Richard
Hughes, the PackageKit maintainer. I wrote a prototype of a SQLite
based package-cache, which will make querying data super-fast and will
make it possible to do this in parallel to PK transactions.
First, the cache was super-slow, but with some optimizations in
PkPackageSack routines, it now runs with acceptable speed so we can
use it. I also found some other optimizations together with Richard,
which will make PK itself a lot faster on some operations. (it will
save from a few msecs up to 10secs, depending on what you're trying to
do)
In the process of talking about changes and reviewing patches and
suggestions, Richard decided that it's time now to _really_ break
stuff and make it more sane. So right now we're doing a new PackageKit
0.8.x series, which will contain lots of cool improvements, not only
relevant for the stuff I want to do, but also for other new features,
like systemd-offline-upgrade.
My changes are already merged upstream and I will do a public API to
access the cache now, after discussing that upstream. Also, there are
some other changes on PKs DBus-API I and some other people would like
to have, discussion is going on there right now.
We're also improving backend interaction and broke plugin API, so
there's lots of stuff going on right now which will make developing a
SC based on PackageKit a lot easier.
At time, all PackageKit backends are broken and there's lots of stuff
which needs to be fixed and even more to be discussed.
Doing cross-distro-work is sometimes even more discussion than coding,
but I am certain right now that we will have a usable AppStream
Software-Center with the end of my SoC project.
If you read through this now, I'd like to ask you if you have anything
you want to do with PackageKit (which is not very backend-specific)
and haven't been able to do until now. - If there is any of these
issues, we might now be able to fix it.
Next steps are even more discussion and work on PackageKit to get the
API right, as well as some changes on SC and probably a C++
implementation of AppStream Xapian generator, so other implementations
of an AppStream-SC are possible (hey, KDE!) and we can use it even
without the SC.
Also, backend developers, please fix your backends soon! I want to
find people responsible for the Zypper backend, so they can take a
look at it and adjust it to our changes. (I have no knowledge about
Zypper, and developing in a VM is a pain, but I could of course make
some changes by myself later, if the basic stuff is working)
Test results about overall performance is helpful too.
--
Overall the start of this SoC was promising. First after experiencing
the first issues, I thought it might become extremely difficult to
complete this project, as there were many issues to work around, but
now problems are solved and we're really doing amazing stuff! Working
with Richard and the PK crows is a pleasure, as always and very
productive.
I'm looking forward to the next weeks, as everything is now working as
planned again. :-)
(Especially I need feedback from other distributions later)
Thanks,
Matthias
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Dear openSUSE people,
Right now, the openSUSE Travel Support team helps you out with travel
costs for representing openSUSE at events. From now on, the team will
also reimburse booth costs and marketing material costs up to a limit.
We'll be able to support expenses up to € 100 in Europe or $ 100 in
the US and everywhere else. You can use this to print stickers,
t-shirts, flyers and many other things in addition to the materials we
can send you with the DVD’s.
There are many materials available in our github repository on
https://github.com/openSUSE/artwork - feel free to modify and improve
any of that and submit changes back to our repo!
The process will work the same way as the Travel Support: you let us
know in advance; we agree on an amount and you get the money back
based on the receipts. More info:
http://en.opensuse.org/openSUSE:Travel_Support_Program
The process:
* Send the request to travel-support(a)opensuse.org
* Tell and show us what you want to produce, why and for what event.
* Wait patiently to get questions or suggestions about your request
* Any extra information can be required, please provide it asap
* Expect a confirmation of your approval, or if it's taking too long,
feel free to ping any member of the committee
The reimbursement process:
* After the material produced take a picture from what you did.
* Send the receipts, pictures and form filled to travel-support(a)opensuse.org
* The receipts submitted for reimbursement must contain the itemized expenses
We’re happy to improve on our support for the ambassador activities
for openSUSE and welcome any suggestions for further improvements!
Thank you for your support,
The Travel Support Team
--
Izabel Valverde
openSUSE Travel Support Program
http://en.opensuse.org/openSUSE:Travel_Support_Programhttp://news.opensuse.org/
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hey all,
If you think there's something cool coming in openSUSE 12.2 which deserves
some attention of press and users, add it to this page:
http://en.opensuse.org/openSUSE:Upcoming_features
If you notice something there which is wrong - please fix it!
Note that you don't have to be a developer or packager for either of the
things above - if you're an user reading this list but you happen to know
of something that's new and missing, just add it!
Links to explanations of the feature or new or much improved package are
appreciated. We'll use this page for the release announcement and articles
about the new release.
If you want to help with anything around promo, tell us on the opensuse-
marketing list!
Let's make 12.2 rock. And let's make sure the world KNOWS it!
Hugs,
Jos
Hi,
So, what's been done this week:
- Sent a patchet that gets rid of a good number of global variables and
uses them from function parameter, preparing for device topology and
geometry integration.
- Implemented device topology discovery in the internal API - some
regressions were introduced handling physical and logical misalignment,
this is currently being worked on. I'm hoping to send out the patchset
by today.
- General cleanups.
Thanks,
Davidlohr
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
