Great news, the Cloud and Env&Stacks working groups have heard us and
added some of our use cases to their F21 PRDs!
Here are two great opportunities for folks to lead collaboration between
the Big Data SIG and working groups...
https://fedoraproject.org/wiki/Cloud_PRD includes,
Requirement #4: Needs for Big Data Image
Since large and complex data sets that are difficult to process using
RDBMS and traditional data processing tools are now common, and the big
data open source big data ecosystem is now quite mature, we ought to
provide a ready-to-go image for these usages. Hadoop and its ecosystem
is clearly a key player and the Big Data SIG is working to bring it on
Fedora. Should. Real-time analysis is also growing, and components like
Spark and Storm are also something we'd like to include.
https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document
includes,
Persona #1: Alan the Big Data analyst
Alan is a Big Data analyst and member of the Fedora Big Data SIG. He
uses a number of applications written in different languages to perform
the data analysis. He wants to focus his time and effort in the
application and the actual data analysis. He want to minimize the time
and hassle spent obtaining, compiling, packaging and maintaining the
applications that he needs. The form of packaging (rpm, deb, npm, other)
isn't as important to him.
Problem statement: Currently, there is a lot of hassle and pain in
dealing with non-primary (i.e. C/C++, Python, Perl) language stacks in
Fedora. Although Alan wants to focus his time in the application and the
actual data analysis, he too often finds himself spending time managing
the language-specific toolchain needed by the application.
Cause #1: The upstream application authors usually assume that any
developer would just be using the language-specific packaging ecosystem
rather that also taking into account the downstream distribution-based
packaging and dependency management systems. This is a problem since
there are many differences between language-specific packaging
ecosystems and the Fedora way of packaging software.
Cause #2: Many upstream applications use very brittle versioning. In
other words, each application expects the user will be able to have its
particular versions of the runtime, compiler and libraries available.
Example #1: Applications written in Scala require different versions of
Scala, some need v2.9 and some need v2.10. Although Fedora could provide
both versions in the same release (via SCLs or by manually maintaining
two Scala packages), they would both need to be resolvable via Apache
Ivy, rather than just providing both binaries, "scalac29" and
"scalac210".
Example #2: The version of Jetty in Fedora does not work with Java 6 and
the Apache Hadoop upstream isn't ready to abandon Java 6 yet. So the Big
Data SIG ends up maintaining a patch to Apache Hadoop for Jetty 9 that
will live purely in Fedora for quite a while to come. Although this
could be worked-around by using compat packages for Jetty for a couple
of Fedora releases, it just hides the fact that there is a mismatch in
expectations between Fedora and upstream application authors.
Example #3: Node.js has its package/dep management tool available in
Fedora, but very little of the language ecosystem / base libraries are
packaged and available in Fedora.
Possible solution: Fedora would need a way to provide language-specific
ecosystems in a way that aligns with how these language itself are used
and applications written in them are developed and distributed.
-------- Original Message --------
Subject: FESCo announces acceptance of Fedora.next PRDs
Date: Tue, 4 Feb 2014 11:21:46 -0500
From: Bill Nottingham <notting(a)redhat.com>
Reply-To: devel(a)lists.fedoraproject.org
To: devel-announce(a)lists.fedoraproject.org
Recently, as part of the Fedora.next effort, FESCo has accepted the PRDs
from
the following Working Groups:
- Workstation
https://fedoraproject.org/wiki/Workstation/Workstation_PRD
- Server
https://fedoraproject.org/wiki/Server/Product_Requirements_Document
- Cloud
https://fedoraproject.org/wiki/Cloud_PRD
- Environments and Stacks
https://fedoraproject.org/wiki/Env_and_Stacks/Product_Requirements_Document
FESCo would like to thank all the members of these working groups, and all
those that have contributed to these documents, for all their time and
effort on creating these on short notice, with next to no requirements,
while
still doing their other Fedora work. Thanks to the all the contributors
that worked on this process.
We are now ready to move on to concrete technical plans for how the
products can be created, tested, distributed and marketed. Help Fedora
dream big and we can work with our infrastructure, QA, releng, websites,
design, translation and marketing teams to do great things for Fedora
21. We encourage those interested in these areas to check out these links
and participate in these communities and discussions, as we work together
to make Fedora the best it can be.
Bill Nottingham, on behalf of FESCo
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce