I just noticed today that the gmane.linux.suse.opensuse.user group is
missing from gmane.org - did the project request the list be removed from
gmane?
Just wondering if it was intentional or if something went wrong somewhere.
Thanks,
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Of course we still see people getting this wrong on a regular basis,
but googling for "SUSE capitalization" doesn't reveal anything
helpful. IMHO we need a wiki page covering the One Absolute Truth,
and also a bit of the history behind it. I found this thread from
2005:
http://lists.opensuse.org/opensuse/2005-08/msg00377.html
but it didn't provide the full story.
Additionally,
https://en.wikipedia.org/wiki/SUSEhttps://en.wikipedia.org/wiki/SuSE
are (somewhat depressingly) two entirely different articles, neither
of which gives any real detail over the renaming from SuSE to SUSE.
Shouldn't there be a page
https://en.opensuse.org/Capitalization
or something?
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi All,
I'm hawake, i work to the Italian translation of the wiki, and I'm
writing here just to share some thoughts about openSUSE assuming the
point of view of a desktop user. In the following list i've collected
not just my suggestions and critics but also those of all my friends
that I converted to openSUSE 13.1 (after a migration from Ubuntu
13.10, which was unstable... :S ). I hope to be useful to all of you
guys contributing to make openSUSE better day by day.
I've distinguished 6 main categories.
Communication.
First of all, as pointed out in other discussions, the communication
between developers and community is fundamental. I don't want to
reopen this discussion here, i just want to tell you that many
non-expert users perceive this lack of communication because they
found ambiguous posts around the web and obviously in particular on
social networks. BTW I think that the lesson has been learned and we
(as a Community of supporters + Developers) are improving. ;)
Installation.
Installing openSUSE is not a difficult task for someone who can manage
installation of a Windows OS but during the partitioning phase there
are too many advanced options that are useless and scary for most part
of our desktop users [0]. For example, you could hide some of these
advanced options (like RAID, tmpfs, NFS, LVM and "Use Btrfs as default
filesystem") under an "Advanced options" entry, or redesign that part
of the installer so that the basic partition screen has a simpler
layout.
Software installation.
Software.opensuse.org is very nice, I think it could be useful to have
it accessible from the desktop because not all users know that it
exists (and they use untrusted RPMs found through Google...). In fact
it should be an important part of our marketing strategy.
System configuration.
There is a bit of confusing redundancy between some settings available
through YaST and through the settings manager of a DE (for instance
printer installation/configuration). We should modify the settings
manager of supported DE to tell to the user when are needed root
privileges, so that when it's necessary to open YaST. For instance the
installation of proprietary stuff for HP printers.
Help.
I think that the openSUSE Activedoc Start Up guide should be
accessible offline as default and in a simple way from desktop. For
example, take a look at Ubuntu, you go to the shutdown menu (top-right
of the screen) and you have an entry that opens a new window with the
common questions about desktop usage (Unity in this case, [1] [2] ):
video drivers, printers, information about the desktop environment and
how to use it etc.. We still have shortcuts for KDE4, GNOME3 and so
on, but they don't bring to Activedoc (which is well written) and is a
little bit confusing because they bring to the SDB or HCL (not to an
index of ready to use and problem-oriented guides). "Online help"
links yet to the Novell documentation for openSUSE 11.0 which is
translated only in german [3] and very... very outdated. So here, in
the Italian wiki, we are discussing about how we should modify that
SDB pages to allow the user to easily find solutions to common
problems but we can't modify help.opensuse.org. So it's up to you.
Interestingly the Gentoo documentation it's much more problem-solving
oriented with an index very complete, see for example [4]. I know that
pages like that one are very scary, but they collect a set of useful
key questions right at the beginning of the page. I think that layouts
like that one should be further studied (obviously not blindly
applied!) to improve the usability and accessibility of our wiki.
Other.
Last but not least, I also report here two annoying issues: SUSE
ImageWriter it is not automatically setup to use the file filter *.*
(so the unexpert user is unable to see ISO images -> read all of my
friends asked me how to use it); after the installation from the 4 GB
ISO image, YaST does not automatically disable the DVD local
repository, so the user have to handle with YaST's repository manager.
In conclusion, all of my friends are enjoying openSUSE and they are
using it both for work or study because of its stability, all DE
equally supported, YaST, Zypper and someone (like me) really
appreciate that is pure FOSS without privacy issues. Although it needs
some little refinements to the user-experience as I said before but
nothing impossible to do.
Thank you and keep up the good work! :)
Best regards,
hawake
[0] http://www.mediafire.com/view/jocz56r29yude8d/screenshot25modificata.png#
[1] http://www.mediafire.com/view/bzrrpdgxejvxy9w/screenshot21.png#
[2] http://www.mediafire.com/view/92n6youe70rmxxn/screenshot24.png#
[3] http://www.novell.com/documentation/opensuse110/
[4] https://wiki.gentoo.org/wiki/AMD64/FAQ
--
Linux user number 433087
Linux registered machine number 351448
http://linuxcounter.net/
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi all,
Last October I saw on opensuse-factory that gitorious is deprecated in
favour of github:
http://lists.opensuse.org/archive/opensuse-factory/2013-08/msg00183.html
Personally I think I agree with this move[1], but it seems that there
is still quite a bit of activity at https://gitorious.org/opensuse/ -
so please can someone confirm that this really is the general
consensus?
Either way, IMHO it would be very helpful to have an official policy
on git hosting, and the only effective way to do that is to publically
document it (on the wiki) and then announce it.
I see a few options for what this policy page could say:
1. "Please move from gitorious to github; here's how to do it, and
make sure you [leave behind a redirect|delete the gitorious
project]."
2. "We recommend that new projects should be started on github
and that existing projects on gitorious be moved but it's also OK
to keep them at gitorious."
3. "Host projects wherever you want. Here are steps for how to host
on gitorious and github."
Of course it should also clarify what makes a project "officially
openSUSE" vs. someone's personal hack.
Sorry if this is already covered somewhere and I missed it. For
example there's nothing obvious linked from
https://en.opensuse.org/Portal:Development
Cheers,
Adam
[1] github is clearly technically superior, although there is a debate
about the suitability of using a hosting service based on closed
technology, even when export/migration isn't too problematic. I
wonder what the FSF thinks about GitHub, but that's another
discussion ...
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On Friday 21 March 2014 12:19:18 Andres Silva wrote:
> Jos Poortvliet wrote:
> > There are some articles still pending for oSC14.
> >
> > First of all, the location Sneak Peek. Will publish that coming Monday or
> > Tuesday. Review welcome!
> > https://news.opensuse.org/?p=17734&preview=true
> >
> > I just published this:
> > https://news.opensuse.org/2014/03/21/help-promote-osc14/
> > You should all help out, put these things online on your blogs etc too!
> >
> > We should write a sponsorship article... If nobody picks that up, I will
> > start it next week.
> >
> >
> > Hugs,
> > /J
>
> Reviewing...
Thanks1
On Monday 24 March 2014 11:33:44 Ebrahim Al Mahfoodh wrote:
> Dear Sir/Madam,
>
> I am looking for your reply to start our process, because it take time
> process it.
Hi Sayed,
You can find most of the information on our website:
http://conference.opensuse.org
* Entree is free, paying for a ticket to support the event is optional.
You will of course have to pay for hotel and flight.
* Schedule is not finished yet but a preview can be found on:
https://news.opensuse.org/2014/03/11/sneak-preview-of-osc14-sessions/
The final schedule comes in about two weeks.
* We can provide a certificate of attendance, you can ask during
registration.
I hope this answers your questions.
Greetings,
Jos Poortvliet
>
> Best Regards,
>
>
>
> *Sayed Ebrahim Al Mahfoodh*
> *Supervisor Network & Support*
> Tel:+973 17879421
> Mobile: +973 39830060
> Email:ebrahim.almahfoodh@hajihasan.com
> *Haji Hassan Group B.S.C.(c)*
> P.O.Box 530 Manama,
> Kingdom of Bahrain.
> Website:www.hajihassan.com
>
>
> On Wed, Mar 19, 2014 at 1:13 PM, Ebrahim Al Mahfoodh <
>
> ebrahim.almahfoodh(a)hajihassan.com> wrote:
> > Dear Sir/Madam,
> >
> > I would like to register in the conference oSC14 , and I need the
> > following information to clarify the registration to take approval from
> > our company.
> >
> > 1 -Can you provide me attendance certificate
> > 2- Conference Schedule
> > 3- Conference cost
> >
> >
> > Best Regards,
> >
> > *Sayed Ebrahim Al Mahfoodh*
> > *Supervisor Network & Support*
> >
> > Tel:+973 17879421
> >
> > Mobile: +973 39830060
> > Email:ebrahim.almahfoodh@hajihasan.com
> > *Haji Hassan Group B.S.C.(c)*
> > P.O.Box 530 Manama,
> > Kingdom of Bahrain.
> > Website:www.hajihassan.com
>
> </PRE>
> <div style="font-face:arial,verdana;color:#666666;font-size:12px">
> NOTICE: This e-mail message and all attachments transmitted with it are
> intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message is
> not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any dissemination, distribution, copying, or other use of this
> message or its attachments is strictly prohibited. If you have received
> this message in error, please notify the sender immediately by replying to
> this message and please delete it from your computer. </div>
All,
Will openSUSE/SUSE have a booth or be providing any presentation at The Texas
Linux Fest in Austin Texas USA this Jul 13-14?
If you are looking for anyone to work a booth please let me know.
Thanks
Tim
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi, all,
I am a student and I like to involve in gsoc 2014. Here is my proposal .
Project goals
My goal is to add ePub format support in Atril(MATE), so that ePub
files information can be get. and the file can be easily read.
Implementation
I will divide the goal into following steps.
1. Get familiar with current Atril package, read source code and konw
how the whole thing works. And also the coding format will be studied.
2. Get familiar with ePub format by reading offical documents or read
other open source codes.
3. Integrate the ePub translator in to the Atril package. In this
period the code will be write and basic test will be performed.
4. Do test and submitting pathches, and fix bugs.
I think the most important thing is to make a good model of the ePub
files, as this can be regarded as a plug-in and the whole framework
should better not be effected too much. So I think both Atril and
popular ePub reader codes need to be read carefully.
Timeline
To be frank, I want to start this project as soon as possible. I don't
know if things will change during this summer. By now I know that I
have 1 project from my lab to be contuinue all the time, the final
exam will be at 5.15 or so, so there will be 2 week break. and I will
take 1 week travel from 6.20-6-27. I don't want to make promises to
move mountains. Here is a detailed plan.
3.20-3.30, Set up the openSUSE env stable, with necessary packages and
tools ready.
4.1-4.3, Find proper open source ePub reader software, make a list in
order to compare.
4.5 - 4.20 +/- 10, read Atril source code, find out how the things
work and list all the interfaces that deals with different kinds of
file formats (I guess there must be some commonly used interface for
different kinds of file formats)
5.1 - 5.7 , 5.15 - 5.30, get familiar with ePub format and write some
small codes to get basic ePub file informations. (This will be the
midterm evaluation check point for me) and make the 1st patch.
6.1 - 6.20, porting some other source code if possible, and if not
then try to write own codes on the ePub implementation. and test these
basic functions.
6.28 - 7.15 integrate the source code together. Do system test and
make the 2nd patch.
7.17 - 8.5 Test the program and make final patches to solve potential bugs.
8.5 - end. Prepare for the final evaluation.
About me
Hi, all. I'm suyu, a graduate student in Missouri, US and my major is
EE. I used to be a GSoC student in 2011 and worked for tianocore, in
that program I modified a text-editor and fixed some existing bugs.
I've been using C for 4 years and I like programming though I'm
studying EE not CS. Hope to do something this year for GSoC.
To be frank, I'm not very confidence with myself and I am alway
worrying about that I may not having enough time to do this. But
andway I will try to do it well.
Thanks for your time and wish I can see your response.
P.S: Sorry to submit the proposal so late, I wantted to submit a patch
before submit the proposal, but after I installed openSUSE for half a
day my grub got a mess and can only enter ubuntu(I got openSUSE,
ubuntu, and windows 7 ...), I will figure it out as soon as possible.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi, all
Is there any comments on my proposal?
Thanks and wish to see your feedback,
On Thu, Mar 20, 2014 at 6:09 PM, <sydy7(a)mst.edu> wrote:
>
> Hi, all,
>
> I am a student and I like to involve in gsoc 2014. Here is my proposal .
>
>
> Project goals
>
>
>
> My goal is to add ePub format support in Atril(MATE), so that ePub files
> information can be get. and the file can be easily read.
>
>
>
> Implementation
>
>
>
> I will divide the goal into following steps.
>
> 1. Get familiar with current Atril package, read source code and konw how
> the whole thing works. And also the coding format will be studied.
>
> 2. Get familiar with ePub format by reading offical documents or read other
> open source codes.
>
> 3. Integrate the ePub translator in to the Atril package. In this period the
> code will be write and basic test will be performed.
>
> 4. Do test and submitting pathches, and fix bugs.
>
>
>
> I think the most important thing is to make a good model of the ePub files,
> as this can be regarded as a plug-in and the whole framework should better
> not be effected too much. So I think both Atril and popular ePub reader
> codes need to be read carefully.
>
>
>
> Timeline
>
>
>
> To be frank, I want to start this project as soon as possible. I don't know
> if things will change during this summer. By now I know that I have 1
> project from my lab to be contuinue all the time, the final exam will be at
> 5.15 or so, so there will be 2 week break. and I will take 1 week travel
> from 6.20-6-27. I don't want to make promises to move mountains. Here is a
> detailed plan.
>
> 3.20-3.30, Set up the openSUSE env stable, with necessary packages and tools
> ready.
>
> 4.1-4.3, Find proper open source ePub reader software, make a list in order
> to compare.
>
> 4.5 - 4.20 +/- 10, read Atril source code, find out how the things work and
> list all the interfaces that deals with different kinds of file formats (I
> guess there must be some commonly used interface for different kinds of file
> formats)
>
> 5.1 - 5.7 , 5.15 - 5.30, get familiar with ePub format and write some small
> codes to get basic ePub file informations. (This will be the midterm
> evaluation check point for me) and make the 1st patch.
>
> 6.1 - 6.20, porting some other source code if possible, and if not then try
> to write own codes on the ePub implementation. and test these basic
> functions.
>
> 6.28 - 7.15 integrate the source code together. Do system test and make the
> 2nd patch.
>
> 7.17 - 8.5 Test the program and make final patches to solve potential bugs.
>
> 8.5 - end. Prepare for the final evaluation.
>
>
>
> About me
>
>
>
> Hi, all. I'm suyu, a graduate student in Missouri, US and my major is EE. I
> used to be a GSoC student in 2011 and worked for tianocore, in that program
> I modified a text-editor and fixed some existing bugs.
>
> I've been using C for 4 years and I like programming though I'm studying EE
> not CS. Hope to do something this year for GSoC.
>
>
>
> To be frank, I'm not very confidence with myself and I am alway worrying
> about that I may not having enough time to do this. But andway I will try to
> do it well.
>
>
>
> Thanks for your time and wish I can see your response.
>
>
>
> P.S: Sorry to submit the proposal so late, I wantted to submit a patch
> before submit the proposal, but after I installed openSUSE for half a day my
> grub got a mess and can only enter ubuntu(I got openSUSE, ubuntu, and
> windows 7 ...), I will figure it out as soon as possible.
--
Suyu Yang
Missouri University of Science and Technology
EMC Laboratory
TEL: 573-578-2968
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org