August 2012 - openSUSE Project - openSUSE Mailing Lists

Re: [opensuse-project] Getting OpenSUSE community together
by Richard Brown 10 Aug '12

10 Aug '12

> How does the idea sound like to you? Interesting, I do like the idea of better exposing the tools and facilities we already have in the hope that it will encourage their use. > Your always thoughtful ARTWORK TEAM Did I miss an artwork team meeting where we agreed on this idea? If not, I don't think you should be signing in the name of the team - not exactly the best foot for community relations.. Richard / Ilmehtar on IRC >>> Eugene Trounev 08/06/12 9:34 PM >>> Dear OpenSUSE, As a part of an ongoing effort to make our distro better visually and user experience-wise we have come to a realization that things would be much easier if we had some sort of a unified community tool (or a set of those) to help us widen our outreach. We are aware that there is already SUSE Connect, as well as an abundance of various mailing lists and IRC channels. However, few of our users actually know about those, or actively use them. So the idea so far is to make a desktop application which would ultimately bind all those services together into a sort of a single SUSE account (just like the service available in by Ubuntu, and OSX). So far this is just an idea and we need your input to see just how far can we take this and just what exactly we should be looking into in terms of functionality. So the brief description so far is this: "A desktop application connecting the whole of openSUSE fandom into a single network in order to widen the community, lower the communication and contribution barriers and add a unique twist to openSUSE ecosystem where every new user has an opportunity to share and communicate with other openSUSE users." Basically this should be as simple as integrating all our existing social services (Open Fate, SUSE Connect, mailing lists and IRC canals into a single easy to use "Control Centre". How does the idea sound like to you? What would be advantages of this effort? What would be the drawbacks of it? Would you create yet another account for our openSUSE social services? Your always thoughtful ARTWORK TEAM-- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

5 5

[opensuse-project] Re:
by Single Dating Online 09 Aug '12

09 Aug '12

Meet Hot Singles Online Largest Casual Dating Site In The World Speed Dating & Hookup Tonight No Cost To Join Now! http://hailey91.info/goto.php You will not get anymore of our emails if you go here: http://natalie555.info/unsubscribe.php?email=opensuse-project@opensuse.org This email and any files transmitted with it are personal and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. 1502 Redfield Road, Riverside, California, CA, 92507 USA -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Getting OpenSUSE community together
by Eugene Trounev 08 Aug '12

08 Aug '12

