6:15 p.m.
Zikula Meeting Agenda
2009-08-05
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_res...
* 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 ==
* Next Wednesday @ 15:00 UTC ?
10:27 p.m.
On Mon, Aug 03, 2009 at 04:15:05PM -0700, John Poelstra wrote:
** stickster to push zikula-module-News to stable
** stickster to resolve phpSmug naming, build and push
Both done.
** ke4qqq: review stickster's renamed packages
I haven't had time to take care of the phpFlickr and
php-LightweightPicasaAPI yet.
=== Stuff blocked by licensing: ===
[...snip...]
DISCUSS: next actions and plans to resolve these blockers
J5 looked into a few of these today, I'll see if he's able to come to
the meeting tomorrow.
--
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
7 a.m.
On Tue, Aug 4, 2009 at 4:45 AM, John Poelstra<poelstra(a)redhat.com> wrote:
Zikula Meeting Agenda
2009-08-05
15:00 UTC
Can Beacon be added to agenda as well if there is anything the list
would like to discuss? I can make it at the scheduled time. I have
informed the Beacon upstream about this meeting and have got a
response in the affirmative.
Regards,
Satya
12:03 p.m.
satya komaragiri said the following on 08/04/2009 05:00 AM Pacific Time:
On Tue, Aug 4, 2009 at 4:45 AM, John
Poelstra<poelstra(a)redhat.com> wrote:
> Zikula Meeting Agenda
> 2009-08-05
> 15:00 UTC
>
Can Beacon be added to agenda as well if there is anything the list
would like to discuss? I can make it at the scheduled time. I have
informed the Beacon upstream about this meeting and have got a
response in the affirmative.
Regards,
Satya
I'm sorry we haven't been able to get this onto the meeting agenda. Do
we still need to discuss it? Is there a bug to tracking its packaging?
Thanks,
John
12:26 p.m.
On Tue, Aug 11, 2009 at 13:03, John Poelstra<poelstra(a)redhat.com> wrote:
satya komaragiri said the following on 08/04/2009 05:00 AM Pacific
Time:
> Can Beacon be added to agenda as well if there is anything the list
> would like to discuss? I can make it at the scheduled time. I have
> informed the Beacon upstream about this meeting and have got a
> response in the affirmative.
>
> Regards,
> Satya
I'm sorry we haven't been able to get this onto the meeting agenda. Do
we still need to discuss it? Is there a bug to tracking its packaging?
Thanks,
John
Beacon is still in development so no bug has been filed for packaging.
Probably should make one so we don't forget about it.
Satya: Can you give the list an update and progress report on Beacon, please?
--Eric
3:56 p.m.
On Tue, Aug 11, 2009 at 01:26:50PM -0400, Eric Christensen wrote:
On Tue, Aug 11, 2009 at 13:03, John
Poelstra<poelstra(a)redhat.com> wrote:
> satya komaragiri said the following on 08/04/2009 05:00 AM Pacific Time:
>> Can Beacon be added to agenda as well if there is anything the list
>> would like to discuss? I can make it at the scheduled time. I have
>> informed the Beacon upstream about this meeting and have got a
>> response in the affirmative.
>>
>> Regards,
>> Satya
>
> I'm sorry we haven't been able to get this onto the meeting agenda. Do
> we still need to discuss it? Is there a bug to tracking its packaging?
>
> Thanks,
> John
Beacon is still in development so no bug has been filed for packaging.
Probably should make one so we don't forget about it.
Huh, I was sure that filing a package for review was early in the
process, but I don't see an obvious request filed.
Satya: Can you give the list an update and progress report on Beacon,
please?
This is from last week to f-docs-l:
http://www.redhat.com/archives/fedora-docs-list/2009-August/msg00041.html
We've had some changes this Summer with expectations for Beacon. I
wanted to see it integrated with Zikula, but there can't be a
dependency between the two efforts. My last recommendation, which
mainly concurred with Yaakov's, is to get Beacon running stand-alone
and integrated with FAS access to fedorahosted.org DocBook XML
sources.
https://fedorahosted.org/fedora-infrastructure/ticket/1580
- Karsten
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
8:28 a.m.
2009/8/11 Karsten Wade <kwade(a)redhat.com>:
On Tue, Aug 11, 2009 at 01:26:50PM -0400, Eric Christensen wrote:
> On Tue, Aug 11, 2009 at 13:03, John Poelstra<poelstra(a)redhat.com> wrote:
> > satya komaragiri said the following on 08/04/2009 05:00 AM Pacific Time:
> >> Can Beacon be added to agenda as well if there is anything the list
> >> would like to discuss? I can make it at the scheduled time. I have
> >> informed the Beacon upstream about this meeting and have got a
> >> response in the affirmative.
> >>
> >> Regards,
> >> Satya
> >
> > I'm sorry we haven't been able to get this onto the meeting agenda. Do
> > we still need to discuss it? Is there a bug to tracking its packaging?
> >
> > Thanks,
> > John
>
> Beacon is still in development so no bug has been filed for packaging.
> Probably should make one so we don't forget about it.
Huh, I was sure that filing a package for review was early in the
process, but I don't see an obvious request filed.
I'm not aware of any package for review as I don't think the software
has been completed.
> Satya: Can you give the list an update and progress report on Beacon, please?
This is from last week to f-docs-l:
http://www.redhat.com/archives/fedora-docs-list/2009-August/msg00041.html
Yeah, I'm hoping to have an update of this for tonight's meeting.
We've had some changes this Summer with expectations for Beacon. I
wanted to see it integrated with Zikula, but there can't be a
dependency between the two efforts. My last recommendation, which
mainly concurred with Yaakov's, is to get Beacon running stand-alone
and integrated with FAS access to fedorahosted.org DocBook XML
sources.
https://fedorahosted.org/fedora-infrastructure/ticket/1580
- Karsten
--Eric
6:53 a.m.
Hello,
>> >
>> > I'm sorry we haven't been able to get this onto the meeting agenda.
Do
>> > we still need to discuss it? Is there a bug to tracking its packaging?
>> >
>> > Thanks,
>> > John
The goals were revised and it was decided that I first put up a
standalone demo where we can get enough feedback to make Beacon usable
and then concentrate on integrating it in Zikula and Publican.
The demo is up at http://publictest1.fedoraproject.org/beacon/php/beacon.php
The login page requires the user's FAS account details.
It would be really nice if you could take some time to test it out and
give some feedback.
>>
>> Beacon is still in development so no bug has been filed for packaging.
>> Probably should make one so we don't forget about it.
>
> Huh, I was sure that filing a package for review was early in the
> process, but I don't see an obvious request filed.
I know this has been delayed quite a bit as I was having some trouble
with packaging it. Its almost done and I will submit the standalone
package for review by tonight.
I'm not aware of any package for review as I don't think the
software
has been completed.
>
>> Satya: Can you give the list an update and progress report on Beacon, please?
>
> This is from last week to f-docs-l:
>
> http://www.redhat.com/archives/fedora-docs-list/2009-August/msg00041.html
Yeah, I'm hoping to have an update of this for tonight's meeting.
I tried to join the meeting today morning but I had some trouble
connecting with VoIP. I will mail in a detailed report once I am done
packaging. The demo is up so anyone can try it and give me some
feedback.
>
> We've had some changes this Summer with expectations for Beacon. I
> wanted to see it integrated with Zikula, but there can't be a
> dependency between the two efforts. My last recommendation, which
> mainly concurred with Yaakov's, is to get Beacon running stand-alone
> and integrated with FAS access to fedorahosted.org DocBook XML
> sources.
>
> https://fedorahosted.org/fedora-infrastructure/ticket/1580
>
The infra team sponsored me for sysadmin-test and I have been able to
set up the demo.
Regards,
Satya
10:16 a.m.
On 08/13/2009 04:53 AM, satya komaragiri wrote:
Hello,
>>>>
>>>> I'm sorry we haven't been able to get this onto the meeting
agenda. Do
>>>> we still need to discuss it? Is there a bug to tracking its packaging?
>>>>
>>>> Thanks,
>>>> John
The goals were revised and it was decided that I first put up a
standalone demo where we can get enough feedback to make Beacon usable
and then concentrate on integrating it in Zikula and Publican.
The demo is up at http://publictest1.fedoraproject.org/beacon/php/beacon.php
When hitting the login screen:
"Error: This browser maybe incompatible with Beacon. Please use Firefox
3.0+ only."
That's not a very nice message. If Beacon uses standards compliant
javascript we should be able to get it to work with webkit-based
browsers as well. Maybe downgrade to a warning? Or having a blacklist
instead of a whitelist? (Note that it already seems to be a warning --
I'm able to login and use Beacon using arora (webkit based) despite the
"Error").
I took a brief look. Creating a new document was intuitive. Saving it
a few times generated new revisions which is a nice feature. I was able
to change titles in the sample docbook document and highlight some
paragraph text and change what type it was and edit the paragraph. Some
questions:
* How do I enter a new paragraph or section?
* The Source tab lets me edit the content but the changes don't seem to
be persisted. Should they or should I not be able to make changes there?
* The list of types in "Insert inline Elements" is not alphabetical.
Sorting them would make it easier to find the type of element we want to
apply to the text we're editing.
The login page requires the user's FAS account details.
It would be really nice if you could take some time to test it out and
give some feedback.
As long as this is running on publictest we should hit the publictest3
fas server instead of the real fas server. publictest doesn't have SSL
which makes it insecure to type your real username and password in.
I've changed the server being pointed to on publictest1 by editing
/var/www/html/beacon/php/auth.php.
So if you want to try this out, create an account on
http://publictest3.fedoraproject.org/accounts/
Then use that test account to log into beacon on publictest1.
Thanks,
Toshio
5:07 a.m.
2009/8/13 Toshio Kuratomi <a.badger(a)gmail.com>:
When hitting the login screen:
"Error: This browser maybe incompatible with Beacon. Please use Firefox
3.0+ only."
That's not a very nice message. If Beacon uses standards compliant
javascript we should be able to get it to work with webkit-based
browsers as well. Maybe downgrade to a warning? Or having a blacklist
instead of a whitelist? (Note that it already seems to be a warning --
I'm able to login and use Beacon using arora (webkit based) despite the
"Error").
The problem with other browsers is that contentEditable (or
designMode) implementation varies a lot and Firefox has the most
consistent behaviour (I have not checked *all* the browsers but tried
on most of the widely used browsers). Other than that Beacon uses
standards compliant JS.
Beacon does not prevent you from using any other browser but it cannot
guarantee that the document will be sane in any other browser. Which
is why it let you log in through arora. Its known to run in Safari,
Opera and even IE to some extent.
I'll change it to a warning and tone the color to yellow or orange.
The only reason I called it an error was because warnings are most of
the times ignored. :)
I took a brief look. Creating a new document was intuitive. Saving
it
a few times generated new revisions which is a nice feature. I was able
to change titles in the sample docbook document and highlight some
paragraph text and change what type it was and edit the paragraph. Some
questions:
* How do I enter a new paragraph or section?
You need to add a new node in the document tree. Right click on the
node after or before which you want to add the new node. It will give
option for adding a sibling before the selected node, adding it after
the selected node or deleting the selected node. Once you choose the
add at appropriate location, you will get a drop down for the type of
node you want to add. (The list only contains those tags that are
allowed in order to maintain the sanity of the document.) I'll add an
"Add Child Node" function soon as well.
* The Source tab lets me edit the content but the changes don't seem to
be persisted. Should they or should I not be able to make changes there?
Could you please try it again? I checked to confirm and it was
persistent. It is supposed to be persistent so we can have a way of
inserting tags that are not yet supported by Design view at least.
(More like a 'for experts only' feature)
* The list of types in "Insert inline Elements" is not
alphabetical.
Sorting them would make it easier to find the type of element we want to
apply to the text we're editing.
Yeah sure will do. Will be a small change. :)
> The login page requires the user's FAS account details.
> It would be really nice if you could take some time to test it out and
> give some feedback.
>
As long as this is running on publictest we should hit the publictest3
fas server instead of the real fas server. publictest doesn't have SSL
which makes it insecure to type your real username and password in.
I've changed the server being pointed to on publictest1 by editing
/var/www/html/beacon/php/auth.php.
So if you want to try this out, create an account on
http://publictest3.fedoraproject.org/accounts/
Then use that test account to log into beacon on publictest1.
Thanks a lot :)
Regards,
Satya
2:29 p.m.
On 08/14/2009 03:07 AM, satya komaragiri wrote:
2009/8/13 Toshio Kuratomi <a.badger(a)gmail.com>:
>
> * The Source tab lets me edit the content but the changes don't seem to
> be persisted. Should they or should I not be able to make changes there?
>
Could you please try it again? I checked to confirm and it was
persistent. It is supposed to be persistent so we can have a way of
inserting tags that are not yet supported by Design view at least.
(More like a 'for experts only' feature)
Excellent. This and adding a new node are working. I'm getting
something strange, though. When I click on the save icon, I get a popup
that says "Please finish editing before saving." What does that mean?
-Toshio
2:34 a.m.
2009/8/15 Toshio Kuratomi <a.badger(a)gmail.com>:
Excellent. This and adding a new node are working. I'm getting
something strange, though. When I click on the save icon, I get a popup
that says "Please finish editing before saving." What does that mean?
-Toshio
Ah, Maybe you clicked somewhere in the document and that part is
selected for editing. Is any part of the document still selected? If
it is, the click out of it anywhere else in the document and then you
will be able to save it. When you click on any part of the document,
Beacon thinks you want to edit it and it reminds you to finish editing
before you can save.
Regards,
Satya
5366
days inactive
5378
days old
logistics@lists.fedoraproject.org
11 comments
6 participants
participants (6)
-
Eric Christensen -
John Poelstra -
Karsten Wade -
Paul W. Frields -
satya komaragiri -
Toshio Kuratomi