= Proposed Self Contained Change: Netizen Spin =
Change owner(s): Corey Leong <cleong at fedoraproject dot org>
A Fedora Spin for promoting and supporting internet citizenship and citizen engagement.
== Detailed Description ==
Fedora Netizen is an open source operating system for enabling internet citizens to engage with online services and communities. The goal for Netizen is to pattern the operating system's features after Maslow's Hierarchy of Needs which was published in his 1943 paper, "A Theory of Human Motivation". As a professor of pyschology, Abraham Maslow theorized that individuals attempt to experience five stages of needs starting with physiological, safety, social, esteem, and then ending with self-actualization. Beginning with the first level of physiological needs, individuals' motivational needs ascend upwards to higher levels of needs in order, however, only after establishing lower levels of needs first before ascending to the next level.
The philosophy for Netizen closely relates to Maslow's Hierarchy of Needs by establishing three primary software package levels in a hierarchical model. The first and lowest software package level addresses the need for Netizen Privacy in the areas of personal privacy, informational privacy, and communication privacy. After Netizen Privacy, the second software package level addresses the need for Netizen Security in the areas of data security, local security, and network security. After Netizen Security, the third software package level addresses the need for Netizen Engagement in the areas of publishing, education, and social engagement.
Future Netizen software package levels will address analytics, awareness, design, develop, and others.
== Scope ==
A Netizen theme is the final requirement to be developed per marketing department support of a look and feel in order to replace the current default theme. This is an isolated change.
* Other developers: N/A (not a System Wide Change)
* Release engineering: Add spin to spin-kickstarts, ensure spin has been tested, and release with rest of spins
* Policies and guidelines: N/A (not a System Wide Change)
devel-announce mailing list
I'm encountering a few problems with GCC 5 due to code that fails to
work with GCC major releases above 4. In particular, there are at least
problems with the kernel and with Coverity.
Unfortunately, downgrading to Fedora 21's GCC 4.9 is very hard in Fedora
22, unless you only care about the C compiler. This is because the C++
compiler wants a matching libstdc++, and most C++ packages need the GCC
5 libstdc++ (maybe because of the ABI changes, I don't know).
Is it outrageous to ask for a "compatibility" GCC package that declares
itself as 4.10? This is similar to how kernel 3.0 was initially
packaged as 2.6.40. Or perhaps there is another possibility that I
haven't thought of?
A year ago, I started working on a new storage library for low-level
operations with various types of block devices -- *libblockdev*. Today,
I'm happy to announce that the library reached the **1.0** milestone
which means that it covers all the functionality that has been stated
in the initial goals and it's going to keep the API stable.
Read the blog post I wrote for more information:
Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic
[Previous discussion here:
Unison is a fairly widely used file synchronization package. Think of
it as a more efficient, multi-directional 'rsync'.
Unison has the unfortunate property that versions of Unison are not
compatible with each other unless they have the exact same major.minor
release. eg. Unison 2.40.128 is compatible with Unison 2.40.102, but
incompatible with Unison 2.48.3 (the latest upstream).
The reason that matters is you might be running Unison across multiple
machines, running different Linux distros, which have different
versions of Unison.
For this reason, Fedora packages three different Unison branches in
- unison213 (currently Unison 2.13.16)
- unison227 (currently Unison 2.27.57)
- unison240 (currently Unison 2.40.128)
- There was a "unison" package, but it is retired
We don't package the latest upstream (Unison 2.48.3) at all.
For comparison, Debian packages:
- unison (which contains 2.40.x)
- unison-all, a meta-package, which pulls in all of the above
AFAICT Debian also does not package the latest upstream version.
So you can see that someone who needed to synchronize across Fedora
and Debian machines would have two compatible choices:
- Fedora unison227 <-> Debian unison2.27.57
- Fedora unison240 <-> Debian unison
Anyway, I think this situation is crazy. One reason is that in order
to add the latest upstream Unison (2.48) I'm going to have to submit a
new unison248 package. And then if there's another version, I'll
have to submit a new package for that.
I think Fedora should have a single "unison" source package, and it
should contain the multiple upstream branch sources and build
different binary subpackages. The binary subpackages would have the
same names as now (unison227 etc), making this a compatible update for
existing Fedora Unison users.
This way I only need to submit a single new package review, we can
delete the unison2xx source packages, and there'll be a single place
for unison in Fedora for ever more.
 BTW there is a COPR build of unison248 if you search for it.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
i am not sure for which package file a bug
Waiting for Bodhi for a list of packages in updates-testing (F21)...
InsecurePlatformWarning: A true SSLContext object is not available. This
prevents urllib3 from configuring SSL appropriately and may cause
certain SSL connections to fail. For more information, see
Quite a few people are going to be installing Fedora 22 in the coming
days, searching for things in the software center and not finding
their esoteric GUI tool. This is because some applications still don’t
ship AppData files, which have become compulsory in the workstation
spin for this release. Luckily, the vast majority of applications that
don't include AppData are not popular and most have little-to-no
If you want to check an application without installing F22 you can use
this link http://alt.fedoraproject.org/pub/alt/screenshots/f22/matrix.html
-- if you fix an application I'll be regenerating that status page
every 48 hours and shipping new a metadata release in a couple of