Hi,
As I noted in the last marketing meeting could have done a better than
with the release notes for the Alpha release than we did. I just ran out
of time. The Beta release is schedule at 2009-10-13. So we don't really
have too much time. As promised, here are more details.
The Beta release notes is a important source of information for our
users, testers, ambassadors, even fellow developers and press for that
release. So I am asking you all to help you a bit. Here is how:
I have "open sourced" my process of finding information and my notes and
copied over all that information to
https://fedoraproject.org/wiki/Fedora_12_Beta_release_notes
If you don't have much time, take one item in this list and add more
information. I will also help you avoid even clicking on a link and copy
the same information below:
Quick notes:
* Hybrid ISO - earlier revision in Alpha release notes history. Confirm
that it works well before adding it here
* Status of http://www.ing.unibs.it/openfwwf/ in Fedora? How well does
it work?
* Moblin - Explain in detail with potentially a screencast
* GNOME Shell - Ogg Screencast possibly with voice over
* Yum Presto - In GNOME and KDE groups. What about delta rpm generation?
* http://live.gnome.org/GTK%2B/ClientSideWindows - Eclipse and Adobe
Reader needs a workaround
* Abrt - whats the status?
* Anaconda MDRaid - Explain in detail
* Lower Process Capabilities
* Contact KDE SIG and gather important changes. Phonon has changed to
gstreamer backend in Alpha release and was not mentioned. So call it out
in the Beta release.
Additional sources:
* Look at F11 Preview release notes and use it as a template. It matches
the beta this release because of rel eng decision to tweak the release
process a bit
* Read rawhide reports in between alpha and beta release for new
packages as well as import changes worth noting here
* Quickly skimp through all threads in fedora-devel and fedora-test list
for note worthy changes
* Read Planet Fedora and reference developer blogs when important
changes are mentioned
* Consult with QA team and make sure note worth issues are mentioned. If
anything needs explicit testing, highlight it
* More details at
https://fedoraproject.org/wiki/Releases/12/FeatureList. Read the release
notes section of each of the approved feature
Thanks.
Rahul
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
00:02:47 #startmeeting Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
00:02:47 Meeting started Thu Aug 27 00:02:47 2009 UTC. The chair is
Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:02:47 Useful Commands: #action #agreed #halp #info #idea #link #topic.
00:02:54 #topic Roll Call
00:02:55 * Sparks
00:03:38 * rudi is here
00:03:56 * itbegins here
00:05:18 * Sparks wonders where everyone is today
00:06:24 * laubersm is here
00:07:05 Okay, lets get started...
00:07:11 #topic Last week's action items
00:07:23 Sparks to create BZ component Deployment Guide --Third alarm
00:07:31 Finally done.
00:07:43 Sparks to write up CVE checking/validation procedures in the
wiki --third alarm
00:07:48 Still in progress
00:07:56 #action Sparks to write up CVE checking/validation
procedures in the wiki
00:08:08 quaid to follow up with Mizmo on the Zikula theme
00:08:13 quaid: You around?
00:08:42 I know Mo has been working on the Zikula theme. I'm sure
this is in progress.
00:08:56 rudi to follow up with Jeff about changing the license
information in Publican 0.44 and 1.0
00:09:10 rudi: Got an update?
00:09:21 We're still a few steps away from that
00:09:26 * ianweller rolls in
00:09:45 I can report a little on the theme, depending on what you want to knwo
00:10:04 rudi: Okay, I'll put it down for next week so we can talk
about it again.
00:10:11 Yep
00:10:14 #action rudi to follow up with Jeff about changing the
license information in Publican 0.44 and 1.0
00:10:18 ianweller: Go
00:10:40 about my part of it? the writing up of the announcement?
00:11:32 Sparks: hi?
00:11:42 the theme
00:11:48 oh for zikula
00:12:05 hmm i'm not sure what i need to say, other than taht school
is eating me alive
00:12:14 * ianweller wasn't sure he had anything assigned for zikula right now
00:12:37 Sparks: You mean me?
00:12:39 ianweller: Opps.. sorry
00:12:46 itbegins: Yeah, I meant you. sorry
00:12:49 quaid: yep, zikula theme is all rolling for FI
00:12:55 * Sparks is not doing a good job of multitasking tonight
00:13:05 * quaid either
00:13:07 mizmo is in progress on the theme:
http://publictest6.fedoraproject.org/zikula/
00:13:17 and Zikula is getting rolled out to staging
00:13:35 and things are prepared in the repo (ideally) so she can
have related Docs theme in there to make a Docs-specific RPM of the
theme (AIUI)
00:13:44 or I'm confused and it's all going to run from one instance, one theme
00:14:06 quaid: One filesystem instance, mutliple databases -> multiple themes
00:14:21 I think I'm confused; that was my old idea, but Paul said
we'll likely all be on the same instance
00:14:36 i.e turning on docs.fedoraproject.org Zikula is a case of
installing a few new packages and updating the config file
00:14:50 ok
00:15:34 Okay, we'll come back to Zikula in a little bit for a more
indepth discussion.
00:15:45 quaid to follow up with Richard about the use of the CC logo
on the wiki.
00:15:50 quaid: Got an update on this?
00:17:16 ;/me sneaks in late...
00:17:26 quaid: hello?
00:18:48 Okay, quaid must have rushed off...
00:18:59 Any more old business?
00:19:06 #action quaid to follow up with Richard about the use of the
CC logo on the wiki.
00:19:29 #topic Status on CMS (Zikula)
00:19:44 #link https://fedoraproject.org/wiki/Zikula#Module_status
00:19:58 itbegins: So what is the status on rolling out Zikula for docs.fp.o?
00:20:24 Sparks: well, we're still waiting on those modules held up
with license problems I think
00:20:43 Sparks: but marketing have kindly packaged a couple of
modules we can use for the docs instance too.
00:20:50 Sadly not the blockers for the docs instance
00:21:14 I think we both need at least one editor to go with Scribite.
00:21:28 * Sparks hasn't had any time to even look at packaging one of those.
00:21:37 yes,that's true
00:22:16 Sparks: sorry, phone call
00:22:23 do you want to hear about the CC logos?
00:22:53 quaid: That will be the next topic
00:23:02 itbegins: Okay so we are close but not there
00:23:17 itbegins: Does marketing have everything they need to roll
out their instance?
00:24:21 apart from a visual editor, probably
00:24:24 after a last minute scramble with chitlesh++, bobjensen++,
toshio++ getting a few last minute packages done last night/today
00:24:26 though things may still come up
00:24:34 oh! no visual editor? heh heh
00:25:24 So we need one of the editors packaged
00:25:32 anyone want to stand up to take that task?
00:26:52 * danielsmw can try if no body else will, but he's never
successfully packaged anything...
00:27:25 danielsmw: Well, this would be a good time to start being
successful... there are templates for the SPEC and everything
00:27:25 Also I haven't been involved in this process at all so far
00:27:40 Sparks: Alright, well...
00:27:48 I suppose I can give it a shot and report back next week.
00:28:19 danielsmw: I'm sure ianweller or someone will be around to help
00:28:35 #action danielsmw to package an editor for Scribite
00:28:46 Okay, anything else on Zikula?
00:29:04 * quaid notes Beacon was accepted for F10/F11
00:29:13 but I guess it's not integrated?
00:29:18 danielsmw: Try pinging Toshio, he is involved with Zikula packaging
00:29:20 * danielsmw really likes beacon, btw.
00:29:22 quaid: And Beacon is the DocBook editor?
00:29:24 itbegins: Will do
00:29:27 Sparks: yep
00:29:45 Sparks: well, it's a web wysiwyg editor that now has
upstream code to read/write docbook :)
00:29:48 Yeah, we need to get that integrated
00:30:17 satya has it running on a publictest instance, we can look
at how to use it plain, too
00:30:22 * quaid is wandering topics now
00:31:02 Okay, let's move on. Lots of work to be done on Zikula but
things are starting to come together
00:31:14 #topic Status on CC license rollout.
00:31:22 quaid: So what's the skinny on the CC logos?
00:31:53 ok
00:31:59 I read and read that page
00:32:03
http://www.redhat.com/archives/fedora-docs-list/2009-August/msg00075.html
00:32:16 and it's clear that the ball is in Richard's court with
folks from Creative Commons
00:32:36 And we haven't heard back from him on this, yet.
00:32:37 it only having been a few weeks ... and he being a proactive
and busy guy ... I think we have our clear answer for now
00:32:44 and will hear when there is something more
00:33:10 ianweller: Do you have the text for the wiki?
00:33:28 I would put this on the back-burner; don't forget about it,
but revisit if a month goes by, then prod for a status.
00:33:44 so ... a few more weeks at least, then see if we can kindly
get a status. :)
00:33:54 Well, we can go ahead with the change over, use the text
version of the license, and change later as necessary
00:33:58 * danielsmw has to go, sorry for the short visit.
00:33:59 yes
00:34:02 ciao danielsmw
00:34:06 au revoir.
00:34:07 danielsmw: Have a good day!
00:34:11 Sparks: Thanks!
00:34:41 #action ianweller to bring to the list the text for the CC
license for the wiki so it can be approved
00:35:03 #link https://fedoraproject.org/wiki/License_changeover_schedule
00:35:17 ^^^ That is the timeline if anyone would like to take a peek at it.
00:35:56 I guess we are still waiting on the text being approved and
then we can move on to step 4.
00:36:27 rudi: So what needs to happen to get the license changed in
Publican for step 6?
00:37:19 The people involved in doc publishing could do it at any
time by hacking their Publican 0 installs
00:38:12 rudi: Yeah, but I want to push it to everyone. That way
there is 1) no confusion, 2) no differences, 3) and everyone does it.
00:38:44 I think it's unlikely that any more changes are forthcoming
to brand packages for 0
00:38:52 since 1 handles brands so differently.
00:39:28 (And we're not quite up to testing brands in 1)
00:40:02 Well, that's a problem.
00:40:17 If 1 isn't out then 0 still needs to be supported
00:40:19 um, hmm
00:40:26 Not really; there are very few people actually publishing
00:40:36 is there any technical reason not to change brand pkg for 0?
00:40:49 it's just text strings, right?
00:41:05 and I'm quite happy to wrap those notices up in the package
that I've got parked on my Fedora people page.
00:41:10 quaid -- correct.
00:41:18 No technical reason
00:41:22 Well if we get new people in we should be able to say
"install publican" not "install publican and then do all these changes
before you can use it"
00:41:29 rudi: is CS waiting to rebuild RHEL guides with the new
license until 1.x handles brands?
00:41:32 * ianweller notes his action item and makes a sticky note
00:41:39 ianweller: Thank you
00:41:56 rudi: Can you adopt the brand and just make the changes there?
00:42:04 rudi: Or one of us?
00:42:25 Sparks - I can check into that.
00:42:28 does publican need a co-maintainer for the package?
00:42:38 * Sparks thinks 1.x should be released as publican-devel
00:42:53 -devel has a specific meaning, though
00:43:10 or was that a joke!
00:43:23 rudi: I'm not saying anything bad about Jeff... I know he's
busy and he has this new tool he's putting a lot of effort into. But
we still need the old tool to work for now.
00:43:25 because if it was, very funny! just don't tell it to jfearn
if you are on the same continent.
00:43:46 quaid: I thougth -devel was for the development version of a
package... a beta
00:43:51 nope
00:43:57 Sparks: -devel is development headers
00:44:00 yep
00:44:03 in C, those would be the .h files
00:44:06 Sparks -- yeah, but "work" for about three people :)
00:44:22 Sparks: and Publican was originally proposed as
'docs-devel', with much arguing about why that wasn't OK and such
00:44:58 rudi: sorry, where is the approv text for the license page?
or proposed-and-under-review?
00:45:00 Well... I don't know. I'd like it to be in the repos... :)
00:45:28 rudi: it's not the people count, it's the F12 release
00:45:35 we have a dependency on a workingn tool for the F12 release
00:45:43 quaid -- proposed and review version is here :
http://rlandmann.fedorapeople.org/license/
00:45:54 we've had a rocky time for three releases with Publican feature status
00:46:06 The source is in the Publican repo already
00:46:20 and I thought with RHEL content upstream out here using
Publican, it would work for Fedora :)
00:48:06 Sparks: well, there is no moving backward for now, so if
Publican upstream isn't going to issue an update we can use, we'll
have to do manual process around it again.
00:48:47 * Sparks thinks hijacking the package is an option... :)
00:48:50 quaid: Yeah
00:48:52 (Fedora *is* the Publican upstream)
00:49:13 Okay, anything else on the license changeover?
00:49:25 what is the reason for not pushing the brand update?
00:51:30 * quaid wonders if he has bad breath?
00:51:49 rudi: ^^^
00:52:31 sorry, I haven't been reading publican-list; you can tell me
to read the archives, if that's it
00:52:39 Basically that energies are elsewhere at the moment
00:53:09 can we have a packager apply to be co-maintainer?
00:53:19 we can get some help to do the work, if that's the block.
00:53:43 I'll ask :)
00:53:47
https://fedorahosted.org/publican/browser/branches/0.45/publican-fedora/en-…
is the old stuff
00:54:22 sparks, stickster, ke4qqq, or ianweller would all be good choices
00:54:53 Yes, because the new is here:
https://fedorahosted.org/publican/browser/trunk/publican-fedora/en-US/Legal…
00:55:36 what's the bz for this?
00:56:34 For what?
00:57:12 the bz for publican-fedora requesting the license update
00:57:42 I don't know that there is one
00:57:44 Might not be
00:57:54 heh, ok
00:58:05 rudi: thanks, that XML was helpful; I'm building a book I
want to be clearly under the CC
00:58:19 NP
00:58:50 rudi: and many thanks for working on the update of the content
00:58:51 If it's your own book, you might want to include the CC logo too ;)
00:59:09 * quaid is doing a Red Hat branded book, so knows the answer
to that already
00:59:10 I know I would :)
00:59:14 Ah OK :)
00:59:49 NO CC LOGO IN PRINT!!! :)
01:00:33 Okay... anything else on this topic?
01:01:04 Action -- rudi to investigate getting a co-maintainer for 0
01:01:16 #Action -- rudi to investigate getting a co-maintainer for 0
01:01:20 * quaid thinks he can do that?
01:01:49 Let me test the waters first :)
01:02:30 Okay, lets move on to the last few topics so we can wrap
things up for the day
01:02:39 #topic Guide needs?
01:02:48 Does anyone need anything for their guide?
01:03:14 #topic New Guides
01:03:22 How about new guides? Any of them?
01:04:22 Okay, there is a new guide in the works...
01:05:12 there will be an Amateur Radio Guide coming out discussing
the various pieces of software in Fedora for hams
01:05:24 Any others?
01:05:51 #topic All other business
01:06:01 * laubersm is available for proofreading
01:06:06 Okay, anything else for the meeting?
01:06:09 I have lots of little sturts of time
01:06:15 I have very little predictable time
01:06:29 But ping me and I am happy to review materials...
01:06:30 laubersm: Yeah... understood
01:06:33 Thanks!
01:06:35 I know RN is coming up fast
01:06:47 and IG and UG for example
01:07:23 Thanks laubersm -- I'll be needing you :)
01:07:33 are the guides using Trac for one-task-per-chapter?
01:07:46 there is a workflow we can impose there, with writer owning
then passing to an open editor
01:07:51 it's manual ...
01:08:36 Each chapter would be in its own file
01:08:53 The AR Guide will be in git
01:10:08 Anything else?
01:11:24 Okay, thanks everyone for coming tonight!
01:11:27 #endmeeting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.7)
iEYEARECAAYFAkqV3ZYACgkQfQTSQL0MFMEwhgCgyIVs7mVPpWg8C+5NYr04hMFd
lgAAnRs42hyuiolykUm+FvNsetds0eO4
=q8W5
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 00:02:47 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2009-08-27/fedora-meeting.2…
.
Meeting log
- -----------
* Roll Call (Sparks, 00:02:54)
* Last week's action items (Sparks, 00:07:11)
* ACTION: Sparks to write up CVE checking/validation procedures in the
wiki (Sparks, 00:07:56)
* ACTION: rudi to follow up with Jeff about changing the license
information in Publican 0.44 and 1.0 (Sparks, 00:10:14)
* ACTION: quaid to follow up with Richard about the use of the CC logo
on the wiki. (Sparks, 00:19:06)
* Status on CMS (Zikula) (Sparks, 00:19:29)
* LINK: https://fedoraproject.org/wiki/Zikula#Module_status (Sparks,
00:19:44)
* ACTION: danielsmw to package an editor for Scribite (Sparks,
00:28:35)
* Status on CC license rollout. (Sparks, 00:31:14)
* LINK:
http://www.redhat.com/archives/fedora-docs-list/2009-August/msg00075.html
(quaid, 00:32:03)
* ACTION: ianweller to bring to the list the text for the CC license
for the wiki so it can be approved (Sparks, 00:34:41)
* LINK: https://fedoraproject.org/wiki/License_changeover_schedule
(Sparks, 00:35:03)
* LINK:
https://fedorahosted.org/publican/browser/branches/0.45/publican-fedora/en-…
is the old stuff (quaid, 00:53:47)
* ACTION: -- rudi to investigate getting a co-maintainer for 0
(quaid, 01:01:16)
* Guide needs? (Sparks, 01:02:39)
* New Guides (Sparks, 01:03:14)
* All other business (Sparks, 01:05:51)
Meeting ended at 01:11:27 UTC.
Action Items
- ------------
* Sparks to write up CVE checking/validation procedures in the wiki
* rudi to follow up with Jeff about changing the license information in
Publican 0.44 and 1.0
* quaid to follow up with Richard about the use of the CC logo on the
wiki.
* danielsmw to package an editor for Scribite
* ianweller to bring to the list the text for the CC license for the
wiki so it can be approved
* -- rudi to investigate getting a co-maintainer for 0
Action Items, by person
- -----------------------
* danielsmw
* danielsmw to package an editor for Scribite
* ianweller
* ianweller to bring to the list the text for the CC license for the
wiki so it can be approved
* quaid
* quaid to follow up with Richard about the use of the CC logo on the
wiki.
* rudi
* rudi to follow up with Jeff about changing the license information
in Publican 0.44 and 1.0
* -- rudi to investigate getting a co-maintainer for 0
* Sparks
* Sparks to write up CVE checking/validation procedures in the wiki
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* Sparks (93)
* quaid (61)
* rudi (28)
* itbegins (14)
* danielsmw (10)
* ianweller (9)
* laubersm (7)
* zodbot (2)
Generated by `MeetBot`_ 0.1.3
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.7)
iEYEARECAAYFAkqV3ckACgkQfQTSQL0MFMEPFQCgjafAbn28Im2dakE5qzZmkwjz
ZNAAoMGwDNW9c794VJLGGSGqG8XCmwLR
=4kbY
-----END PGP SIGNATURE-----
00:02:48 <Sparks> #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings
00:02:53 <Sparks> #topic Roll Call
00:02:54 * Sparks
00:03:29 * rudi is here
00:03:40 * ianweller
00:04:16 * quaid too
00:06:32 <quaid> hail hail etc.
00:06:42 * Sparks waits a few more seconds for folks
00:07:05 <Sparks> #topic Last week's action items
00:07:11 <Sparks> Okay... this should be interesting...
00:07:53 <Sparks> Sparks to follow up with Pascal Calarco from News to make sure we are including all packages necessary for Zikula for them. -- Second Alarm
00:08:16 <Sparks> Okay, I sent a message to the News folks and didn't really hear anything back from them, IIRC.
00:08:32 <Sparks> I think they'll be set with what we're planning.
00:08:51 <Sparks> rudi to help sparks on changing the fedora-brand in Publican for CC license -- Second Alarm
00:09:03 <quaid> I agree, Marketing is finding it sufficient with similar needs, I reckon.
00:09:10 <Sparks> rudi: That is pretty much ready to go, correctly?
00:09:24 <Sparks> errr... correct?
00:09:28 * quaid rubs his hands gleefully
00:09:34 <rudi> Sparks -- yes. I have a draft that legal is happy with
00:09:50 <Sparks> rudi: Excellent. Let's push forward with that, then.
00:10:10 <Sparks> Sparks to package the three GPL editors for Zikula -- Second Alarm
00:10:18 <Sparks> Okay, I haven't had a chance to even think about that.
00:10:29 <Sparks> Can someone pick this task up for me?
00:11:20 <Sparks> We don't actually need all three packaged but it would be nice as a long term goal. We do need one of them packaged, though.
00:12:25 <Sparks> #action Sparks to send an email to the list to pass this task on.
00:12:40 <Sparks> #action Sparks to put a note on the list about Shared Open-Source Style Guide
00:12:55 <rudi> Sparks -- I have some news there
00:13:02 <Sparks> rudi: Go ahead
00:13:33 <rudi> I have approval from Red Hat legal to share the bulk of our external Style Guide
00:13:57 * itbegins is here now
00:14:06 <quaid> rudi: srsly?
00:14:21 <Sparks> Very cool
00:14:23 <rudi> So I have agreed to put together a subset of it for review; after that, we can share it.
00:14:29 <quaid> rudi++
00:15:09 <quaid> rudi: am I correct that this is the RHT internal style guide/"word usage" document?
00:15:20 <rudi> Yes -- those documents
00:15:31 * quaid faints with happiness
00:15:42 * Sparks fans quaid
00:16:12 <Sparks> rudi: Any idea when this might be available?
00:16:24 <rudi> There is material there that represents internal Red Hat legal advice and brand considerations that we will not be able to share -- but for the most part, that stuff is irrelevant to anyone else who wants to use it.
00:16:48 <rudi> Sparks -- at the moment, I'm bogged down in the preparations for RHEL5.4, which is why I've been quiet on the Fedora front for the last few weeks
00:16:55 * quaid sorry for the drama, it's just good stuff and a nice leg up for everyone
00:17:08 <rudi> I expect to have a draft together for legal to review within the next 2 weeks or so
00:17:29 <quaid> rudi: feel free to draw on me in any way, such as helping pre-review before legal, etc.
00:17:38 <rudi> quaid -- thanks
00:17:43 <quaid> aye, thank you
00:18:15 <Sparks> rudi: That's cool.
00:18:24 <Sparks> rudi: BTW, when is 5.4 going to hit the streets?
00:18:40 <rudi> I'd have to check to see what the public is supposed to know :)
00:19:11 <Sparks> Gees...
00:19:19 <Sparks> I have many servers that are aching to upgrade
00:19:20 <Sparks> :)
00:19:24 <rudi> Wikipedia doesn't know ;)
00:19:28 <Sparks> Okay, moving on...
00:19:46 <Sparks> #action Sparks to create BZ component Deployment Guide --Third alarm
00:20:06 <Sparks> #action Sparks to write up CVE checking/validation procedures in the wiki --third alarm
00:20:18 <Sparks> ianweller to do something useful and write a draft announcement
00:20:19 <Sparks> DONE
00:20:30 <Sparks> jjmcd to do recon on Zikula for useful docs
00:20:33 <Sparks> DONE and found none
00:20:36 <quaid> Sparks: I find Wikipedia makes good guesses there :)
00:21:02 <Sparks> I think this is all the old business. Does anyone have anything else that is old business/tasks?
00:21:10 <quaid> whoops, withdrawn :)
00:21:42 <Sparks> quaid: Ya... we were just talking about that today.
00:21:47 <Sparks> Okay, moving on
00:21:52 <Sparks> #topic Status on CMS (Zikula) <-- ke4qqq
00:22:04 <Sparks> #link https://fedoraproject.org/wiki/Zikula#Module_status
00:22:13 <Sparks> I don't think ke4qqq is here tonight...
00:22:27 <Sparks> Does anyone have an update on Zikula?
00:22:33 <itbegins> The instance for marketing is moving along fast
00:22:39 <itbegins> but that will pass by the blockers for docs
00:22:56 <itbegins> on the plus side, puppetization etc will be partly done for docs purposes by marketing
00:23:02 <Sparks> +1
00:23:06 <itbegins> The same with performance checks etc
00:23:22 <Sparks> That's good.
00:23:45 <itbegins> So, IMHO if we can get the last few modules packaged, a roll out for immediately following the F12 change freeze is perfectly achievable
00:24:03 <Sparks> itbegins: Can you provide a delta of what we need versus what we have, package wise, to stand up the docs instance?
00:24:33 * quaid calls for a wiki page to be created!
00:24:50 <itbegins> packaging side, we need one of mediashare or mediaattach packaged
00:24:54 <itbegins> otherwise you have no media manager
00:25:05 * Sparks points quaid to the link at the top of this topic discussion
00:25:21 <itbegins> and preferably one editor - unless you like hard coding HTML
00:25:32 <itbegins> and of course we need the theme packaged
00:25:45 <itbegins> With those three, I think you are ready to go
00:25:52 * Sparks thinks the theme is packaged and ready
00:25:58 <itbegins> and over time we can upgrade the instance with more features as they come online
00:26:11 <itbegins> Sparks: yes, but I wouldn't call the files currently in git production ready
00:26:24 <itbegins> I made that theme using File>Save as in Firefox, and a quick n dirty conversion
00:26:27 <quaid> heh
00:26:36 <itbegins> there will be all sorts of useful images and possibly css missing from that
00:26:53 <itbegins> the correct way to do it would be to convert based on the files currently in the websites git repository
00:26:54 <quaid> itbegins: I think we showed it to mizmo though, I'll make sure she's on the bz for that package review
00:27:19 <quaid> ... and anyone know that bz # for the theme?
00:27:26 <itbegins> If Mizmo approves, then I defer to her - she's also runnign point for the marketing team on design issues
00:28:05 <itbegins> Content and Mediashare are blocking on the window library
00:28:30 <itbegins> it just so happens I've had experience with the replacement suggested by stickster_afk in the last couple of weeks at work, so I could in theory make those changes for you
00:28:51 <itbegins> But it will take me some time to get up to speed with the modules and figure out the needed changes
00:29:19 <itbegins> Equally there may already be someone working on making that very change
00:30:29 * Sparks is back
00:30:36 <Sparks> Sorry, storm and power outage
00:30:49 <Sparks> Are we done with the CMS discussion?
00:31:10 <quaid> I'm updating the modules list a bit from this discussion
00:31:14 <Sparks> #chair quaid
00:31:22 <Sparks> quaid: Excellent, thank you.
00:31:44 <quaid> #task need to resolve theme package, review, and Design Team help; borrow from FI work?
00:32:01 <itbegins> Sparks: http://www.fpaste.org/CJke/
00:32:17 <itbegins> Log from when you last typed
00:32:49 <Sparks> itbegins: Thanks!
00:33:02 <itbegins> Anyway, if we're agreed we're going to miss Fedora 12 for the docs instance, then there is much less pressure on timescales for the CMS project
00:33:29 <Sparks> quaid: Can you talk to mizmo tomorrow and make sure she's on the same pages as us?
00:33:37 <quaid> Sparks: got it
00:33:42 <Sparks> itbegins: Agreed.
00:33:47 <Sparks> quaid: Cool, thanks.
00:34:03 <Sparks> #action quaid to follow up with Mizmo on the Zikula theme
00:34:34 <Sparks> Anything else on the CMS/Zikula?
00:35:08 <Sparks> #topic Status on CC license rollout.\
00:35:19 <Sparks> #link https://fedoraproject.org/wiki/License_changeover_schedule
00:35:51 <Sparks> rudi: So we now have a happy version of the license page for Publican, correct?
00:36:05 <rudi> Sparks -- correct
00:36:18 <Sparks> rudi: I'm assuming you are updating this in Publican 1.0... can you patch the 0.44 version as well?
00:36:35 <quaid> are we subject to Infrastructure freeze for this change?
00:36:41 <quaid> i.e. wiki, websites, etc.
00:36:50 <Sparks> maybe
00:36:56 <rudi> Sparks -- I'm not sure -- I will have to check with Jeff (who is on leave at the moment)
00:37:05 <Sparks> ianweller: What's the procedure for updating the license of the wiki?
00:37:15 <Sparks> rudi: Okay, that's cool.
00:37:22 <ianweller> we stuff some variables in LocalSettings.php
00:37:25 <ianweller> which is in puppet, in our case
00:37:34 <rudi> I suspect that it may just end up in the "unofficial" patch that I maintain on my Fedorapeople page
00:37:35 <ianweller> and then it adds the cute little button to the bottom automatically i believe
00:37:43 <Sparks> #action rudi to follow up with Jeff about changing the license information in Publican 0.44 and 1.0
00:37:50 <rudi> ianweller -- what button?
00:38:06 <Sparks> uh oh
00:38:08 <Sparks> :)
00:38:14 <quaid> is there a chance that a current version of Fedora won't have Publican 1.0?
00:38:22 <ianweller> rudi: the cc icon
00:38:27 <ianweller> http://i.creativecommons.org/l/by-sa/3.0/88x31.png
00:38:28 <ianweller> that thing
00:38:30 <rudi> ianweller -- we can't use the icon
00:38:36 <quaid> +1 to button website
00:38:40 <ianweller> *thud*
00:38:42 <quaid> not for publican
00:38:46 <Sparks> rudi: I'd prefer that the license information go into the official release but I know you know that.
00:38:48 <ianweller> well we can for the wiki
00:38:52 <rudi> We can't use it for the wiki
00:38:55 <ianweller> why not
00:39:03 <quaid> rudi: I understood Richard to be talking about the legal notice for Publican
00:39:04 <ianweller> sure we can't redistribute it but we're not
00:39:10 <ianweller> we're just hotlinking it
00:39:15 <quaid> right because of the redistrib.
00:39:19 <rudi> quaid -- if you read his emails, he talks about both
00:39:34 <rudi> ianweller -- yes, but it's an unfree element appearing on a Fedora page
00:39:43 <rudi> Therefore, we can't use it.
00:39:48 <Sparks> I have a problem with his interpretation of not using it on the wiki...
00:39:58 <ianweller> augghhghhggghsdoagosrgjwjgoajldfjksfakgherjkojar <-- what is going through my mind right now
00:39:59 <quaid> um
00:40:01 <Sparks> the Fedora logo is an unfree element and yet we use it on the webpages
00:40:06 <ianweller> that's correct!
00:40:07 <quaid> so is ServerBeach's logo
00:40:12 <ianweller> fedora logo is non-redistributable
00:40:15 <rudi> Sparks -- yes, but it's an unfree element that we own
00:40:16 <quaid> and Dell's
00:40:23 <ianweller> we don't own the dell logo
00:40:34 <quaid> http://fedoraproject.org/sponsors
00:40:35 <Sparks> and we are using the CC logo per its terms of use
00:40:52 <quaid> ok, I'll re-read richard's email, and then we'll ask him for clarification.
00:41:15 * Sparks finds it increadibly ironic that the very symbol of freedom is an unfree element.
00:41:25 <quaid> well, it's a trademark, in't?
00:41:32 <Sparks> yeah
00:41:34 <quaid> Fedora is for freedom, but our logo sure ain't free
00:41:42 <Sparks> exactly
00:43:19 <Sparks> #action quaid to follow up with Richard about the use of the CC logo on the wiki.
00:43:42 <Sparks> ianweller: So is the infrastructure freeze going to affect the license change?
00:43:52 <ianweller> yyyyyyyyyno it should be minor
00:43:53 <ianweller> ricky: ping ^^
00:44:00 <ricky> ianweller: pong
00:44:27 <ricky> Ugh, are we going to run into pain for our sponsors page?
00:44:29 <ianweller> ricky: if i send a patch to the infra list saying "here's what i'm doing to change the license on the wiki" and it gets 2 +1s then it's ok during a freeze right?
00:44:37 <ianweller> ricky: well that wasn't why i pinged you but possibly :(
00:44:52 <ricky> Yup as long as it's low risk and doesn't have a high chance of breaking anything else :-)
00:45:00 <ricky> So more than likely, yes :-)
00:45:22 <ianweller> yeh it prolly won't!
00:46:24 <Sparks> okay...
00:46:31 <Sparks> anything else about the license change?
00:47:11 <rudi> It might be worth checking with Richard Fontana about the logos on the sponsors page
00:47:32 <Sparks> quaid: Can you tack that onto your discussion?
00:47:38 <quaid> rudi: "These are not the droids you are looking for."
00:47:43 <quaid> Sparks: "These are not the droids you are looking for."
00:47:58 <Sparks> quaid: huh?
00:47:59 <quaid> "Move along"
00:48:06 <Sparks> roger
00:48:20 <Sparks> #topic Draft Documentation on the wiki
00:48:29 <Sparks> #link https://fedoraproject.org/wiki/Category:Draft_Documentation
00:48:43 <Sparks> For anyone looking for something more to do... ^^^
00:48:53 <quaid> get out your machete
00:49:26 <Sparks> Yeah... we probably need to go through that and see what's stale
00:49:48 <Sparks> Anything else on this?
00:49:56 <quaid> Hint: if it's in Archive:, it's stale
00:50:10 <quaid> do we want to do something about it for real?
00:50:15 <Sparks> sure
00:50:24 <quaid> i.e., do an online sprint some time?
00:50:34 <quaid> do we have any "lulls" in the F12 storm?
00:50:48 <Sparks> Not especially
00:50:50 <Sparks> :)
00:51:18 <Sparks> I think a lot of what I'm seeing in the Archive: can be deleted/removed.
00:51:39 <Sparks> It appears that it has been incorporated into a DocBook guide
00:52:10 <quaid> OK, maybe a post-F12 fun activity
00:52:18 <quaid> we'll all buy our own beer, etc.
00:52:31 <Sparks> ianweller: https://fedoraproject.org/wiki/Category:Delete
00:52:51 <Sparks> ianweller: What happened to the delete policy? There are 97 pages ready to be blasted!
00:52:51 <ianweller> yay more work
00:52:58 <ianweller> Sparks: i don't do anything about it until someone mentions it
00:52:59 <ianweller> ^_^
00:53:19 <ianweller> so i'll do something about it
00:53:42 <Sparks> ianweller: I know you have a big red button over there that nukes all those pages
00:53:57 <ianweller> no but ricky does, it's called "nuke db2"
00:54:02 <ianweller> ;)
00:54:15 <Sparks> Yikes
00:54:32 <ianweller> yeah i'll go thruogh those tonight just for you
00:54:36 * ianweller stops holding up the meeting
00:54:45 <Sparks> Okay, so that should clear up some items... :)
00:54:50 <Sparks> Anything else?
00:55:27 <Sparks> #topic Guide needs?
00:55:37 <Sparks> Anyone have a guide that is in need?
00:56:09 <Sparks> #topic New Guides
00:56:16 <Sparks> Okay, I have one...
00:56:51 <Sparks> I've Publicanized (apparently not the first person to do this) the old Accessibility information that used to go out with the RNs.
00:57:17 <Sparks> It is on fh.org and I'm going to start updating it as I get time.
00:57:42 <Sparks> Feel free to check it out and provide patches! :)
00:57:54 <Sparks> Does anyone else have a new guide?
00:58:48 <Sparks> #topic All other business
00:58:55 <Sparks> Okay, does anyone have anything else?
00:59:35 <Sparks> Anyone?
00:59:37 <Sparks> Anything?
00:59:54 <itbegins> *silence*
01:00:18 <itbegins> Good timing
01:00:29 <Sparks> Okay... thanks everyone for coming tonight! Don't forget to tip your wait staff.
01:00:33 <Sparks> #endmeeting
Hi,
Is there some way which allows me to do the following and still get
the right formatting in wiki?
{| |- style="color: white; background-color: #3074c2; font-weight:
bold" align="justified" |'''Name'''||'''Email''' |- | [[User:ccc|
ccc]] ||(ccc AT fedoraproject DOT org) |- |[[User:ddd|ddd]] ||(ddd AT
fedoraproject DOT org) |}
The correct one is this:
{|
|- style="color: white; background-color: #3074c2; font-weight: bold"
align="justified"
|'''Name'''||'''Email'''
|-
| [[User:ccc| ccc]] ||(ccc AT fedoraproject DOT org)
|-
|[[User:ddd|ddd]] ||(ddd AT fedoraproject DOT org)
|}
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
Sent from Calcutta, WB, India