AN OPEN PROPOSAL ON openSUSE VERSION NUMBERING:
I have been giving the openSUSE version numbering issue some serious
thought lately. I have come up with an interesting solution to the issue that
I would like to propose to the community. I am in no way married to this idea
but I do feel it is the best solution out of everything else that has been
proposed.
The core idea of the model that I am proposing is to have a set of minor
number releases within an 8 month major number release cycle. I have outlined
my idea to illustrate what I mean by this.
1) Every 8 months we should launch a major version number release. This would
be kind of like Fedora does with their number every 6 months but ours would be
every 8. (e.g. openSUSE 12.0)
2) After launch, we should release a new image(GoldMaster) with the
updates/patches applied as a minor version number release, once a month for
the next 4 months. This will help people who have not installed the major
version release because of a bug to install a minor number release as bugs get
patched. Also this will help to denote stability and maturity in the release
(e.g. openSUSE 12.1, 12.2, 12.3, 12.4)
3) 2 months from the last minor number release we should release one more
minor number(this will be 6 months from the original release of our major
number)… this will mean the x.5 releases of openSUSE will earn a reputation
and respect for being very stable (e.g. openSUSE 12.5)
4) After the x.5 release we should not release any more minor number images in
preparation for our next major version number launch!
I think this model would make our 8 month cycle more competitive while
providing a more structured meaning to our version numbering and, more
importantly, maintaining an identity of our own. Also this will show the fast
development of our 8 month cycle.
Some things to consider before deciding on or implementing this for our
project:
1) The increased frequency of version numbering will mean we will have more
opportunities to make noise about our distribution in a marketing sense. Also,
the transition and change to this model will give use marketing opportunities
to ensure the FOSS community knows of the changes before implementation.
Keep in mind that more noise means more energy from our marketing team and
ambassadors.
2) This is something that CAN be done however, we would need volunteers from
the community to help with the added man power it will take to crank out the
minor number releases. Though it may take some added effort to achieve this
model, we have the infrastructure in place to help facilitate it (OBS,
openFATE, Connect, Lizards blogs, Wiki pages, Forums, etc.).
3) The frequency of the minor number releases proposed above is NOT the heart
of this proposal. Rather, it is a personal opinion on how the idea of
interim(minor number) patched releases within our 8 month cycle can look.
A NOTE: I know some will have an issue with this thinking that it abandons the
8 month development cycle but in my opinion this enhances it.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Am 12.04.2011 19:50, schrieb James Mason:
> I don't want to remove any packages; this is the same package set used
> for the downloadable ISOs, and it is important to maintain integrity
makes sense to me.
--
Kim Leyendecker (kimleyendecker(a)hotmail.de)
openSUSE Ambassador / openSUSE Wiki Team DE
HAVE A LOT OF FUN!
http://www.opensuse.org | http://www.suse.de
Have you tried SUSE Studio? Need to create a Live CD, an app you want
to package and distribute , or create your own linux distro. Give SUSE
Studio a try. www.susestudio.com.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hello-
I have put together a simple search interface to opensuse.org that uses
Google CSE by default but allows for submissions to application specific
webforms. You can find it here:
http://search.opensuse.org/
Found a bug? Want to contribute? Fork it on gitorious.org:
http://gitorious.org/search-opensuse-org/search-opensuse-org
I would like to thank Marcus Rückert and Pascal Bleser for their help.
Have Fun,
Brandon
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
The "Libre Software Meeting" (RMLL) will be held in Strasbourg in the
second/third week of july (9-14)
http://2011.rmll.info/
This is the larger international free software fest in France.
Being near the Est french side, it could be easy for openSUSE official
to come.
I hope to be able to attend. I wrote to the organisation (no answer
yet), but alone I wont do much good :-(
usually it's held in an university campus, so accomodation and food
are cheap.
I had little answers on th french list until now :-(
Josh offered to help (including with money), but we first have to have
attendees :-)
jdd
NB I cross post on project and marketting, don't knowing what is the
best list
last year web site: http://2010.rmll.info/spip.php
--
http://www.dodin.nethttp://www.dailymotion.com/video/xgxog7_clip-l-ombre-et-la-lumiere-3-bad-pi…http://www.youtube.com/watch?v=FGgv_ZFtV14
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi,
I'm Sergey Ivanov, I'd like to be a mentor for the proposal "Hot File
system Backup using Ext4 Snapshots". Freenode IRC Nick: seriv.
I work in OmniTI as a system administrator. I'd like to have good
snapshots with means to serialize the changes made on the filesystem
between them and to send/receive these from one filesystem to another
on linux. I use this every day in solaris on zfs and miss it in
linux. I was a packager in Altlinux team (dovecot, reiser4...), and
helped by testing and benchmarking filesystems.
If I need to send more details or information, please tell what and
where to supply.
--
Regards,
Sergey Ivanov
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi all,
I am writing my proposal here before uploading to the gsoc-melange
portal , please do let me know how i can further refine it:
Title: spec-cleaner redesign to make it modular and easy to extend.
Abstract:
RPM packaging is done using a build recipe , the "spec file". Spec
file authoring has been done for a very long time.
As the distribution moves to newer releases of rpm, the old spec files
(and newer ones) must be checked to make sure they use
newer macros and better spec authoring practices.
The project aims to facilitate this by further improving the
spec-cleaner project with a spec file parser, and an xml based
extension
system (to add more cleaning recipes in the future).
Detailed Description:
Background:
The project is a simple spec file checker and cleaner. The code goes
over all available spec files looking for common spec authoring errors
and replaces them
with more readable and correct code.
As opensuse moves to newer versions of rpm, older macros may be
deprecated , some shorthand used in earlier versions of the spec file
may break with newer rpmbuild.
It is not possible to manually look at each spec file and modify them.
This project aims to perform a bunch of the checking and modification
task automatically leaving the packager to look for only subtle
details, there by greatly reducing his/her workload.
Use Cases:
This project will mainly be used by the packagers (actors).
When opensuse moves to newer releases the packagers run the
spec-cleaner through all their spec files.
Spec-cleaner reports any errors along with changes made to files.
The packager can then run tests on the modified spec files to make
sure nothing breaks. He/she then rpmbuilds from the spec-files and
corrects small errors if any to make
the spec file run with newer versions of rpm.
Benefits:
The packager's time looking for common coding errors is greatly reduced.
Specification changes between different version of rpms is taken care
of automatically.
Caveats:
This is an automatic code checker and cleaner. It will not be able to
look for hacks that the packager might have employed to package a
particular software. In some cases it might regard the hack as a bad
coding practice. The packager must look for these manually and apply
necessary corrections.
Technical Details:
The Project would be divided into 3 parts:
Part 1: Read existing code and evaluate how best to modularize it. Run
tests on existing code to make sure the working and the
caveats are well understood.
Part 2: Implement the changes:
Write a spec file parser
Having done a preliminary search for spec file parsers , i
have not found any.
I have looked at python-rpm and its more of a package to
work with rpm packages than spec files, so there arises a need for
a generic spec file parser.
python-rpm and rpm in general contains a specific module
called "rpmSpecParse()" which could be isolated and used as a
parser for the cleaner, this needs further looking into.
Come up with a XML schema which is easy to understand and
easy to extend.
Adding new clean-up recipes is not very semantically
organized. A simple XML file wrapping new cleaning recipes in
appropriate tags would be more appropriate.
The rough markup could be ,
<recipe>
<rpm version>
<macro affected>
<regexp>
</regexp>
<replace with>
</replace with>
</macro affected>
</rpm version>
</recipe>
Move portions of current spec-cleaner code that are hard
coded , into separate configuration files so that they can be
modified without touching the code and also have more
semantically organized.
Part 3:
Extend available test cases and write a more if time permits.
Write documentation / augment the code written with doxygen headers.
Why me:
I have used python extensively in my projects (reference
https://github.com/face-rec-mvit/Code_PyRec )
also i am working on converting IPS (opensolaris) binary packages to
RPM, for belenix.org (here we use rpm5)
so i have a fair understanding of how the spec file is authored and
what are the available macros etc.
Also , from past projects i have worked on. I have learnt (the hardway
:( ) that "shipping" of the project must be a feature and
i will follow the same in the current spec-cleaner project and all
future projects.
Contact Information:
IRC nick: gancient (on most irc channels , freenode ,oftc)
email: kunal.t2(a)gmail.com
IM : kunal.t2 (on gtalk)
--
regards
-------
Kunal Ghosh
Dept of Computer Sc. & Engineering.
Sir MVIT
Bangalore,India
permalink: member.acm.org/~kunal.t2Blog:kunalghosh.wordpress.comWebsite:www.kunalghosh.net46.net
--
regards
-------
Kunal Ghosh
Dept of Computer Sc. & Engineering.
Sir MVIT
Bangalore,India
permalink: member.acm.org/~kunal.t2Blog:kunalghosh.wordpress.comWebsite:www.kunalghosh.net46.net
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hi,
My name is Priyanka. I am in my second year of B.Tech (Bachelor of
Technology), in Computer Science. My inclinations are
towards C, C++, PHP and Ruby-on-Rails. I am also comfortable with git.
I am strongly inclined to apply to openSUSE for GSoC. The idea that
interested me was the End-User Oriented Web Interface. Currently the
user page is extremely limited to displaying the projects the user is
a part of. I propose the following changes in the interface,
Expansion of the User Profile
------------------------------------------
* Expanding the user profile to include profiles on GitHub, Gitorious, Ohloh.
* The ability to pull the recent activity done by the user on these
websites. This would be great if the user has a couple of famous
repositories.
* IRC networks, and channels frequented.
* An 'about me' text.
* An ability for users to comment on the user activities, which
include apart from their usual activities on the build-service, other
things which have been pulled, like github commits, etc.
Karma
----------
I believe there should be a 'Karma' system on the build-service. This
would encourage users to contribute.
* For example, if a user is working on a personal repository and
pushes a bug-fix or the implementation of a new-features, he/she can
be rewarded with Karma. This Karma can be attained either by
'up-votes', or by other members donating their own Karma.
* Ohloh's statistics using their public API can be used for getting Karma too.
* Karma can be auto-assigned to maintainers of popular packages, etc.
And it all gets gelled up to be a more informative user page, which
helps people know each other more. With the user's development
activities getting space on his/her homepage, the end-users would be
able to connect with the user's open-source work. This would help add
an element of interaction to the process.
The Karma component is an essential element to this interaction
because the community recognizes an individual's effort. And we all
can do with a little praise :-)
Background Information
----------------------------------
I have already set up the development environment, I even reported a
bug in the Build Service to Sascha :-) My experience with
web-development has been using Rails and PHP for college activities
like online treasure hunts, etc. However, I am into serious
development as well. I have been working on a Q & A application using
MongoDB as a NoSQL database. [0]
The proposal is an informal one. I would be polishing it, and include
a time line, where I will be breaking the work down, as far as
possible, into atomic modules with realistic deadlines.
As frequent users of the Build Service, I would be extremely glad to
hear some suggestions / feedback on the above proposal.
Thanks & Regards,
Priyanka
[0] https://github.com/priyanka-m/ask
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Hello opensuse-projects!
I learned just today that I won't have a lot to do in summer. So I
want to try and commit myself to open source and openSUSE!
I have put up a preliminary application at
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/nei/1
The project that I'm talking about is a convenient way to update and
install packages on a "offline" openSUSE box. (Of course the
intermediate step with an "online" computer is unavoidable if you
don't want to mirror all the repos for offline usage. Also, I have the
feeling that this might already exist somewhere but I haven't found it
yet :-) )
I'm hoping to see if anyone is interested in this project or thinks
that this would be useful. If so, I'd also be lacking a mentor ;-)
Looking forward to feedback!
To introduce myself, I've been using SuSE some time back in 2001 and
since 10.2 also openSUSE. I'm mostly a user and I wrote some scripts
for personal use or for IRC. Currently a student in Leipzig, Germany.
I've been in touch with freely available source code for a while,
probably 1999 when I was working with iKonboard setting up a web
community and later on providing free tech support for phpBB, before I
switched to mostly administration tasks on then debian-based
webservers. Most of the programming work I've done happened to be in
Perl, if that has any meaning. But so far I didn't manage to get
involved in anything big.
Cheers, Nei
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Dear friends,
Henne has stepped up to organize Linuxtag attendance. If you don't get
rooms from LinuxTag, we can book for you. We all stay in the linuxtag
hotel (provided there is still room... let's hope so, otherwise henne
will try and find something else).
It works as follows:
send me an official ambassador support request for sponsoring per mail
so I have a papertrail.
send the following:
- Name (like in passport), address, phone (international!)
- if you need us to book hotel nights and how many
- if you need travel cost support, and if so, most up to date travel
costs guestimation in USD or Eur. We reimburse 80% at most!
- a short description/explanation of why you should be there - what do
you intend to contribute and what are your contributions to date
If any of that is missing I won't be able to pay :D
Please CC Henne (so he can book if it's OK'ed) and AJ.
Grtz
Jos
Hi, I've lurked around here a bit and have already submitted the first
version of my proposal, but I'd like to introduce myself to the list
also. My name is Bjørn Arild Mæland and I'm a master's student at the
University of Bergen in Norway. I've been doing a bunch of web
development through the years (mainly Ruby on Rails), and I am a
long-time Linux user. I'd love to work on dister, the Heroku-like
solution for SUSE Studio, this summer. I think it's a great project
which will increase openSUSE's attractiveness for web developers and
others.
For formatting purposes I'm linking directly to my application on
melange: http://socghop.appspot.com/gsoc/proposal/review/google/gsoc2011/bma025/1
Any comments or suggestions would be greatly appreciated.
-Bjørn
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org