Dear OpenSUSE, As a part of an ongoing effort to make our distro better visually and user experience-wise we have come to a realization that things would be much easier if we had some sort of a unified community tool (or a set of those) to help us widen our outreach. We are aware that there is already SUSE Connect, as well as an abundance of various mailing lists and IRC channels. However, few of our users actually know about those, or actively use them. So the idea so far is to make a desktop application which would ultimately bind all those services together into a sort of a single SUSE account (just like the service available in by Ubuntu, and OSX). So far this is just an idea and we need your input to see just how far can we take this and just what exactly we should be looking into in terms of functionality. So the brief description so far is this: "A desktop application connecting the whole of openSUSE fandom into a single network in order to widen the community, lower the communication and contribution barriers and add a unique twist to openSUSE ecosystem where every new user has an opportunity to share and communicate with other openSUSE users." Basically this should be as simple as integrating all our existing social services (Open Fate, SUSE Connect, mailing lists and IRC canals into a single easy to use "Control Centre". How does the idea sound like to you? What would be advantages of this effort? What would be the drawbacks of it? Would you create yet another account for our openSUSE social services? Your always thoughtful ARTWORK TEAM-- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

12 19

[opensuse-project] Upstream Tracker - Weekly Report
by N B Prashanth 08 Aug '12

08 Aug '12

Hi, Progress last week: 1. Implemented DEHS import. DEHS watch files can now be used to track upstream versions. 2. Optimized CustomURL support. Supports HTTP, FTP and Sourceforge. 3. Added Multithreading and Job Queue support. 4. Added paper trail support with a history table for each record. Each row displays a previous version of the record and contains a revert button. What's left: 1. Security. Reverting and deleting records should only be done by site administrators. However, anyone can add new records and update existing records. 2. Minor UI updates. 3. Documentation. -- 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

1 0

[opensuse-project] [gsoc] osc2 client - summary of week 11
by Marcus Hüwe 07 Aug '12

07 Aug '12

Hi, here's a small summary of the 11th (coding) week. Last week I worked on implementing the new commandline interface. While doing so I faced several "issues": * How to combine argparse and our oscargs url-like syntax? Basically we have to run our oscargs parser on the result which is returned by argparse.ArgumentParser's parse_args method. The problem is that both parsers have a different "syntax" that is using a naive approach will lead to some redundancies (we specify the ui twice: one time for argparse and one time for oscargs). In order to avoid this we need some "interface" to which the oscargs syntax is passed and which configures the argparse parser accordingly. * How to support custom commands? We also have to provide an "easy" way to specify custom commands. Additionally it might be handy if existing commands can be enhanced (either by adding additional options etc. or by adding a new subcommand etc.). The best would be if the user simply drop his/her plugins in a specific directory and osc will scan this directory and use the new plugins/commands. * Specifying the ui programmatically is somehow confusing/cluttered. It would be much better if the ui can be specified in a more "declarative" way without the syntactic "overhead" (well that's a bit exaggerated) which is needed to configure the parser. Additionally it would be nice to have a convenient way to specify a multi line description for a command (hardcoding the str into the source makes the code "harder" to read). Finally I ended up with a small DSL which can be used to specify the ui in a "declarative" way (the initial idea + syntax is taken from the django framework (see [1])). Example: Assume we want to implement a request command which consists (for the sake of simplicity) of 2 subcommands "list" and "accept". This can be specified like the following: # file: osc/cli/request/ui.py class Request(CommandDescription, OscCommand): """Show and modify requests.""" cmd = 'request' class RequestList(CommandDescription, Request): """List requests. By default open requests for a specific project or package will be listed. Examples: osc request list api:// osc request list api://project osc request list api://project/package """ cmd = 'list' args = 'api://project?/package?' opt_user = Option('U', 'user', 'list only requests for USER') opt_group = Option('G', 'group', 'list only requests for GROUP') opt_state = Option('s', 'state', 'list only requests with state STATE', choices=['new', 'review', 'accepted', 'revoked', 'declined', 'superseded'], action='append') func = request_list class RequestAccept(CommandDescription, Request): """Accept a specific request. ... """ cmd = 'accept' args = 'api://reqid' func = request_accept In order to add the request command it is sufficient to add an import osc.cli.request.ui statement to the main cli module. This produces the following output: marcus@linux:~/osc2/osc/cli> python cli.py request -h usage: cli.py request [-h] {list,accept} ... Show and modify requests. positional arguments: {list,accept} list List requests. accept Accept a specific request. optional arguments: -h, --help show this help message and exit marcus@linux:~/osc2/osc/cli> and marcus@linux:~/osc2/osc/cli> python cli.py request list -h usage: cli.py request list [-h] [-s {new,review,accepted,revoked,declined,superseded}] [-G GROUP] [-U USER] api://project?/package? List requests. By default open requests for a specific project or package will be listed. Examples: osc request list api:// osc request list api://project osc request list api://project/package positional arguments: api://project?/package? optional arguments: -h, --help show this help message and exit -s {new,review,accepted,revoked,declined,superseded}, --state {new,review,accepted,revoked,declined,superseded} list only requests with state STATE -G GROUP, --group GROUP list only requests for GROUP -U USER, --user USER list only requests for USER marcus@linux:~/osc2/osc/cli> How does it work? First of all each class which defines a command or subcommand has to inherit from class "CommandDescription". If a subcommand is to be defined it also has to inherit from the "parent" command (that is in our example "RequestList" and "RequestAccept" inherit from class "Request" (which in turn inherits from class "OscCommand" (from this class all toplevel commands have to inherit))). In short: with the help of the inheritance hierarchy it is possible to define a command <- subcommand hierarchy. Note: actually the classes "RequestList" and "RequestAccept" only inherit from "CommandDescription". The "parent" command base class is only needed for a "marking" purpose (it is filtered out with the help of a metaclass when the concrete class is "constructed" - I'll leave out the details for now and may write a dedicated blogpost about it). Now the remaining task is to define and implement the commands (note: we will definitely not finish the project on the "suggested pencils down" date and use the week until the "firm pencils down" date for coding...). Marcus [1] https://docs.djangoproject.com/en/1.4/topics/db/models Here's a small example how to modify an existing command: # plugins/myrequestaccept.py from osc.cli.description import Option import osc.cli.request.ui class MyRequestAccept(osc.cli.request.ui.RequestAccept): # add a new option opt_foo = Option('f', 'foo', help='foo option') This leads to marcus@linux:~/osc2/osc/cli> python cli.py request accept -h usage: cli.py request accept [-h] [-f FOO] api://reqid positional arguments: api://reqid optional arguments: -h, --help show this help message and exit -f FOO, --foo FOO foo option marcus@linux:~/osc2/osc/cli> -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] UEFI situation
by Chris Jones 07 Aug '12

07 Aug '12

17 55

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 17:00 UTC
by openSUSE Meeting Reminder 07 Aug '12

07 Aug '12

Hello all, The biweekly project meeting will be held tomorrow at 17:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=8&month=8&year=2012&ho… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, please add your question to: http://en.opensuse.org/openSUSE:Project_meeting#Questions_Section Minutes and logs of previous meetings can be found at: http://community.opensuse.org/meetings/opensuse-project/ Thanks, -- openSUSE Meeting Reminder -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] fdisk project - GSoC weekly report 10
by Davidlohr Bueso 05 Aug '12

05 Aug '12

Hi, As mentioned in last week's report, this week I focused entirely on GPT, implementing the following features: - List partitions - Delete partitions - Write data to disk - Verify data integrity (header and partitions). Now I plan on working on adding partitions and looking into supporting hybrid MBRs. Thanks, Davidlohr -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Clossing of old bugs
by Carlos E. R. 02 Aug '12

02 Aug '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have had several bugs closed withing minutes, with a copy pasted excuse, because they are reported against 11.4 and 12.2 is coming. This is demeaning! Why on earth should I care and report bugs, if nobody is going even to read them! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAlAasfEACgkQtTMYHG2NR9WjdQCffVDr3P8SZoKBAnH1V4nqo2c8 /TUAnj7JkitOnQU7jM8ymVLD/HYF7Flq =sbzB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 3

[opensuse-project] Created openSUSE-artwork group in Flickr
by Rajko 01 Aug '12

01 Aug '12

Created openSUSE-artwork group on Flickr: http://www.flickr.com/groups/opensuse-artwork/ it is open group so anyone with affinity to collect artwork for openSUSE benefit can join. Basic idea is described in this thread: http://lists.opensuse.org/opensuse-artwork/2012-07/msg00031.html Gist is a collection of artwork and some selection that will go into next release. Why Flickr: http://lists.opensuse.org/opensuse-artwork/2012-07/msg00050.html it has few tools that will allow people that are not active in other parts of openSUSE to communicate. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 2