Hosted identi.ca
by Paul W. Frields
Evan, the principal and CEO behind laconi.ca and identi.ca (Control
Yourself, Inc. in Montreal), has started offering free hosted
instances to some free projects. I met Evan at Open Source Bridge in
Portland last month and he asked me if the Fedora Project would be
interested in one. I told him we would definitely love to try it out,
because of our mission of and support for 100% free and open software
and services. I believe this is their status.net service, launched
very recently.
Now that Evan says there are some of these in existence now, I can let
that cat out of the bag and start a discussion here. This would
probably involve people in Infrastructure, Design, and potentially
Websites and Marketing. The goals are to:
(1) Find someone interested from each involved team to work with the
folks at CY on getting a hosted instance established. Timeline is
flexible, but I think establishing the instance probably comes
before applying any design so we can try it out privately before
launching it as a *.fedoraproject.org service.
(2) Assuming things look good, provide a status.fedoraproject.org for
our users that includes Fedora branding.
There are some other issues involved like sponsorship that I can take
care of either personally or with the Board, but which don't really
matter in the context of this list. Details I know about the service:
* The accounts would be separate from those on the normal identi.ca
service, but people on identi.ca could subscribe to feeds from the
hosted instance, and vice versa
* The service would act as an OpenID consumer, and since FAS is an
OpenID provider, that could be sufficient to establish an account
I don't know yet how the public timelines can be combined. Obviously
we don't want to *fragment* public status information, but on the
other hand, I really like the idea of having a true Fedora Project
public timeline that's always full of relevant information. Now that
we have tools like gwibber and other software and services that allow
you to set all status at once, the risk of sequestering our
information away from the larger public are very low. We can even
write an instruction guide that would help people stay connected while
using this service.
So, who's interested in working on this?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 7 months
Licensing problems, solution strategy
by Paul W. Frields
Without a meeting today, it's probably best to bring this up on the
list.
I know that we've been reaching out to upstream to get licensing
problems fixed. The responses on the couple of threads I've seen seem
generally positive about us providing the licensing audits, and have
usually provided some idea of what's needed to fix the problem (at
least in terms of scoping out the required changes). But they don't
seem to always provide firm commitments to fixing the problems, as all
the normal IRL rules apply. In other words, the upstream maintainer
may simply be too busy to work on the solution.
I propose that we simply make the rollout a first priority. If there
are licensing concerns which must be fixed to install the application
somewhere, then module owners must fix the licensing problems
themselves (or find someone to commit to doing it within a specific
time frame). If we're able to wait for packaging until some later
time, then we install now, set a date where we will have all those
problems solved, and start the process of fixing them.
In other words, what I'm trying to avoid is blocking on upstream if
this team has the capacity to fix these problems and send them
patches.
Paul
14 years, 8 months
Fedora 12 Alpha testing update
by James Laska
Oops, wrong list address ...
I believe this might be of interest to multiple teams monitoring
progress towards the F12 Alpha milestone.
Thanks,
James
-------- Forwarded Message --------
> From: James Laska <jlaska(a)redhat.com>
> Reply-to: For testers of Fedora Core development releases
> <fedora-test-list(a)redhat.com>
> To: fedora-test-list(a)redhat.com
> Cc: logistics-list(a)redhat.com
> Subject: Fedora 12 Alpha testing update
> Date: Thu, 30 Jul 2009 11:50:30 -0400
>
> Greetings folks,
>
> Just a quick heads up to keep folks informed on F12 Alpha testing.
>
> o Feature freeze 2009-07-28
> o Alpha Test Compose (TC) 2009-07-29
> o Test 'Test Compose' 2009-07-29
> ---------------- N O W ----------------
> o Alpha Blocker Bug Day#3 2009-07-31
> o Alpha Freeze 2009-08-04
> o Compose Alpha 2009-08-06
> o Test Alpha Candidate 2009-08-06
> o Alpha Release 2009-08-18
>
> = Physical media testing =
>
> Fedora QA is currently waiting for an Alpha Test Compose to exercise a
> full installation test run [1]. However, testing prior to the compose
> has unearthed several 'test blocker' bugs. As the name suggests, these
> are issues that prevent further testing, notably they are blocking all
> (or a majority of) tests in the installation test matrix [2]. The
> current list of open 'test blocker' issues includes:
>
> * 514501 - MODIFIED - dbus.exceptions.DBusException:
> org.freedesktop.Hal.NoSuchDevice?: No device with
> id /org/freedesktop/NetworkManager/Devices/0
> * 511907 - MODIFIED - parted.Disk.duplicate exception in storage
> scan
> * 510033 - MODIFIED - AttributeError?: 'NoneType?' object has no
> attribute 'name'
> * 514718 - MODIFIED - install exited abnormally - AttributeError?:
> 'NoneType?' object has no attribute 'has_key'
>
> There is additional work underway to address installer integration with
> a recent NetworkManager version. A ticket has been filed [3] for anyone
> interested in monitoring the status of the Alpha test compose milestone.
>
> = Rawhide testing =
>
> Because rawhide testing never stops, there are several Alpha blocker bug
> events [4] to help identify high-impact defects that would put the Alpha
> in jeopardy. The next blocker bug event is scheduled for this Friday @
> 15:00 UTC in #fedora-bugzappers.
>
> Any defects discovered while testing rawhide that should be addressed in
> the Alpha should block the tracker bug#F12Alpha. Please keep in mind
> the following criteria when escalating an issue:
>
> * Can this issue be fixed with a future rawhide update or is it
> part of the media kit?
> * Is this defect a high (or greater) severity [5] with no, or an
> unreasonable, workaround?
> * Does the presence of this bug dramatically reduce test coverage?
>
> Thanks,
> James
>
> [1]
> https://www.redhat.com/archives/fedora-test-list/2009-July/msg00429.html
> [2]
> https://fedoraproject.org/wiki/QA:Fedora_12_Alpha_Install_Test_Results
> [3] https://fedorahosted.org/rel-eng/ticket/2016
> [4]
> https://www.redhat.com/archives/fedora-test-list/2009-July/msg00498.html
> and
> https://www.redhat.com/archives/fedora-test-list/2009-July/msg00472.html
> [5] http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#Severity
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
--
==========================================
James Laska -- jlaska(a)redhat.com
Quality Engineering -- Red Hat, Inc.
==========================================
14 years, 8 months
Reminder: Zikula Meeting 2009-07-29 @ 15:00 UTC (11 AM EDT)
by John Poelstra
Zikula Meeting Agenda
2009-07-29
15:00 UTC
== Last Meeting ==
* https://fedoraproject.org/wiki/Meeting:Zikula_20090722
== Packaging Status Follow up ==
*
https://bugzilla.redhat.com/showdependencytree.cgi?id=504066&hide_resolved=1
* https://fedoraproject.org/wiki/Zikula#Module_status
* '''ACTIONS:'''
** stickster to push zikula-module-News to stable
** stickster to resolve phpSmug naming, build and push
** Sparks to review license problems in scribite! to determine if he can
just remove the "broken" pieces.
** ke4qqq: review stickster's renamed packages
** ke4qqq will contact upstream authors of cc-licensed js by eow and see
if relicensing can happen.
== Information from ke4qqq ===
Found yet another bundled library in Zikula - phpmenulayers.
Fortunately this is already being packaged
https://bugzilla.redhat.com/process_bug.cgi
However, phpmenulayers bundles the following library:
http://pear.php.net/package/HTML_Template_PHPLIB/
We may want to jump on that (esp since there are some relatively
automated spec building tools for pear packages.)
To my knowledge - everything not blocked on licensing has been
approved except zikula-module-mediashare. This was waiting on a number
of dependencies, (4 or 5, which have at least all been approved, if
not already built)
There may likewise be licensing issues, but if there are, we need to
get them in front of upstream and/or fixed by us asap.
=== Stuff blocked by licensing: ===
* zikula-module-menutree
https://bugzilla.redhat.com/show_bug.cgi?id=511998
Upstream said they were working on this, but I haven't heard anything
in a while.
Some of this is merely a set of icons, the one package with no
licensing information is problematic and we might need to see what we
can do with it/without it.
Let's ping upstream again on this issue as well
* zikula-module-mediaattach
https://bugzilla.redhat.com/show_bug.cgi?id=506038
Ian has really not even started packaging this one because he found so
many licensing issues.
I've notified upstream, but we may need to see what we can do to purge
some of this stuff.
* zikula-module-content
https://bugzilla.redhat.com/show_bug.cgi?id=492091
Lukas has this moving along - there is a licensing issue with lightboxXL.
I fired off an email re: relicensing/dual licensing to lightboxXL's
author on 22 June, but to date have received no response.
It might help if a native spanish speaker sent an email explaining the
situation, but it looks like this might have to get jettisoned which
might involve patching source.
DISCUSS: next actions and plans to resolve these blockers
== Test Instance ==
* '''ACTIONS''': Need to set a date to template the conf files for
puppet and create package lists, etc.
== Project Management ==
* '''ACTIONS''': Poelcat to work on creating draft schedule by the first
part of next week and follow through on coordinating finalizing it
== Draft Zikula Schedule ==
--Promised skeleton is below... Poelstra needs detailed tasks from all
the teams to fill in this schedule. Suggest doing this with Gobby (and
possibly Fedora Talk) ASAP
* DISCUSS: set time and date using--http://whenisgood.net/RKQ8tE
Packaging Modules Tue 2009-06-10 ???
--when will we really be done?
Start Alpha Freeze Tue 2009-08-04 Tue
2009-08-04
Alpha Public Availability Tue 2009-08-18 Tue
2009-08-18
Test Instance "Go Live" Tue 2009-08-25 Tue
2009-08-25
Performance Testing Wed 2009-08-26 Fri
2009-09-04
Final (Beta) Freeze Tue 2009-09-22 Tue
2009-09-22
Build Production Box ???
???
Deploy Production Box ???
???
Beta Release Public Availability Tue 2009-10-06 Tue
2009-10-06
Zikula "Go Live" for F12 Release ???
???
GA Release Tue 2009-11-03 Tue
2009-11-03
== Next Meeting Date & Time ==
* Anyone heard from 'itbegins'?
* Next Wednesday @ 15:00 UTC ?
14 years, 8 months
LightboxXL replacement
by Paul W. Frields
I might be wrong about this, but it looks to me less likely that
upstream is going to get some code changes done to fix their licensing
problems, timely enough for it to make a difference for us.
I started investigating some ways to replace troublesome code, and
found this:
http://herr-schuessler.de/blog/jquerypopeye-an-inline-lightbox-alternative/
It's actually a bit more elegant, licensed GPLv2+, and my hope is it
can be dropped in as a replacement for the illicit, CC-licensed
LightboxXL that's being used in a couple places. I have absolutely no
skill in PHP so I can't sign up in good conscience to make these
changes.
I could use help from somebody who knows how to try that proposed
change out to see if it helps.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
14 years, 8 months
Beacon in Zikula
by satya komaragiri
Hello,
I just subscribed to this list after being pointed by my mentor Yaakov
to the thread about WYSIWYG editors that need to be packaged.
The standalone version is almost ready (I finished testing it earlier
this week and am now adding a few very necessary features I found it
was lacking, like the ability to save the document on one's computer
and also to be able to have a persistent history of the changes made
so far). This will complete in a few days and then I will proceed
again with Zikula integration.
I had submitted the initial pakage (without the docbook plug-in) to my
mentor who has suggested some changes in the spec file. I will update
the package with the new source code alongwith those changes and
resubmit for review.
The current source can be obtained from git clone
git://git.tuxfamily.org/gitroot/beacon/trunk.git
I am now looking at scribite! to figure out how to integrate Beacon
with Zikula. We could have a discussion on what is the best way to fit
Beacon in (whatever suits the workflow).
I'll hang out more on IRC and this mailing list.
Regards,
Satya
14 years, 8 months
Quick Zikula SitRep
by David Nalley
I have informed many of you that I will be less available than normal
over the next 2-3 weeks, so I want to make sure I am not a constraint
on the zikula front and thus here is a bit of a brain dump.
Found yet another bundled library in Zikula - phpmenulayers.
Fortunately this is already being packaged
https://bugzilla.redhat.com/process_bug.cgi
However, phpmenulayers bundles the following library:
http://pear.php.net/package/HTML_Template_PHPLIB/
We may want to jump on that (esp since there are some relatively
automated spec building tools for pear packages.)
To my knowledge - everything not blocked on licensing has been
approved except zikula-module-mediashare. This was waiting on a number
of dependencies, (4 or 5, which have at least all been approved, if
not already built)
There may likewise be licensing issues, but if there are, we need to
get them in front of upstream and/or fixed by us asap.
==Stuff blocked by licensing: ==
* zikula-module-menutree
https://bugzilla.redhat.com/show_bug.cgi?id=511998
Upstream said they were working on this, but I haven't heard anything
in a while.
Some of this is merely a set of icons, the one package with no
licensing information is problematic and we might need to see what we
can do with it/without it.
Let's ping upstream again on this issue as well
* zikula-module-mediaattach
https://bugzilla.redhat.com/show_bug.cgi?id=506038
Ian has really not even started packaging this one because he found so
many licensing issues.
I've notified upstream, but we may need to see what we can do to purge
some of this stuff.
* zikula-module-content
https://bugzilla.redhat.com/show_bug.cgi?id=492091
Lukas has this moving along - there is a licensing issue with lightboxXL.
I fired off an email re: relicensing/dual licensing to lightboxXL's
author on 22 June, but to date have received no response.
It might help if a native spanish speaker sent an email explaining the
situation, but it looks like this might have to get jettisoned which
might involve patching source.
We either need to seriously help and motivate upstream or fix these
issues ourselves and send the patches upstream.
14 years, 8 months
Package builds for Zikula
by Eric Christensen
I've been pushing my packages to devel, F-10, F-11, and EL-5. Is
everyone else doing the same?
Eric
14 years, 8 months
Release Notes for Fedora 12
by John J. McDonough
The Release Notes Beat page at:
https://fedoraproject.org/wiki/Documentation_Beats
has been updated to reflect Fedora 12.
IF YOU WERE A FEDORA 11 BEAT WRITER
Review the page, if you intend to write the same beat for Fedora 12 that you
wrote for Fedora 11, remove the asterisk from your name. If you would like
to contribute to an additional beat, add your name to that beat.
IF YOU ARE A DEVELOPER
Check the Developer PoC column for your name. If you are on the list, and
will still be the point of contact for Fedora 12, remove the asterisk from
your name. If you are not on the list, and would like to ensure that the
area you are working in gets proper attention in the release notes, add your
name. Multiple names are fine.
Perhaps you felt that your particular area didn't get the attention it
deserved in Fedora 11. Consider writing the beat yourself. Add your name
to the Writer column.
IF YOU WOULD LIKE TO CONTRIBUTE TO THE RELEASE NOTES
Look through the beats for an area that interests you, and add your name to
the Writer column. If there is already someone there, that is fine. Two (or
more) heads are better than one.
IF YOU ARE UNCERTAIN
Feel free to contact me by email, via the fedora-docs-list, or on the
#Fedora-Docs IRC channel. You don't need to be some sort of expert to
contribute to the release notes. All it takes is an interest, and the
ability to string a few words together into a coherent sentence. Even if
you don't feel like you are a writer, that is fine; there will be plenty of
editing and review opportunities. What we really need is for folks to
capture the changes.
--McD
14 years, 8 months